All retail examples
Store replenishment exceptions
Flags the store and SKU combinations at risk of stockout or overstock, recommends a transfer, expedite, substitute or hold, and asks the planner to approve it.
The operation
Show planners the store/SKU replenishment exceptions that need a decision, with transfer, expedite, substitute, or hold recommendations from demand, DC, transfer, carrier, and store signals.
Built it in 4 steps. The planner approves the move in Slack, and Malleable handles the rest.
Starts when
Scheduled replenishment scan or low-stock alert
Trigger
Spot Risk
Identify store/SKU combinations at risk of stockout or overstock.
Looker
Flags store/SKU combinations at replenishment risk.
Check Availability
Review DC inventory, transfers, shipments, and local constraints.
NetSuite
Checks DC inventory, transfers, and local stock constraints.
project44
Checks carrier status for transfers and inbound shipments.
Recommend Move
Propose transfer, expedite, substitute, or hold with rationale.
Planner Review
Needs input
Ask planner to approve action and notify affected stores.
Slack
Sends the replenishment action request to the planner.
Spotting SKU and store replenishment risk...
Step by step
- 1Spot Risk: Identify store/SKU combinations at risk of stockout or overstock.
- 2Check Availability: Review DC inventory, transfers, shipments, and local constraints.
- 3Recommend Move: Propose transfer, expedite, substitute, or hold with rationale.
- 4Planner Review: Ask planner to approve action and notify affected stores.
What the team gets
- Replenishment focuses on exceptions
- Transfers use current logistics reality
- Store risk is visible before stockout
Apps it uses
Want to see one of your processes run like this?
Book a demo and bring the process you have in mind.
Book a demo