Reorder point and days of cover for Amazon FBA
When to create the next FBA shipment and how many units to send: the four numbers you need, the formulas, and the velocity mistakes that cause repeat stockouts.
- Your Inventory Ledger, or a sales and stock export per fulfilment centre
- Dates of your last few inbound shipments
- A spreadsheet
- About 20 minutes for the first SKU
The four numbers
Every replenishment decision for an FBA product comes down to four numbers, for one SKU at one fulfilment centre:
Scroll the table sideways for the remaining columns.
| Number | What it is | Where it comes from |
|---|---|---|
| Daily velocity | Units sold per day | Customer shipments in the Inventory Ledger, over a window you choose |
| On hand | Sellable units at that centre now | The ledger's ending balance for the SELLABLE disposition |
| On the way | Units already shipped in but not yet sellable | Your open inbound shipments |
| Lead time | Days from creating a shipment to units being sellable | Your own past shipments |
Everything else is arithmetic on those four:
daily velocity = units sold in window ÷ days in window
days of cover = sellable units on hand ÷ daily velocity
reorder point = daily velocity × (lead time + safety days)
units to send = daily velocity × (lead time + target cover days)
− (units on hand + units already on the way)Every number in the worked examples below is illustrative, chosen so the sums are easy to follow.
Days of cover
Days of cover answers "how long until this runs out?" A SKU with 60 sellable units that sells 4 a day has 15 days of cover. It is the single most useful number on a stock report, because it puts a fast seller with 200 units and a slow one with 20 on the same scale.
One edge case matters. A SKU that sold nothing in the window has no days of cover - not infinite cover. Dividing by zero sales and reporting "999 days" makes a dead SKU look like your healthiest one. Treat zero-sales SKUs as their own list: they are candidates for removal, not for replenishment.
The reorder point
The reorder point is the stock level at which you create the next shipment. It has to cover what you will sell while that shipment is on its way, plus a buffer for the days when sales run hot or the shipment runs late:
reorder point = velocity × (lead time + safety days)
= 4 × (14 + 5)
= 76 unitsScroll the diagram sideways to see all of it.
Compare stock plus units on the way with the reorder point, not stock alone. Otherwise you will create a second shipment while the first is still in transit.
How much to send
The reorder point tells you when. The quantity comes from how many days of stock you want to have when the shipment lands - the target cover. You will keep selling while it travels, so the lead time goes in too:
units to send = velocity × (lead time + target cover)
− (on hand + on the way)
= 4 × (14 + 30) − (76 + 0)
= 100 unitsSent at the reorder point in the chart above, those 100 units land when 20 are left, which takes stock to 120 - exactly 30 days of cover at 4 a day.
The target is a trade-off. Longer cover means fewer, larger shipments and less risk of running out; it also means more stock sitting in the fulfilment centre collecting storage fees, and more exposed if demand drops. Unilytic's send list defaults to 30 days of cover and flags stock as excess beyond 45 - starting points to tune, not rules. One difference to know: it counts that target from today rather than from arrival, and recalculates every time your ledger syncs, so it suits topping up little and often. If you ship less often, set a longer target.
Running out costs you sales you never get back. Overstocking costs you rent.
Getting velocity right
Velocity is where most replenishment maths quietly goes wrong.
Scroll the table sideways for the remaining columns.
| Problem | What happens | What to do |
|---|---|---|
| Window too short | One good weekend doubles the velocity and you over-send | Use enough days to smooth out single spikes |
| Window too long | A product that is taking off still looks slow | Compare the latest period with the one before it |
| Stockout inside the window | Days with no stock sold nothing, so velocity reads low and you send too little - which causes the next stockout | Count only the days the SKU was in stock |
| Sale events | A festival sale inflates the window and the next order is too big | Plan sale-period stock separately, from the same period last year |
The third row is the one that catches people. A SKU that was out of stock for ten days of a thirty-day window shows two-thirds of its real velocity, so the next shipment is two-thirds of what it should be, so it runs out again. If a SKU keeps running out no matter what you send, check this first.
Per fulfilment centre, not per country
FBA stock in India does not sit in one place. In one seller's ledger, stock and sales touched 31 different fulfilment-centre codes in three months. A national total can show a comfortable 40 days of cover while the centre serving one region is empty.
So run every calculation above per centre: velocity from that centre's shipments, stock from that centre's sellable balance, and a send quantity for that centre. The Inventory Ledger guide explains how to pull stock and sales per centre from the Summary view.
Measuring your lead time
Lead time is the number most sellers guess, and the one that moves the reorder point most. Measure it from your own last several shipments: the day you created the shipment to the day its units became sellable. It is made of:
- packing and labelling at your end,
- transit to the fulfilment centre,
- waiting for the centre to receive the shipment, and
- receiving and checking the units in until they show as sellable.
Use a typical recent figure, not your best one. The last two steps are outside your control and vary by centre and by season, so a lead time that was right in a quiet month can be a week short in a busy one. Unilytic's Ship Now screen assumes 14 days until you change it.
The send list, worked out for you
Unilytic runs this arithmetic on your Inventory Ledger each time it syncs, per fulfilment centre, and turns it into a ranked send list: which centres to ship to first, which SKUs, and how many units - counting stock already on the way.

See it on your own data without signing up: preview your send list. The full feature is replenishment send list.
Questions sellers ask
How do I calculate the reorder point for an Amazon FBA product?
Multiply the product's daily sales velocity by your lead time plus a few days of safety stock. For example, a SKU selling 4 units a day with a 14-day lead time and 5 safety days has a reorder point of 4 × 19 = 76 units. When sellable stock plus stock already on the way falls to 76, create the next shipment.
What does days of cover mean?
Days of cover is how long your current sellable stock will last at the current rate of sales: units on hand divided by units sold per day. 60 units selling 4 a day is 15 days of cover. A SKU with no sales has no meaningful days of cover - it is not infinite, it is undefined.
How many units should I send to Amazon FBA?
Decide how many days of stock you want to have when the shipment lands, add your lead time, multiply by daily velocity, and subtract what is already on hand and on the way. With 4 units a day, a 14-day lead time, a 30-day target, 76 units on hand and nothing in transit, that is 4 × (14 + 30) − 76 = 100 units - which lands when 20 are left and takes you to 120, or 30 days of cover.
What lead time should I use for FBA replenishment?
Your own, measured: the time from creating a shipment to the units being sellable at the fulfilment centre, taken from your last several shipments. It includes packing, transit, waiting to be received and receiving. Use a typical recent figure, not your fastest one.
Should I calculate stock per fulfilment centre or for the whole country?
Per fulfilment centre. FBA stock in India is spread across many centres, so a SKU can have plenty of stock in total and none at the centre that serves a particular region. Calculate days of cover and send quantities for each centre separately.
How to read the Amazon Inventory Ledger
The bank statement for your FBA stock: the two views, the columns and event types, how to reconcile a SKU, and the three traps that make stock look lost when it is not.
Reimbursements & claimsFBA reimbursements in India
Amazon now pays some losses without a case - but its report only shows what it paid, never what it missed. How to read the reimbursement report, what Amazon pays for a lost unit, and how to find what is still owed.