Single-Node vs. Multi-Node Fulfillment: When to Add a Second Warehouse
Single-node vs. multi-node fulfillment is a real operational decision, not something to back into after a bad peak season. This guide covers what changes when you add a second warehouse — inventory splitting, per-node minimums, and the software complexity of running two facilities — plus the signals that tell you when a second node is actually worth it.
Most brands don't decide to add a second warehouse. They back into it, usually after a bad peak season or a customer complaint about a nine-day transit time. That's the wrong way to make this call. Single-node vs. multi-node fulfillment is a real operational decision with real tradeoffs, and it deserves the same structured evaluation you'd apply to picking a 3PL in the first place.
This post is about what actually changes when you go from one facility to two: how inventory splitting works, what per-node minimums do to your cost structure, and where the software complexity shows up. If you haven't yet read when multi-node fulfillment actually works, start there for the strategic case. This is the operational one.
What's the difference between single-node and multi-node fulfillment?
Single-node fulfillment means every order ships from one facility, regardless of where the customer lives. Multi-node fulfillment means orders ship from whichever of two or more facilities gets the product to the customer fastest or cheapest, based on where inventory sits.
A single node is simpler to run: one inventory count, one set of pick-pack rules, one relationship to manage. A multi-node network adds speed and shipping-zone savings, but it also adds a second full set of operational decisions layered on top of the first. Neither is inherently better. The right answer depends on your order volume, SKU count, and how concentrated your customer base is.
What actually changes when you add a second warehouse?
Three things change immediately, and none of them are optional extras you can defer:
- Inventory allocation. You now have to decide how much of each SKU sits at each node, and that decision has to be revisited constantly.
- Contract minimums. Most 3PLs price nodes individually, so a second facility usually means a second minimum commitment.
- Systems and visibility. You need real-time inventory and order-routing logic across two locations instead of one, or you'll ship from the wrong node more often than not.
Each of these is manageable on its own. Together, they're why brands underestimate the lift of going multi-node until they're already in it.
How does inventory splitting actually work across two nodes?
Inventory splitting means dividing your stock of each SKU between nodes based on regional demand, instead of holding one pool in one place. In practice, this is harder than it sounds because demand forecasting gets exponentially more difficult once you break it down by region instead of forecasting nationally.
The immediate risk is the split shipment: an order for two items where each item sits at a different node, so the order goes out in two boxes instead of one. Split shipments already made up roughly 21% of ecommerce orders as of 2021, up from under 17% before 2020, according to Narvar's research on the trend. Each split shipment usually means extra shipping cost, extra packaging, and extra labor, on top of whatever savings the second node was supposed to deliver on the rest of your orders.
The practical fix is allocation logic, not guesswork: set clear rules for which SKUs get split across nodes and which stay consolidated at one location, and revisit the split as your top sellers and regional mix shift.
What are per-node minimums, and how do they change your cost structure?
A per-node minimum is the baseline fee a 3PL charges to keep a facility staffed and ready for your volume, independent of how many orders you actually ship from it. When you had one node, you paid one minimum. With two, you're paying two, whether or not the second node is running at full capacity yet.
This matters because the shipping-zone savings that make multi-node attractive on paper (cheaper zone 2-3 shipping instead of zone 7-8) only materialize once volume through the second node is high enough to clear that minimum comfortably. Below that line, you're paying for standby capacity you're not using efficiently, and the math can look worse than staying single-node until volume catches up.
This is exactly the kind of cost comparison an RFP is built to surface: real minimums, real per-order pricing, and real zone-skip savings from providers who actually operate the geographic footprint you need, not estimates.
What software complexity does a second node add?
A single node tolerates a fairly basic setup: one inventory feed, one shipping rule set, manual order routing if it comes to that. A second node removes that margin for error. You need order-routing logic that assigns each order to the right facility automatically, inventory visibility that's accurate at both locations in real time, and reporting that can tell you which node is actually driving your cost and speed numbers.
None of that has to mean an expensive new tech stack. It does mean confirming, before you sign a second contract, that your WMS or OMS (and your 3PL's systems) can actually support two-node routing, not just two-node storage.
When does a second warehouse actually pay off?
A second node tends to make sense when several of these are true at once, not just one:
- Your order volume is high and consistent enough to clear two sets of minimums
- Your customer base is genuinely national, not concentrated in one region
- Your SKU count is manageable enough to split without creating a forecasting mess
- You have the systems (or the 3PL has the systems) to route orders and track inventory across both nodes in real time
If you're only hitting one or two of those, the fix is usually a better single-node setup, not a second facility. Our companion post on the signals that mean it's time to add a node walks through those triggers in more depth.
FAQ
Does adding a second warehouse always lower shipping costs? Not automatically. It lowers shipping costs on orders that ship from the closer node once volume through that node is high enough to clear its minimum commitment. Below that volume, the added fixed costs can offset or exceed the shipping savings.
What's the biggest operational risk of going multi-node? Inventory splitting gone wrong: either stockouts at one node while the other is overstocked, or a rise in split shipments that quietly erodes the margin the second node was supposed to protect.
Do I need new software to run two fulfillment nodes? You need order-routing and real-time inventory visibility across both locations, whether that comes from your own systems or your 3PL's. You don't necessarily need to replace your existing stack, but you do need to confirm it can handle two-node logic before you commit.
Get real numbers before you commit to a second node
The gap between "multi-node should save us money" and "multi-node is actually saving us money" comes down to the specific minimums, per-order pricing, and zone coverage a given 3PL offers, not general industry averages. Start your RFP on Slotted to get structured, comparable proposals from providers who can actually support the second node you're considering, so the decision is based on your numbers instead of a guess.