Carrier connection
Mainfreight.
Connected to dispatch.
Scope Mainfreight service selection, labels and dispatch handoff against your carrier account.
Responsibilities
Agree where each record belongs.
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.
| Record | From → to | Trigger | Scope note |
|---|---|---|---|
| Service and shipment details | OpsUI → Mainfreight | At dispatch preparation | Confirm rating and service-selection scope. |
| Label and tracking reference | Mainfreight → OpsUI | After shipment acceptance | Connection and account support to confirm. |
| Manifest / dispatch handoff | OpsUI → Mainfreight | Agreed dispatch cut-off | Confirm direct API, aggregator or file requirements. |
| Tracking updates | Mainfreight → OpsUI | When supported events arrive | Event coverage and timing require verification. |
Set up the connection around your operation.
Confirm access
Bring your Mainfreight account type, service mix and shipping locations.
Agree the mapping
Confirm rate, label, tracking and manifest access, including printer formats.
Test the handoff
Test representative parcels, rejected addresses, label retries and end-of-day handoff.
Questions about Mainfreight.
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.
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.