Prepared for The Coca-Cola Company · ~270 sites · one network standard
Your TMS runs the road. Your WMS runs the building.
Your supply chain is connected. Your yards are not.
Routing, SKU velocity, and delivery windows all run to the minute. The yards do not. Across roughly 270 sites, each runs as its own island, so the rest of your stack plans against a guess. YardFlow is the network layer for the yards: one system of record across every site that turns the same footprint into artificial capacity.
- $1.2B/yr
- modeled across the network
- $4.3M/yr
- added contribution margin per site
- 3.2 mo
- payback, before rollout completes
- The gapEvery yard is an island. The rest of your stack plans against a guess.
- The network layerOne system of record across every yard. Live truth into your TMS, WMS, and plan.
- Artificial capacityMore throughput on the same footprint. No capex, no new heads.
- ProvenPrimo standardized roughly 260 sites on the protocol. Turns cut 48 to 24.
The problem
You do not run one yard. You run a network of about 270, and it is not connected.
Here is the part no planning system can see.
Your TMS knows the truck on the road. Your WMS knows the freight inside the building. Between them sits the yard. Across roughly 270 sites, that is a network of disconnected islands. Some run a legacy system. Most run on radios and a single gate. None run on one standard. At Columbus, 60 dock doors funnel through one truck gate, so the choke is the gate, not the building. So every upstream system you bought assumes it knows where the trailer is. In a yard with no network, the schedule is a guess. That is the gap. You can see it on the ground. A driver climbs down to ask a human where to drop. Three bill-of-lading copies print for one shipment. A trailer sits lost on your own concrete. Those are the symptoms. The disease is that your yards were never on the network. It is 2026, and every other tier of your supply chain is connected. The yards are the last one that is not. Routing, SKU velocity, and delivery windows all run to the minute, and a blind yard turns a dock delay into a missed route. We mapped 30 of your US sites from satellite to show the pattern. 27 of those 30 already run drop yards, where the 48 to 24 minute drop-and-hook win lands.
The lost time lives in the gaps. Now multiply it across ~270 plants, each running its own version. YardFlow runs the whole network as one chain.
Why now
Capacity is the constraint, and a blind yard is capacity you cannot use.
Coca-Cola runs routing, SKU velocity, and delivery windows on live data, but never the yards, and the freight market just put a price on that gap.
It is 2026. Every other tier is connected. The yards never were. Capacity is the constraint now, and a yard you cannot see is capacity you cannot use. A networked yard is the cheapest capacity you will ever add. It turns drop and live loads sooner and frees dock hours, so peak volume moves through the same sites with no new concrete. That is capacity you create, not capacity you buy. Every dollar you spent upstream keeps underdelivering while the yards stay blind. All of it assumes a trailer position the yard cannot confirm. 25 of your 30 audited sites burn dray on every inbound, with only 5 on rail, so a networked yard turns those moves faster first. The longer the yards stay off the network, the more that silo tax compounds.
Who we are
The Yard Network System. The network layer your stack was missing.
Start with what it is not. It is not a single-site yard tool, and it is not a 40-year-old legacy YMS. The Yard Network System is the network layer for your yards. It is the system of record between your TMS, WMS, and planning stack and the physical trailer, across every site. One standard, priced to run every plant, not just the flagship. flowGATE reads the truck at the gate. flowDRIVER routes the driver. flowTWIN puts every trailer on one live map. Same system, same standard, at every site. See it running.
The proof · already at scale
This is the way. We are just getting started.
Primo Brands retired their legacy YMS (PINC) and standardized on the YardFlow protocol across their North American network. They used that consolidation to take on more shipping volume while holding dock-office headcount flat, about 5 percent more shipped on the same heads, and cut drop-and-hook turns from about 48 minutes to about 24. One platform, one source of truth, lower licensing. They are rolling it network-wide across roughly 260 sites.
“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.”
Figures from the YardFlow deck and the live network. 24 sites live today, rolling out to 200 more.
The prize, sized for Coca-Cola
Across ~270 plants. Payback in 3.2 mo. Recovered throughput, avoided detention, and freed dock hours, every year.
The per-plant numbers are measured at Primo Brands, a multi-temp, multi-site beverage network running the hardest freight in CPG. Applied across Coca-Cola’s roughly 270-plant bottling network at a conservative 50 percent turn-time improvement, the model returns $1.2B a year in recovered throughput, avoided detention, and freed dock capacity. The $1M+ per site is the proven floor at Primo; the model adds throughput at beverage margins. The IRR range is in the table below. We will build Coca-Cola’s exact number with your team.
| Scenario | Payback | Monthly IRR |
|---|---|---|
| Paper-only savings | 20.5 mo | 2.97% |
| Hard savings | 7.0 mo | 24.63% |
| Full modeled value | 3.2 mo | 141.69% |
Monthly IRR from the YardFlow ROI model: monthly cash flows net of subscription, 24-month horizon. The paper-only scenario is the conservative floor.
Your own audit
This is Coca-Cola’s own audit, not a generic benchmark. We mapped 30 US bottling sites from satellite. Here is what the handoffs cost across the network.
- 27 of 30
- Already run drop yardswhere the 48 to 24 minute drop-and-hook win lands
- 24 of 30
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
- 17 of 30
- Gated with a guard or boothflowGATE automates the check-in step
See all 30 sitesOpen the audit →Easy
Start at one DC. Prove it in 60 days. Standardize from there.
Nothing gets ripped out to start. Begin at the Columbus distribution center, where 60 dock doors funnel through one gate and the drop yard is already in place. First measurable impact in 30 to 60 days, on the exact metric that hurts: trucks through the gate and onto a door. Then the same system rolls to Charlotte, Nashville, and the rest of the network, on economics that legacy YMS never allowed.
- 01Audit30 minutes. Map the network to archetypes.
- 02PilotColumbus DC. 60 days to first impact.
- 03StandardizeThe network, on proven economics.
The brief, one more time
- The problemThe yards are the last tier of your stack with no network, run site by site across the bottler network.
- The proofPrimo retired its legacy YMS and standardized roughly 260 sites. More volume, flat headcount.
- The prize$1.2B a year, payback 3.2 mo, on economics legacy YMS never allowed.
- The first stepOne DC at Columbus. Sixty days to first impact. Zero displacement risk.
A problem you already own, a system already proven at Primo, a prize worth ten figures, and a first step that risks nothing. That is the brief.