Amazon · 16 of the largest US freight sites, mapped from satellite
The Yard Network System, by FreightRoll.
You opened the network to everyone. Every one of them arrives at a gate.
In May you launched Amazon Supply Chain Services and opened your logistics network to every business, on a fleet of 80,000 trailers. More freight now lands on the same gates. You run the most automated network on earth, with over 750,000 robots inside your buildings and more than a million deployed to date. The one node the robots never reached is the yard. We mapped 16 of your largest freight sites. Fifteen gate the yard and twelve staff a guard booth. What we cannot see from orbit is what happens after the gate arm lifts.
YardFlow is the Yard Network System, the software layer between your TMS and your WMS. When you sell that network to outside shippers, every booked load still ends at one of your gates, so the yard becomes the promise you have to keep. It turns every gated checkpoint into one orchestrated gate-to-dock flow, across robotics fulfillment, the cross-dock, sortation, and the air hub. Primo Brands has implemented the driver journey system wide, cut trailer turn times by 50%, and shipped about 5% more volume on the same dock-office headcount. The audit shows where the same gain sits in your network.
- The gapYour TMS runs the road, your WMS runs the building, nothing runs the yards.
- What we doOne digital standard for all sites. EZ-Pass at the gate, air-traffic control for the trailers.
- The proofPrimo: about 5% more volume on flat headcount, turns cut 48 to 24, and 100% of the network committed.
- The payoffReduce turn times, gain 5% capacity per location. Eliminate paper and detention expenses. No change to headcount.
Already live at scale · the Primo Brands network
The Yard Network System runs the yards behind these household brands. Live today, rolling to 100% of the network.
Using actual results from Primo Brands, we modeled the potential prize for Amazon.
Proven at Primo, modeled across the network
The problem
Every yard "does it their own way." That is not strategy. That is drift.
Ask two of your sites and we would expect the same line: our yards are different.
In our experience they are not. Same trucks, same trailers, same moves. What differs is the workaround each site improvised, hardened into a process nobody chose. The Stockton inbound cross-dock runs about 200 dock doors and a packed trailer lot, gated and guarded. Now run that play across robotics fulfillment, sortation, and the CVG air hub, each with its own rhythm. Across the 16 sites we mapped, we count 1,890 dock doors and about 3,825 trailer positions. We cannot see from orbit what sequences them. Sell that network to outside shippers and you pour more trucks onto the same gates. The robots stop at the dock. Our read is that the yards are where the gain leaks back out.
Why now
You just sold the network to everyone. The yards are the promise behind it.
In May you opened Amazon Supply Chain Services to every business, on a fleet of 80,000 trailers.
Outside shippers now book your freight, your warehouses, and your docks. Every booked load still ends at a gate, a yard, and a dock. The faster the network feeds those sites, the more a slow yard backs up the whole chain. Detention starts at hour two and runs $50 to $100 an hour, and carriers now pick their shippers. Every printed BOL, every forced check-in, every drop-and-hook instruction, every trailer a driver hunts down is added cost. Fix the yards and the capacity you could not see starts to surface, which is more loads out the same doors. The buildings are solved. The yards are the unfinished half.
The Yard Network System
A new layer of your stack, between the TMS and the WMS.
Every yard runs the same jobs, and the same people run them. The Yard Network System gives each of them one standard across every site. The driver checks in from their phone with flowDRIVER. The spotter moves the trailer while a cab camera maps the yard with flowTWIN. The dock coordinator assigns the door from flowYMS. The dock office signs the BOL with flowBOL. The executive watches every yard on flowNETWORK. Under all of it, machine vision reads the truck at the gate and an agent dispatches the next move. Think EZ-Pass at the gate and air-traffic control for your trailers.
The proof · already at scale
No company had ever put its whole yard network on one system. Primo just did.
The point is not faster trucks. It is realized production capacity: 5% more volume out the door on the same headcount, capacity those plants could not ship before.
Primo started with one layer: the driver journey. Text the truck instead of checking it in. Paper out of the gate. No more driver-to-dock-office handoff. Across the 24 sites where it went live, those yards shipped about 5% more volume than the sites without it, on the same dock-office headcount. That alone is why Primo committed all ~260 sites to the full Yard Network System, the first national shipper to standardize every yard on one protocol. The YMS is rolling now. Live at 10 plants, every production site by the end of Q3. The highest-volume campus is going fully automated end to end, on a trailer map that updates itself in real time. The 5% came from the lightest touch. The rest is still ahead. Amazon automated the buildings first. The yards are the one node that automation stops at, and standardizing them is the same playbook Primo just proved at scale.
“Your software enabled us to take on additional volume while remaining headcount neutral in the dock office. That was an integral part of our strategy, and it has been proven.”
Result measured on the driver-journey layer, before the YMS rollout. Primo is live at 10 plants today, every production site by the end of Q3.
What it touches
A new layer, not a new migration.
YardFlow runs in the yard and talks to the systems you already have. Your TMS and WMS stay the systems of record. Nobody is ripping anything out.
Built for enterprise infosec review. We connect over your standard API or EDI and scope to yard operations, not your ERP of record. Full integration and security review happen in the audit.
- In the yardflowDRIVER (driver app, no install) and flowGATE (camera gate) run on YardFlow. Nothing changes inside the building.
- ReadsYour TMS appointments, over standard API or EDI.
- WritesGate and turn events back to your WMS, so dock and inventory stay current.
- IT liftOne connection per system. No rip-and-replace, no platform migration.
Your own audit
This is Amazon's own audit, not a generic benchmark. We mapped 16 of your largest freight sites from satellite. Here is what the handoffs cost today, and where the standard lands first.
- 16 of 16
- Run drop yards todaywhere the 48 to 24 minute drop-and-hook win lands
- 15 of 16
- Gated with a guard or boothflowGATE automates the check-in step
- 16 of 16
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
See all 16 sitesOpen the audit →We are not asking for a pilot. We are asking for a conversation.
A 30-minute call, direct with Casey. We show you what we found on your network, you tell us straight where it fits. We will not tell you which site to start at. We have only seen your yards from orbit. You run them, so you already know which one goes first. If the call goes well, we talk about where that is. If the call does not land, you keep the analysis.
None of these times work? Email me at casey@freightroll.com or call or text me at 410-236-7434, and we’ll find one.
Casey Larkin, YardFlow. Jake, our founder, joins when it helps.
