Inventory Replenishment Planner — example input brief

Purpose: connect replenishment evidence, human review, supply plans, receipts and exceptions.
This is a tutorial input brief, not a complete data export or production dataset.
Project: https://81789a0a2bf14c59bcd21178ce935e5d.prod.enterapp.pro/overview

Input tables: Stores; Products; Inventory; Sales History; Confirmed Inbound; Suppliers; Rules; Recommendations; Plans; Receipts; Exceptions; Users.
Fields: SKU, store_id, on_hand, reserved, confirmed_inbound, daily_sales, cycle_demand, safety_stock, lead_time, reorder_point, pack_size, MOQ, supplier_capacity, unit_cost, budget.
Rules: available = on_hand - reserved; raw_need = max(0, cycle_demand + safety_stock - available - confirmed_inbound). Apply explicit pack, MOQ, capacity and budget constraints. Display every adjustment, not just the final quantity.
Workflow: identify shortage -> explain suggestion and approve -> assign concrete plan -> compare actual receipt and resolve exceptions.
Roles: Inventory Manager approves, Store Operator confirms need and receipt, Procurement coordinates source.

Observed example, 2026-09-11: SKU-06 Bluetooth Speaker at San Francisco Union Square; recommendation rec_mtjifhri_naxoh -> PLN-2026-0001 -> receipt rcpt_01. Available 39, reorder point 60; existing plan 72 units at $3,240; received 42, shortage 30, Avery Chen, exception Open. Use 72 as the existing demo plan, not as proof that every displayed rounding/date rule reconciles.
If additional demo data is needed, generate clearly labelled synthetic records with consistent IDs and dates.