ShipStation Automation Rules: The Complete Guide (+ 12 Real Examples)

I spent four years running fulfillment out of ShipStation, processing 1,000 to 2,000 orders a day. Automation rules were the single biggest lever I had. Set up well, they quietly do the work of a person — tagging, routing, picking services, adding insurance — before an order ever hits your screen. Set up badly, they silently do nothing, or worse, they fight each other and you don't notice until a customer emails.

This is the guide I wish I'd had on day one: how rules actually work, twelve examples you can copy into your own account today, the limits nobody warns you about, and what to do when a rule genuinely can't reach far enough.

How ShipStation automation rules actually work

An automation rule has two halves: criteria (what an order has to look like) and actions (what ShipStation does to it). An order has to meet all of a rule's criteria for the actions to fire — criteria are AND'd together. If you want "either/or" logic, that's usually two separate rules.

Actions are AND'd too — you can stack several in one rule and every one of them runs. So a single rule can set the service, add a tag, assign a warehouse, and add insurance all at once, as long as the order clears the criteria. That's a lot of leverage from one well-aimed rule.

The single most important thing to understand — and the thing that trips up almost everyone — is when rules run:

ShipStation applies automation rules when an order first enters the Awaiting Shipment or On Hold status. That's it. Rules run once, at import (or when an order is created manually). Editing an order that's already sitting in Awaiting Shipment does not re-trigger your rules.

So a rule isn't a live formula that keeps recalculating. It's a stamp applied once, the moment the order lands. Internalize that and half of the "why didn't my rule work?" mysteries disappear.

If you change a rule and want it to apply to orders already waiting, you have to click Reprocess Automation Rules, which reapplies all active rules to everything currently in Awaiting Shipment. More on that below.

Creating a rule, step by step

The flow is the same every time:

1. Go to Settings → Automation → Automation Rules and click to create a new rule.
2. Add your criteria. Pick a field (Order Total, Total Weight, Ship To Country, Item SKU, Store, and so on), a condition (Equals, Is Greater Than, Is Less Than, Contains), and a value. Add more criteria to narrow it — remember they all have to be true.
3. Add your actions. Set a service, add a tag, assign a warehouse, add insurance. You can stack multiple actions in one rule; each one runs.
4. Save, and mind the order. Rules run top to bottom, and position matters (I'll come back to this — it's the other big gotcha).

That's the whole model. The power is in combining a handful of simple rules into a pipeline that handles your real order mix. A good rule set reads like a checklist your best employee would run through on every order — route it, weigh it, price the service, protect the valuable ones, flag the weird ones — except it happens in the half-second between the order importing and it showing up in your queue.

One habit worth building from the start: give every rule a clear, descriptive name. Six months in, "Insurance $100+" tells you what a rule does at a glance; "Rule 14" tells you nothing, and you'll be afraid to touch it.

12 real automation rule examples

Every one of these uses criteria and actions that exist in ShipStation today. Copy the pattern, swap in your own values.

1. Tag a product line by SKU. Criteria: Item SKU Equals PLANT-4IN. Action: Add Tag → "Live Plant". Heads up — SKU criteria only evaluates on single-item orders, so this is best for products that ship on their own.

2. Route orders to a warehouse by store. Criteria: Store Equals "eBay Store". Action: Set Ship From Location → Secondary Warehouse. Build one rule per store so each channel ships from the right place.

3. Route by destination to your nearest warehouse. Criteria: Ship To State is one of CA, OR, WA, NV, AZ. Action: Set Ship From Location → West Coast Warehouse. Cuts zones and transit time on half your map.

4. Pick a cheap service for lightweight orders. Criteria: Total Weight Is Less Than 1 lb. Action: Set Carrier/Service/Package → your lightweight USPS service. The sub-pound tier is where the savings live.

5. Set a service by destination. Criteria: Ship To Country Equals United States AND Ship To State Equals AK. Action: Set Carrier/Service. Handy for Alaska, Hawaii, and territories where your default carrier gets expensive.

6. Add insurance on orders over $100. Criteria: Order Total Is Greater Than 100. Action: Set Insurance. Important: insurance is carrier-specific, so this rule has to run after the rule that sets the service — otherwise there's no service for the insurance to attach to and the action fails.

7. Require signature on high-value orders. Criteria: Order Total Is Greater Than 500. Action: Set Confirmation → Signature. Cheap protection against "it never arrived" claims on your biggest orders.

8. Handle international orders end to end. Criteria: Ship To Country Does Not Equal United States. Actions: Add Tag → "International", Set Customs Content Type, and Set International Non-Delivery to Treat as Abandoned. One rule that stamps the customs decisions you'd otherwise set by hand on every foreign order.

9. Assign big orders to your best packer. Criteria: Order Total Is Greater Than 300. Action: Assign to User → [your senior packer]. Route the orders you can't afford to get wrong to the person least likely to.

10. Flag heavy orders for a special station. Criteria: Total Weight Is Greater Than 20 lb. Action: Add Tag → "Freight Review". Gives the floor a filter to pull oversized orders before they jam a normal pack line.

11. Force the right box for a known product. Criteria: Item SKU Equals POSTER-TUBE. Action: Set Carrier/Service/Package → Package Type: Tube. Presets the package so nobody has to remember the odd-shaped items.

12. Combine store and weight to choose a service. Criteria: Store Equals "Walmart" AND Total Weight Is Less Than 16 oz. Action: Set Carrier/Service. Channel-specific service selection, exactly the kind of AND logic rules are good at.

The limits nobody tells you about

Rules are great inside their box. The trouble starts when you assume they can do things they can't. Here's where I kept hitting walls:

• They run once, at import — not on edit. This is the big one. If an order is already in Awaiting Shipment and you fix a weight, add a SKU, or change the address, your rules do not re-run against it. You have to click Reprocess Automation Rules to reapply everything to the current Awaiting Shipment queue.

• Rule order is load-bearing, and a broken rule stops the line. Rules process first to last, so a rule that adds insurance must sit after the one that sets the service. And if any rule is saved with blank criteria or a blank action, it fails — and takes every rule after it down with it. One empty rule can silently disable half your automation.

• No external data. Rules only see what ShipStation already knows: order fields, product attributes, tags, addresses. There is no criterion for the weather at the destination, live inventory, or anything from outside ShipStation. You cannot write "if the forecast is below 40°F, add a heat pack."

• No cross-carrier rate comparison inside a rule. A rule can set a service, but it can't compare live rates across USPS, UPS, and FedEx and choose the cheapest one that still hits the delivery date. The decision has to be static — a fixed service tied to fixed criteria.

• SKU criteria only fire on single-item orders. As soon as an order has multiple line items, SKU-based rules stop matching. Multi-item logic needs a different approach.

None of these are bugs. They're the natural edges of a rules engine that only works with the data it holds and only runs at one moment. But if your fulfillment has any real complexity, you will run into them.

Automating past the limits

This is exactly the gap I built ShipExtension to close. It connects to ShipStation through the API and adds the pieces the native rules engine can't reach — mapped straight to the limits above:

• Runs beyond once-at-import. ShipExtension can re-run automation per order off a webhook the moment an order changes, and on a scheduled nightly pass that reconciles anything that slipped through — so you're not manually clicking Reprocess.
• Weather-based heat pack automation. It checks the forecast at the recipient's location and adds heat packs (and adjusts package weight to match) automatically — the external-data decision a rule literally can't make.
• Bulk cross-carrier rate shopping. Instead of a static service, it compares live rates across carriers and picks the cheapest one that still meets your delivery requirement.
• 3D box selection. Real cartonization for multi-item orders — figuring out what actually fits in which box — instead of a single preset package type.
• Retailer packing slips. Compliant slip formats for Home Depot, Macy's, and Lowe's, generated automatically.

The point isn't to replace ShipStation's rules. I still use them for the simple, static stuff — and you should too. It's to have somewhere to go when "run once, no outside data, no rate compare" stops being enough.

Setup habits that kept my rules trustworthy

A few things I learned the expensive way, running this at volume:

• Test with Reprocess, not with a live import. After you build or change a rule, click Reprocess Automation Rules and watch what it does to the orders already in Awaiting Shipment. It's the fastest feedback loop you have, and you don't have to wait for the next real order to find out you got a criterion wrong.
• Read the order activity log. When a rule doesn't do what you expected, the activity log on the order usually tells you which rules touched it and in what order. That's where you catch one rule quietly overwriting another.
• Sequence dependent rules deliberately. Anything that sets a carrier-specific option — insurance, confirmation, a package type tied to a service — belongs below the rule that picks the service. Get the order wrong and the dependent action just fails, often without an obvious error.
• Keep criteria tight. A rule that's too broad is worse than no rule, because it fires on orders you never meant it to and you won't notice until something ships wrong. Start narrow, then loosen only if you're sure.
• Never leave a rule half-built. A rule with blank criteria or a blank action doesn't just do nothing — it stops every rule below it. If you're not ready to finish a rule, delete it rather than saving it empty.

Frequently asked questions

Do automation rules run on existing orders?

Not by default. Rules run once, when an order first enters the Awaiting Shipment or On Hold status at import or manual creation. To apply a new or changed rule to orders already sitting in Awaiting Shipment, click the Reprocess Automation Rules button, which reapplies all active rules to the current queue.

What order do automation rules run in?

ShipStation processes rules from first to last in your list, and the order matters. A rule that adds a carrier-specific option like insurance must run after the rule that sets the service, or it will fail. Also watch for empty rules: a rule saved with blank criteria or a blank action fails and stops every rule after it from running.

Is there a limit to how many automation rules I can have?

ShipStation does not publish a hard cap on the number of automation rules, so in practice the real constraint is managing them: as the list grows, the order of operations between rules becomes the thing that breaks, not the count. Keep rules focused and sequence the dependent ones carefully.

Why didn't my automation rule fire?

Usually one of four things: the order did not meet every one of the rule's criteria, a later rule overrode the change this rule made, the order was already in Awaiting Shipment so editing it did not re-trigger rules, or an upstream rule with blank criteria or a blank action halted the chain. Reprocess the rules and check the order activity log to see what happened.

Where to start

If you're setting up rules this week, start with three or four simple ones, watch the order activity log, and add complexity slowly. That's the difference between automation that quietly saves you hours and automation you can't trust.