Carrier connection
NZ Couriers.
Connected to dispatch.
Connect NZ Couriers label, tracking and manifest workflows to dispatch.
Responsibilities
Agree where each record belongs.
Confirm the services, rate access, label formats and manifest requirements enabled for your account.
What flows where
Review the records in each direction.
These are the catalogue flows to validate against your deployment.
| Record | From → to | Trigger | Scope note |
|---|---|---|---|
| Service and shipment details | OpsUI → NZ Couriers | At dispatch preparation | Confirm rating and service-selection scope. |
| Label and tracking reference | NZ Couriers → OpsUI | After shipment acceptance | Confirm enabled services and label formats. |
| Manifest / dispatch handoff | OpsUI → NZ Couriers | Agreed dispatch cut-off | Confirm direct API, aggregator or file requirements. |
| Tracking updates | NZ Couriers → OpsUI | When supported events arrive | Event coverage and timing require verification. |
Set up the connection around your operation.
Confirm access
Bring your NZ Couriers 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 NZ Couriers.
Do I need a separate NZ Couriers account or contract?
Yes. OpsUI plugs into your existing NZ Couriers account using your own API credentials. We do not resell carrier services; pricing stays between you and NZ Couriers.
What about International Air and overnight services?
Any service tier your NZ Couriers account is contracted for is available through the rate call. We do not gate which services are quotable. That is set on the NZ Couriers side.
How fast do tracking events appear in OpsUI?
Agree the required update timing during scoping and test it with representative transactions. The delivery model does not establish a guaranteed latency or support for every event.
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.