Three systems touch a trailer between the motorway and the dock door, and most arguments about which one to buy are really arguments about where one ends and the next begins. The boundary is not a matter of taste: each system owns a different object, and the handoffs between them are where operations lose visibility. A yard management system owns the trailer between the gate and the door, and that single sentence settles most of the confusion.
This is the boundary map: what each system owns, what it does not, where the data has to pass across, and which one to buy first depending on where your operation actually hurts.
What each system owns
The clean way to separate them is by the object each one is authoritative for.
- TMS — the shipment. Rates, tendering, carrier selection, consolidation, freight audit and settlement. Its world starts when a load needs moving and ends when the invoice is paid. The full scope is set out in the guide to transportation management systems.
- WMS — the inventory. Stock location, picking, packing, replenishment, labour and the four walls of the building. Its world is what is inside the box and where the box sits on a rack.
- YMS — the trailer. Gate check-in, spot assignment, moves by shunters, door assignment, dwell and departure. Its world starts at the gate and ends at the gate.
Stated that way the overlaps become obvious. The TMS knows a load is arriving but not which spot the trailer is in. The WMS knows a receipt is expected but not whether the trailer carrying it is on site. Only the YMS knows that trailer 4471 arrived at 06:12, sat on spot B14 for nine hours and has still not been called to a door.
The handoffs, and where they break
Three handoffs carry almost all the failure:
TMS to YMS: the expected arrival. The yard needs to know what is coming, when, and against which appointment. Without it the gate becomes a discovery process, with a guard phoning the office to ask whether this trailer is expected. This is the handoff that decides whether gate check-in takes ninety seconds or twelve minutes.
YMS to WMS: the trailer is at the door. The warehouse should start work when the trailer is physically presented, not when someone walks over to look. Where this handoff is missing, the labour plan is built on the appointment time rather than on reality, and every late arrival propagates into idle pickers.
WMS to YMS: the load is finished. The yard needs to know a trailer is ready so it can be moved off the door and a waiting trailer brought on. Missing this one is the most expensive of the three: it produces loaded trailers occupying doors, which is the classic cause of the dwell measured in the guide to yard dwell time.
The WMS yard module question
Most tier-one WMS products ship a yard module, and the honest answer is that it is sufficient for a real set of operations and structurally insufficient for another.
A WMS yard module is usually enough when the site has fewer than about 20 doors, holds few or no drop trailers, runs mostly live loads, and has a yard visible from the office window. In that operation the module gives you a trailer list and a door assignment, and a dedicated system would be overhead.
It stops being enough at a predictable set of thresholds: a trailer pool that outgrows the doors, shunter moves that need to be dispatched and tracked rather than shouted, multiple buildings sharing one yard, automatic gate identification, or any requirement to measure dwell as a decomposed number rather than a single duration. The underlying reason is architectural. A WMS models a location as a storage bin; a yard spot is not a storage bin, it is a queue position with a move history, and modules built on the bin abstraction cannot express shunting.
Where the TMS overlaps, and where it does not
Modern TMS suites increasingly sell dock appointment scheduling, which creates a genuine overlap with the YMS at the door. The workable split: the TMS owns the appointment because the appointment belongs to the shipment, and the YMS owns the door because the door belongs to the site. Where a single vendor supplies both, this is a configuration choice. Where they are separate, the appointment has to flow from TMS to the site, which is exactly the integration described above and exactly the one most often left as a nightly file.
What a TMS does not do, at any tier, is know where a trailer physically is inside the fence. That is not a gap in any particular product, it is outside the object the TMS is authoritative for. Broader stack combinations are compared in the guide to the trucking technology stack.
Which to buy first
The sequence follows the pain, not the org chart.
- Buy the TMS first if the cost of transport is the problem: rates are unmanaged, tendering is manual, freight invoices are not audited.
- Buy the WMS first if the inventory is the problem: stock accuracy is poor, picking is inefficient, the building cannot scale.
- Buy the YMS first if the trailer is the problem: drivers wait at the gate, nobody can locate a specific trailer, doors sit occupied by finished loads, or detention charges arrive that cannot be disputed because there is no timestamped record.
The third case is more common than it looks, because yard pain is usually misdiagnosed as dock pain. The tell is simple: if appointments are being kept but trailers still wait, the constraint is the yard, and adding rules to the dock calendar will not move it. If appointments are being missed in the first place, the constraint is the schedule, and that is where dock scheduling software belongs.
The one-line test
Ask any site: which system can tell you, right now, how long trailer X has been on the property and what it is waiting for? If the answer is a person rather than a system, the yard is unmanaged, whatever the WMS and TMS are doing well.
