How RMS handles the vastly different requirements of stocking a distribution center versus stocking a retail shelf.
Store Replenishment
When RMS replenishes a Store, the goal is simple: ensure the shelf has enough inventory to meet customer demand until the next delivery arrives.
Store replenishment is almost always evaluated daily (subject to review cycles) and relies heavily on exact, granular sales data (e.g., "Store 101 sold 3 units of Item A yesterday").
Sourcing Store Replenishment
When a store needs stock, RMS looks at the Supplier/Sourcing setup to determine where the stock should come from.
- Warehouse Sourcing: The most common. The store needs 10 units; RMS generates an internal Transfer from the primary servicing warehouse to the store.
- Direct to Store Delivery (DSD): For perishable goods (like bread) or highly localized items, RMS generates a Purchase Order directly to the supplier, bypassing the warehouse entirely.
Warehouse Replenishment
Replenishing a Warehouse (or Distribution Center) is vastly different. A warehouse doesn't have "sales" in the traditional sense; its "demand" is entirely driven by the combined demand of all the stores it services.
The Two Methods of DC Replenishment
- Independent Replenishment: The warehouse acts like a giant store. It has its own Min/Max levels based on historical warehouse outbound shipments. When the warehouse stock gets low, RMS cuts a PO.
- Investment Buying / Forward Buying: The warehouse buys in massive bulk ahead of a known price increase or promotional event, intentionally overflowing normal max levels.
The Bullwhip Effect
If warehouse replenishment isn't perfectly tuned to store demand, retailers suffer from the Bullwhip Effect—where tiny fluctuations in store sales cause massive over-ordering at the warehouse level.
Flow-Through & Cross-Docking
The holy grail of modern retail supply chain is minimizing the time inventory spends sitting in a warehouse. RMS supports two primary methods to achieve this:
1. Cross-Docking (XD)
In a pure cross-dock scenario, the warehouse never holds the inventory.
- RMS evaluates that Stores A, B, and C need a total of 1,000 units.
- RMS cuts a single PO to the supplier for 1,000 units, but it includes an Allocation Directive.
- The supplier pre-packs the boxes specifically for Stores A, B, and C.
- When the truck arrives at the warehouse, the warehouse workers simply move the boxes from the inbound dock straight to the outbound trucks for Stores A, B, and C. The stock never hits the warehouse stock ledger as "available".
2. Flow-Through
Similar to cross-docking, but the supplier delivers in bulk (not pre-packed for stores). The warehouse workers must open the bulk pallets and break them down into store-level shipments immediately on the dock, then put them on the outbound trucks.
The Role of Allocations
When replenishing stores from a warehouse, what happens if the warehouse only has 500 units, but the combined store demand is 1,000 units?
RMS uses the Allocation engine (often tightly coupled with Oracle Retail Allocation) to determine who gets the limited stock.
- Does every store get 50% of what they asked for?
- Do top-tier stores get 100% and bottom-tier stores get 0%?
- Are priority backorders fulfilled first?
The replenishment batch generates the need, but the Allocation module dictates the distribution rules when scarcity occurs.
Key Takeaways
- Store replenishment focuses on precise shelf-level inventory via Transfers or DSD.
- Warehouse replenishment aggregates demand and generates bulk Purchase Orders.
- Cross-docking and Flow-through minimize warehouse holding times by routing stock directly from receiving to shipping.
- When warehouse stock is insufficient to meet store demand, Allocation rules determine the priority of distribution.
