Replenishment Report

The Replenishment Report flags every SKU that is at risk of running low at its assigned locations, so you can restock pick faces before they actually go empty. A SKU appears here when its coverage — the on-hand in its Location Profile divided by its recent pick rate — drops below its Replenishment Policy's Trigger DOI (days of inventory), or when it is selling but has no location assigned in the profile yet.

Opening the Report

Navigate to Operations -> Replenishment.

The report is read-only. It shows the latest published snapshot, so the figures you see are exactly what replenishment decisions were last computed against. You can export the current view to CSV or Excel from the Export control.

At least one Replenishment Policy must exist for the selected warehouse, or for an active warehouse when viewing all warehouses, before replenishment results can be built.

Reading the Report

• Status summarizes each SKU's situation:
  • Slot (amber) — the SKU is selling but is not assigned a location in its Location Profile, so it cannot be stocked there yet. A SKU that ships only from reserve appears here only when its Policy's Demand Basis is Overall; see Choosing a Demand Basis.
  • Replenish (red) — the SKU is stocked in the profile but its coverage has fallen below the trigger.
  • OK (green) — the SKU is not flagged for action.
• Insufficient Stock — a badge shown when the stock available elsewhere in the warehouse cannot cover the suggested quantity, so even a perfect move would leave the SKU short.
• DOI, Trigger DOI, and Target DOI show the SKU's current days of inventory and the band its policy targets. Values are the snapshot captured when the index was computed, not live policy settings.
• Qty Outside Profile and Shortfall show how much stock sits outside the chosen locations and how much must move to restore Target DOI.

By default the report shows only flagged SKUs (the Below Trigger DOI filter is set to Yes). Clear that filter, or use the Merchant Filter at the top, to narrow the view to a specific merchant.

Replenishment flags depend on your active Replenishment Policies and their shared Location Profiles — a SKU with no matching policy, no recorded demand on its Policy's Demand Basis, or that Slotting Rules forbid everywhere in the profile, is excluded automatically.

Build Freshness

A chip above the grid reports the state of the warehouse's last build: Ready with the time it finished, Building… while one is running, Build failed, or Not built yet. A requested rebuild is noted alongside it, and the existing rows stay readable until it publishes.

With all warehouses in view, the chip instead counts the warehouses whose results failed, are still building, or were never built. Inactive warehouses are never built, so they are left out of both that count and the rows below; selecting one shows a Warehouse inactive chip in place of a build state.