Kanban or Reorder Replenishment Rule¶
Control rule — instantiates Push-Pull Decoupling Point Design
Refills the decoupling buffer only on real consumption, tying upstream production to actual draw-down rather than forecast.
The Kanban or Reorder Replenishment Rule is the standing control law that keeps the decoupling buffer topped up — and it does so on one strict condition: replenishment is authorized only when real consumption draws the buffer down past a trigger. A returned kanban card, or an on-hand level falling to a reorder point, releases a fixed replenishment quantity upstream; absent that consumption signal, nothing is made. Its defining idea is that the refill loop is pull-governed: the authority to produce is actual draw-down, never a forecast. It controls the flow of stock into the buffer. It is not the buffer, and it is not the customer-order boundary — it is the small, self-limiting rule that decides when and how much to put back.
Example¶
On an automotive final-assembly line, a bin of a specific bracket sits at the station, and each bin carries a card. When the line empties a bin, that card travels back to the feeder process as authorization to make exactly one more bin — the kanban loop. No returned card, no production, however optimistic the plant's forecast might be. The reorder-point variant works the same way without cards: when on-hand brackets fall to a level calculated to cover demand during the replenishment lead time, an order for the fixed lot is released. Because the number of cards in circulation (or the reorder point and lot size) is fixed, the loop caps work-in-process automatically: an upstream planner cannot flood the line with brackets nobody has consumed, and a demand lull simply leaves cards parked instead of piling up stock. The rule ties the feeder's build rate to the line's actual draw.
How it works¶
- Define the trigger. A physical card return, an electronic consumption event, or an on-hand quantity hitting the reorder point — the one thing that authorizes a refill.
- Fix the replenishment quantity. One bin, one container, or one economic lot per trigger, chosen against changeover cost and desired flow.
- Cap the loop. The number of circulating cards (or the reorder point plus lot) sets the buffer's ceiling, so the rule is inherently self-limiting.
- Admit only genuine consumption. Forecasts, tentative demand, and expediting pressure are not valid triggers; only real draw-down releases production.
Tuning parameters¶
- Card count / reorder point — how much buffer the loop tolerates before refilling. Higher protects against stockout and lead-time wobble; lower shrinks inventory but risks starving the point.
- Replenishment lot size — units authorized per trigger. Larger lots amortize changeovers but coarsen flow and enlarge the buffer; smaller lots smooth flow but demand upstream agility.
- Trigger definition — what counts as consumption (a full bin emptied, a single unit withdrawn). Finer triggers respond faster but generate more replenishment signals.
- Safety allowance inside the loop — extra cards held for demand or lead-time variability. More cushions surprises; less exposes the point to stockout.
- Single-card versus two-bin — the physical protocol. Two-bin is simple and robust; single-card systems are leaner but less forgiving of errors.
When it helps, and when it misleads¶
The rule's strength is that it makes the buffer self-maintaining with almost no planning overhead, and it enforces the pull discipline the archetype depends on — it is the just-in-time / kanban[n1] mechanism that keeps forecast error from leaking across the boundary into the buffer. Where demand at the point is reasonably level and replenishment lead time is stable, it is hard to beat.
Its failure mode is that kanban assumes relatively level demand and stable lead times. Under spiky demand or long, erratic replenishment, a fixed-loop rule either starves the point or thrashes, and large lot sizes can amplify variability upstream rather than absorb it. The classic misuse is bigger and more damaging: treating a kanban loop as if it placed the decoupling point. Running pull everywhere without a deliberately designed buffer does not create a boundary — it just relocates the queue and calls it lean. The guarding discipline is to level demand feeding the loop, keep replenishment lead times short, and remember that the rule presupposes a buffer that some other mechanism sized and positioned.
How it implements the components¶
buffer_replenishment_rule— the rule is the refill law: trigger, fixed quantity, and hard ceiling that together govern how the buffer is restocked.pull_signal_contract— the card or reorder trigger defines what counts as a valid pull signal (real consumption) and explicitly bars forecasts and pressure from authorizing production, keeping false demand out of the buffer.
The rule refills the buffer but neither defines nor holds it — the decoupling_buffer and its intermediate_state_specification are the Semi-Finished Goods Buffer's — and it does not create order-specific variety (downstream_order_pull_regime — that is the Configuration Cell or Final Assembly Cell's). Nearest twin is the semi-finished buffer, with which it is routinely conflated: the buffer is the stock sitting at the point; this rule decides when and how much to put back into it.
Related¶
- Instantiates: Push-Pull Decoupling Point Design — the rule is the standing control that keeps the buffer alive between orders.
- Consumes: Semi-Finished Goods Buffer — the rule acts on the stock the buffer holds, keeping it replenished.
- Sibling mechanisms: Configuration Cell or Final Assembly Cell · Customer-Order Decoupling Point Map · Demand Segmentation ABC/XYZ Matrix · Lead-Time / Inventory Trade-off Curve · Make-to-Stock / Make-to-Order Split Policy · Order-Penetration Point Audit · Postponement Strategy Matrix · Sales and Operations Boundary Review · Semi-Finished Goods Buffer
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Kanban or Reorder Replenishment Rule operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it refills the decoupling buffer only on real consumption, tying upstream production to actual draw-down rather than forecast
Independent corroboration: The frozen evidence defines Kanban or Reorder Replenishment Rule as 'Refills the decoupling buffer only on real consumption, tying upstream production to actual draw-down rather than forecast', so its operative form is Control, Automation & Runtime.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Logistics & Supply Chain Management
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Supply-chain and production practice developed replenishment authorization from actual buffer drawdown.
Related originating lineages:
- Operations Research — Inventory-control theory supplied threshold and replenishment-quantity rules.
- Organizational & Management Science — Toyota's lean-management tradition materially shaped kanban as visible pull governance.
Review resolution: Both independent reviews place the primary lineage in logistics_supply_chain. The queued differences (reported_ambiguity, encyclopedia_synthesis_disagreement) concern secondary metadata rather than primary provenance. The final retains operations_research, organizational_management only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=specialized records application breadth separately. encyclopedia_synthesis=true reflects whether either reviewer identified a corpus-specific synthesis, and confidence=high preserves the more cautious evidence assessment.
Attribution caveat: The title intentionally unifies kanban and reorder-point implementations under a pull rule.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Kanban — the just-in-time replenishment signal popularized within the Toyota Production System, in which a card (Japanese for "signboard") returned on consumption authorizes upstream production of a fixed quantity, capping work-in-process and tying build rate to actual draw-down. ↩