This guide walks through the real decision points: when a second warehouse is actually justified, what it costs against a 3PL, the GST rules nobody explains clearly, how to handle COD and returns once stock sits in two places, and the routing math that makes or breaks the whole setup.<\/p>\n\n\n\n
Multi-Warehouse Inventory Management at a Glance<\/strong><\/h2>\n\n\n\n\n- Centralized Control:<\/strong> Track stock across every warehouse from one dashboard, with reorder points set per location based on regional RTO rates, not just demand.<\/li>\n\n\n\n
- GST-Compliant Transfers:<\/strong> Movement of goods valued above Rs 50,000 between your own warehouses generally requires an e-way bill, unless a specific GST exemption applies.<\/li>\n\n\n\n
- COD-Aware Routing:<\/strong> Route returns to the nearest warehouse and reconcile COD cash against the shipping warehouse separately, so cash and stock don’t get mixed up across locations.<\/li>\n\n\n\n
- Cost-Based Model Choice:<\/strong> Many growing sellers start with a 3PL to limit upfront investment, then evaluate owned warehousing once volume, rent, and labour costs make it the cheaper option long-term.<\/li>\n<\/ul>\n\n\n\n
When You Actually Need a Second Warehouse<\/strong><\/h2>\n\n\n\nYou need a second warehouse<\/a> when your data shows a regional problem, not a general growth feeling.<\/p>\n\n\n\n![\"When](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01143622\/When-You-Actually-Need-a-Second-Warehouse.webp\")
<\/figure>\n\n\n\nThree signals matter more than revenue targets, and one cheaper fix is worth ruling out first.<\/p>\n\n\n\n
Check if you’ve actually outgrown the space you have<\/strong><\/h3>\n\n\n\nBefore you sign a new lease, look at whether better racking or a tighter inventory layout inside your current warehouse<\/a> solves the problem.<\/p>\n\n\n\nA lot of “we need a second warehouse” conversations are really “our shelving is inefficient” conversations. This costs a weekend of reorganizing instead of months of new setup.<\/p>\n\n\n\n
RTO concentration in one zone<\/strong><\/h3>\n\n\n\nIf RTO rates in a specific state or cluster of pincodes run well above your national average, distance is often the cause.<\/p>\n\n\n\n
A warehouse closer to that demand cuts transit time and gives the customer less time to change their mind before the order arrives.<\/p>\n\n\n\n
SLA breaches by pincode cluster<\/strong><\/h3>\n\n\n\nPull your delivery performance by pincode group, not by city. If one cluster consistently misses your promised delivery window while others don’t, one warehouse is serving too wide a radius.<\/p>\n\n\n\n
This is the same pattern any fulfillment team recognizes: a two-day promise that quietly slips to four or five days for one part of the country is a warehouse-placement problem, not a courier problem.<\/p>\n\n\n\n
Order concentration outside your warehouse’s efficient range<\/strong><\/h3>\n\n\n\nIf 30% or more of your order volume comes from a region more than two days’ transit from your current warehouse, you’re paying a structural shipping cost every single day.<\/p>\n\n\n\n
A second warehouse converts that recurring cost into a one-time setup cost.<\/p>\n\n\n\n
None of these signals need to hit at once. Even one, sustained over two or three months, is a stronger case for expansion than “we’re growing so we should probably get another warehouse.”<\/p>\n\n\n\n
Owned Warehouse vs 3PL vs Hybrid: A Cost Threshold Framework<\/strong><\/h2>\n\n\n\nMulti-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n![\"Owned](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01143742\/Owned-Warehouse-vs-3PL-vs-Hybrid-A-Cost-Threshold-Framework.webp\")
<\/figure>\n\n\n\nThere’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\nmany growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n
3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n
Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\nThis is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n
An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\nOwned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n
One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n
Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\nMoving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n![\"The](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01144238\/The-GST-Side-of-Inter-Warehouse-Transfers.webp\")
<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\nIn general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n
This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\nIf both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n
If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n
It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\nMaintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n
Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n
It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n
Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\nManaging inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n![\"\"](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01144312\/Handling-COD-and-RTO-Across-Multiple-Warehouses.webp\")
<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\nBefore an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n
This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n
It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\nA customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\nWithout a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\nRoute RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n
Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\nCOD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\nGetting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n
Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n
When You Actually Need a Second Warehouse<\/strong><\/h2>\n\n\n\nYou need a second warehouse<\/a> when your data shows a regional problem, not a general growth feeling.<\/p>\n\n\n\n<\/figure>\n\n\n\nThree signals matter more than revenue targets, and one cheaper fix is worth ruling out first.<\/p>\n\n\n\n
Check if you’ve actually outgrown the space you have<\/strong><\/h3>\n\n\n\nBefore you sign a new lease, look at whether better racking or a tighter inventory layout inside your current warehouse<\/a> solves the problem.<\/p>\n\n\n\nA lot of “we need a second warehouse” conversations are really “our shelving is inefficient” conversations. This costs a weekend of reorganizing instead of months of new setup.<\/p>\n\n\n\n
RTO concentration in one zone<\/strong><\/h3>\n\n\n\nIf RTO rates in a specific state or cluster of pincodes run well above your national average, distance is often the cause.<\/p>\n\n\n\n
A warehouse closer to that demand cuts transit time and gives the customer less time to change their mind before the order arrives.<\/p>\n\n\n\n
SLA breaches by pincode cluster<\/strong><\/h3>\n\n\n\nPull your delivery performance by pincode group, not by city. If one cluster consistently misses your promised delivery window while others don’t, one warehouse is serving too wide a radius.<\/p>\n\n\n\n
This is the same pattern any fulfillment team recognizes: a two-day promise that quietly slips to four or five days for one part of the country is a warehouse-placement problem, not a courier problem.<\/p>\n\n\n\n
Order concentration outside your warehouse’s efficient range<\/strong><\/h3>\n\n\n\nIf 30% or more of your order volume comes from a region more than two days’ transit from your current warehouse, you’re paying a structural shipping cost every single day.<\/p>\n\n\n\n
A second warehouse converts that recurring cost into a one-time setup cost.<\/p>\n\n\n\n
None of these signals need to hit at once. Even one, sustained over two or three months, is a stronger case for expansion than “we’re growing so we should probably get another warehouse.”<\/p>\n\n\n\n
Owned Warehouse vs 3PL vs Hybrid: A Cost Threshold Framework<\/strong><\/h2>\n\n\n\nMulti-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n<\/figure>\n\n\n\nThere’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\nmany growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n
3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n
Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\nThis is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n
An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\nOwned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n
One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n
Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\nMoving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\nIn general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n
This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\nIf both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n
If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n
It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\nMaintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n
Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n
It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n
Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\nManaging inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\nBefore an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n
This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n
It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\nA customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\nWithout a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\nRoute RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n
Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\nCOD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\nGetting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n
Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n
<\/figure>\n\n\n\nThree signals matter more than revenue targets, and one cheaper fix is worth ruling out first.<\/p>\n\n\n\n
Check if you’ve actually outgrown the space you have<\/strong><\/h3>\n\n\n\nBefore you sign a new lease, look at whether better racking or a tighter inventory layout inside your current warehouse<\/a> solves the problem.<\/p>\n\n\n\nA lot of “we need a second warehouse” conversations are really “our shelving is inefficient” conversations. This costs a weekend of reorganizing instead of months of new setup.<\/p>\n\n\n\n
RTO concentration in one zone<\/strong><\/h3>\n\n\n\nIf RTO rates in a specific state or cluster of pincodes run well above your national average, distance is often the cause.<\/p>\n\n\n\n
A warehouse closer to that demand cuts transit time and gives the customer less time to change their mind before the order arrives.<\/p>\n\n\n\n
SLA breaches by pincode cluster<\/strong><\/h3>\n\n\n\nPull your delivery performance by pincode group, not by city. If one cluster consistently misses your promised delivery window while others don’t, one warehouse is serving too wide a radius.<\/p>\n\n\n\n
This is the same pattern any fulfillment team recognizes: a two-day promise that quietly slips to four or five days for one part of the country is a warehouse-placement problem, not a courier problem.<\/p>\n\n\n\n
Order concentration outside your warehouse’s efficient range<\/strong><\/h3>\n\n\n\nIf 30% or more of your order volume comes from a region more than two days’ transit from your current warehouse, you’re paying a structural shipping cost every single day.<\/p>\n\n\n\n
A second warehouse converts that recurring cost into a one-time setup cost.<\/p>\n\n\n\n
None of these signals need to hit at once. Even one, sustained over two or three months, is a stronger case for expansion than “we’re growing so we should probably get another warehouse.”<\/p>\n\n\n\n
Owned Warehouse vs 3PL vs Hybrid: A Cost Threshold Framework<\/strong><\/h2>\n\n\n\nMulti-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n<\/figure>\n\n\n\nThere’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\nmany growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n
3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n
Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\nThis is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n
An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\nOwned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n
One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n
Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\nMoving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\nIn general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n
This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\nIf both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n
If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n
It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\nMaintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n
Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n
It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n
Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\nManaging inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\nBefore an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n
This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n
It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\nA customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\nWithout a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\nRoute RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n
Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\nCOD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\nGetting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n
Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n
A lot of “we need a second warehouse” conversations are really “our shelving is inefficient” conversations. This costs a weekend of reorganizing instead of months of new setup.<\/p>\n\n\n\n
RTO concentration in one zone<\/strong><\/h3>\n\n\n\nIf RTO rates in a specific state or cluster of pincodes run well above your national average, distance is often the cause.<\/p>\n\n\n\n
A warehouse closer to that demand cuts transit time and gives the customer less time to change their mind before the order arrives.<\/p>\n\n\n\n
SLA breaches by pincode cluster<\/strong><\/h3>\n\n\n\nPull your delivery performance by pincode group, not by city. If one cluster consistently misses your promised delivery window while others don’t, one warehouse is serving too wide a radius.<\/p>\n\n\n\n
This is the same pattern any fulfillment team recognizes: a two-day promise that quietly slips to four or five days for one part of the country is a warehouse-placement problem, not a courier problem.<\/p>\n\n\n\n
Order concentration outside your warehouse’s efficient range<\/strong><\/h3>\n\n\n\nIf 30% or more of your order volume comes from a region more than two days’ transit from your current warehouse, you’re paying a structural shipping cost every single day.<\/p>\n\n\n\n
A second warehouse converts that recurring cost into a one-time setup cost.<\/p>\n\n\n\n
None of these signals need to hit at once. Even one, sustained over two or three months, is a stronger case for expansion than “we’re growing so we should probably get another warehouse.”<\/p>\n\n\n\n
Owned Warehouse vs 3PL vs Hybrid: A Cost Threshold Framework<\/strong><\/h2>\n\n\n\nMulti-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n<\/figure>\n\n\n\nThere’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\nmany growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n
3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n
Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\nThis is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n
An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\nOwned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n
One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n
Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\nMoving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\nIn general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n
This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\nIf both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n
If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n
It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\nMaintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n
Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n
It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n
Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\nManaging inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\nBefore an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n
This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n
It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\nA customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\nWithout a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\nRoute RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n
Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\nCOD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\nGetting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n
Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n
Pull your delivery performance by pincode group, not by city. If one cluster consistently misses your promised delivery window while others don’t, one warehouse is serving too wide a radius.<\/p>\n\n\n\n
This is the same pattern any fulfillment team recognizes: a two-day promise that quietly slips to four or five days for one part of the country is a warehouse-placement problem, not a courier problem.<\/p>\n\n\n\n
Order concentration outside your warehouse’s efficient range<\/strong><\/h3>\n\n\n\nIf 30% or more of your order volume comes from a region more than two days’ transit from your current warehouse, you’re paying a structural shipping cost every single day.<\/p>\n\n\n\n
A second warehouse converts that recurring cost into a one-time setup cost.<\/p>\n\n\n\n
None of these signals need to hit at once. Even one, sustained over two or three months, is a stronger case for expansion than “we’re growing so we should probably get another warehouse.”<\/p>\n\n\n\n
Owned Warehouse vs 3PL vs Hybrid: A Cost Threshold Framework<\/strong><\/h2>\n\n\n\nMulti-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n<\/figure>\n\n\n\nThere’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\nmany growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n
3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n
Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\nThis is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n
An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\nOwned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n
One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n
Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\nMoving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\nIn general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n
This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\nIf both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n
If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n
It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\nMaintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n
Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n
It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n
Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\nManaging inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\nBefore an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n
This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n
It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\nA customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\nWithout a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\nRoute RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n
Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\nCOD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\nGetting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n
Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n
Multi-warehouse management starts with picking the right model, and that depends on your order volume in the new region, not your total company size.<\/p>\n\n\n\n There’s no official benchmark for exactly where each model stops making sense. The break-even point depends on your storage costs, order mix, labor costs, and what a 3PL<\/a> charges at your volume, so treat what follows as a starting point to test against your own numbers, not a fixed rule.<\/p>\n\n\n\n many growing ecommerce brands start with a 3PL here because it avoids the upfront capital cost of setting up a facility.<\/p>\n\n\n\n 3PL pricing in India commonly runs in the Rs 25-50 per order range for pick-pack fees, plus monthly storage, though this varies by provider and volume, so get an actual quote rather than assuming a number.<\/p>\n\n\n\n Setting up your own warehouse at this stage often means paying fixed rent and staff costs that a 3PL can absorb across many clients.<\/p>\n\n\n\n This is where the decision gets closer. A 3PL still gives you flexibility if the demand is seasonal or unproven.<\/p>\n\n\n\n An owned warehouse starts to make sense once volume is stable and you can negotiate a lower per-unit fulfillment cost than what the 3PL charges at that scale.<\/p>\n\n\n\n Owned warehousing more often pays for itself here, especially if you’re also paying a 3PL premium for peak-season surcharges.<\/p>\n\n\n\n One hybrid approach worth considering: keep an owned warehouse in your primary metro (often handling 60-70% of orders, since that’s usually where the bulk of your customers sit) and use a 3PL for secondary regions where volume doesn’t justify your own facility.<\/p>\n\n\n\n Don’t decide this once and forget it. Revisit the comparison every quarter, especially after a big sale event changes your regional order mix.<\/p>\n\n\n\n Moving stock between your own warehouses is not a sale, but it still has compliance requirements most sellers miss until an audit flags it.<\/p>\n\n\n\n In general, movement of goods valued above Rs 50,000 between your own warehouses requires an e-way bill, unless a specific exemption applies under GST rules.<\/p>\n\n\n\n This applies whether the transfer is within the same state or across states, even though no sale is taking place.<\/p>\n\n\n\n If both warehouses operate under the same GST registration, you need a delivery challan, not a tax invoice, since there’s no sale involved.<\/p>\n\n\n\n If the warehouses are registered under different GSTINs, which happens whenever you hold a separate GST registration per state (not necessarily a separate legal entity), the transfer counts as a supply between distinct persons.<\/p>\n\n\n\n It needs a proper tax invoice with applicable GST.<\/p>\n\n\n\n Maintain the delivery challan or tax invoice and the e-way bill, since these are the statutory documents.<\/p>\n\n\n\n Alongside these, keep an internal goods receipt note (GRN) from the receiving warehouse.<\/p>\n\n\n\n It isn’t a mandated GST document, but it completes your audit trail and helps you reconcile stock discrepancies between locations.<\/p>\n\n\n\n Set this up as a fixed process from day one. Retrofitting compliance after you’ve already been running two warehouses informally is far more painful than building it in from the start, and this is one area worth a quick sanity check with your CA before you scale it, since the valuation and reporting details can get specific to your setup.<\/p>\n\n\n\n Managing inventory<\/a> across multiple warehouses gets genuinely complicated the moment your shipping origin and your return destination aren’t the same warehouse.<\/p>\n\n\n\n Before an order even reaches the warehouse floor, run a quick automated check on the buyer’s details, and consider a WhatsApp or IVR confirmation message right after a COD order comes in.<\/p>\n\n\n\n This single step, catching a likely-fake or likely-canceled order before you pack and ship it, prevents a chunk of the reconciliation headache below from ever happening.<\/p>\n\n\n\n It’s cheaper to stop an RTO before it starts than to untangle it across two warehouses afterward.<\/p>\n\n\n\n A customer orders COD, the order ships from Warehouse A, but the return needs to land at Warehouse B because that’s the nearer facility for the reverse pickup<\/a>.<\/p>\n\n\n\n Without a clear rule, this creates two separate problems: the cash collected on delivery has to reconcile against the correct warehouse’s books, and the returned stock has to get logged back into inventory without double-counting or losing track of it.<\/p>\n\n\n\n Route RTO and customer returns to the nearest warehouse by default, not back to the shipping origin.<\/p>\n\n\n\n Then run a weekly reconciliation that matches COD cash collected against the warehouse that shipped the order, separately from the stock that came back into whichever warehouse received the return.<\/p>\n\n\n\n COD continues to be a significant payment method across Indian ecommerce<\/a>, and many sellers observe higher return-to-origin rates on COD shipments than on prepaid orders.<\/p>\n\n\n\n Getting this reconciliation wrong across two warehouses doesn’t just create bookkeeping headaches; it can hide real problems like a specific product or region driving disproportionate returns.<\/p>\n\n\n\n Track RTO and COD reconciliation by warehouse pair (which warehouse shipped, which warehouse received the return), not just by warehouse in isolation.<\/p>\n\n\n\n<\/figure>\n\n\n\nLower order volume from a region<\/strong><\/h3>\n\n\n\n
Moderate, sustained order volume<\/strong><\/h3>\n\n\n\n
High, stable order volume over several months<\/strong><\/h3>\n\n\n\n
The GST Side of Inter-Warehouse Transfers<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nE-way bill requirement<\/strong><\/h3>\n\n\n\n
Same GSTIN vs different GSTIN<\/strong><\/h3>\n\n\n\n
What to keep on file<\/strong><\/h3>\n\n\n\n
Handling COD and RTO Across Multiple Warehouses<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nCatch problem orders before they ship, not after they bounce back<\/strong><\/h3>\n\n\n\n
The core problem is once an order does ship<\/strong><\/h3>\n\n\n\n
A workable rule<\/strong><\/h3>\n\n\n\n
Why this matters more in India<\/strong><\/h3>\n\n\n\n
![\"](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01144344\/routing-a-single-order.webp\")
<\/figure>\n\n\n\n![\"setting](\"https:\/\/itl-blog-aws.s3.ap-south-1.amazonaws.com\/blog\/wp-content\/uploads\/2026\/08\/01144431\/setting-stock-levels-across-warehouses-over-time.webp\")
<\/figure>\n\n\n\n