Rate, label, track and manifest CouriersPlease parcels straight from OpsUI
OpsUI's Shipping/Outbound module drives CouriersPlease rating, label printing, tracking and end-of-day manifests as part of your pick-pack-dispatch flow. You ship on your own CouriersPlease account and rate card, with the connector confirmed during scoping.
CouriersPlease dispatch, on the same screen as the rest of ops.
- §01
Metro ecommerce delivery built in
CouriersPlease is a franchised metro parcel courier with strong city coverage and a network of POPStation lockers and collection points. OpsUI books the right service for each order at pack time, mapping your warehouse rules to the service level that fits the order rather than defaulting everything to one option.
- §02
Parcel lockers and POPStation options
Where an order is set for a parcel locker or POPStation collection point, OpsUI carries that destination through the dispatch workflow so the label and manifest reflect it correctly. Pickup-point and to-the-door deliveries are handled in the same outbound flow without separate tooling.
- §03
Labels and manifests at the pack bench
OpsUI generates compliant CouriersPlease labels at the pack station and builds the end-of-day manifest for driver collection, so dispatch stays paperless and auditable. Consignment numbers are written back to the order the moment the label prints.
- §04
Tracking back on the order and CRM
Tracking events flow back onto the OpsUI order and customer record, so support and sales see delivery status without logging into the carrier portal. Exceptions and failed scans surface in OpsUI's Exceptions Management workflow for follow-up before the customer calls.
Order in, label out, manifest done.
Four stages, one screen — the same shape OpsUI runs for every carrier so dispatch teams do not relearn the workflow per customer.
- §01On order entry
Service selection
Carrier service and rate are selected from your configured CouriersPlease setup as the order is captured — no separate console.
- §02At pack
Label workflow
Carrier-ready labels and packing references print from the pack station against your CouriersPlease account.
- §03In transit
Tracking references
Tracking numbers and dispatch events stay attached to the order timeline so support and ops see status in one place.
- §04End of day
Manifest handoff
Manifest and dispatch handoff are prepared from the dispatch queue ready for CouriersPlease — direct API, aggregator, or file-based depending on scoping.
OpsUI's Shipping/Outbound module owns the dispatch workflow — labels, tracking, manifest, and dispatch events. The specific CouriersPlease connector (direct API, aggregator, or file-based handoff) is confirmed during scoping against your existing account and account type. No iPaaS in the path.
The honest answers.
Is the CouriersPlease integration live in OpsUI?
The CouriersPlease connector is configurable, not a prebuilt live API like NetSuite sync. OpsUI owns the full dispatch workflow regardless of carrier, and the exact connection method (direct API, aggregator such as Shippit, or file-based) is confirmed during scoping. Rating, labels, tracking and manifests then run inside the Shipping/Outbound module.
Do we use our own CouriersPlease account?
Yes. You ship on your own CouriersPlease account and negotiated rate card. OpsUI sits on top as the operations layer, booking consignments and printing labels against your account, so your carrier commercials and franchise relationship stay exactly as they are.
Can OpsUI choose CouriersPlease only for the right orders?
Yes. OpsUI's Business Rules Engine and Shipping/Outbound module let you route orders to CouriersPlease for metro and locker-friendly deliveries while sending other parcels to carriers like Australia Post, StarTrack, Sendle, Toll, DHL, Aramex or via the Shippit aggregator. Each order gets the service that fits.
Where does tracking information end up?
Consignment numbers and tracking events are written back to the order and the customer record in OpsUI. Your warehouse, support and CRM teams see delivery status in one place, and delivery exceptions route into the Exceptions Management workflow so issues are actioned early.
Already dispatching with CouriersPlease? Let’s wire it in.
Walk us through your current CouriersPlease setup and we’ll show how the Shipping/Outbound module fits — labels, tracking, and manifest, all from inside OpsUI.