The product and SKU automation rule triggers match an order on what is in it: which SKUs, how many, and which vendor supplies them. Use them to add a gift for a specific SKU, pick a box for single-item orders, or flag bulk orders. ShipHero has 16 of these triggers: SKU, SKU quantity, two all-items SKU triggers, Product name, Product tag, two vendor triggers, and four line-item count triggers.
Before You Begin
- Vendors: The vendor triggers need vendors assigned to your products. A product with no vendor never matches "All items in the order are from vendor".
- Product tags: The Product tag trigger reads tags saved on the product in ShipHero. A tag added in Shopify appears after the product syncs.
- When rules run: Automation rules run once, when an order is created or imported, and only on orders that arrive after the rule exists. Orders already in ShipHero are not updated.
For every trigger ShipHero offers, see Automation Rule Triggers Reference. To build a rule, see How to Use Automation Rules in ShipHero. If a rule does not run, see Troubleshooting: Why Is My Automation Rule Not Working?
Table of Contents
- SKU and Product Automation Rule Triggers
- All Items SKUs Automation Rule Triggers
- Vendor Automation Rule Triggers
- Line-Item Count Automation Rule Triggers
- Product and SKU Automation Rule Trigger Examples
SKU and Product Automation Rule Triggers
The SKU, Product name, and Product tag triggers match items on the order and use the Text conditions: equals, not equals, contains, does not contain, starts with, not starts with, ends with, not ends with, greater than, greater than or equal to, less than, less than or equal to, in list, not in list, in list contains, not in list contains, in list starts with, not in list starts with, in list ends with, and not in list ends with. SKU quantity uses the Numeric conditions: equals, not equals, greater than, greater than or equal to, less than, less than or equal to, in list, and not in list.
Upper and lower case are treated the same. The SKU, Product name, and All Items SKUs Are triggers check every line on the order, including canceled, fulfilled, and auto-fulfilled lines.
| Trigger | What it checks | What to enter | When it does not fire |
|---|---|---|---|
| SKU | A SKU on any line of the order. ShipHero checks every line, including canceled, fulfilled, and auto-fulfilled lines. | Type the SKU as saved on the product. Upper and lower case are treated the same. | The SKU on the order has a variant suffix or a space that your value does not. |
| SKU quantity | The ordered quantity of the SKU that the SKU trigger matched. | A whole number, such as 2. | The rule has no SKU trigger above it, or the SKU trigger matched no line. Add the SKU trigger first, then SKU quantity in the same rule. |
| Product name | The product name saved on the order line when the order imported. | Type the name as it appears on the order. | The product was renamed in ShipHero after the order imported. The order line keeps the old name. |
| Product tag | A tag saved on a product. Tags can be added in ShipHero or Shopify. | Tags from Shopify start with "shopify tag", so enter shopify tag summer for a Shopify tag named summer. | Your value is missing the "shopify tag" prefix, or the tag was added in Shopify after the product last synced. Shopify tags are cut off at 52 characters including the prefix. A line whose product is not in your catalog is skipped. |
All Items SKUs Automation Rule Triggers
The All Items SKUs Are and All Pending Items SKUs Are triggers match only when every line meets the condition. They use the Text (limited) conditions: equals, not equals, contains, does not contain, starts with, ends with, not ends with, greater than, greater than or equal to, less than, less than or equal to, in list, not in list, in list contains, not in list contains, in list starts with, and not in list starts with.
| Trigger | What it checks | What to enter | When it does not fire |
|---|---|---|---|
| All Items SKUs Are | Every line on the order has a SKU that meets the condition, including fulfilled and canceled lines. | A SKU, or use in list to match a group of SKUs. | One line, even a canceled line, has a SKU that does not meet the condition. |
| All Pending Items SKUs Are | Every pending line on the order has a SKU that meets the condition. Fulfilled and canceled lines are ignored. | A SKU, or use in list to match a group of SKUs. | One pending line has a SKU that does not meet the condition, or no line on the order is pending. |
For an order with three lines where one is fulfilled and two are pending, All Items SKUs Are checks all three lines and All Pending Items SKUs Are checks only the two pending lines.
Vendor Automation Rule Triggers
The vendor triggers match an order on the vendor assigned to its products. Each one uses the Exact match only conditions: equals and not equals.
| Trigger | What it checks | What to enter | When it does not fire |
|---|---|---|---|
| All items in the order are from vendor | Every item on the order is assigned to the vendor you select. On accounts without Multi-Warehouse Allocation, this is the only trigger that requires all items to match. | Select the vendor from the list. | One item has no vendor, or a different vendor. |
| Any items in the order are from vendor | At least one item on the order is assigned to the vendor you select. | Select the vendor from the list. A vendor with no name shows as "No name". | No item on the order is assigned to that vendor. |
A product with more than one vendor matches when any one of its vendors meets the condition. For a kit, ShipHero checks the vendor on the kit SKU, not on its component products. Canceled and fulfilled lines are included.
Line-Item Count Automation Rule Triggers
The line-item count triggers match an order on how many SKUs, lines, or units it has. Each one uses the Numeric conditions: equals, not equals, greater than, greater than or equal to, less than, less than or equal to, in list, and not in list. The four triggers count different things, so choose by what you want to count.
| Trigger | What it checks | What to enter | When it does not fire |
|---|---|---|---|
| Number of unique SKUs | How many different SKUs are still pending on the order. A SKU counts only while it has pending quantity, so the count drops as lines ship. | A whole number, such as 3. | The same SKU on two lines counts once, so an order with two lines of one SKU has a count of 1. |
| Number of pending line items | How many line items are still open. A pending line item has the status pending. Lines in any other status, such as fulfilled or canceled, are not counted. This counts lines, not units. | A whole number, such as 2. | A line with 5 units counts as 1, so use a quantity trigger when you want to count units. |
| Sum of line items quantities | The total units ordered across all lines, including auto-fulfilled products. | A whole number, such as 50. | Units that already shipped still count. Use the pending sum to count only units still to ship. |
| Sum of line items pending quantities | The total units still waiting to ship across pending lines. Canceled and fulfilled lines are excluded. | A whole number, such as 10. | All units on the order already shipped or were canceled, so the sum is 0. |
Product and SKU Automation Rule Trigger Examples
These examples pair a product or SKU trigger with an action. Change the SKUs and numbers to fit your catalog.
| Use case | Trigger | Action |
|---|---|---|
| Flag a bulk order of one SKU | SKU equals WIDGET-1 and SKU quantity is greater than or equal to 10 | Add Warehouse Note |
| Use a small box for single-SKU orders | Number of unique SKUs equals 1 | Set box to use |
| Prioritize large orders | Sum of line items quantities is greater than or equal to 50 | Set priority flag |
| Tag orders that contain a seasonal product | Product tag equals shopify tag summer | Set order tag |