E-commerce Across Multiple Warehouses: Stock, Reservations and Allocation

For an e-commerce seller, multi-warehouse typically arrives in three waves: a second self-operated warehouse for faster delivery to another zone; FBA-style stock held in marketplace warehouses; and 3PL fulfilment hubs in different cities. Each adds complexity. Without the right approach, stock visibility breaks down and orders fail. Here is the working method.

What changes vs single warehouse

Three things, all at once:

• Which warehouse fulfils — an order can be served from more than one place; choose deliberately
• Inventory reservation — the same physical stock cannot be allocated to multiple orders across multiple channels
• Per-warehouse vs consolidated visibility — both views matter; both need to be accurate

These are not independent — the allocation rule depends on per-warehouse stock, which depends on reservations, which depend on what's been allocated. The system has to handle the cycle correctly.

The allocation question

When a customer orders, which warehouse fulfils? The rule should be explicit:

• Nearest warehouse to the ship-to address — usually best for shipping cost and delivery time
• Highest-stock warehouse — balances inventory across locations naturally
• Channel-specific routing — Amazon orders always from the FBA stock; Shopify orders from your own warehouse
• Specific warehouse for specific SKUs — large items always from the warehouse with the loading dock
• Override-able default — system default with a manual override for exceptions

For most growing e-commerce businesses, a hybrid is right: a default rule (typically nearest-to-ship-to) with explicit overrides for specific channels or SKUs.

Reservations: the integrity problem

When an order is placed but not yet shipped, the stock allocated to it is reserved — not available to other orders. The classic failure mode without reservations:

• Customer A orders 10 units on Amazon at 11:00
• Customer B orders 10 units on Shopify at 11:01 — system says stock is available
• Customer C orders 10 units on Flipkart at 11:02 — system says stock is available
• Only 12 units actually exist; two of A, B or C will not be fulfilled

Reservations prevent this — but only if every channel respects them in real time. The mechanics:

• Order placed → stock reserved in the chosen warehouse for the SKU
• Reserved stock = total minus reservations = available
• Available is what's shown to all channels
• Order shipped → reservation becomes actual consumption (stock reduces, reservation released)
• Order cancelled → reservation released (no stock movement)

A reservation system with a sync mechanism to all channels is the foundation of multi-warehouse e-commerce.

FBA-style stock in marketplace warehouses

When a marketplace holds your inventory in their warehouses (Amazon's FBA, Flipkart's similar service), you have a unique multi-warehouse situation:

• The marketplace is, in effect, a remote warehouse
• They control the physical inventory
• They report stock levels to you periodically
• Orders on that marketplace ship from their warehouse without your involvement
• Orders on other channels can sometimes still ship from your own warehouse for the same SKU

The accounting needs:

• A separate "FBA Inventory" sub-stock per marketplace — distinct from your own warehouses
• Reconciliation against the marketplace's stock report (typically monthly)
• Inbound flow when you ship stock to the marketplace's warehouse (a stock transfer, not a sale)
• Outbound flow when the marketplace fulfils — they tell you, you book the sale and the stock reduction

Mismatches between your books' FBA stock and the marketplace's report are common: damaged stock, lost stock, returned stock not yet processed. Reconcile monthly.

Shipping origin and GST

For multi-warehouse operations across states, the dispatching warehouse's state determines the place of supply from origin — and therefore whether the transaction is intra-state or inter-state.

A practical example: you have warehouses in Mumbai and Bangalore (different GSTINs). A customer in Pune orders. If you ship from Mumbai (intra-state to Maharashtra), CGST+SGST. If you ship from Bangalore (inter-state to Maharashtra), IGST.

The allocation decision (which warehouse fulfils) has direct GST consequences. Your accounting needs to reflect the actual origin, not a "default origin" assumption.

Per-channel stock reservations vs centralised

Two philosophies on multi-channel + multi-warehouse stock:

Centralised — all stock is one pool; every channel sees the same available number (minus a safety buffer). Simplest, most efficient inventory use, requires reliable sync.

Reserved per channel — stock is virtually split across channels (10 units for Amazon, 5 for Shopify, 5 for Flipkart). Each channel sees only its bucket. No oversells possible; risk of one channel stocking out while another has stock.

For most operations, centralised with a safety buffer is the right default — but for high-stakes channels (your own brand store) sometimes reserving a guaranteed bucket is worth the trade-off.

The visibility dashboard

A working multi-warehouse e-commerce operation needs at minimum:

• Stock by SKU × warehouse — the matrix view
• Reserved vs available per cell
• In-transit between warehouses
• FBA stock separated from own stock
• Days of inventory per warehouse — overstock and understock at a glance
• Allocation log — which warehouse fulfilled which orders, with reasons (for audit and tuning)

Without this view, multi-warehouse decisions are guesswork.

When 3PL fulfilment changes everything

If you outsource fulfilment entirely to a 3PL — they hold your stock, pick, pack and ship — the accounting layer is similar to FBA: their warehouse is a remote location in your books, and reconciliation against their reports is the monthly discipline.

The advantage: their tech stack often handles allocation, reservation and channel sync for you. The cost: less direct control, and you depend on their reports being accurate.

How Booksmor helps

Booksmor handles multi-warehouse e-commerce with per-warehouse stock, real-time reservations across channels, FBA / 3PL stock as separate locations, allocation rules per channel or per SKU, and GSTIN-aware dispatch handling for inter-state shipping. The stock-by-warehouse matrix is one screen. Start a 30-day free trial and run multi-warehouse without the chaos.