Carrier connection
CouriersPlease.
Connected to dispatch.
Scope CouriersPlease service selection, labels and dispatch handoff against your carrier account.
Responsibilities
Agree where each record belongs.
A supported dispatch workflow does not establish a pre-built carrier connector. Agree the connection method and limitations during scoping.
What flows where
Scope the records in each direction.
These are proposed flows for scoping, not a promise that every object or event is already supported.
| Record | From → to | Trigger | Scope note |
|---|---|---|---|
| Service and shipment details | OpsUI → CouriersPlease | At dispatch preparation | Confirm rating and service-selection scope. |
| Label and tracking reference | CouriersPlease → OpsUI | After shipment acceptance | Connection and account support to confirm. |
| Manifest / dispatch handoff | OpsUI → CouriersPlease | Agreed dispatch cut-off | Confirm direct API, aggregator or file requirements. |
| Tracking updates | CouriersPlease → OpsUI | When supported events arrive | Event coverage and timing require verification. |
Set up the connection around your operation.
Confirm access
Bring your CouriersPlease account type, service mix and shipping locations.
Agree the mapping
Confirm rate, label, tracking and manifest access, including printer formats.
Test the handoff
Test representative parcels, rejected addresses, label retries and end-of-day handoff.
Questions about CouriersPlease.
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.
Your next step
Bring your system. Map the connection.
Share the account or version you use, the records that matter and the exceptions your team needs to handle.