Start with an allocation decision
Opening another warehouse creates a question that a transit map cannot answer: which products should live there? Sending a little of everything may leave both locations short of popular variants while multiplying positions for products that rarely sell.
Ask prospective 3PLs to work through a SKU allocation file. Include sellable units, replenishment lead times, regional demand and products commonly bought together. Warehouse count is a network decision; stock placement is a product decision. Evaluate both before signing a transfer order.
Compare two policies using the same stock
Consider an illustrative catalog with three products and 900 sellable units: 600 of A, 240 of B and 60 of C. This is a constructed example, not a demand forecast or a recommended safety-stock level.
An equal split puts 300 A, 120 B and 30 C at each location. A selective policy puts 240 A and 60 B at the new location and leaves 360 A, 180 B and all 60 C at the original warehouse. Both policies use exactly 900 units. The selective policy sends 300 units instead of 450 and creates five occupied SKU-location combinations instead of six.
That difference is not automatically a saving. The new location cannot fulfill C locally. If C frequently travels with A, the selective policy may create split shipments or send the whole basket from the original warehouse. A lower transfer quantity is only useful if the resulting order allocation still meets the commercial promise.
Count inventory that can actually ship
Do not allocate from a single total-stock number. Shopify separates available stock from committed and unavailable quantities; incoming stock has its own state. A transfer in transit should not be treated as ready inventory at the destination. Shopify inventory states.
Have the 3PL identify which system owns each state and what event changes it. Request a sample export showing location, SKU, available units and inventory holds. A verbal assurance that the integration is real time does not resolve a disagreement about what the numbers mean.
Use a placement gate for each product
Before moving a SKU, answer four questions: Is regional demand substantial enough to justify a position? Which companion products must also be present? How quickly can stock be replenished? What happens when the destination runs out?
Then replay actual recent baskets against the proposed placement. Count orders fulfilled from one location, orders split and orders routed back to the original warehouse. Historical baskets do not predict future demand, but they expose obvious incompatibilities before stock moves.
Approve the second warehouse with an explicit starting assortment and a review trigger. Add products when order evidence supports them. The goal is useful regional availability, not a symmetrical warehouse spreadsheet.
Related reading
Sources
- Primary source or planning context — accessed 2026-10-15. Shopify distinguishes available, committed, unavailable and incoming inventory; incoming inventory becomes available after receipt.