Once an order is downloaded and saved in the system Rules Engine will immediately check if there are any corresponding active rule that should perform an action to the order.


Rules Engine can:

  • Assign a Tag to order
  • Assigns an identifier to the order
  • Assign order extended property
  • Assign order to folder
  • Assign order to location
  • Assign postal service to order
  • Execute a macro
  • Lock order
  • Park order
  • Split order into packages of maximum value
  • Split order into packages of maximum weight
  • Split order into packages of single items

There are few important points about Rules Engine logic that should be clear beforeĀ  you start to create them:


Rules are executed in sequence, from top to bottom of the list. They each have a number in the Order column and execute from lowest to the highest number. This sequence can be changed using arrows.


Conditions inside each rule are also checked in the same sequence, from top to the bottom of the list.



If while the check, the system will identify matching rule it will perform the actions specified in it and will not check further. That is why it is important to set mutually exclusive conditions on the rules. Mutually exclusive means that these conditions cannot occur simultaneously.



  • All of the enabled rules will always run on each order and will overwrite each other if multiple rule conditions are matched.
    • The rule will ignore the order if it is Not Paid or if order source is FBA.
  • Within the rule, condition evaluation will stop as soon as it gets to the first action.
  • Rules can apply multiple actions to a single order as long as the actions are different.




Articles that might be useful:


Testing Rules

Complex Rule examples

Rules Engine - rule did not work on the order [troubleshooting]