ShipStation Automation: What It Does and Where It Stops
ShipStation automates more than most people who own it are using. It also has real boundaries, and they're structural — they follow from what the rules engine is, not from features nobody got around to building. This page covers both halves: what it handles, and where it stops. We've cited ShipStation's own documentation throughout so you can check any of it.
Last updated . ShipStation ships changes regularly; if something here has gone stale, tell us and we'll fix it.
What it handles
ShipStation's automation is a static IF/THEN engine layered over product defaults, service mapping, and live rate shopping. For a great many shipping operations it is completely sufficient, and it's worth knowing what you already have before you go looking for something else.
- Can ShipStation rate shop across carriers automatically?
-
Yes. Rate Shopper pulls live rates from your connected carriers and applies the winner, using a Cheapest, Fastest, or Best Value strategy — or a custom configuration on higher plans. It runs per shipment or automatically via the Set Rate Shopper rule action.
It's more thoughtful than people expect. Service Preferences let a preferred carrier win when it's within a cost threshold of the cheapest. Delivery time constraints restrict eligible services by carrier transit estimate, counted in business days from the day after ship date. Available for US, UK, Canada, Australia, and New Zealand accounts; plan-gated.
- Can ShipStation pick a service based on weight and destination?
-
Yes, and it's the most common rule people build. Total Weight, Country, State, City, zone, order value, and residential-vs-commercial classification are all available as criteria, and none of them carry the single-line-item restriction that trips up SKU-based rules.
The classic pair — Ground Advantage under 16 oz, Priority above — takes about five minutes to set up and covers a large share of domestic volume for a lot of brands.
- Can rules react to which products are in an order?
-
Yes, via tags — and this is the most underused capability in the product. Tag a product record and ShipStation applies that tag to any order containing it at import, before any automation runs. Same for customer tags. Rules keyed to tags work on orders of any size.
Tags also chain: a rule can apply a tag that later rules use as criteria, which gives you a workable classification pass followed by an action pass. Combined with order-level criteria like total weight, this covers most of what people initially reach for SKU criteria to do.
- Can ShipStation split orders into separate shipments automatically?
-
Yes, when the rule is a property of the product. Auto-Split creates separate shipments based on settings you configure per product: Exclusive Bulk Shipping, Ships Individually, or Ship on Custom Quantity.
Exactly right for an oversized item that always ships alone, or products that ship a fixed number to a box. Plan-gated (High Volume for US/Canada/ANZ, Enterprise for UK/EU, or an add-on) and doesn't apply to manual orders.
- Can ShipStation choose which warehouse fulfills an order?
-
Yes. Auto-Routing determines fulfillment based on which warehouses stock the items and which is closest to the recipient. Available for US and Canada accounts on the High Volume plan.
You can also set Ship From Location per store with a basic rule, if your routing logic is simply 'Shopify orders ship from the main warehouse.'
- Can ShipStation hold orders and flag exceptions?
-
Yes. Hold Until moves an order out of the queue until a date you set — the standard pre-order pattern. Rules can also create alerts, add internal notes, set custom fields, assign users, add insurance, and flag dry ice with a declared weight.
The tag-and-alert pattern is genuinely useful for anything the engine can't decide: identify the order, flag it, let a person handle it. That's a legitimate automation strategy, not a failure.
How the engine behaves
Most of what surprises people follows directly from the engine being static and evaluating once. None of this is a defect — it's the shape of the thing.
- Do automation rules re-run when an order changes?
-
No. Rules fire once, when an order first enters Awaiting Shipment or On Hold. ShipStation's documentation is explicit that changes to orders already in Awaiting Shipment do not trigger rules.
Reprocess Automation Rules re-applies them manually to everything in Awaiting Shipment, but it deliberately skips order weight adjustments — so reprocessing and importing aren't equivalent events.
- What order does ShipStation automation run in?
-
Auto-Split and Auto-Routing, then Preset Groups, then Product Defaults, then Service Mapping, then Automation Rules last. Within rules, ShipStation processes your list top to bottom, and later rules override earlier ones.
This is why rules have dependencies you manage yourself: service before insurance, dimensions before Rate Shopper, a tag before any rule keyed to that tag.
- Can automation rules use OR logic?
-
Only inside a single criterion. Multiple values within one criterion are OR (semicolon-separated for typed values). Separate criteria lines are always AND. There's no OR across lines and no nesting.
So (A AND B) OR (C AND D) becomes two rules, and you own the sequencing and override interactions between them. Fine at five rules. Harder to reason about at fifty.
- Why did all my automation rules stop working at once?
-
Most likely a rule with a blank criteria or blank action. ShipStation fails that rule and every rule below it in the list, with no warning.
Reading what's in an order
Tags cover more ground here than most people realize. What they can't carry is the one thing packing decisions need.
- Why do my SKU-based rules only work on some orders?
-
The Item Name, Item SKU, and Warehouse Location criteria only evaluate orders with a single line item. Multi-item orders are skipped. The same caveat applies to Saved Filter criteria keyed on those fields.
ShipStation support has confirmed the engine can't parse multiple SKUs when it runs. The documented answer is product tags, and it's a good answer — see the capabilities section above.
- What can't product tags do?
-
Tags give you set membership, not the bill of materials. A tag says FRAGILE is in the order. It can't say whether that's one wine glass or nine, or what each item's dimensions are.
Which is exactly what every packing decision needs. You can't cartonize from a tag — fitting items in a box requires knowing which items, how many, and how big.
- Can automation rules do calculations?
-
No. Criteria compare a field to a value you typed. The engine can't compute density or dimensional weight, can't compare two fields to each other, and can't sum across line items.
- Can automation rules use data from outside ShipStation?
-
No. Criteria read fields already on the order record. There's no action to fetch a forecast, query an ERP, or check anything external.
This is the limit behind most cold-chain requirements: the right packaging depends on the forecasted temperature at the destination at ship time, which isn't on the order.
Packing
Choosing a box for an arbitrary set of items is a computational problem, not a rule — and it needs SKU dimensions ShipStation doesn't own.
- Does ShipStation do cartonization?
-
No. Cartonization solves for the smallest package that fits every item in an order. ShipStation's rules apply assumptive logic you wrote in advance — 'if 3 products, use box X' — which works for a narrow catalog and degrades as SKUs and package types multiply.
- Can ShipStation apply the right package dimensions automatically?
-
For single-item orders with stable packaging, yes — via Product Defaults, and it works well. For multi-item orders with mixed sizes, no. Item-count rules approximate it; accuracy falls as composition varies.
- Why can't I apply a custom package without setting a carrier?
-
The Set Carrier/Service/Package action sets all three together. The alternative, Set Package Dimensions, applies dimensions but leaves the package name off the order — which breaks anything downstream that reads it.
- Can ShipStation split an order across multiple boxes automatically?
-
Not by fit. Auto-Split handles it when the rule is a product property (see above). But deciding how to divide an order that doesn't fit in one box — and building the multi-package shipment — isn't automatable. ShipStation support has confirmed there's no rule action to create multi-package shipments.
Split Ship, Auto-Split, and multi-package shipments are three different features that get conflated constantly, and only one of them is automatic.
Rates
Rate Shopper does real work. Its boundary is architectural rather than a setting you've missed.
- Can ShipStation compare flat-rate programs against standard rates?
-
No. Rate Shopper takes the package as an input — ShipStation's setup docs require the dimensions rule to run before the Rate Shopper rule. Since flat-rate programs require packing into the carrier's box, eligibility is decided upstream of rating, and a box you didn't pack into can't win on price.
These misses are invisible. Rate Shopper reports a win every time, because it correctly found the cheapest service for the box you handed it. There's no report line for the box nobody considered.
- Why didn't Rate Shopper pick the service I expected?
-
It only chooses from services you made eligible in the rule. An economy option that would have arrived in time can't win if it isn't in the set. Delivery time constraints help, but only within what you pre-selected — and a service the carrier returns no transit estimate for drops out entirely.
- Can automation rules pick the cheapest service without Rate Shopper?
-
Only by approximation. Rules don't query live rates, so you're encoding assumptions about weight and zone that go stale when carrier rates change or an unmodelled surcharge applies.
- Why is my carrier bill higher than the rate I was quoted?
-
Fuel, residential delivery, oversize and overweight handling, address corrections, and delivery-area surcharges are applied after the fact and often aren't reflected in a base-rate comparison.
Business-specific logic
Rules specific enough that no horizontal platform would reasonably build them.
- Can ShipStation hold orders based on inventory levels?
-
Not against live stock with FIFO sequencing. You can hold on a tag or a date, but checking whether stock actually covers an order — and holding rather than shipping out of sequence — needs logic that reads inventory at import time.
- Can ShipStation batch by multiple criteria at once?
-
Native batching handles straightforward grouping well. Most warehouses batch by several dimensions at once — zone, cutoff, priority, carrier, product — in a combination that only makes sense given their physical layout. That part usually gets assembled by hand.
- How do I set Purolator's confirmation with automation rules?
-
Confirmation options are carrier-specific, and Purolator's aren't obvious in the rules UI.
If you've hit one of the boundaries
There are three honest options, and two of them aren't us. You can simplify until the rules fit — fewer box sizes, fewer services, more assumptive logic, which is the right answer more often than vendors like to admit. You can accept the manual work, because at low volume a person handling exceptions is genuinely cheaper than software. Or you can add a layer above ShipStation that reads the full order, does the calculation, and writes the decision back before your warehouse sees it.
String is the third one. We sit above your ShipStation account — nothing gets rerouted, and your team keeps the screen they already know. Tell us what you're trying to do and we'll tell you which of the three you actually need, including when the answer is that ShipStation already covers it.