Once you are shipping from more than one location — a primary warehouse plus a marketplace fulfilment hub, a second city for faster delivery, or separate stock for online and offline channels — multi-warehouse stock management stops being a spreadsheet problem and becomes an operational one. Stock that looks available in your combined total can be sitting in the wrong city when an order comes in, and a transfer between your own locations can carry GST implications you do not expect.
This guide covers how to structure warehouses, move stock between them correctly, keep reorder levels location-aware, and avoid the mistakes that show up most often once a business crosses from one warehouse to several.
Why Stock Across Locations Gets Complicated Fast
With a single warehouse, "available stock" is one number. With multiple warehouses, you need available-per-location, in-transit quantities between locations, and a rule for which warehouse fulfils which order. Get any of these wrong and you will oversell from a location that is actually empty, or under-utilise a warehouse that is fully stocked while another runs out.
The problem compounds with marketplace selling: Amazon, Flipkart, Meesho and similar platforms may fulfil orders from your own warehouse, from a marketplace-owned fulfilment centre, or a mix — meaning your single source of truth for stock now spans systems you do not fully control.
Structuring Warehouses and Locations Correctly
Before worrying about transfers or reorder logic, get the setup right:
- Treat each physical location — including a marketplace fulfilment centre where your stock physically sits — as a distinct warehouse in your records, not a sub-note under one combined total.
- Use one item master across all warehouses so a SKU means the same product everywhere, with warehouse-wise stock quantities layered on top rather than separate item lists per location.
- Record the GSTIN each warehouse operates under. If warehouses sit in different states, they will typically be registered under different GSTINs, which affects how a stock movement between them is treated.
- Name locations consistently (a short code plus city, for example WH-BLR-01) so reports and order-routing rules stay unambiguous as you add more.
Recording Stock Transfers Between Warehouses
The Transfer Workflow
A clean transfer has three states: dispatched from the source warehouse, in-transit, and received at the destination. Recording only "moved" as a single instant step hides discrepancies — if 100 units leave one warehouse and only 97 are recorded as received, you want that gap visible rather than silently absorbed into one location's stock count.
Generate a delivery challan or transfer document for every inter-warehouse movement, even between your own locations, so there is a paper trail matching physical movement to the stock ledger.
GST on Stock Transfers Between Your Own Locations
This is the part sellers most often get wrong. If two warehouses are registered under the same GSTIN (same state, same legal entity), an internal stock transfer is generally not a taxable supply — it is just a movement of your own goods. But if the warehouses are under different GSTINs (typically different states, or separate registrations for the same state), the transfer can be treated as a supply between "distinct persons" under GST, which may require an invoice and applicable tax, with input tax credit generally available at the receiving end.
Rules and valuation for such transfers can be detailed and do change, so treat this as a general pointer rather than a final answer — verify the current position with your GST practitioner or through support, and check the official GST portal (www.gst.gov.in) before relying on it for a transfer of material value.
Warehouse-Wise Reorder Levels
A single reorder point across your combined stock does not work once you have multiple locations — a warehouse can hit zero while your total still looks healthy. Set a minimum stock level per SKU per warehouse, based on that location's own sales velocity and lead time from its usual supplier or transfer source.
| Warehouse | Typical Daily Sales (SKU X) | Supplier Lead Time | Suggested Reorder Level |
|---|---|---|---|
| Mumbai (WH-BOM-01) | 40 units | 4 days | 200 units |
| Bengaluru (WH-BLR-01) | 25 units | 6 days | 180 units |
| Delhi (WH-DEL-01) | 55 units | 3 days | 200 units |
Reorder level here is a simple buffer: daily sales × lead time, plus a safety margin for demand spikes. Revisit these numbers every quarter or after a seasonal spike — a static reorder level set once during setup tends to go stale.
Routing Orders to the Right Warehouse
When an order comes in — whether from your own storefront or a marketplace — it should be allocated to a warehouse based on stock availability at that location first, then proximity to the delivery address to control shipping cost and time, and finally any channel-specific rule, such as marketplace-fulfilled orders that must ship from a designated fulfilment centre regardless of your other stock levels.
Common Multi-Warehouse Problems and How to Fix Them
| Problem | Likely Cause | Fix |
|---|---|---|
| Oversold at one location while another has stock | No warehouse-wise availability check at order time | Route orders against per-location stock, not the combined total |
| Stock count drifts from physical count | Transfers recorded late or not at all | Log every dispatch and receipt immediately; reconcile monthly |
| Duplicate SKUs per warehouse | Location-specific item lists instead of one shared item master | Standardise to a single item master with warehouse-level quantities |
| Confusion over GST on transfers | Same-GSTIN and cross-GSTIN transfers treated identically | Flag each transfer as intra-GSTIN or inter-GSTIN and apply the correct treatment |
| Reorder alerts arriving too late | One combined reorder level for all locations | Set per-warehouse reorder levels based on that location's own velocity and lead time |
A Practical Multi-Warehouse Checklist
- Every warehouse recorded with its own code, address and GSTIN.
- One item master shared across all locations; no duplicate SKUs per warehouse.
- Every inter-warehouse movement logged with a document, not just a stock count adjustment.
- Cross-GSTIN transfers reviewed for GST treatment before they become routine.
- Reorder levels set per SKU per warehouse and revisited quarterly.
- A monthly physical stock count reconciled against system quantities per location.
Where OneBooks GST Is Headed on Multi-Warehouse Inventory
Multi-warehouse stock ledgers, transfer documents and location-wise reorder alerts are part of the inventory capability planned for OneBooks GST, building on the multi-organisation and multi-GSTIN structure already supported for GST filing today. You can see the current state of GST and marketplace features on the inventory software page, and read more about how the roadmap connects to GST filing across locations in our guide on the OneBooks GST inventory roadmap.
If you are valuing stock across these warehouses too, see our comparison of FIFO versus weighted average valuation, and for the tax treatment of movement across states, our guide to place of supply rules under GST.
Frequently asked questions
Is a stock transfer between my own warehouses always GST-exempt?
Not always. It generally is not taxable when both warehouses share the same GSTIN. When they are registered under different GSTINs, commonly because they are in different states, the transfer can be treated as a supply between distinct persons and may need an invoice and applicable tax. Confirm the current treatment for your situation with your GST practitioner.
How many warehouses can I manage before I need dedicated software?
There is no fixed number, but once you are juggling more than two or three locations, or splitting stock across your own warehouse and marketplace fulfilment centres, manually reconciling spreadsheets typically becomes error-prone enough that a shared item master with per-location tracking pays for itself quickly.
Should marketplace fulfilment centres count as a separate warehouse in my records?
Yes. If your stock physically sits at an Amazon, Flipkart or similar fulfilment centre, treat it as its own location in your stock records, since it has its own available quantity, its own state and GSTIN implications, and its own replenishment lead time.
How often should I do a physical stock count per warehouse?
A monthly reconciliation per location is a reasonable baseline for most businesses, with more frequent counts for high-value or fast-moving SKUs. The key is consistency, since irregular counts make it hard to tell whether a discrepancy is new or has been accumulating for months.
What is the biggest mistake businesses make when they add a second warehouse?
Continuing to track stock as one combined number instead of splitting it per location. This hides the fact that one warehouse can be out of stock while your total still looks fine, leading to overselling and delayed fulfilment.
