Milk Run

A milk run is a material-delivery method that operates on a fixed route and predictable schedule to support just-in-time production. A delivery vehicle travels along a predetermined loop, delivering standardized, small batches of parts directly to workstations or plants while simultaneously collecting empty containers and pull-signal kanbans. By linking replenishment directly to downstream consumption rates, milk runs reduce line-side floor space requirements, lower work-in-process inventory levels, improve defect containment, and transform reactive material handling into standardized work.

Loading the route…

Key facts

Core principles: Fixed route, fixed schedule, standardized containers, simultaneous exchange, pull authorization
Application environments: Internal line-side replenishment and external supplier networks
Primary design input: Plan for every part (PFEP)
Replenishment trigger: Kanban cards from consumed containers
Key operational impacts: Lower inventory, reduced floor space, and paced material flow

By Matthew Savas — Founder of Kaizumi. Reviewed 29 August 2026.

A milk run is an internal or external material-delivery method operating on a fixed route and a fixed schedule. In a lean production environment, a delivery vehicle completes a predictable loop at set intervals, delivering small standard batches of parts, collecting empty containers, and returning consumed signals to authorize the next replenishment cycle. The method establishes consistent material movement between central storage areas or external suppliers and point-of-use workstations, supporting just-in-time production by linking part deliveries directly to the consumption rate of downstream operations.

Core principles

The milk run operates on five core structural principles:

Fixed route: The delivery vehicle travels along a pre-established sequence of delivery and collection points. The vehicle does not deviate from this sequence based on ad hoc requests.
Fixed schedule: Deliveries occur at regular, predetermined intervals. The schedule is synchronized with the pace of production so that delivery frequency matches line consumption.
Standardized containerization: Materials move in standardized totes, bins, or carts with fixed quantities per container. This removes the need for counting parts during transit or line-side delivery.
Simultaneous delivery and collection: At every stop, the material handler unloads full containers of parts and collects empty containers alongside replenishment signals.
Pull authorization: Material movement occurs only in response to consumption. A full container is replenished only when an empty container and its associated kanban signal are retrieved from the workstation.

Internal versus external milk runs

Milk runs are applied in two distinct operational environments: inside a manufacturing facility and across an external supply network.

Internal milk runs, frequently referred to as line-side replenishment loops, connect a central warehouse, kitting area, or supermarket to production workstations. An internal delivery vehicle, such as an electric tow tractor pulling multiple trailing carts, moves through defined factory aisles. The operator delivers small lot sizes directly to gravity feed racks or dedicated point-of-use locations at each workstation.

External milk runs coordinate logistics across multiple geographical locations. A single logistics truck departs from a central facility or assembly plant, visits several supplier facilities in a predefined sequence to pick up designated quantities of components, and returns to the plant. Alternatively, a single vehicle may depart from a central distribution center to deliver parts to multiple customer plants along a dedicated loop. External milk runs replace separate direct shipments from each supplier with a consolidated routing structure, increasing vehicle volume utilization while maintaining low delivery batch sizes.

Design parameters and data requirements

Designing a reliable milk run requires accurate operational data derived from a plan for every part. The design process defines the route topology, delivery frequency, container sizes, and equipment capacity.

The plan for every part provides component dimensions, packaging quantities, storage locations, point-of-use consumption rates, and supplier sources. Engineers use this data to determine the total volumetric and weight demand per delivery cycle for each workstation on the route.

The delivery interval is set by balancing workstation storage limits against material handling capacity. Shorter intervals reduce line-side inventory footprints but require more frequent material handler loops. The total loop time consists of travel time between stops, unload time for full containers, load time for empty containers, and return time to the replenishment base.

Workstation storage capacity is calculated based on the delivery interval and the consumption rate. The minimum inventory required at a workstation equals the consumption rate multiplied by the delivery interval, plus a safety margin to account for slight cycle time variations. If a workstation consumes parts from two standard containers during one delivery interval, the rack must hold at least four containers: two being consumed during the current cycle and two delivered for the subsequent cycle.

Operational workflow

A milk run follows a closed-loop operational sequence that repeats throughout the working shift:

Supermarket staging: Warehouse operators or water striders prepare full containers in the central supermarket according to consumed kanban cards collected during the previous loop. Containers are loaded onto the delivery carts in reverse sequence of the route stops.
Route departure: The delivery vehicle departs from the central supermarket at the scheduled departure time, regardless of whether all carts are filled to maximum volume capacity.
Point-of-use exchange: At each scheduled stop, the operator unloads the specific full containers required by that workstation into the designated gravity feed lane or shelf location.
Empty and signal collection: The operator retrieves empty totes and the kanban cards detached from consumed containers, placing the empty containers onto the transport carts.
Loop completion and trigger handoff: The vehicle returns to the central supermarket. The operator unloads empty containers to their return staging lanes and deposits the collected kanban cards into the production or picking queue. These cards immediately authorize the replenishment picking for the next scheduled loop.

Worked example: Assembly plant replenishment loop

Consider an internal manufacturing milk run configured for an assembly plant with four distinct assembly cells:

Vehicle configuration: Electric tugger pulling three delivery carts.
Route structure: Four point-of-use stops arranged in one fixed loop through the plant.
Delivery interval: Every 60 minutes.
Outbound cargo: Small standard quantities in full totes.
Inbound cargo: Empty totes and consumed kanban cards.
Replenishment rule: Actual consumption authorizes the next refill cycle.

The loop operates according to the following exact sequence:

Minute zero: The electric tugger departs the central supermarket hauling three delivery carts loaded with full totes. Each tote contains a standardized count of parts assigned to specific workstations.
Minute 12: The tugger arrives at Stop 1. The material handler delivers two full totes of fasteners and collects two empty totes along with two consumed kanban cards.
Minute 24: The tugger arrives at Stop 2. The material handler delivers three full totes of subassemblies and collects three empty totes and three consumed kanban cards.
Minute 36: The tugger arrives at Stop 3. The material handler delivers one full tote of wiring harnesses, collects one empty tote, and collects one consumed kanban card.
Minute 48: The tugger arrives at Stop 4. The material handler delivers two full totes of stamped brackets, collects two empty totes, and collects two consumed kanban cards.
Minute 55: The tugger returns to the central supermarket. The material handler unloads eight total empty totes into the container return lane and places eight collected kanban cards into the replenishment dispatch board.
Minute 55 to 60: Supermarket material handlers pick parts from storage according to the eight returned kanban cards, loading eight full replacement totes onto the three delivery carts.
Minute 60: The electric tugger departs for the next loop.

In this system, if Stop 2 consumes only two totes during a particular hour instead of three, the operator returns only two empty totes and two kanban cards. Consequently, the supermarket prepares and loads only two full totes for Stop 2 on the following run. Point-of-use stock remains stable without overflowing line-side floor space.

Impact on manufacturing operations

Implementing a milk run changes internal logistics from batch-and-queue movement to paced flow.

Line-side floor space requirements decline because workstations receive only enough inventory to cover the duration of the delivery interval plus safety stock. Workstations do not store full supplier pallets or multi-day supplies. The space saved can be repurposed for production activities or value-adding processes.

Work-in-process inventory levels drop across the facility. Because material delivery occurs in small, frequent increments, the amount of capital tied up in stationary material decreases proportionally with the delivery interval length.

Material handling labor shifts from reactive expediting to standardized work. The material handler follows a timed script and defined walking paths, which makes schedule deviations immediately visible.

Defect containment improves. When a quality defect occurs in a supplied batch of parts, the number of defective parts present on the production floor is limited to the small quantity delivered in the current cycle, rather than an entire pallet or weekly batch.

Operational requirements and challenges

A milk run requires high process discipline across multiple operating departments:

Strict adherence to standardized work: If the material handler pauses to perform unscheduled tasks or skips stops, the delivery schedule collapses, causing line stoppages due to part shortages.
Visual control maintenance: Racks, floor markings, and kanban posts must be clearly identified. Deliveries cannot be completed accurately if designated line-side drop locations are blocked by debris or unorganized stock.
Schedule synchronization: If production takt time changes significantly, the milk run route timing, vehicle capacity, or delivery frequency must be recalculated and rebalanced.
Rigorous container standardization: Deviations in container dimensions or quantities disrupt the loading plan of the delivery carts and rack spacing at workstations.

Frequently asked questions

What is the difference between an internal and an external milk run?: An internal milk run operates within a single facility, using vehicles such as electric tuggers to transfer small batches of parts between a central supermarket and workstation racks. An external milk run coordinates transport across separate geographic sites, using a truck to collect materials from multiple suppliers or deliver goods to multiple customer plants along a single route. While internal runs manage line-side replenishment, external runs consolidate freight to increase vehicle volume utilization.
How does a milk run adjust when a workstation consumes fewer parts than expected?: Replenishment operates strictly on pull authorization, so a delivery driver only collects empty containers and kanban cards for materials actually used. If a workstation consumes less during a cycle, fewer empty containers are returned to the central supermarket. Consequently, the supermarket prepares fewer full replacement totes for the next loop, preventing point-of-use inventory from overflowing.
How is workstation storage capacity calculated for a milk run?: Workstation storage is calculated by multiplying the consumption rate by the delivery interval, then adding a safety margin for slight cycle variations. The designated rack must hold both the containers currently being consumed and the replacement containers delivered for the following cycle. For example, if a workstation uses parts from two containers per interval, the rack must hold at least four containers.
What happens if a milk run delivery vehicle is not fully loaded at departure time?: The delivery vehicle departs at its scheduled departure time regardless of whether its carts are filled to capacity. Delaying departure to accumulate a full vehicle load disrupts delivery intervals and risks causing part shortages at downstream workstations. Adhering to the timetable ensures material movement remains synchronized with the pace of production.
Why are standardized containers necessary for a milk run?: Standardized containers hold fixed part quantities, which eliminates the need for material handlers to count individual parts during transit or line-side delivery. They also ensure predictable physical dimensions that match the transport carts and workstation gravity feed racks. Inconsistent container sizes disrupt vehicle loading sequences and prevent efficient storage at line-side drop locations.

Terms

Just-in-Time Kanban