This has been a constant headache between our ops and supply chain teams, and I’m curious how other Amazon/seller teams handle this.
Our current restock logic is based on:
-
Recent sell-through
-
Historical & YoY sales (ours + competitors)
-
Lead times & transit times
with a typical 1.5x safety stock buffer.
It works fine in steady sales scenarios.
The problem comes when operations ramps promotion aggressively and suddenly:
-
Higher ad spend
-
More deals & promotions
-
Sometimes external traffic / influencers
-
Sales double or spike hard in a short window
Then supply chain can’t keep up:
-
Stock dries up fast
-
Inbound can’t cover the gap
-
Listing rank & weight drop after stockouts
-
Extremely hard to pull back up
This doesn’t feel like a forecasting error — it’s a mismatch between restock rhythm and promotion velocity.
A few questions I’m trying to solve:
- Should restock be tied directly to ops promotion targets, not just historical velocity?
If ops plan to push a SKU hard, they need to provide expected uplift and timeline upfront, so we plan for “promoted sales,” not baseline sales.
-
Is 1.5x safety stock too low for promoted SKUs?
-
Should we cap promotion intensity if inventory / inbound / production can’t support it?
Pushing too hard only to lose ranking due to stockout hurts more in the long run.
- Does anyone use multiple forecast scenarios?
Conservative / base / aggressive — with pre-built restock plans for each.
I’d love real-world input from mature teams:
-
How do you sync operations & supply chain?
-
Is there a mandatory pre-launch/push review process?
-
Do you replenish based on historical sell-through or ops targets?
-
Any proven frameworks or sheet models for sudden demand spikes?
The core conflict at our company:
Ops wants to scale fast, supply chain can’t support it; supply chain plans for steady sales, ops thinks it’s too conservative.
Curious how you structure this to avoid “boom then stockout then crash.”
Answers (5)
The core conflict you described — ops wants to push, supply chain can’t keep up — is usually a negotiation over inventory levels. Sales is the fastest-moving part of the business, so in most setups, ops drives replenishment decisions.
Our process: our ERP pushes replenishment proposals weekly. Ops has to confirm or adjust by a deadline. This forces ops to think about sales forecasts and communicate any changes — especially if they’re planning a BD, off-Amazon push, or ad ramp. If a quantity deviates by more than 20%, we require a reason.
On safety stock: we calculate based on:
The real variable is the sales forecast. If you’re confident, you add more. If not, you keep it tight. Profit margin, category volatility, and product lifecycle all factor in — higher margin, more stable products get larger buffers.
A few thoughts:
On tying restock to ops targets: absolutely. If your target is 500 units, you need 500 units in stock. Stock is ammunition. Doesn’t matter how good your aim is if you run out of bullets.
On the 1.5x multiplier: I think the problem isn’t the multiplier — it’s forecast accuracy. If your forecast is accurate, 1.1x is plenty. If you’re still going out of stock with 1.5x, the forecast itself is off. Running out of stock just means you missed some sales. But overstocking? That’s real money sitting in a warehouse.
On capping promotion intensity: if ops can generate sales, the right answer is fixing supply chain, not slowing down ops. We’re on Amazon to sell. Don’t get it backwards.
On multiple forecast scenarios: you can run three scenarios, but you still have to pick one to execute. What matters more is having contingency plans:
You can’t hit perfect inventory every time. The goal is to avoid major stockouts or major overstocks. Paying a little extra in storage during slow seasons is cheaper than rebuilding momentum after a stockout.
On the core conflict: if ops is selling and making money, the company should be figuring out how to support them, not slowing them down. Keep building supply chain relationships. Over time, suppliers get more flexible.
On tying restock to ops targets: yeah, we do that. Ops fills out a projected sales forecast along a timeline, and we back into the inventory needed (existing + in-transit subtracted). They have to commit to that forecast — once it’s locked, they execute against it.
On the 1.5x rule: I don’t think it’s about the multiplier being too high or low. It’s just a blunt tool. Instead of a flat multiplier, we build in a buffer based on lead time uncertainty — like an extra 15 days of safety stock on a 40-day shipping cycle.
On capping promotion intensity: absolutely. If ops pushes without checking inventory, that’s on them. Avoiding stockouts should be part of ops’ performance metrics. If they see a risk, they need to act to minimize the outage window.
On multiple forecast scenarios: probably overkill. If you’re testing one product it’s fine, but for a portfolio it becomes a mess. Better to build a solid restock logic and focus on getting the forecast right.
How we sync ops and supply chain:ops owns the sales forecast. Supply chain executes against it. That’s the cleanest split.
Pre-launch review: we align on the target ranking and work backward to inventory.
Historical vs ops targets: we restock based on ops targets — but that only works if ops has a track record of accurate forecasting.
On sudden spikes:those are forecast failures on ops’ side. The spike might come from a deal, influencer, or ad push that wasn’t planned. That’s not just a supply chain issue — it’s a process breakdown. We review those cases together and figure out what went wrong.