Vendor managed inventory (VMI) and milk run collection are two of the most commonly misunderstood terms in inbound logistics, and forwarders get asked about both more than the plain-English versions of the terms would suggest. VMI is a replenishment model: the supplier, or a third party acting for the supplier, decides when to ship based on the buyer's actual consumption data, rather than waiting for the buyer to issue a purchase order. A milk run is a routing model: one vehicle collects from several suppliers on a fixed route and timetable instead of each supplier sending a separate, often half-empty, shipment. The two are frequently run together, but they answer different questions, and a forwarder asked to support either one is being asked to do something specific and measurable, not just "help with logistics."
What Vendor Managed Inventory Actually Means in a Freight Context
Under a traditional purchase order model, the buyer watches its own stock levels and decides when to order. Under VMI, that decision moves upstream: the supplier, or a third-party logistics provider acting on the supplier's behalf, monitors the buyer's inventory position and consumption rate and decides when and how much to ship, within limits both sides agree in advance (minimum and maximum stock levels, order frequency, lead time). The buyer stops issuing individual POs for routine replenishment and instead shares the data the supplier needs to make that call.
VMI Is Not the Same Thing as Consignment Stock
The two get conflated constantly, and the difference is about who owns the goods and when. According to TrueCommerce, an established EDI and supply-chain data provider, under VMI "the supplier manages the deliveries and subsequent stock levels of the retailer, who purchases the products as part of the process," which means title and payment obligation transfer to the buyer at delivery, on whatever terms the two parties have agreed, exactly as it would under a standard purchase order. Consignment stock is a different arrangement layered on top of a similar physical setup: "the retailer controls stock levels, but the stock is still owned by the supplier while it's in the retailer's warehouse," so the buyer is not invoiced until the goods are actually used or sold. VMI is a decision-rights model (who decides when to replenish); consignment is an ownership model (who holds title while the goods sit on the shelf). The two are independent choices that can be combined or run separately, and a forwarder handling a VMI program should confirm early which one, or both, the contract actually specifies, because it changes who is liable for loss or damage on stock sitting in a buffer warehouse.
What a Forwarder Is Actually Asked to Do Inside a VMI Program
The buyer and supplier set the commercial terms; the forwarder is usually the one who has to make the physical and data mechanics work. In practice that means:
- Scheduled collections. Rather than picking up whatever is ready whenever the supplier calls, collections run on a fixed cadence (daily, twice-weekly, weekly) sized to keep the buyer inside its agreed min/max stock band without over-collecting.
- Buffer-stock warehousing. Many VMI programs route goods through a forwarder-operated or forwarder-contracted warehouse near the buyer, holding a cushion of stock that gets drawn down as the buyer consumes it, rather than shipping directly from the supplier's own facility every time.
- Advance ship notices and inventory data feeds. The buyer needs to know what is coming before it arrives, and the supplier (or the forwarder relaying on its behalf) needs to see what the buyer actually has on hand. The advance ship notice, EDI transaction 856, carries shipment numbers, ship and expected delivery dates, item and quantity detail, and tracking references, and is "required by many major retailers to be sent in a specific timeframe before the product arrives at the retailer's distribution center or store." The inventory side runs on a separate document, EDI 852, Product Activity Data, described as being "used primarily to share data related to inventory positions and movements... between suppliers and retailers" and called out as "especially helpful for those using Vendor Managed Inventory," typically sent on a recurring schedule (daily, weekly or biweekly) rather than triggered by a single event. A forwarder that cannot produce a reliable ASN, or relay a retailer's inventory feed accurately, is asking the supplier to make replenishment decisions on stale or missing data.
- Pick-to-order at the buffer point. Where the forwarder runs the buffer warehouse, it is also usually the one picking and releasing stock against the buyer's call-off or consumption trigger, not just storing pallets until someone else asks for them.
What a Milk Run Actually Is
A milk run is a single vehicle running a fixed route to multiple pickup or drop points on a set timetable, named for the dairy trucks that used to collect from several farms and deliver to one processing plant. Two industries use the term for genuinely different things, and mixing them up in a conversation with a client is an easy way to look like you have not done this before.
The trucking and automotive sense: scheduled multi-supplier collection
This is the sense most forwarders will actually be asked about. One truck (or one container being filled over a route) visits several suppliers in a region on a fixed schedule, collecting a partial load from each, rather than every supplier separately sending a smaller, less-than-truckload shipment on its own timetable. Penske Logistics, describing it in its own logistics glossary, defines it as "a delivery method used to transport mixed loads from various suppliers to one customer," tracing the term to World War II-era dairy delivery routes. The pattern is most strongly associated with automotive and other high-frequency assembly supply chains, where inbound parts arrive from several nearby suppliers in small, regular batches timed to line consumption rather than in occasional full truckloads, a practice widely documented in lean-manufacturing literature connected to the Toyota Production System's just-in-time approach.
The liner and feeder shipping sense: a looser, informal use of the same word
Some carriers and forwarders also use "milk run" informally to describe an ocean service, typically a feeder or short-sea rotation, that calls several ports in sequence on one voyage rather than sailing point to point, picking up and setting down cargo at each stop along the way. Be aware this is genuinely a looser, secondary usage: unlike the trucking and automotive sense, it is not a term with a single standard definition in liner shipping the way "milk run" has become for inbound parts collection, and no major carrier's own published glossary checked for this article used the term at all. If a client uses "milk run" about an ocean movement, confirm what they actually mean before quoting: it is more likely shorthand for a multi-port rotation than a request for the scheduled-collection service the term usually describes.
| Term | What moves | Fixed element | Most associated with |
|---|---|---|---|
| Milk run (trucking/automotive) | Partial loads from several suppliers | Route and pickup timetable | Inbound parts, JIT assembly lines |
| Milk run (liner/feeder, informal) | Containers at several ports | Port rotation on one voyage | Regional feeder and short-sea services |
Why Milk Runs Cut Cost, and Why a Late Supplier Breaks the Whole Route
The logic is straightforward: five suppliers each sending a half-full truck five times a week costs more, in both freight spend and dock congestion, than one truck visiting all five once and arriving full. Consolidating partial loads onto one scheduled route reduces the number of less-than-truckload movements and lets the buyer hold less safety stock, because replenishment arrives on a predictable cadence instead of whenever each supplier happens to ship.
The cost of that efficiency is schedule dependency. A milk run only works if every stop is ready when the truck arrives: a supplier that is not loaded, or whose paperwork is not ready, does not just delay its own shipment, it delays every stop scheduled after it on the same route, and can push the whole load past the receiving window at the destination. A single-supplier LTL shipment that runs late is that supplier's problem. A milk run that runs late is everyone's problem, which is why a credible milk run operator needs real slot-confirmation and exception-handling discipline, not just a truck and a map.
The Data and Visibility a Forwarder Must Provide to Run Either Program Credibly
Both VMI and milk run programs run on trust that the physical movement is happening on schedule, which means a forwarder has to be able to show it, not just promise it. At minimum, that means:
- Real-time or near-real-time slot confirmation at each pickup point, so the buyer and supplier both know a stop was completed on time, not just that the truck eventually arrived somewhere.
- Exception alerts the moment a stop is going to run late or be missed, sent early enough that the receiving side can adjust, rather than discovered when the truck fails to show up.
- Accurate, on-time ASNs (EDI 856 or an equivalent digital notice) so the buyer's receiving team, and its own downstream production or resupply planning, is not working from a guess.
- Consistent inventory reporting at any buffer point the forwarder operates, matching whatever cadence the buyer's own data feed (EDI 852 or equivalent) expects.
None of this is exotic technology. It is discipline: the same pickup confirmed the same way every time, and a data feed that matches what was physically loaded, not a phone call after something has already gone wrong.
Who These Programs Actually Fit
It is worth being honest about this rather than presenting VMI and milk runs as something every shipper should ask for. Both require investment before they pay off: a data integration between the buyer's inventory system and the supplier or forwarder, an agreed min/max stock band, and a route that only makes sense once there is enough regular volume across enough nearby suppliers to fill a truck. That setup cost is difficult to justify against a single shipment or a brand-new supplier relationship with no track record to base a min/max band on. In practice, these are programs that get built once a relationship has enough volume and history to make the fixed overhead worth carrying, not something to propose on a first shipment.
Before You Commit to Either Program
- Confirm whether the arrangement is VMI, consignment, or both. They answer different questions (who decides replenishment versus who owns the stock) and the contract should say which applies, since it changes who carries the risk on buffer inventory.
- Agree the data feed and its cadence before the first pickup, not after the first missed shipment. Know whether the buyer expects an ASN per shipment, a periodic inventory feed, or both, and confirm your systems can actually produce them on schedule.
- Size the buffer warehouse to the agreed min/max band, not to whatever space happens to be available, and confirm who is liable for stock sitting in it.
- Build in exception handling for a late supplier before the route goes live: a plan for what happens to the rest of the stops when one supplier is not ready, not an improvised response the first time it happens.
- Do not assume "milk run" means the same thing on an ocean quote as it does on a trucking quote. Confirm which service the client is actually describing before you price it.
Freight forwarder KPIs are a reasonable place to track whether a VMI or milk run program is actually performing once it is running: our guide to freight forwarder KPIs and scorecards covers the metrics worth measuring against your own baseline. If the physical flow runs through a shared facility rather than direct collection, cross-docking and consolidation hubs covers how freight moves through that kind of point without sitting still, and warehousing and 3PL pricing covers what a buffer-stock arrangement like this actually costs to run.
A forwarder that can show, not just claim, scheduling discipline and accurate data feeds is the one worth trusting with a program like this. You can search more than 29,300 logistics companies by country and service in the CargoLinked directory, or post your shipment and let forwarders come to you.
This article explains general supply-chain and logistics concepts and is not a substitute for the specific terms of a VMI, consignment or transportation agreement. Confirm ownership, liability and data requirements directly in your own contract.
