UnilyticStop losing rank and revenue to FBA stockouts.
A stockout costs more than the sales you miss that week. Your listing loses velocity, your organic rank slips, and the ad spend you were running against that SKU converts to nothing. Recovering rank afterwards routinely takes longer than the stockout itself. Here is why it keeps happening on Amazon India, and how to make replenishment a decision rather than a guess.
You are probably here because one of these happened.
- A SKU went to zero at a fulfilment centre while you still had plenty of stock sitting in your own warehouse.
- You found out about the stockout from a flat sales chart, not from a warning.
- One fulfilment centre is empty while another holds three months of cover for the same SKU.
- You send round numbers — 100, 200, 500 — because working out the real number per SKU takes too long.
- Your restock decisions live in a spreadsheet that only one person fully understands.
- After a stockout, the listing takes weeks to climb back to where it was.
Why it keeps happening.
Current stock is the wrong signal
Units on hand tells you nothing about how long they will last. Two SKUs with 300 units each are in completely different positions if one sells 4 a day and the other 40. Without sell-through, every restock decision is a guess dressed up as a number.
Inbound stock is invisible
Shipments already in transit are easy to forget, so sellers either double-send and tie up cash, or hold back and stock out anyway. What matters is on-hand plus pending, not on-hand alone.
Lead time gets ignored
The relevant question is not whether you have stock today. It is whether you will have stock on the day the next shipment can realistically arrive and be checked in. Amazon India's receive times vary enough that this gap is where most stockouts are actually born.
Per-warehouse demand differs
Amazon scatters your inventory across fulfilment centres, and demand is not uniform across them. A network-level total hides the specific centre that is about to run dry.
How Unilytic handles it.
Rebuild the real history from your Inventory Ledger
Upload the Inventory Ledger CSV from Seller Central, or connect SP-API and let it sync on a schedule. Unilytic reconstructs the full movement history per SKU, per fulfilment centre, per disposition — the actual record of what moved where, not a snapshot of this morning.
Turn sell-through into days of cover
Every SKU gets a days-of-cover figure from its own sales velocity rather than a shared rule of thumb. The dashboard then splits your catalogue into Out-of-Stock, Low-Stock and Excess, so the SKUs that need attention today separate themselves from the ones that do not.
Count pending shipments as real stock
Future Stock nets on-hand against shipments already in transit, so a SKU with a delivery arriving on Thursday is not flagged as urgent on Wednesday. This is what stops the double-send that quietly eats working capital.
Get an explicit send quantity, not an alert
The output is a number you can act on: this SKU, this many units, this fulfilment centre. Tune days-of-stock-to-send, round-up multiple and minimum out-of-stock quantity to match how you actually ship — carton multiples included.
Be told before it happens
Automated email and Slack alerts fire on low-stock and out-of-stock conditions, so replenishment stops depending on somebody remembering to open a dashboard on a busy morning.
Answered.
How far in advance can I see a stockout coming?
As far ahead as the SKU's own velocity allows. Each SKU shows days of cover based on its recent sell-through, so a product with 9 days left is visible as such today rather than on the morning it hits zero. Set your low-stock threshold to comfortably exceed your usual shipment lead time and the warning always arrives with room to act.
Does this work with just a CSV, or do I need SP-API?
A CSV is enough. Export the Inventory Ledger from Seller Central and upload it — no Amazon connection required. SP-API is optional and only removes the manual export step by syncing on a schedule. The calculations are identical either way.
How does it decide how many units to send?
From your parameters, not a black box. You set the days of stock to send, a round-up multiple so quantities match your carton sizes, and a minimum quantity for out-of-stock SKUs. Unilytic applies those to each SKU's velocity and current position, including stock already in transit. Defaults work out of the box and most sellers tune them within the first week.
I have stock in my own warehouse too. Does that count?
Yes. Local warehouse stock is tracked alongside FBA and netted against pending shipments, so recommendations reflect what you can actually ship rather than treating your own inventory as invisible.
Will this help a listing that already stocked out?
It cannot undo lost rank — nothing can. What it does is stop the repeat. The Analytics warehouse grid shows exactly which fulfilment centres ran dry and when, so the same SKU does not go down the same way next quarter.
Related.
Daily send list
The full mechanics of how send quantities are calculated per SKU and per warehouse.
See the send list FeatureSell-through analytics
30-day SKU history, per-warehouse grids and Future Stock projections.
Explore analytics Use caseMulti-warehouse visibility
When one fulfilment centre is empty and another is overstocked with the same SKU.
Read moreKnow what to ship before you run out.
No card · Built for Amazon India · Email support from the founder.