
Key takeaways
Short answer: Pull means downstream pulls from upstream. Kanban caps WIP at each step. CONWIP caps total WIP across the whole line. Kanban gives smoother flow; CONWIP gives higher throughput. The choice depends on whether even workload or maximum output matters more. See also Kanban Cards vs Electronic Kanban.
Production is signaled by downstream consumption, not pushed by upstream schedule. Reduces overproduction, the worst of the seven wastes.
1. Calling MRP "pull." MRP is push.
2. Kanban without sized buffers. Stockouts or overproduction result.
3. CONWIP without bottleneck identification. System floods upstream of bottleneck.
4. No review. WIP caps stay stale as demand changes.
Pull systems affect OEE Performance (smoother flow, less micro-stoppage) and Availability (less starvation at bottleneck).
Fabrico's OEE module visualizes WIP and queue at each station and supports kanban/CONWIP-style monitoring.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
Yes; both are pull.
Yes; hybrid systems are common.
CONWIP usually.
Kanban.