Stop & Shop · 7 ADUSA DCs, mapped from satellite
The Yard Network System, by FreightRoll.
You are automating the buildings. The yards are the half that is left.
In February 2026 you broke ground on an $860 million automated DC in Burlington, the largest facility in your network, built to modernize your supply chain. Inside, robots will move the cases. Outside is the yard, the half that the automation contract does not cover, the gate-to-dock handoff a driver still walks on foot. You self-distribute now, much of it on buildings you pulled back from C&S. Our read is that no two of those DCs run the yard the same way. The one place your flow still clogs is the space between the gate and the dock.
YardFlow is the Yard Network System, the software layer between your TMS and your WMS. It gives ADUSA one gate-to-dock view across the whole network. 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 DCs. 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 DC. 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 Stop & Shop.
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 DCs 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 network splits by temperature into dry grocery, fresh, and frozen, so no two DCs check a truck in alike. Two of your largest grocery DCs, Schodack NY and Bethlehem PA, sit open to the road with no checkpoint at all. Several buildings are former C&S sites you pulled in-house, each carrying its old habits. Burlington will move cases by robot inside while its yard waits on the same gate the others do. A faster building only ships faster if trucks clear the gate. Legacy YMS was built to run one site, not a network. Our read is that the rest are flying blind. You would know better than we would.
Why now
You are spending $860 million to modernize the buildings. Standardize the yards in the same window.
Burlington is your largest facility and your bet on automation, with operations targeted for 2029.
That same modernization should reach the yards, not stop at the dock door. You pulled distribution back from C&S and made ADUSA the operator, so the moment to set one yard standard is now, before every DC reinvents its own. The freight cycle is turning too. For the first time in four years, pricing power is swinging to carriers as capacity tightens. The next spot market will punish shippers whose yards burn a driver's afternoon. 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 trailer a driver hunts down is added cost. When trucks cost this much, that cost counts double. Fix the yards and the capacity you could not see starts to surface, which is more loads out the same doors. For fresh and frozen the clock is unforgiving. A reefer your yards lose today is shrink this week.
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. Stop & Shop just took distribution in-house, and ADUSA would be the first Northeast grocer to put its whole yard network on one protocol.
“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 in the DC.
- 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 the Stop & Shop network's own audit, not a generic benchmark. We mapped 7 ADUSA DCs from satellite. Here is what the handoffs cost today, and where the standard lands first.
- 7 of 7
- Already run drop yardswhere the 48 to 24 minute drop-and-hook win lands
- 5 of 7
- Gated with a guard or boothflowGATE automates the check-in step
- 7 of 7
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
See all 7 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.
