Skip to content
Shipping · for Ecommerce

NZ Couriers is live in OpsUI's Shipping/Outbound module. Australia Post, StarTrack, Sendle, Toll, DHL and Mainfreight connections are scoped and configured during rollout against your carrier accounts.

Ecommerce shipping costs in ANZ are made worse by middleware. Most operators stack their WMS plus a shipping aggregator plus the carrier: three layers, three monthly fees, three reconciliation surfaces. NZ Couriers connects directly today; other carrier connections are scoped during rollout against your accounts and workflow.

Built for ecommerce & d2c

What this module brings to ecommerce & d2c operations.

First-party NZ carriers

NZ Couriers live in production today. NZ Post, Mainfreight configurable. No MyParcels round-trip, no aggregator subscription.

AU carriers configured during rollout

Australia Post, StarTrack, Sendle, Toll, DHL all configurable through the Shipping module against your existing carrier accounts.

Wave picking aligned to carrier cutoffs

Picks can release in waves aligned to the cutoffs of each configured carrier. The pick screen shows priority orders first; the cutoff timer is visible to the picker.

Live rates at order entry

Once a carrier connection is configured, rates can be quoted at the storefront or order desk before the order is committed. Service tier selection drives the right pick wave automatically.

End-of-day manifest, auto-submitted

For configured connections, the manifest generates from the dispatch queue and submits through the agreed API, aggregator or file workflow.

Tracking events on the order timeline

Where the configured carrier method exposes tracking events, scans flow back into the OpsUI order timeline alongside picking, packing, and customer comms.

Common questions

Does this replace Starshipit / ShipStation?
It can where the carrier connection agreed during rollout covers the workflow you currently run through an aggregator. If you rely on Starshipit- or ShipStation-specific automation, the aggregator can continue alongside OpsUI. We confirm that boundary during scoping rather than claiming every carrier workflow is already live.
Can I switch carriers mid-flight?
Carrier selection happens per shipment. Switching to another service requires that carrier connection to be configured for your account first; OpsUI does not pre-claim an unconfigured carrier path.
What about trans-Tasman shipping (NZ to AU or AU to NZ)?
OpsUI runs on separate regional domains (opsui.co.nz and opsui.au) with separate data residency. A trans-Tasman carrier method such as DHL or Australia Post International is scoped against your account during rollout, then handled in the normal Shipping workflow.

Ready to see this in production?

Book a consultation and we will scope the Shipping/Outbound module against your ecommerce & d2c operation specifically: your order volume, your channels, your team.