Menu

Kanban in Manufacturing: How the Pull System Works

Learn how kanban works in manufacturing: cards, signals, pull vs push, the card-count formula with a worked example, benefits, and digital kanban.

Kanban in manufacturing is a lean scheduling method that uses visual cards or signals to trigger production and material movement only when a downstream process actually consumes inventory. It replaces forecast-driven push with demand-driven pull, capping work in progress, exposing bottlenecks, and keeping stock lean without starving the line.

How the kanban pull system works

Kanban links every workstation to real consumption instead of a central schedule. When a downstream station uses parts, it sends a signal upstream authorizing exactly one refill, and nothing moves without that signal.

  • Kanban card: a physical or digital ticket attached to a standard container of parts. An empty container returns its card as an order to produce or replenish.
  • Production kanban: authorizes a workcell to make a specific quantity of a specific part.
  • Withdrawal (move) kanban: authorizes transport of a container from a supermarket to the point of use.
  • Supermarket: a controlled buffer of finished sub-assemblies sized to the card count.
  • WIP cap: the total number of cards in circulation is a hard ceiling on inventory. No spare card, no extra production.

The rule is simple: produce only to replace what was taken. This self-regulating loop is why kanban is central to the Toyota Production System and to total productive maintenance programs.

Pull vs push: the core difference

Push and pull answer the same question differently: what tells a station to start working?

  • Push: a central plan or forecast releases work whether or not the next station is ready. Overproduction, growing WIP, and hidden defects are common.
  • Pull: actual downstream demand releases work. WIP is capped, lead time is shorter, and problems surface fast because there is no buffer to hide behind.

Push optimizes each station in isolation. Pull optimizes flow across the whole line, which is why a stoppage or quality issue becomes visible almost immediately instead of being buried under excess inventory.

How to calculate the number of kanban cards

The card count sets your inventory ceiling, so getting it right matters. A widely used formula is:

Number of kanbans = (D x L x (1 + S)) / C

  1. D = average demand per unit of time
  2. L = replenishment lead time (produce plus transport plus wait)
  3. S = safety factor as a decimal (buffer for variability)
  4. C = container capacity (parts per card)

Worked example: a line consumes D = 400 parts per hour, replenishment lead time is L = 2 hours, safety factor S = 0.20 (20%), and each container holds C = 100 parts.

Kanbans = (400 x 2 x 1.20) / 100 = 960 / 100 = 9.6, rounded up to 10 cards. That caps WIP at 10 x 100 = 1,000 parts. Cut lead time to 1 hour and the requirement drops to (400 x 1 x 1.20) / 100 = 4.8, rounded to 5 cards, halving inventory. This is why kanban and lead-time reduction reinforce each other: every hour you remove from L directly removes buffer stock.

Benefits of kanban on the factory floor

Kanban delivers measurable operational gains when applied to stable, repetitive demand.

  • Lower inventory and carrying cost: WIP is mathematically capped by the card count.
  • Shorter lead times: parts flow on demand rather than sitting in queues.
  • Fewer defects escaping: small batches make quality problems visible within one container, not one week.
  • Visual bottleneck detection: a pile of returned production cards at one cell instantly shows where flow is stuck.
  • Less overproduction: the single biggest lean waste is structurally prevented.

Kanban also protects uptime. A card cap only holds if machines run reliably, so pairing pull scheduling with proactive maintenance keeps the loop from breaking. A single unplanned stop can drain a supermarket faster than it refills. See the drivers of unplanned downtime to protect your pull system.

Steps to implement kanban

Roll kanban out on one value stream first, then expand once the loop is stable.

  1. Map the value stream and pick a product family with steady, repeatable demand.
  2. Standardize containers and set container capacity (C).
  3. Calculate card count using the formula above, starting conservative.
  4. Design the cards or signals and define clear rules for when each one moves.
  5. Size supermarkets to match the card count, no more.
  6. Train operators so the pull rules become habit, then remove cards gradually to expose the next constraint.

Digital kanban and connected production

Physical cards work well on a single line, but they get lost, are hard to audit, and give no real-time visibility across plants. Digital kanban replaces the ticket with an electronic signal triggered automatically by consumption or a scan, so replenishment orders, card counts, and cycle times are logged and analyzable.

Digital pull becomes far stronger when tied to live machine data. When production monitoring feeds actual output and stoppage data into the same platform, you can see the moment a bottleneck forms rather than discovering it when a supermarket empties. Fabrico provides real-time production and OEE monitoring, including camera-based machine monitoring that works without a PLC, so even older equipment can signal consumption and status. Pairing that signal with a CMMS means the maintenance work orders that keep the pull loop alive live alongside the production data driving it. Note that automatic reordering, SCADA control, and digital-twin modeling are separate industry concepts, not part of a kanban signaling setup.

Frequently Asked Questions

Is kanban the same as just-in-time?

No, but they are closely related. Just-in-time (JIT) is the broad strategy of producing only what is needed, when it is needed, in the amount needed. Kanban is one of the practical signaling tools used to execute JIT on the shop floor. You can pursue JIT with other pull mechanisms, but kanban is the most common way to make it work in practice.

Does kanban work for high-variety, low-volume production?

Kanban performs best with stable, repetitive demand and standard parts, because the card count depends on predictable consumption. For high-variety or highly seasonal production, fixed card counts break down. Teams in those settings often use hybrid approaches, adjusting card counts seasonally or reserving pull only for high-runner components while scheduling irregular items with other planning methods.

How does kanban relate to OEE?

Kanban controls flow, while OEE measures how effectively equipment runs. They reinforce each other: a low availability score means machines stop often, draining kanban supermarkets faster than they refill and forcing larger buffers. Improving OEE lets you safely reduce card counts and inventory. Monitoring both together shows whether your pull system is genuinely lean or quietly hiding equipment problems behind extra stock.

Book a Fabrico demo to see how real-time production monitoring and CMMS give your kanban pull system the live machine data and maintenance reliability it needs to run lean without stockouts.

Latest from our blog

Autonomous Maintenance (Jishu Hozen): A TPM Pillar
Read now
Net Equipment Effectiveness (NEE) vs OEE and TEEP
Read now
The Kano Model: Prioritizing Quality and Features
Read now
8D Problem Solving: The 8 Disciplines Explained
Read now
Little's Law in Manufacturing: WIP, Throughput, Lead Time
Read now
Spaghetti Diagram: Mapping Motion and Transport Waste
Read now
Pull System in Manufacturing: A Practical Guide
Read now
Drum-Buffer-Rope (DBR) Scheduling Explained
Read now
Theory of Constraints (TOC): The Manufacturing Guide
Read now
Reorder Point (ROP): Formula and Spare-Parts Example
Read now
The Bathtub Curve in Reliability Engineering
Read now
Run-to-Failure Maintenance: When It Makes Sense
Read now
Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration