Skip to main content

Order rule action - ValidatePricing

How the Validate Pricing order rule action automatically checks for missing or invalid pricing on order items and flags orders that need attention.

Tom Higgs avatar
Written by Tom Higgs
Updated over a week ago

The ValidatePricing order rule action is an automated quality control feature that helps you identify orders containing items with missing or invalid pricing information. When this rule runs on an order, it checks every item in the order to ensure proper pricing has been set, helping you catch potential billing issues before orders are processed.

  • Param Value: (Blank)


What the Validate Pricing rule does

When the Validate Pricing rule is triggered, the system automatically examines each item in the order and checks whether the item price is greater than zero. If any items are found with a price of zero or less, the system takes action to flag the order for your attention.

How the validation process works

The validation process follows these steps:

  1. The rule examines all items in the order.

  2. For each item, it checks if the price is set to zero or a negative value.

  3. If any items have invalid pricing (zero or negative), the system automatically adds a tag called Invalid-Pricing to the order.

  4. If all items have valid pricing (prices greater than zero), the rule completes successfully with a confirmation message.


What happens when invalid pricing is found

When the rule detects items with invalid pricing, it automatically tags the order with Invalid-Pricing. This tag makes it easy for you to:

  • Quickly identify problematic orders in your order list by filtering for the Invalid-Pricing tag.

  • Set up alerts or notifications for orders that need pricing attention.

  • Create workflows to route these orders to specific team members for review.

  • Prevent orders with pricing issues from progressing through your fulfilment process.


When to use the Validate Pricing rule

This rule is particularly useful in scenarios such as:

  • Orders imported from external systems where pricing data might be incomplete.

  • New product launches where pricing hasn't been fully configured.

  • Promotional or special orders that require manual price verification.

  • Integration testing to ensure pricing data is flowing correctly from your sales channels.

  • Quality assurance checks before orders enter the fulfilment workflow.

Did this answer your question?