Never stock out. Never overstock. The loop decides when.
Replenishment is event-driven, not calendar-driven. When stock falls below threshold, the replenishment loop fires automatically and opens procurement or transfer action without manual intervention.
Bond Repair Serum
DC-East · LMB-BRS-001
11%
Hydro Boost Mask
DC-West · LMB-HBM-220
28%
Repair Shampoo
DC-Central · LMB-RSH-300
62%
Event-driven
Threshold breach fires the loop - no overnight batch job
Loop-spawning
Replenishment loop auto-creates procurement loop on breach
Transfer-aware
Surplus at one location covers deficit at another before ordering
Thresholds that trigger loops, not emails
Every SKU/location pair has min, max, reorder point, and safety stock controls. When stock crosses reorder, the loop opens automatically so planners are not manually watching dashboards all day. The BRS-001 DC-East scenario shows this flow in action.
- - Min/max and reorder point configurable per SKU per location
- - Safety stock calculated from demand variability and lead time
- - Event trigger generated when reorder point is crossed
- - Loop opens automatically - no manual trigger required
Threshold config · Bond Repair Serum
Min Qty
500
Reorder Point
1,200
Safety Stock
300
Max Qty
5,000
Transfer before ordering?
From: DC-Central · 2,400 units available
To: DC-East · 840 units needed
SKU: Bond Repair Serum (LMB-BRS-001)
Recommended qty: 840 units
Transfer before you order
Replenishment checks network surplus before raising supplier demand. If another location can cover the shortage, the loop creates a transfer recommendation first. Teams can approve manually or auto-approve based on configured trust thresholds.
- - Surplus scan across all locations before procurement loop spawns
- - Transfer recommendation with from/to location, SKU, and quantity
- - Human review or auto-approve based on configured trust level
- - Transfer execution updates both location inventories in real time
Procurement loop spawned automatically
If transfer cannot fully resolve demand, replenishment creates a draft procurement loop with supplier, pack size, and expected dates already populated. Buyers start with a ready PO record, not a request to build one from scratch.
- - Draft PO created in procurement loop with pre-populated line items
- - Preferred supplier and pack size pulled from catalog mapping
- - Expected delivery calculated from supplier lead time
- - Procurement loop inherits audit trail from replenishment trigger event
Draft PO created by replenishment loop
PO: LMB-PO-2026-0015 · DRAFT
Supplier: Lumebonde Manufacturing Co
Line: Bond Repair Serum × 2,000 units · $14,200
Triggered by: threshold_breach_detected · DC-East · 12 Mar 2026
Built for operators
Replenishment is the seam between planning and execution. Demand signals and forecast posture feed threshold controls, then the loop acts autonomously so teams focus on exceptions and approvals rather than manual trigger work.
API and integration
- REST API - threshold configuration, replenishment loop management, transfer recommendation endpoints
- Loop events - scm.replenishment spawns scm.procurement and emits transfer_recommended signals
- Planning integration - inventory planning feeds demand-aware safety stock into threshold configuration
Related modules
Let the loop handle replenishment. You handle exceptions.
Book a 30-minute demo. We will show the threshold-to-PO flow end to end.
Book a demo