Automation rules run on every order that imports into ShipHero. Each rule pairs a trigger, which is the condition ShipHero checks on the order, with an action, which is the change ShipHero makes when that condition is true. This page lists all 58 triggers you can build an automation rule on, the operators each one accepts, and the article that documents it.
To build a rule, go to How to Use Automation Rules in ShipHero. Any trigger on this page can be paired with any action. For the actions, see Automation Rule Actions Reference.
Table of Contents
Available Automation Rule Triggers
ShipHero has 58 automation rule triggers, grouped below by the article that documents them. Every trigger works with any action. Triggers marked Multi-warehouse only require Multi-Warehouse Allocation and run only after your Multi-Warehouse Allocation rules finish.
How Automation Rule Trigger Conditions Work
Each trigger accepts one of nine condition sets. The Conditions column in each table below names the set a trigger uses. Match that name to this table to see the operators available.
| Condition set | Operators available |
|---|---|
| Text | 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, not in list ends with |
| Text (limited) | 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, not in list starts with |
| Text (basic) | equals, not equals, contains, does not contain, starts with, ends with |
| Numeric | equals, not equals, greater than, greater than or equal to, less than, less than or equal to, in list, not in list |
| Numeric (limited) | equals, greater than, greater than or equal to, less than, less than or equal to |
| Yes or No | yes, no |
| Exact match or list | equals, not equals, in list, not in list |
| Exact match only | equals, not equals |
| Time comparison | greater than, greater than or equal to, less than, less than or equal to |
Address and Customer Automation Rule Triggers
Match on where the order is going and who placed it. Address triggers read the shipping address on the order, not the billing address. For each trigger's value format, what it checks, and when it does not fire, see Automation Rule Triggers for Address and Customer.
| Trigger | Conditions |
|---|---|
| Address 1 | Text |
| Address 2 | Text |
| City | Text |
| Company | Text |
| Country | Text |
| State | Text |
| Zipcode | Text |
| Shipping and billing address 1 match | Yes or No |
| Shipping and billing Zip match | Yes or No |
| USPS Zone | Numeric |
| Text | |
| Phone Number | Text |
Products and SKUs Automation Rule Triggers
Match on what is in the order: which SKUs, how many, and which vendor supplies them. For each trigger's value format, what it checks, and when it does not fire, see Automation Rule Triggers for Products and SKUs.
| Trigger | Conditions |
|---|---|
| SKU | Text |
| SKU quantity | Numeric |
| All Items SKUs Are | Text (limited) |
| All Pending Items SKUs Are | Text (limited) |
| Product name | Text |
| Product tag | Text |
| Number of unique SKUs | Numeric |
| Number of pending line items | Numeric |
| Sum of line items quantities | Numeric |
| Sum of line items pending quantities | Numeric |
| All items in the order are from vendor | Exact match only |
| Any items in the order are from vendor | Exact match only |
Order Details Automation Rule Triggers
Match on the order's own labels: its number, store, profile, status, box, and sales channel. For each trigger's value format, what it checks, and when it does not fire, see Automation Rule Triggers for Order Details.
| Trigger | Conditions |
|---|---|
| Order number | Text |
| Store Name | Text |
| Order Profile | Text |
| Fulfillment Status | Text (limited) |
| Box Name | Text (limited) |
| Order Partner Source Name | Text (basic) |
Date and Time Automation Rule Triggers
Match on when the order imported, in your account time zone. For each trigger's value format, what it checks, and when it does not fire, see How to Use Date and Time Triggers in Automation Rules.
| Trigger | Conditions |
|---|---|
| Order date and time | Numeric |
| Day of Week (0:Sun, 1:Mon, etc) | Numeric |
| Time of Day (HH:MM[am/pm]) | Time comparison |
Order Value, Size, and Weight Automation Rule Triggers
Match on what the order costs and how big and heavy its products are. For each trigger's value format, what it checks, and when it does not fire, see Automation Rule Triggers for Order Value, Size, and Weight.
| Trigger | Conditions |
|---|---|
| Order Total | Numeric |
| Subtotal | Numeric |
| Sales tax | Numeric |
| Shipping price | Numeric |
| Total weight of products in the order in ounces (oz) | Numeric |
| Products Total Cubic Inches | Numeric |
| Any product dimension in inches | Numeric |
| All product dimensions in inches | Numeric |
Shipping Automation Rule Triggers
Match on how the order will ship. These three triggers read different values and are not interchangeable. For each trigger's value format, what it checks, and when it does not fire, see How to Use Shipping Triggers in Automation Rules.
| Trigger | Conditions |
|---|---|
| Shipping carrier | Text |
| Shipping method | Text |
| Shipping name | Text |
Customer Order Count Automation Rule Trigger
Match on how many previous orders the customer has placed. For each trigger's value format, what it checks, and when it does not fire, see How to Use Customer Order Count in Automation Rules.
| Trigger | Conditions |
|---|---|
| Customer orders count | Numeric |
Order Tag Automation Rule Trigger
Match on a tag on the order. For each trigger's value format, what it checks, and when it does not fire, see How to Use Order Tags in ShipHero.
| Trigger | Conditions |
|---|---|
| Order Tag | Text |
Existing Hold Automation Rule Triggers
Match on a hold that is already on the order. Pair a Has trigger with a Set action to release a hold automatically. For each trigger's value format, what it checks, and when it does not fire, see How to Manage Order Holds with Automation Rules.
| Trigger | Conditions |
|---|---|
| Has Address Hold | Yes or No |
| Has Fraud Hold | Yes or No |
| Has Operator Hold | Yes or No |
| Has Payment Hold | Yes or No |
Multi-Warehouse Allocation Automation Rule Triggers
Match on where inventory was allocated or back ordered. These triggers require Multi-Warehouse Allocation and run only after your Multi-Warehouse Allocation rules finish. For each trigger's value format, what it checks, and when it does not fire, see How to Use Automation Rules with Multi-Warehouse Allocation.
| Trigger | Conditions | Multi-warehouse only |
|---|---|---|
| All items allocated to warehouse | Exact match or list | Yes |
| Any item allocated to warehouse | Exact match or list | Yes |
| No items allocated to warehouse | Exact match or list | Yes |
| Any item back ordered to warehouse | Exact match or list | Yes |
| Order Has Backordered Products | Yes or No | Yes |
| Allocated Warehouse Count | Numeric (limited) | Yes |
Location Automation Rule Triggers
Match on where an item is assigned. For the Shopify location trigger, see How to Use Shopify Locations as an Automation Rule Trigger.
| Trigger | Conditions | Multi-warehouse only |
|---|---|---|
| Shopify item assigned to location | Exact match or list | No |
| Item bin location | Text | No |
Trigger Details That Affect Whether Your Automation Rule Fires
The article linked in each trigger group above covers the value formats, setup requirements, and rule order for its triggers. Item bin location is the one trigger without its own article, so its limitation is here.
Item Bin Location Automation Rule Trigger
Important
The Item bin location trigger is unreliable unless a SKU is only ever stored in one bin. Slotting moves inventory between bins, so an item that matched the bin in your rule yesterday may not match it today. Keeping every SKU restricted to a single bin takes enough manual work that this trigger is not recommended for most accounts.
If a rule is built but not running, see Troubleshooting: Why Is My Automation Rule Not Working?