UnilyticLead time is a dial
Lead time decides which SKUs are even at risk. Change it on the page — from a 14-day default — and the whole ranking recomputes, so you can see what a slower supplier would do to your week.
Prioritise
One shipment first. This one.
Knowing forty SKUs are low is not the same as knowing what to do this morning. Ship Now ranks your warehouse groups by what it costs you, in rupees per day, to keep waiting — so the shipment you build first is the one that is actually bleeding.
Ranked in ₹/dayGrouped by regionOne suggested FCBlocked items separated
A number, not a feeling
What does waiting actually cost?
If a SKU has fewer days of cover than your lead time, that location runs dry before any shipment can land — and every extra day of delay costs you the units you would have sold times what you net on each one. Unilytic computes that marginal cost per SKU and adds it up per warehouse group, because the cost is additive. That total is the ranking. It is a real number in rupees, so a shipment of cheap fast movers can legitimately outrank a shipment of expensive slow ones.
- ₹/day at risk is the sort key — the cost of one more day of delay.
- Demand is not under-counted. A SKU that has been starved looks slow, so Unilytic uses the higher of its engine velocity and its 90-day sells-when-in-stock rate.
- Loss-making SKUs are flagged rather than ranked — if a unit earns nothing, rushing it in earns nothing.
Ship to a region, not a pin
Group your FCs the way you actually ship.
Amazon scatters your stock across fulfilment centres, but you do not build a separate shipment for each one. Group the FCs you treat as a single destination — your southern cluster, your western cluster — and Ship Now ranks the groups, names every FC inside each one, and rings the single warehouse to actually send to. Two problems get pulled out of the ranking entirely: SKUs you cannot replenish because your own stock is out, and SKUs that another group already has too much of.
- One suggested destination per group, with every member FC listed.
- Transfer, don't buy — SKUs covered by excess elsewhere are tagged to move instead.
- Blocked items are separated, so a supply problem never masquerades as a shipping decision.
In the product
This is the actual screen.
Captured from a live Unilytic workspace — not a mockup, and not a roadmap promise.
Controls
Tuned to how you buy.
The ranking changes with your lead time and your assortment, so both are controls on the page rather than settings buried in a menu.
Filter to the assortment you buy
Narrow to the categories you are actually placing an order for, and pick the sales window the velocity is read from. The ranking answers the question you are holding, not a general one.
It tells you when it is guessing
The money side needs fee data. When Unilytic is working from estimated fees or listing prices rather than actual Amazon figures, it says so on the page instead of quietly presenting a weaker number as a firm one.
Why this matters
Every replenishment tool gives you a list. A list has no order.
On any given Monday a dozen SKUs across four fulfilment centres will all be below threshold. You cannot build a dozen shipments, so you pick — usually by whichever name you recognise, or whichever number looks biggest. But the biggest shortfall is not the most expensive one: a slow SKU that is 400 units short can matter far less than a fast one that is 40 short, and a stockout at the FC serving your densest region costs more than the same stockout somewhere quiet. Ranking by rupees per day makes that comparison explicit instead of instinctive.
The first decision of the day is made
Open the page and the shipment worth building is already at the top, with a number attached.
Stock you already own gets used
Transfers are surfaced separately from purchases, so excess in one region can cover a gap in another.
Starved SKUs stop being invisible
Demand is read from how a SKU sells when it is actually in stock, not from a period when it wasn't.
Common seller mistakes
- Ranking by units short instead of money at stakeUnit gaps say nothing about velocity or margin. The SKU with the largest shortfall is frequently not the one costing you the most today.
- Judging demand by recent sales aloneA SKU that has been out of stock for three weeks sold almost nothing — which makes it look slow, so it gets deprioritised, so it stays out. The starvation becomes self-confirming.
- Buying more of something you already have too much ofExcess sitting in your western cluster does not show up when you are looking at a shortfall in the south. So you purchase stock you already own.
- Treating an out-of-stock supplier as a shipping problemIf your own stock is gone, no amount of shipment planning helps. Mixed into the same list, those SKUs just add noise to a decision they cannot inform.
Questions
Shipment priority, answered.
Which FBA shipment should I send first?01
Ship Now answers this directly. It ranks your warehouse groups by the rupees per day you lose while a needed shipment waits — computed per SKU as the units you would sell times what you net on each, summed across the group. The group at the top is the shipment to build first.
How is the cost of waiting calculated?02
For every SKU and group, if days of cover is less than your lead time, that location runs dry before a shipment can arrive. Each additional day of delay then costs the daily sales rate times the net proceeds per unit. Unilytic sums that across the group, so the score is additive and directly comparable between groups.
Can I set my own lead time?03
Yes. Lead time defaults to 14 days and is adjustable on the page itself, so you can see immediately how a slower or faster supplier changes what is urgent. Your organisation's saved default is used when you have not overridden it.
What if I have excess stock in another region?04
Those SKUs are tagged as transfers rather than counted as things to purchase, so you can move stock you already own instead of buying more of it.
What happens to SKUs I cannot restock right now?05
If a SKU is marked out of stock in your Local Stock, it moves into a separate Blocked section instead of sitting in the ranking. It is a supply problem, not a shipment decision, and keeping the two apart stops one from hiding the other.
Do I have to group my fulfilment centres first?06
For a useful ranking, yes. An ungrouped FC is treated as its own group, which works but overstates risk by splitting one real shipment into several. Unilytic prompts you to group co-located FCs the first time you open the page.
Explore more
Keep going.
Plan
Back to all featuresReplenishment & send list
Where the per-SKU quantities come from — a tunable formula over your Inventory Ledger.
Know what to ship InventoryMulti-warehouse inventory
The warehouse groups and local-stock netting that Ship Now ranks on top of.
See every location AutomationAmazon sync & automation
The nightly SP-API sync that keeps the ranking current without you uploading anything.
Put it on autopilotGet started
Stop guessing which shipment goes out first.
No card · Built for Amazon India · Email support from the founder.