ShipStation Automation Rules for Multi-Item Orders: What Works, What Doesn't, and the Fix

If you built a ShipStation automation rule on Item SKU and it never fires on mixed carts, the rule isn't broken. ShipStation's item criteria skip any order with more than one line item. Their answer is product tags. Tags work for a lot of cases and break in a few predictable ones.

Which criteria skip multi-item orders

As of October 30, 2026, ShipStation's Automation Rule Criteria and Actions reference puts the same caution under three criteria, Item Name, Item SKU and Warehouse Location:

Automation Rules using item specific criteria will not apply to orders that have more than one line item in the order. Because of this, we recommend that you add tags to your product records and use the product tag as automation criteria.

Their FAQ, How do I create Automation Rules for Multi-product Orders?, says rules on those criteria "will ignore orders that include more than one product."

• Quantity isn't the trigger. Five units of one SKU is one line item, so the rule applies. ShipStation's criteria list keeps the two apart: # of Line Items is "the number of unique line items in the order - not to be confused with Total Quantity."
• Two Item SKU lines don't make an "A and B" rule. An order with A and B has two line items, so the rule doesn't apply to it.
• Order-level criteria still work. Only the three item criteria carry that caution. Order Weight, Order Total, Total Quantity, # of Line Items and Order Tags don't. ShipStation's FAQ starts there: "In most cases, you can work around this by creating automation rules based on more general criteria, such as Total Weight or the State of the Ship To address."

ShipStation's fix: product tags

That caution already names the fix. From the Order Tags article: tag a product on the Products tab, and "ShipStation will then add the product's tag to orders containing that product when they import into ShipStation." Then you write rules on Order Tags, which don't care how many lines the order has.

The multi-product FAQ uses a clothing store with four tags: shirts, pants, hats and shoes. Its example rules:

• Any order with the shoes tag ships UPS Ground, whatever else is in it.
• Only hats: Order Tags include hats, and Do Not Include lists the other three tags. Those orders ship First Class Mail in a thick envelope.
• Pants and shirts together upgrade to Priority Mail.
• Hats with pants or shirts upgrade to Priority Mail, unless shoes are in the order too.

One detail catches people. Per the criteria reference, several tags in one Order Tags line means any of them. If you need all of them, "each tag should have its own criteria line."

If your logic is "this order contains something from group X," product tags are the right answer.

Where product tags break

A tag says what kind of product is in the order. Nothing more.

• Quantities. A tag is there or it isn't. One shirt and five shirts put the same tag on the order. Total Quantity counts every unit in the order, so "three or more shirts in a mixed cart" has no criterion.
• Products you haven't tagged. The "only hats" rule works by listing every other tag under Do Not Include. A product with no tag adds nothing to the order, so an order with hats and a new, untagged product still matches "only hats." Every new tag also has to be added to every "only" rule.
• Specific SKUs. Tags work at the level you tag. If the rule is about SKU A and SKU B, not shirts and pants, you need a tag per SKU.
• Split shipments. From the Order Tags article: "Currently, split shipments do not inherit the tags from the original shipment." Split a mixed order and the new shipment starts with no tags.
• Bundles. The Product Bundles and Kits article says a bundle's defaults, including service, package and dimensions, apply "when that bundle is the only item on an incoming order and the quantity of that bundle is 1." Add a second product and they don't. The same article says Reprocess Automation Rules "does not apply automation to Product Bundles on existing orders in Awaiting Shipment."

What people ask for

The ShipStation Community idea Allow for automation rules to work on multiple item orders was posted on May 18, 2017. On October 30, 2026 it is still marked Under Review. The first post:

Need the ability for the automation rules to see multiple item orders. So you can create logic that IF it includes this SKU and also this SKU it will process these rules.

A 2022 reply on the same thread sums up the tag workaround: "This isn't a complete solution, but a workaround for the majority of multi-order use cases." ShipStation's community managers still answer with product tags, most recently in July 2026.

How ShipExtension's rules read multi-item orders

ShipExtension connects to ShipStation through the API, reads the full order and checks conditions against every line. No condition skips an order because it has more than one line. These are the conditions that matter here, named as they appear in the rule builder.

• Item SKU, Contains all of. The order has every SKU you list, whatever else is on it. "A and B" is one condition.
• Item SKU, Only contains. Every SKU on the order is in your list. A SKU you didn't list fails it, tagged or not.
• Item SKU, Not In List. None of the listed SKUs is on the order. Pair it with Contains all of for "A and B but not C."
• Item SKU, Contains. Any line's SKU contains the text, so PLANT- matches PLANT-4IN and PLANT-6IN.
• Number of Line Items. How many lines the order has. SKUs you add to Automation Excluded SKUs in settings, like inserts or a free sticker, don't count, so "one product plus a free sticker" reads as one line.
• Product Tags (from catalog), Count of X at least. Each line's tags come from your product catalog, synced from ShipStation. Count of X counts how many lines carry a tag, so "three or more different hats" works.
• Per-Item Product Tag Groups, Every group contains. Every line carries the tag. An untagged product fails it, which closes the "only hats" gap. No group contains is the reverse.

Excluded SKUs apply to line counts and product tag conditions. They don't change Item SKU conditions.

One limit to know up front. Item Quantity is the total units across all lines, like ShipStation's Total Quantity. ShipExtension doesn't count units of one SKU or one tag inside a mixed cart either. Count of X counts lines, not units.

ShipExtension runs alongside your ShipStation rules. It doesn't replace them.

When ShipStation's built-in rules are enough

• Your rules key on order-level fields: weight, total, store, destination, # of Line Items, Total Quantity. Those work on multi-item orders.
• Your item logic is about groups of products, not specific SKUs, every product is tagged, and the tag list rarely changes. ShipStation's FAQ shows how to build it.
• Most of your orders have one line. Item SKU rules do what they say on those.

Look past native rules when you need specific SKU combinations, line counts that ignore add-ons, or a check that every line carries a tag. That's what I built ShipExtension's automation rules for.

Frequently asked questions

Do ShipStation SKU rules work on multi-item orders?

No. As of October 30, 2026, ShipStation says rules using item specific criteria (Item Name, Item SKU and Warehouse Location) will not apply to orders with more than one line item. Five units of one SKU is still one line item, so those orders are fine.

What is ShipStation's workaround for multi-item orders?

Product tags. Tag your products, and ShipStation adds those tags to orders that contain them when the orders import. Rules on Order Tags work on any number of lines, so they handle "contains X," "contains X and Y" and "only X" when every product is tagged.

Where do product tags fall short?

Quantities of one product, products you haven't tagged yet, rules about specific SKUs rather than groups, split shipments, which don't inherit tags, and bundles, whose defaults only apply when the bundle is the only item and its quantity is 1.

Can ShipExtension count units of one SKU in a mixed order?

No. Item Quantity is the total across all lines, like ShipStation's Total Quantity. ShipExtension can count how many lines carry a product tag, check that every line carries one, and match exact SKU combinations.

ShipStation behavior is quoted from its help center and community as of October 30, 2026. Check their current docs before you rely on it.