Definition
The warehouse–transport handoff is the moment — and the data set — when an order moves from ready-to-ship in the warehouse management system (WMS) to an assigned trip in the transportation management system (TMS), with appointment, carrier, and evidence accounts payable can retrieve.
WMS marked complete at 16:10; the tractor arrived at 16:00; three cartons were missing in staging. The Late was not GPS — it was the handoff.
System boundary: WMS · TMS vs WMS · warehouse functions.
What it means in practice
A chat “ready” is not enough. A healthy handoff publishes an RTS (Ready to Ship) event with timestamp, weight/cube or pallets, dock door, documents, and the ID the trip will inherit.
If the TMS starts without that data, it quotes and schedules blind: detention, wrong FTL/LTL sizing, and broken OTIF before the truck moves.
Why it matters by role
| Role | What they need from handoff | Typical failure |
|---|---|---|
| Warehouse | Real RTS, not ghost picking | Complete without staging |
| Traffic / 3PL | Appointment and load attributes | Tractor waiting |
| Carrier | Door, seal, docs | Rejection at customer DC |
| Accounts payable | Same trip ID + docs | Paying without a file |
Minimum handoff dataset
| Field | Typical source | Why |
|---|---|---|
| Order / shipment ID | ERP/WMS | Ties node and trip |
| Qty / pallets / weight | WMS | Size the equipment |
| Door + RTS timestamp | WMS/dock | Measure dwell |
| Appointment + carrier | TMS | OTIF On Time |
| Outbound docs | WMS/ERP | Avoid rejection |
| Seal / temperature | Dock | Claims and integrity |
Short WMS a TMS flow
Close picking
Verified in WMS
Publish RTS
Weight and door
Create trip
TMS + appointment
Load
Seal and docs
Depart
GPS / POD
Expensive mistakes in Mexico
1.Handoff by WhatsApp
No system object means no dwell KPI and no defensible detention dispute.
2.RTS without weight/pallets
TMS schedules the wrong equipment; cost shows up in accessorials.
3.Appointment sold without dock capacity
WMS releases waves the dock cannot ship in that hour.
4.Docs that do not travel with the ID
Destination DC rejects; freight is disputed without a tied packing list.
OCL and the trip file
OCL does not replace your WMS. It takes the handoff (RTS + trip), runs tracking, and ties proof of delivery (POD) and documents before pay. It is not an Authorized Certification Provider (PAC).
Sources and further reading
Key takeaways5 points
- Warehouse–transport handoff = the moment and dataset when an order moves from ready-to-ship (WMS) to an assigned trip (TMS).
- Without a Ready-to-Ship (RTS) event with weight/pallets/appointment, OTIF breaks at the dock even if picking closed.
- Minimum message: order ID, quantities, seal, door, appointment, and carrier — same ID freight will use.
- In Mexico the handoff also carries outbound docs accounts payable will match to CFDI/Carta Porte and POD.
- OCL is not a WMS or a PAC: it takes the handoff and runs trip tracking/audit.
Is your OTIF breaking at the dock?
Frequently asked questions
The moment and dataset when an order moves from ready-to-ship (WMS) to an assigned trip (TMS) with a retrievable appointment and evidence.
No. They must share the same ID and the RTS event. See TMS vs WMS.
Minutes from RTS to actual departure (staging dwell), % of trips created within minutes of RTS, and % of OTIF not lost at the dock.
The handoff releases the trip; CFDI/Carta Porte is issued by whoever documents the move (usually the carrier via a PAC). The buyer verifies it in the file.
It requires a trip object with milestones and evidence; exceptions stay in the file for your team, not loose screenshots.
Yes: each customer/DC needs RTS and appointment rules; without them the yard saturates and OTIF dilutes.