Help: Multi-warehouse inventory with NetSuite → Shopify → Amazon/eBay/Walmart + shipping tool that can route by warehouse? Anyone using Linnworks?

Hey everyone — looking for advice on how to properly architect our multi-warehouse setup.

Our setup:

  • Shopify as our main ecommerce site

  • Amazon (2 accounts, soon 4)

  • eBay

  • Walmart

  • We use Marketplace Connect to push inventory from Shopify to all marketplace channels

  • NetSuite is our ERP and true inventory master

  • ~1,000+ orders per month and growing

  • Two warehouses right now (both carry overlapping SKUs), moving to four soon

  • We also sell in store, so inventory must stay accurate in real time

What works today:

  • NetSuite → Shopify inventory sync is good

  • Shopify → Marketplace Connect → Amazon/eBay/Walmart also works fine

  • Marketplaces only need combined inventory, not warehouse-specific

What we need help with:

I’m looking for a shipping/fulfillment system (ShipStation, ShipHero, Linnworks, etc.) that can:

  1. Pull multi-location inventory from Shopify

  2. Let us prioritize shipping from Warehouse A first, and if A is out of stock, automatically route fulfillment to Warehouse B

  3. Eventually handle 4 total warehouses

  4. Integrate cleanly with Shopify’s multi-location system

  5. Ideally not require making the new tool the “inventory master” — NetSuite must remain the master

  6. Provide reliable routing without replacing our whole stack

What I’ve found so far:

  • Veeqo won’t work because it can’t reliably treat Shopify as the inventory master and doesn’t properly use Shopify’s multi-location data

  • ShipStation doesn’t seem to do warehouse routing well

  • ShipHero might, but seems expensive and may want to become the inventory master

  • Linnworks looks promising — but I’m unsure about:

    • How well it supports Shopify as the inventory source

    • Pricing (almost impossible to find clear numbers online)

    • Whether Linnworks + NetSuite requires costly middleware

    • Whether Linnworks can simply read Shopify’s multi-location inventory and route orders Warehouse A → B

If anyone here uses Linnworks or anything similar with Shopify multi-location, please share your experience.


Extra Info — answering questions I know people will ask:

Where is your true inventory master?

NetSuite, 100%. Shopify just receives data pushed in from NetSuite.

Do your warehouses carry overlapping SKUs?

Yes. Both warehouses stock the same SKUs, so we need a routing hierarchy (use Warehouse A first, then fallback to Warehouse B, etc.).

Do marketplaces need per-warehouse inventory?

No — combined inventory is fine. Marketplace Connect already handles pushing Shopify’s combined quantity to Amazon, eBay, Walmart.

What order volume?

1,000+ orders/month, scaling upward.

What kind of routing do you need?

Not geography based.
Just a simple but strict logic:
Try Warehouse A → if out of stock → route to Warehouse B → (future C/D)

Do you need an OMS or just a shipping label tool?

I need more than a label printer — I need warehouse-fallback routing. But I don’t want a full WMS that replaces NetSuite or forces a rebuild of our stack.

Are you open to middleware (Celigo, Boomi, Pipe17, etc.)?

Yes, if needed — but I’d prefer a system that can read Shopify’s inventory directly and make routing decisions without overly complex middleware.

Hey, been through similar pain with multi-warehouse routing. One thing I’d flag though, the “simple A → B fallback” can bite you. Do you really want to always hit Warehouse A first even when it’s down to 3 units and B has 500? Pure priority without considering stock health creates problems you don’t expect.

The core issue is ShipStation, Veeqo etc are basically label printers. You need something sitting between the order and the label. On Linnworks, the pricing opacity alone would make me nervous. And NetSuite integration almost always needs middleware anyway. We use Orlio for this. Reads Shopify multi-location directly, doesn’t try to become inventory master, just makes routing decisions based on stock levels and location preferences. Worth a look alongside whatever else you’re evaluating.

Good luck, this stuff is annoyingly harder than it should be.