Group FCs into regions
Bundle the fulfilment centres you treat as a single destination into a named group. Shipment priority then ranks regions rather than individual pins — which is how you actually build a shipment.
Amazon scatters your inventory across fulfilment centres, then reports it back as one national number. That number is precisely what hides your stockouts. Unilytic keeps every FC and every one of your own locations separate, with each disposition counted honestly — so no warehouse starves while another overflows.
Unilytic reads your ledger at its real grain — one row per date, location, disposition and SKU — so a fulfilment centre is never averaged away. Your own warehouses sit in the same picture through Local Stock, which records what you are actually holding and which SKUs you cannot currently supply at all. Mark a SKU as locally out of stock and you can hide it from the inventory tables in one click, so the list in front of you contains only things you can genuinely act on.
The ledger separates sellable units from defective, customer-damaged, carrier-damaged, warehouse-damaged and distributor-damaged ones, and Unilytic keeps that separation all the way through. It sounds obvious, but a SKU showing twenty-eight units at a fulfilment centre where every last one is damaged is a stockout wearing a disguise — and a single total-inventory figure will never tell you. Those damaged units are not lost either: they are exactly what reimbursement tracking looks at.
Bundle the fulfilment centres you treat as a single destination into a named group. Shipment priority then ranks regions rather than individual pins — which is how you actually build a shipment.
When one region is long on a SKU another is short of, that is a transfer, not a purchase order. Unilytic surfaces it as one, so you use stock you have already paid for.
Every plan caps how many distinct warehouses it tracks. Reach the cap and Unilytic asks which locations matter to you, rather than silently dropping data or refusing the upload.
Suppose you hold 700 units of a SKU nationally and sell twenty a day. That reads as a comfortable month of cover. But if 640 of them sit in one northern fulfilment centre and the south is empty, then for every customer the southern FC serves you are out of stock right now — losing the sale and the search position that came with it, while the report on your screen says everything is fine. This is the most expensive blind spot in FBA inventory management, and it is invisible by construction unless something holds the locations apart.
A warehouse here means a distinct Amazon location code, not a building you operate. Amazon scatters stock automatically, so that count grows on its own — the caps are set with that in mind.
Scroll the table sideways for the remaining columns.
| Free | Pro | Business | |
|---|---|---|---|
| Distinct warehouses | 15 | 40 | Unlimited |
| Distinct SKUs | 50 | 1,500 | 10,000 |
| Inventory rows | 25,000 | 1,000,000 | 5,000,000 |
| Per-warehouse send quantities | Included | Included | Included |
| Local Stock & vendor returns | Included | Included | Included |
Unilytic keeps a separate position for every Amazon fulfilment centre in your ledger, using the location codes Amazon already assigns. Cover, low-stock status and send quantities are all computed per location, so a surplus in one region can never disguise a stockout in another. You can also group co-located FCs into named regions and plan shipments the way you actually send them.
Yes. Local Stock records what you hold in your own depots or factory, in the same workspace as your FBA positions. You can also mark SKUs you cannot currently supply, and hide those rows from the inventory tables so the list only shows things you can act on.
No. The ledger separates sellable stock from defective, customer-damaged, carrier-damaged, warehouse-damaged and distributor-damaged units, and Unilytic preserves that separation. Damaged units feed reimbursement tracking, where they may be worth filing a claim on, rather than inflating what looks available.
Free tracks 15 distinct locations, Pro 40, and Business is unlimited. A warehouse means a distinct Amazon location code rather than a building you operate, and because Amazon scatters stock automatically that count rises on its own. If you reach the cap, Unilytic asks you to choose which locations to keep tracking instead of dropping data without telling you.
That is surfaced as a transfer rather than a purchase. Shipment priority tags SKUs already covered by excess in another group, so you move stock you own instead of buying more of it.
Warehouse groups ranked by what it costs per day to leave each one short.
Rank by ₹/day PlanPer-SKU, per-warehouse quantities from a formula you set yourself.
Know what to ship WarehouseScan returns into your own depot and grade every unit as it arrives.
Process returnsNo card · Built for Amazon India · Email support from the founder.