If you run two or more Shopify stores from one warehouse, the question that decides everything is whether those stores share stock or keep separate piles. Get that wrong and you oversell: the same unit sold twice across two storefronts, with one customer about to get an apology email. This guide covers shared vs separated stock, one pick run vs many, keeping SKUs and bin locations consistent, a single dispatch queue, and reporting per store.
Plenty of Australian retailers end up here without planning it. You launch a main store, then add an outlet for end-of-line gear, then a trade or wholesale storefront, and maybe a second brand. Four Shopify admins, four checkouts, one room, one packing bench. The selling side multiplied; the fulfilment side did not.
Shared vs separated stock: the decision that matters most
There are two honest ways to handle inventory across stores, and you need to pick one per product line.
Pooled (shared): all stores draw from one physical quantity. You have 40 of a SKU; the main store and the outlet both see and sell against the same 40. Good for one catalogue sold through several fronts, because you never strand stock that one store can't shift but another can.
Independent (ring-fenced): each store gets its own allocation. You commit 25 to the main store and 15 to wholesale, and they don't touch each other. Good when you've genuinely promised stock to a channel, or when brands must never compete for the same unit.
The trap is doing neither on purpose. If you set each Shopify store's inventory by hand from the same physical pile and hope the numbers stay aligned, they won't. That's the failure mode below.
| Pooled stock | Independent stock | |
|---|---|---|
| Best for | One catalogue, several storefronts (main + outlet) | Channels with committed allocations (wholesale, exclusives) |
| Upside | No stranded stock; one store's demand covers another's | Clear promises per channel; no cross-store competition |
| Downside | Oversell risk if stores aren't synced to one number | Can strand units one store can't sell while another runs out |
| Needs | A single source of truth pushing the same count to every store | Discipline to rebalance allocations as demand moves |
The real failure mode: selling the same unit twice
Here's how it actually goes wrong. You've got 1 left of a popular item, physically on the shelf. Both your main store and your outlet are showing it as available because each was set independently. Two customers, two different stores, buy it within the same hour. Shopify happily takes both orders. You ship one, then have to cancel and refund the other.
That's not a rare edge case. The more your stores share a physical catalogue, the more often the same low-stock SKU is exposed in two places at once. The cause is always the same: more than one system thinks it owns the true count.
The fix is a single source of truth. One system holds the real, physical quantity, and it pushes that number out to every Shopify store. When a sale lands anywhere, the count drops everywhere, fast enough that the second customer sees sold out before they can check out. Without one writer of the truth, you're relying on luck and refunds.
Keep SKUs and bin locations identical across stores
This is the boring, unglamorous part that quietly saves you. If the same product carries a different SKU in each store, every system downstream has to guess that they're the same thing, and your stock counts drift apart by design.
- One SKU per physical product, used in every store. No store-specific suffixes for the same item.
- One bin location per SKU. The item lives in one place on the floor regardless of which store sold it.
- A clear barcode or scan reference so a picker never has to know which storefront an order came from to find the goods.
Get this right and the rest gets easy, because the warehouse stops caring about brands and only cares about SKUs and bins.
One combined pick run vs per-store runs
Once your SKUs and bins are shared, picking per store is just wasted walking. If three stores all sold from bin A4 this morning, you want to visit A4 once, grab everything, and sort it into orders afterwards. Walking the same aisle three times because the orders came from three Shopify admins is a tax you're paying for no reason.
A combined pick run pulls open orders from every store into one batch, sorts the picks into walking order, and lets you sort to orders at the bench. Per-store runs only make sense when stores live in physically separate areas, or when one channel has packing rules so different it's genuinely a separate workflow. For most people in one room, combine. If you want the detail on getting picks right at volume, see pick and pack accuracy.
A single dispatch queue
The same logic applies to dispatch. Your packers should not have four browser tabs open, flipping between store admins to find what to ship next. They should see one queue of orders to pack, in the order you want them packed, regardless of which store sold the item.
A single queue also means consistent carrier selection and labels. You can still apply different rules per store (wholesale goes on StarTrack, retail on Australia Post, say) without making the human at the bench remember it. The rule lives in the system, not in the packer's head.
Reporting per store
Combining the warehouse work doesn't mean blending the numbers. You still want to know how each store performed: orders, units, freight cost, margin. The goal is one floor, many P&Ls. So pick tooling that physically pools the work but tags every order with its source store, so you can split reporting cleanly afterwards. If you can't tell which store paid for the freight, you can't tell which channel is actually worth running.
Where OrderOps fits
This is squarely the problem OrderOps was built for: it connects multiple Shopify stores and lets you pool stock or keep it separate by choice, with one system holding the true count so the oversell race above doesn't happen. It gives you one shipping queue across all your stores, then tags orders by source store for reporting. You bring your own carrier accounts. See features for the detail. If you're still deciding between building this in-house and outsourcing, the rundown in best fulfilment platforms in Australia is a fairer place to start than a sales page.
The takeaway: decide pooled or independent per product line, give one system ownership of the true stock count, and share SKUs and bins so the warehouse stops caring which store made the sale. Do that and running five stores from one room is barely harder than running one. Skip it and you'll spend your days writing oversell apologies.