Multi-Warehouse Inventory on Shopify: Combine, Filter, or Map?
S&S Activewear ships from eight warehouses across the United States. SanMar runs a similar multi-warehouse footprint. AlphaBroder distributes across several major regions. Each one is, from your store's perspective, a stack of warehouse-level stock counts that have to land in Shopify as one number per variant — or several, if you're running a multi-location Shopify store.
There are three sane ways to do that. Each one fits a different store shape. The fourth way — "default to whichever warehouse has the biggest pile" — is how stores oversell, ship from the wrong region, and spend Tuesday mornings refunding customers.
This article walks through the three sane options. Each one in plain English, each one with the store shape it fits, each one with the wholesale-apparel detail that determines whether it's right for your operation. By the end, you'll know which of combine, filter, or map your store needs — and how to set it up.
Running example used throughout this article: Shoreline Tee Co., a pure dropshipper running on S&S Activewear. They sell Comfort Colors 1717, Bella+Canvas 3001, and Next Level 6210 to customers in 41 states. They ship through S&S directly, do not stock anything themselves, and do not want to oversell.
Key Takeaways
- The decision — pick the warehouse-handling pattern that matches your shipping reality (where your customers are, where you stock if you stock, how you ship).
- The three options — combine all warehouses into one Shopify number; filter to a regional subset; map each warehouse to a Shopify location.
- The fast answer for most pure dropshippers — combine, with a buffer, on a fast inventory loop.
- When each option wins — combine for pure dropshippers shipping the supplier's whole network; filter for decorators shipping from one region; map for multi-location merchants who run their own warehouses alongside the supplier's stock.
- Try it now — Install Supply Master free on the Shopify App Store (5.0★, top-rated for apparel-supplier integration in the U.S. and Canada) or email support@comstack.com and we'll set up your warehouse mapping.
Table of contents
- Why the warehouse question matters more than the sync-cadence question
- The three sane options
- Option 1 — Combine
- Option 2 — Filter
- Option 3 — Map
- Side-by-side: which option does what
- How real stores choose
- Where Supply Master fits
- FAQ
- Try it on your store
Why the warehouse question matters more than the sync-cadence question
When stores oversell, owners look at sync cadence first. "Maybe I need to refresh more often." Sync cadence matters — but for most apparel stores, the bigger source of overselling is warehouse handling, not refresh frequency.
Three reasons this is true:
- Apparel suppliers split stock across warehouses. A Comfort Colors 1717 in Athletic Heather size XL might exist at three of the supplier's eight warehouses on Tuesday morning. Your Shopify store needs to know which three — and whether all three are reachable for your customers' shipping zones.
- Shopify shows one number per variant per location. A multi-warehouse supplier feeding a single-location Shopify store collapses up to eight stock counts into one. The math on what to collapse to drives the overselling rate.
- Shipping speed depends on which warehouse the order pulls from. Fast shipping is the difference between a one-time customer and a repeat one. Pulling from the wrong warehouse for a customer's region eats your shipping-speed advantage even if the supplier technically has the stock.
The warehouse question is not a feature of your integration. It is the design decision your integration is built on top of. Get it right and the sync-cadence and pricing-rule questions become much smaller.
The three sane options
| Option | What it does | Right for |
|---|---|---|
| Combine | Sums every warehouse's stock and writes one number into one Shopify location. | Pure dropshippers, most multi-supplier apparel stores. |
| Filter | Sums only certain warehouses' stock — typically a regional subset — and writes one number into one Shopify location. | Stores with a defined shipping radius (regional dropship, fast-ship promise). |
| Map | Writes each supplier warehouse to a specific Shopify location, preserving the supplier's geographic split. | Stores with their own holding inventory plus supplier overflow, multi-location Shopify stores, hybrid retail-plus-online operations. |
Each option assumes your integration tool actually has the per-warehouse stock data to begin with — which means it pulls in the supplier's native data shape (REST, FTP, PromoStandards, file-based), not a flattened CSV that already collapsed it. For more on the four data shapes, see FTP, SFTP, REST, PromoStandards: The Four Ways Apparel Suppliers Hand You Data to Sell on Shopify.
Option 1 — Combine
The plain-English version. You sum every one of your supplier's warehouse stock counts and write the total as one Shopify stock count, on a single Shopify location.
A Comfort Colors 1717 in Athletic Heather XL has 12 units at S&S's Robbinsville warehouse, 47 at Reading, 0 at Reno, 8 at Lockport, 33 at Mexia, 19 at Las Vegas, 27 at Olathe, and 14 at McDonough. Combine writes 160 as the Shopify stock count.
When the customer orders, Shopify says yes (160 is plenty). The supplier picks the right warehouse to ship from based on their own routing rules (usually the closest in-stock warehouse to the customer).
When it's right. Combine fits if:
- Your fulfillment is 100% supplier-shipped.
- Your customer base is national (or the supplier's warehouse footprint covers your customer base).
- Your supplier handles routing internally and you trust them on it.
- You want simplicity over geographic precision.
This is the right setting for most pure dropshippers and many multi-supplier resellers. It's also the most common starting point — the right default to combine first, then move to filter or map only if there's a reason.
The trade-off. Combine doesn't know about geography. If S&S has 200 of the SKU at Las Vegas and 0 at Robbinsville, Shopify still shows 200, and a customer in New Jersey orders successfully — but the package ships from Nevada. The fulfillment is fine; the shipping speed is not.
If shipping speed matters more than catalog availability, the right option is filter (next).
The buffer. Combine setups benefit from a small per-variant safety buffer (typically 5 units). The buffer absorbs the small lag between the supplier's reality and your last refresh. The cost is a few unsold units per cycle. The benefit is much fewer overselling events.
Shoreline Tee Co.'s read on this. They ship through S&S to all 41 states, don't hold their own stock, and don't want to think about warehouse geography. Combine, with a 5-unit buffer per variant, on an every-few-hours inventory loop. They review the setup once a quarter.
Option 2 — Filter
The plain-English version. You pick which of your supplier's warehouses are eligible for your store, sum only those, and write the total as one Shopify stock count.
Same Comfort Colors 1717 example. Suppose Shoreline Tee Co. wants to promise two-day shipping to its customer base, which is concentrated east of the Mississippi. The S&S warehouses that reach that footprint in two days are Robbinsville, Reading, Lockport, McDonough, and Olathe. Filter writes the sum of those five (12 + 47 + 8 + 27 + 14 = 108) as the Shopify stock count, ignoring the western warehouses entirely.
When the customer orders, Shopify says yes if the eastern-warehouse stock is enough. The supplier picks one of the eligible warehouses to ship from. The package arrives in two days as promised.
When it's right. Filter fits if:
- You make a regional shipping promise (two-day to the East Coast, etc.).
- Your customer base is concentrated in a region where a subset of the supplier's warehouses can serve fast.
- You'd rather sell less catalog than ship long distances.
A clean example: a regional decorator in the Southeast who supplies CrossFit gyms across Georgia, Tennessee, and the Carolinas. Their customers expect package arrival in two business days. The S&S warehouses that hit that promise are Robbinsville, McDonough, and Olathe. Everything west of the Mississippi gets filtered out of the Shopify stock count.
The trade-off. You sell less catalog than you would on combine. The Comfort Colors 1717 with 0 stock east of Mississippi is "out of stock" on your store, even though S&S has 19 at Las Vegas. The customer who would have happily paid for slower shipping doesn't get to. For most regional stores this trade-off is right; for marketplaces it is not.
The bonus. Filter setups dramatically reduce wrong-warehouse shipping (failure mode 2 in Dropshipping Apparel on Shopify: The Five Failure Modes Nobody Tells You About). The supplier can only ship from the warehouses you approved, so the customer in Atlanta gets the package routed from Memphis or Olathe, not Reno.
Option 3 — Map
The plain-English version. You write each supplier warehouse as a separate Shopify location. Shopify keeps the supplier's geographic split. Customers see "in stock at our Texas warehouse" or similar — or, more commonly, Shopify uses the multi-location data to route fulfillment internally without showing it to the customer.
Same example. The S&S Texas warehouse (Mexia) writes its 33 units to a Shopify location called "Texas — S&S overflow." The Pennsylvania warehouse (Reading) writes its 47 to "Pennsylvania — S&S overflow." And so on for each warehouse.
When the customer orders, Shopify's location-aware fulfillment can pick the closest location to the customer's shipping zip and route the order there.
When it's right. Map fits if:
- You're running a multi-location Shopify store today (your own holding stock at one location, supplier overflow as a second).
- You're a hybrid retail-plus-online operation (your physical store is one location; the supplier's warehouse is a second).
- You operate at scale where geographic precision pays off in shipping cost or speed.
A clean example: a healthcare uniform retailer with a small holding warehouse in Pittsburgh that buys overflow stock from SanMar. They map their Pittsburgh warehouse to "Pittsburgh — Holding" and SanMar's Cincinnati warehouse to "Cincinnati — SanMar Overflow." Shopify's fulfillment routes orders to whichever location has stock and is closer to the customer.
Another example: a corporate-merch shop running a hospital stipend program from a holding stock plus a supplier's PromoStandards-driven overflow stock.
The trade-off. Setup complexity. Mapping requires a Shopify multi-location plan, a clean per-location fulfillment workflow, and an integration tool that supports per-warehouse-to-per-location mapping. It also introduces shipping-cost optimization decisions you didn't have on combine or filter.
The bonus. When you have your own holding stock, map is the only option that keeps your stock and your supplier's stock from collapsing into the same Shopify number. Without map, your holding stock and your supplier's overflow stock would be summed together, and you'd lose visibility into which one fulfilled the order.
Side-by-side: which option does what
| Capability | Combine | Filter | Map |
|---|---|---|---|
| Setup complexity | Low | Low-medium | Medium |
| Sees per-warehouse stock | No (collapsed) | Partial (filtered subset only) | Yes (per location) |
| Right for pure dropshippers | Yes | Sometimes (regional) | Rarely |
| Right for multi-location Shopify | No (writes one location) | No | Yes |
| Helps with wrong-warehouse shipping | No | Yes | Yes (via location-aware routing) |
| Plays well with own holding stock | No (no separation) | No (no separation) | Yes |
| Default for most apparel stores | Yes | Where regional shipping matters | Where own stock + supplier overflow |
How real stores choose
Shoreline Tee Co. (pure dropshipper, S&S, national)
National customer base. Ships everything from S&S. No holding stock. No regional shipping promise.
→ Combine with a 5-unit buffer, on an every-few-hours inventory loop. Set once. Reviews quarterly.
A regional decorator on the East Coast
Customer base concentrated east of the Mississippi. Two-day shipping promise. Buys blanks from S&S, ships through S&S directly for many orders.
→ Filter to the Robbinsville, Reading, Lockport, McDonough, and Olathe warehouses. Sums to one Shopify stock count. Customers get the two-day promise; the supplier never ships from Reno on this store.
A healthcare-uniform retailer with a holding warehouse
Holds about 15% of revenue's worth of WonderWink and Cherokee scrubs at a Pittsburgh warehouse. Buys overflow from SanMar. Ships from whichever location has stock.
→ Map. Pittsburgh holding → Shopify location "Pittsburgh — Holding." SanMar Cincinnati → Shopify location "Cincinnati — SanMar Overflow." Shopify's location-aware fulfillment routes the order based on stock + proximity. Holding stock and supplier overflow stay separated.
A multi-supplier decorator (Northside Print Co.)
S&S is 70% of volume; SanMar is 25%; Cap America is 5%. Ships nationally. No holding stock. No regional shipping promise.
→ Combine per supplier. S&S all eight warehouses summed; SanMar's distribution centers summed; Cap America summed. Three combined Shopify stock counts feeding three product groups. They run combine on each, with separate buffers per supplier (because supplier sync cadence varies — Cap America's PromoStandards loop is different from S&S's REST loop).
A youth-baseball team store
Augusta uniforms (file-based), single-supplier, single shipment per season.
→ Combine is fine; warehouse mapping doesn't matter much because Augusta consolidates the season's order anyway. The team store's fulfillment story is "ship the whole season's order in two waves," not "real-time per-customer routing."
Where Supply Master fits
Supply Master, the app this site is for, supports all three options on every supplier where the supplier exposes per-warehouse stock data. Configuration lives at the supplier level (Edit Supplier > Inventory Settings) so you can run combine on one supplier and map on another in the same install.
Specifically:
- Combine is the default. One stock count per variant, written to one Shopify location, on the schedule you set.
- Filter lets you select a subset of the supplier's warehouses (by warehouse ID, name, or your own region grouping). Sum applies only to selected warehouses.
- Map writes each supplier warehouse as a separate Shopify location. Multi-location Shopify required.
- Buffer is a per-variant safety stock subtracted from the supplier number before writing to Shopify. Configured per supplier.
- Schedule is configurable per supplier. Stock can refresh every few hours on supported supplier shapes (REST suppliers especially); prices and full catalog refresh on slower loops.
Per-supplier capability matrix at supported suppliers and features. Setup walk-through at setting up inventory by warehouse location.
What it does well today:
- All three options on every reputable U.S. and Canadian apparel supplier (S&S, SanMar US, SanMar Canada, AlphaBroder, Cap America, OTTO Cap, Goldstar, Atlantic Coast Cotton, Edwards Garment, Scrub Authority, Augusta, AS Colour, CHAMPRO, Decky, JDS Industries, plus custom suppliers).
- Per-supplier configuration in one install (combine on supplier A, map on supplier B).
- Per-variant buffer.
- Schedule-driven refresh per supplier.
- 5.0★ rating on the Shopify App Store; top-rated for apparel-supplier integration in the U.S. and Canada.
What it doesn't do (yet):
- Per-customer-zip routing rules. The current "filter" option uses static warehouse selection, not dynamic zip-aware filtering. Stores that need warehouse-by-zip rules (rare but real) handle them with map and Shopify's location-aware fulfillment, or with a custom fulfillment-routing app on top.
If you're not sure which option fits, email support@comstack.com — a Comstack engineer will walk through your fulfillment story and configure the right one for you.
FAQ
How do I know which option is right?
Three quick questions answer it.
- Do you have your own holding stock? If yes → Map.
- Do you make a regional shipping promise? If yes → Filter.
- Otherwise → Combine.
Most pure dropshippers and most multi-supplier apparel resellers fit Combine. Filter is the right answer for regional stores. Map is the right answer for hybrid stores.
What if my supplier doesn't expose per-warehouse stock?
A few suppliers (especially smaller file-based ones) only expose total catalog stock without warehouse breakdown. For those, Combine is the only option — there's no per-warehouse data to filter or map against. Your integration app should make this clear in the supplier configuration.
Can I switch options later?
Yes. Each option is a configuration setting. Switching from Combine to Filter is a few-minute change. Switching to Map requires multi-location Shopify and the per-location setup, but the underlying supplier connection doesn't change.
What's a good buffer?
5 units per variant is a sensible default for most apparel stores running an every-few-hours stock loop. For slower loops (daily refresh) bump to 10 or 15. For very slow loops (weekly), consider whether the loop frequency itself is the bigger issue.
Will my Shopify variant stock automatically respect Shopify's location settings?
Yes, if you're on Combine or Filter and writing to a single location, Shopify uses that location's stock count. If you're on Map and writing to multiple locations, Shopify's location-aware fulfillment uses each location's stock count separately.
What about Shopify's variant ceiling?
Modern Shopify supports up to 2,048 variants per product, which is more than enough for any apparel SKU including SanMar's deepest style families. The variant ceiling doesn't change with warehouse mapping. See variant splitting (legacy feature) for stores still on the old 100-variant cap.
What if my supplier's data drops mid-day?
Reputable integration apps retry on failure and alert you if a sync fails permanently. Supply Master logs every sync attempt and shows the status in Sync History. If a supplier's data feed goes down for maintenance, your existing Shopify numbers stay as-is until the next successful sync.
What if I have more than one supplier?
Each supplier's warehouse handling is configured independently. You can run S&S as Combine, SanMar as Filter (eastern warehouses only), and Augusta as Combine, all in the same install. Buffers, schedules, and pricing rules also configure per supplier.
What does it cost?
Supply Master offers a free trial. Plan tiers scale with variant count, sync volume, and supplier count. Exact pricing is on the App Store listing.
What if I need help picking?
Email support@comstack.com. Most warehouse-mapping questions can be answered in a short call once we know your fulfillment story.
Related reading
- Sell S&S Activewear Products on Shopify — the eight-warehouse pillar article, including the per-warehouse mapping decisions for the largest U.S. apparel REST-API supplier.
- Sell SanMar Products on Shopify — how SanMar's nine-warehouse FTP feed lands as combined total availability in Shopify.
- FTP, SFTP, REST, PromoStandards: The Four Ways Apparel Suppliers Hand You Data to Sell on Shopify — the four data shapes your suppliers use, and what each one means for whether per-warehouse stock is even available to you.
- Buyer's Guide: How to Evaluate a Shopify Supplier Integration App — criterion 4 (inventory mapping) walks through what to ask any candidate app about its multi-warehouse capabilities.
Try it on your store
Most overselling on Shopify apparel stores comes from warehouse handling, not refresh frequency. Get the warehouse model right and the rest of the integration becomes much smaller.
- Install Supply Master free on the Shopify App Store — 5.0★, top-rated for apparel-supplier integration in the U.S. and Canada.
- Or email support@comstack.com — a Comstack engineer will configure combine, filter, or map for each of your suppliers based on your shipping reality.
Comstack has been building integrations for apparel and promo suppliers since 2012. Warehouse mapping is one of the things we get asked about more than any other capability — and the option you pick today is usually the option you keep for years.
Don't oversell because your data path collapsed eight warehouses into one number it shouldn't have. Pick combine, filter, or map. Then move on with your week.