Carrier connection
Toll.
Connected to dispatch.
Scope Toll 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 → Toll | At dispatch preparation | Confirm rating and service-selection scope. |
| Label and tracking reference | Toll → OpsUI | After shipment acceptance | Connection and account support to confirm. |
| Manifest / dispatch handoff | OpsUI → Toll | Agreed dispatch cut-off | Confirm direct API, aggregator or file requirements. |
| Tracking updates | Toll → OpsUI | When supported events arrive | Event coverage and timing require verification. |
Set up the connection around your operation.
Confirm access
Bring your Toll 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 Toll.
Which Toll services are supported?
Whichever ones your Toll account is contracted for. OpsUI does not gate service tiers. That is set on the Toll side and surfaced through the rate / service selection at order entry.
Do I keep my MyToll login?
Yes. OpsUI does not replace MyToll for account management or rate negotiation. Day-to-day dispatch moves into OpsUI; the carrier relationship stays where it is.
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.