Boston Beer · 5 NA breweries, mapped from satellite
The Yard Network System, by FreightRoll.
You pulled production back in house. The yards carry every extra truck.
You brewed 95% of your domestic volume internally last quarter, up from 85%, and the full year is guided over 90%. Every case you move back in house is another truck through your own gate. You brew Sam Adams, Twisted Tea, Truly, and Angry Orchard, four SKU velocities that share the same yards. We mapped 5 of your sites and count 71 dock doors. The one place your flow still clogs is the yard. We can count the doors from orbit, not what runs them. Our read is that trucks take too long to get in and out, and that is production capacity you never get to sell.
YardFlow is the Yard Network System, the software layer between your TMS and your WMS. The volume you brought home only ships if your gates can turn the trucks that carry it. 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 Boston Beer.
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 breweries 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 Breinigsville plant in Pennsylvania brews about two-thirds of your Sam Adams output, and our read is that it runs the network on its own conventions. At the Cincinnati brewery a truck backs straight off a narrow Over-the-Rhine street into a dock, and one stalled trailer jams the public road behind it. Across the 5 sites we mapped, we count 71 dock doors run on local dock-handling, with only 1 site rail-served. Pulling 10 more points of volume in house pushes more trucks through those same gates. Legacy YMS was built to run one site, not a network. Our read is that the gap shows up everywhere except your biggest plant.
Why now
You are optimizing the network to cut freight. The yard is where that money leaks.
Freight costs rose $2.5 million last quarter on higher rates, and you are reworking the network to claw it back.
The yard is where that leak starts. You can spin a brewery up to make ten percent more cases. It ships nothing if the yard cannot turn ten percent more trucks. Your yards are the cap on what your breweries can sell. The yards never got the upgrade. Twisted Tea is the top flavored malt beverage in America and grows every year. Every new case has to clear a gate. Our read is that the gate is what caps the growth, not the brewhouse. 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 freight cost. When rates climb like this, 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. A truck your yard loses today is a route that runs late tomorrow.
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. Boston Beer would be the first brewer to take it.
“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 on the plant floor.
- 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 Boston Beer's own audit, not a generic benchmark. We mapped 5 NA breweries from satellite. Here is what the handoffs cost today, and where the standard lands first.
- 2 of 5
- Already run drop yardswhere the 48 to 24 minute drop-and-hook win lands
- 1 of 5
- Gated with a guard or boothflowGATE automates the check-in step
- 1 of 5
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
See all 5 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.
