Skip to content

Carrier connection

NZ Post.
Connected to dispatch.

Scope NZ Post service selection, labels and dispatch handoff against your carrier account.

Responsibilities

Agree where each record belongs.

Conceptual illustration: A packing station, label printer and outgoing parcel joined by one violet reference.

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.

Conceptual illustration: An active record tray, storage cartridge and archive drawer with a shared record marker.
NZ Post: records, direction and setup requirements
RecordFrom → toTriggerScope note
Service and shipment detailsOpsUI → NZ PostAt dispatch preparationConfirm rating and service-selection scope.
Label and tracking referenceNZ Post → OpsUIAfter shipment acceptanceConnection and account support to confirm.
Manifest / dispatch handoffOpsUI → NZ PostAgreed dispatch cut-offConfirm direct API, aggregator or file requirements.
Tracking updatesNZ Post → OpsUIWhen supported events arriveEvent coverage and timing require verification.

Set up the connection around your operation.

Conceptual illustration: A disconnected storage module, a second available module and records waiting for review.
  1. Confirm access

    Bring your NZ Post account type, service mix and shipping locations.

  2. Agree the mapping

    Confirm rate, label, tracking and manifest access, including printer formats.

  3. Test the handoff

    Test representative parcels, rejected addresses, label retries and end-of-day handoff.

Questions about NZ Post.

Is the NZ Post connector live today?

The Shipping/Outbound module handles the dispatch workflow today; the specific NZ Post connector (direct API vs eShip handoff) is scoped against your account during implementation. Existing NZ Post customers move across without re-papering the carrier relationship.

Do you support CourierPost and eParcel both?

Yes. Both flows fit the same dispatch lifecycle in OpsUI. The carrier service selected at order entry routes to the right downstream NZ Post product.

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.

Back to all integrations