Connect Shippit to OpsUI — or skip the aggregator and ship carriers direct
Rate, label, track and manifest through Shippit's multi-carrier platform from inside the OpsUI Shipping/Outbound module, on your own Shippit account. Or wire your carriers directly with your own negotiated rates — OpsUI owns the dispatch workflow either way, so the choice is about economics, not your software.
Shippit dispatch, on the same screen as the rest of ops.
- §01
Shippit as your carrier hub
Use Shippit's aggregator to reach Australia Post, StarTrack, Sendle, Aramex, CouriersPlease and more from one connection. OpsUI calls Shippit for rates at the point of dispatch, prints the label, books the consignment and stores the tracking number against the order — all from the Shipping/Outbound queue.
- §02
Or go direct — your WMS already ships
OpsUI can integrate carriers natively with your own commercial accounts and negotiated rates, no middle layer taking a per-label cut. If you have a couple of carriers and decent volume, shipping direct from the WMS often beats paying an aggregator margin on every parcel.
- §03
One dispatch workflow, every order
Whether a parcel goes via Shippit or direct, your pickers and packers see the same screen: scan, confirm weight and dims, pick the service, print. Carrier choice is a configuration decision behind the workflow, not a separate tool your team has to learn.
- §04
Manifest, track and reconcile
End-of-day manifests close out the consignments OpsUI booked through Shippit. Tracking events flow back onto the order and customer record, and freight detail lands in your finance system via the Finance & Accounting module so you can reconcile carrier invoices against what you actually shipped.
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 Shippit 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 Shippit 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 Shippit — 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 Shippit 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.
Do I even need Shippit if OpsUI can ship carriers directly?
Not necessarily. An aggregator like Shippit earns its keep when you want fast access to many carriers, rate-shopping across them and a single support contact — at the cost of a margin on each label. If you run one or two carriers at volume, integrating them directly with your own negotiated rates usually works out cheaper. OpsUI supports both, so you can model the economics and decide; we'll confirm the right connector during scoping.
Which carriers can I reach through Shippit in OpsUI?
Through Shippit you can reach the major AU networks — Australia Post, StarTrack, Sendle, Aramex (ex-Fastway), CouriersPlease and others on your Shippit plan. OpsUI also integrates several of these directly. The deciding factor is whether you'd rather pay an aggregator margin for breadth or hold your own carrier accounts; we map that out with you in scoping.
Is the Shippit connector live in production?
It's configurable. Our one live carrier API today is NZ Couriers; every other carrier and platform, including Shippit, is confirmed and wired during your rollout through the Shipping/Outbound module — direct API, an aggregator like Shippit, or a file-based handoff. OpsUI owns the dispatch workflow regardless of which path we connect.
Whose Shippit account does this use?
Your own. OpsUI connects to your Shippit account and the carrier rates and contracts attached to it — we don't resell freight or sit between you and your carrier pricing. If you later move a lane direct, your negotiated rates stay yours and the dispatch workflow in OpsUI doesn't change.
Already dispatching with Shippit? Let’s wire it in.
Walk us through your current Shippit setup and we’ll show how the Shipping/Outbound module fits — labels, tracking, and manifest, all from inside OpsUI.