When setting up order management rules, you might need to set up rules based on the order Packaging.
The different levels of complexity could include:
- Orders with specific or within a range of Weight (total or box, in Lbs or Kg)
- Orders with specific or within a range of Package Count
If you are going to use just one value as part of the condition, use the equals (=) or not equals (<>) operator.
If you are going to define ranges, use the Greater/Less or Greater/Less or Equal than.
This is the order and its Packaging information we will review in this example:
These are a few possible scenarios:
#1 - Apply actions when the order is over/under/at a specific weight
For this technical scenario, a business case could be:
Whenever the order is over 5 pounds heavy, it should rate shop cheap services under the FreeShipping rate shopping group, while if weighing 5 pounds or less, it should rate shop express services with the Express rate shopping group.
That being the case, it would be defined this way.
Greater Than and Equals and Less Than is used, so whenever the Weight value of a carton is over 5 pounds or below, it shifts the services to rate shop accordingly.
This will require the definition of two separate rules, one for the weight over 5 and the other for equals or below.
#2 - Apply actions when the order is over/under/at a specific
For this technical scenario, a business case could be:
Whenever the order is a volume order (5 packages or more), the customer will automatically get a service upgrade with a 2 day service, otherwise, the order should ship with the service that was passed from the WMS.
That being the case, it would be defined this way.
Greater and Equals Than and Less Than is used, so whenever the Package Count value of an order equals or is over 5, it shifts the service to a 2 day service.
AVAILABLE ACTIONS TO BE USED
To review the full set of actions you could apply, read: Order Management Rules (OMR) available actions [Information]
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article