Kanban and Pull-Based Replenishment
A milk crate disappears from the back of a kirana, and before the owner makes a phone call, the distributor already knows what to send tomorrow. That is the quiet power of pull-based replenishment - the next supply move is triggered by real consumption, not by someone's hopeful forecast.
- Kanban is a visual signal that authorizes production, movement or replenishment only when the downstream process needs it.
- Pull replenishment starts from actual consumption; push replenishment starts from a schedule or forecast.
- The core control is simple: no signal, no production. This prevents overproduction, excess WIP and hidden problems.
- Kanban works best when demand is reasonably stable, lead time is controlled, container size is fixed and standard work is followed.
- Basic card formula: Number of Kanbans = Demand during lead time x Safety factor / Container quantity.
- Track it with service level, stockout rate, replenishment lead time, WIP, inventory turns and expedite rate.
- The biggest interview trap is calling Kanban a “card system” without explaining the operating rules behind the card.
Big Picture: Kanban Is a Replenishment Conversation
Think of Kanban as a disciplined conversation between two processes. The customer process says, “I consumed one container.” The supplier process replies, “That signal gives me permission to replace exactly one container.” For the larger Lean context behind this logic, revise Flow, Pull & Levelling Production.
Core Explanation: The System, Not the Card
A Kanban card, bin, empty tray, barcode scan or digital alert is only the visible part. The real system has four operating rules:
This is why Kanban is closely linked to Lean. It attacks overproduction, the waste that often creates the other wastes - excess inventory, waiting, motion, transport and rework. But Kanban is not magic. If process times vary wildly, suppliers are unreliable or setups are slow, the system either starves or needs too much safety stock.
Kanban vs Push Replenishment
The easiest way to explain Kanban in an interview is to contrast it with push planning. Push asks, “What do we expect to need?” Pull asks, “What has actually been consumed?”
In practice, companies often run a hybrid. Strategic planning may be forecast-driven, while line-side replenishment, supermarket picking or spare-parts feeding may be Kanban-driven.
The Three Core Kanban Types
Kanban signals can authorize different actions. Name these clearly and you sound operationally grounded.
Worked Example: How Many Kanban Cards Are Needed?
The standard sizing logic is:
Number of Kanbans = Demand during replenishment lead time x (1 + Safety factor) / Container quantity
Suppose an assembly line uses 240 clips per day. Replenishment lead time is 0.5 day. The team wants a 20% safety factor. Each container holds 30 clips.
The answer is 5 Kanban cards. If the line frequently stocks out, do not blindly add cards. First check whether demand, lead time, container quantity or supplier reliability changed.
Metrics: What to Track in a Pull System
Kanban is only as good as its control loop. These are the 6 interview-worthy measures to name.
If an interviewer pushes mathematically, connect Kanban to Little's Law and reading a process mathematically: for a stable process, WIP, throughput and flow time move together.
Definitions You Can Say in One Breath
- Kanban: The Lean Enterprise Institute defines kanban as a signaling device authorizing production or withdrawal in a pull system.
- Pull production: The Lean Enterprise Institute describes pull production as downstream activities signaling their needs to upstream activities.
- Pull-based replenishment: Replacing only what has been consumed, in the agreed quantity, after a valid demand signal.
Case Study: Zara and Store-Driven Pull Replenishment
Zara uses store demand signals, rapid feedback and controlled replenishment to reduce blind fashion pushes and respond faster to what customers actually buy.
Situation: Fashion retail is dangerous because the product life is short and demand is uncertain. If a retailer pushes too much inventory into stores too early, it risks markdowns. If it under-supplies winners, it loses sales.
The move: Zara's parent Inditex describes its operating model around close integration of stores, online, design, production and logistics, with store information feeding decisions through the system (Inditex, Our Model). In pull-replenishment terms, the store becomes the demand sensor. Sales, customer reactions and store-level movement guide what gets replenished, reduced or adapted.
Why it works: The primary driver is fast demand sensing from stores. Supporting drivers include shorter design-to-store feedback loops, disciplined assortment decisions, responsive logistics and technology-enabled inventory visibility. This is not “Zara wins because it is fast” - speed matters because it is attached to real demand signals.
Lesson: Kanban is not limited to factory cards. The same logic applies wherever real consumption can trigger controlled replacement - from an Indian kirana's empty milk crate to a fashion retailer's store replenishment loop.
How AI Changes Kanban and Pull-Based Replenishment
AI does not replace Kanban discipline. It improves the signal quality and helps teams size the system more intelligently.
- Dynamic Kanban sizing: ML models can detect changes in demand variability, supplier lead time and seasonality, then recommend when card counts or safety factors need review.
- Computer vision for shelf and bin signals: Cameras can identify empty facings, missing totes or low stock positions and convert them into replenishment alerts, especially in retail and warehouses.
- Exception prioritisation: AI can rank which Kanban misses matter most - for example, a stockout on a bottleneck part gets escalated before a low-risk consumable.
Use ChatGPT or Claude with a simple SKU dataset: daily usage, replenishment lead time, container size and stockout history. Ask it to calculate Kanban cards, flag unstable items and draft 5 interview questions on why some SKUs should stay push-planned instead of pull-replenished.
Interview Relevance
“You are managing an assembly line that often runs out of small components, while stores are full of slow-moving inventory. How would you design a Kanban-based replenishment system?”
Use the phrase: “Kanban is a WIP-limiting replenishment control, not just a visual board.” It shows you understand the operating system behind the tool.
Common Mistake
Mistake: Saying “Kanban means cards or sticky notes” and stopping there. This costs candidates because it reduces an operating-control system to a stationery tool. Fix: Always explain the loop - consumption, signal, authorization, replenishment, WIP limit and metric review.