Mainfreight pickups without the spreadsheet ritual.
Consignments, labels, tracking, and EDI handoff for Mainfreight pickups — wired through the Shipping/Outbound module so freight bookings stop living in shared inboxes.
Mainfreight dispatch, on the same screen as the rest of ops.
- §01
Consignment generation from the order
Consignment numbers and labels generate against your Mainfreight account from order data already in OpsUI — no double-entry into Mainchain.
- §02
B2B-shaped workflow
Freight, palletised, and full-truck flows are first-class — not retrofitted parcel workflows pretending to be freight.
- §03
EDI-ready handoff
Daily pickup manifest and EDI files are prepared from the dispatch queue in the format Mainfreight expects, configured per your account.
- §04
Tracking back into the order
Mainfreight tracking references sit on the order so customer service answers “where is it?” without a phone call to the depot.
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 Mainfreight 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 Mainfreight 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 Mainfreight — 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 Mainfreight 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.
Does this work for full-pallet and full-truck dispatch?
Yes. The Shipping/Outbound module treats freight as a first-class flow alongside parcel, so palletised and full-truck Mainfreight bookings ride the same dispatch lifecycle without a parallel process.
Mainchain or direct?
Either — the handoff shape is confirmed during scoping based on your existing Mainfreight account setup. Most customers run the EDI handoff Mainfreight already provisions for them.
Already dispatching with Mainfreight? Let’s wire it in.
Walk us through your current Mainfreight setup and we’ll show how the Shipping/Outbound module fits — labels, tracking, and manifest, all from inside OpsUI.