String
Running the operation

Can ShipStation Choose Which Warehouse Fulfills an Order?

Published

Yes. The feature is called Auto-Routing, and ShipStation describes it as assigning “orders to ship from a certain warehouse location” — documented in Automation Basics alongside the other things automation can set.

What it decides on

Auto-Routing picks the ship-from location using two inputs: which of your warehouses hold the items on the order, and which of those is closest to the recipient. That is the routing logic most multi-warehouse operations would write by hand, and it is the right default. Shorter distance means a lower zone, which means a cheaper label and a shorter transit.

Who has it

Two constraints worth checking before planning around it. ShipStation documents Auto-Routing as available to US and Canada-based accounts only, and it is plan-gated to High Volume. It also does not apply to manually created orders, which matters if a meaningful share of your volume is entered by hand rather than imported.

The simpler version most operations actually need

Auto-Routing solves the case where the same SKU is stocked in more than one place and the system has to choose. A lot of multi-location setups are not that. They are a fixed mapping — this channel ships from that building, this product line ships from the other one — and a fixed mapping does not need stock-aware routing.

For that, a basic automation rule setting the Ship From Location does the job. Key it on the store, on a product tag, or on any order-level criterion, and it applies at import with no plan gate and no regional restriction.

Worth being honest about which situation you are in. If the answer to “which warehouse should this ship from” never depends on today’s stock, you do not need Auto-Routing and a two-line rule will hold up better.

Where it stops

Auto-Routing decides between warehouses. It does not decide whether to ship at all.

If the question is “does this location have enough stock to cover the order, and what should happen if it does not”, that is a different problem, and one the rules engine does not reach — holding an order against live stock needs something that reads inventory at the moment the order lands.

Whether this is happening in your operation

String builds and maintains logic like this inside existing ShipStation accounts — cartonization, rate selection, batching, inventory-aware holds, cold chain rules. No dashboard, nothing for your team to learn.

Typically for operations past 6,000 orders a month with a dedicated fulfillment team.

See which of the eight patterns are in your own data