NZ Post dispatch, run from the same screen as everything else.
Labels, tracking, and manifest handoff for CourierPost and eParcel — connected through the Shipping/Outbound module so dispatch never leaves OpsUI to talk to NZ Post.
NZ Post dispatch, on the same screen as the rest of ops.
- §01
CourierPost and eParcel ready
Both domestic CourierPost and eParcel (international) workflows are supported through your existing NZ Post account — no separate aggregator account required.
- §02
Address validation at order entry
Delivery addresses are sanity-checked against NZ Post’s address dataset during order capture so failed-delivery surprises drop sharply.
- §03
Print from the pack station
Labels print directly from pack — no jumping to eShip, no copy-pasting addresses, no separate carrier login per dispatcher.
- §04
Manifest workflow that matches NZ Post
End-of-day manifest is structured the way NZ Post expects it, so the driver picks up clean paperwork without a side conversation.
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 NZ Post 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 NZ Post 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 NZ Post — 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 NZ Post 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 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.
Already dispatching with NZ Post? Let’s wire it in.
Walk us through your current NZ Post setup and we’ll show how the Shipping/Outbound module fits — labels, tracking, and manifest, all from inside OpsUI.