Just-in-Time Replenishment Rule¶
Procedure — instantiates Inversion of Control
Triggers production or replenishment from actual downstream demand or threshold signals rather than forecast push alone.
A Just-in-Time Replenishment Rule inverts what authorizes a resupply order: not a forecast-driven schedule pushed from planning, but actual consumption crossing a defined threshold. The defining artifact is the reorder point — a specific stock position that, once hit, converts "we just consumed some" into "reorder a fixed quantity now." It is a quantitative decision procedure keyed to a measured position, and that is what sets it apart from a kanban board: kanban is the visible, WIP-limited signaling workflow between stations, while this rule is the arithmetic that decides when the position has fallen far enough to fire a replenishment.
Example¶
A hardware store manages its fastener aisle with a two-bin rule. Each SKU — say, a bin of 8mm bolts — has a front bin customers draw from and a reserve bin sized to cover the supplier's lead time. There is no per-SKU forecast. The rule is simply: when the front bin empties, that empty bin (with its reorder card) goes to purchasing, which is the trigger to order a fixed replenishment lot; staff sell from the reserve while the order is in transit. The reorder point is baked into how the bins are sized — reaching the bottom of the front bin is crossing the threshold.
The outcome is inventory pinned to real sales rather than a planner's guess: fast-moving SKUs reorder often, slow ones rarely, and the reserve absorbs a lead-time spike — with fragility to demand swings as the standing worry.
How it works¶
- Set the reorder point. Compute it as expected demand over the lead time plus a safety-stock cushion for variability.
- Track the position. Monitor on-hand-plus-on-order continuously (or at periodic reviews); consumption is what moves it.
- Fire on the threshold. When the position falls to or below the reorder point, place a replenishment order of a predetermined quantity — no forecast approval needed.
- Hold a cushion. Safety stock and a minimum service level cover the window where demand outruns the signal or the lead time stretches.
Tuning parameters¶
- Reorder point — how high the threshold sits. Higher points cut stockout risk but raise average inventory.
- Order quantity / lot size — how much each trigger orders. Larger lots cut ordering overhead but hold more stock and coarsen responsiveness.
- Safety stock — the cushion above expected lead-time demand. More buffer survives spikes at the cost of carrying inventory.
- Review mode — continuous (order the instant the point is hit) vs. periodic (check on a cadence). Continuous is more responsive; periodic is cheaper to run.
- Lead-time assumption — the demand-over-lead-time estimate the reorder point is built on; underestimating it silently starves the cushion.
When it helps, and when it misleads¶
Its strength is tying supply to demonstrated consumption: inventory shrinks, obsolete stock falls, and each SKU self-adjusts to its own sales without a planner touching it.
Its failure mode is fragility to signal quality. Thin or lagged consumption signals, plus reorder rules that each overreact locally, amplify small demand wobbles into large upstream swings — the bullwhip effect — and a lead-time shock or demand jump the safety stock never anticipated turns into a stockout.[n1] The classic misuse is running pure pull with a starved safety stock in a volatile, long-lead-time supply chain, where the pull signal simply arrives too late to be acted on. The guarding discipline is to size safety stock to real lead-time variance, hold a minimum service level, and blend in a light forecast or smoothing where demand is spiky rather than trusting bare consumption.
How it implements the components¶
pull_rule— downstream consumption, not an upstream plan, authorizes the replenishment order; demand pulls supply.activation_rule— the reorder point is the specific, quantitative threshold that counts as a valid trigger, keeping resupply from firing arbitrarily.context_holder— the on-hand/consumption position is the signal that carries the timing information the forecast lacked; it is the reason to invert.override_or_fallback_path— safety stock, minimum service levels, and expediting handle the cases where the pull signal spikes, lags, or fails, so the system does not depend on a perfect signal.
It does not visualize flow or cap in-flight work with a shared card protocol and a WIP board (feedback_signal, interface_contract, control_boundary) — that is the Kanban Pull System it often rides on; this rule is the reorder-threshold procedure, kanban is the WIP-limited signaling workflow.
Related¶
- Instantiates: Inversion of Control — the demand-driven replenishment form of the inversion.
- Consumes: Kanban Pull System — a returned card or emptied bin is often the concrete pull signal this rule acts on.
- Sibling mechanisms: Kanban Pull System · Dependency Injection Framework · Callback Function · Event Listener or Webhook · Participant Agenda Setting · Learner-Led Inquiry Protocol · Recipient-Triggered Support Channel
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Just-in-Time Replenishment Rule operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it triggers production or replenishment from actual downstream demand or threshold signals rather than forecast push alone
Independent corroboration: The frozen evidence defines Just-in-Time Replenishment Rule as 'Triggers production or replenishment from actual downstream demand or threshold signals rather than forecast push alone', 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: Lean production and supply-chain practice developed consumption-triggered replenishment in place of forecast push.
Related originating lineages:
- Operations Research — Inventory theory supplied reorder-point and fixed-quantity decision rules.
- Organizational & Management Science — Toyota production-system practice materially shaped pull authorization and waste reduction.
Review resolution: Both independent reviews place the primary lineage in logistics_supply_chain. The queued differences (alternate_origin_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=false reflects whether either reviewer identified a corpus-specific synthesis, and confidence=high preserves the more cautious evidence assessment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The bullwhip effect — small fluctuations in end-customer demand amplify into progressively larger swings at each upstream tier, as every stage reacts to its own local order signal. Thin or delayed pull signals and overreactive reorder rules worsen it, which is why safety stock and signal smoothing matter to a just-in-time rule. ↩