Rules are in ShipHawk composed In ShipHawk TMS, rules consist of two parts: criteria and actions. Both parts are necessary to create a rule in ShipHawk.
Criteria are the conditions that must be met in order to trigger the rule. You can specify multiple criteria per rule in order to automate fulfillment behavior for very specific cases. By default, rules apply to all orders, which will apply to all orders moving forward.
Once triggered by the correct conditions, actions are the changes made by ShipHawk based on the instructions configured in your rule. Actions define what you want to happen to any orders or rates that fulfill your set criteria. You can add multiple actions to one rule. Examples of actions available in ShipHawk are:
...
| Info |
|---|
The multiple criteria and actions provided by ShipHawk’s rules engine function as AND statements. ShipHawk does does not support OR statements. To accomplish this, you must create two different rules. |
...
When creating a rule in ShipHawk, you must understand the hierarchy or order in which ShipHawk applies default settings and rules. The order goes as follows:
Stored default values. ShipHawk will default to using any default values saved in the system given no other contravening instructions.
Specified in the API, or rate request instructions. You can provide instructions in the API rate request to a carrier to, for example, query only one type of service. Results of this rate request overrides the default stored values.
Rules. Any rules whose criteria are met will override specific rate request instructions. If you have a rule instructing certain orders to always use a specific carrier service, this rule will override whatever prices are retrieved by the API request.
Manual changes. Manual changes to an order in ShipHawk supersede all other default settings and rules.
A common issue that customers have when first creating rules is understanding that rules will always supersede rate request results. It is recommended that you carefully audit your rules before enabling.
...
While it is possible to have more than two criteria or actions per rule, it is recommended that you limit the number of each where possible. Simplified, pared down rules are easier to manage, especially when your organization has many rules that it enables for different seasons and events.
If a rule might not be applying as expected, reasons can include the following:
The rule conflicts with another rule. This can be investigated with the Order Audit History function.
Capitalization is not consistent in the rule criteria and the reference in the order.
There might be too many rule actions associated with a particular rule. Try to limit rule actions to two actions per rule.
Prerequisites
To begin using the rules engine to automate decisions about carrier rating, you must first fulfill the following conditions:
Customers must be using ShipHawk for rating on their eCommerce or ERP platforms.
Users must be an administrator or shipping manager role in ShipHawk. Only these two roles have the correct permissions to set up a rating rule.
If you qualify under these conditions, proceed to the following sections for instructions to create and enable or disable rating rules and shipping policies.
...