System-supplied validations for pricing

The following validations are supplied as part of system factory setup. They are generally invoked when the price of an order is calculated.

Note:
In the validations that are listed, not configuring validation overrides results in disallowing all coupons. The only two exceptions are:
  • Limit the coupons taken in a transaction against an item, and
  • Too many coupons taken in a transaction
With these validations, not configuring overrides results in all coupons being allowed.

If the overrides framework or a domain is not configured, or if override rules are not configured for a given validation, then you will get default (non-override) behavior for that validation. The only exception is the coupon grace period violation; in that case, the grace period defined in the validation rule is honored even if no override rule is configured.

Limit the coupons taken in a transaction against an item

This validation requires a validation rule and override rules.
  • Description: This validation is used to limit the number of coupons that can be applied to an item, a category of items, or a combination of items. For example, a business might want to prevent extreme couponing by specifying a limit on how many coupons a customer can use.
  • If validation overrides are configured as:
    • Allow - All coupons are applied, a violation is recorded if validation rule is violated, and no hold is applied.
    • Disallow - All coupons are applied, a violation is recorded, and a hold is put on the order.
    • Allow with approval - All coupons are applied, a violation is recorded, a hold is put on the order pending approval.
  • If validation overrides are not configured: All coupons are allowed. No violation is recorded and a hold is put on the order.

Too few matching items sold

This validation is system-defined; it requires override rules only.
  • Description: This validation is used when the number of items that are required to qualify for a discount is not met. For example, if the coupon specifies that a customer who buys five cans of soup can get 20% off, buying four cans causes the override rules to be evaluated.
  • If manager overrides are configured as:
    • Allow - The coupon is applied, a violation is recorded if validation rule is violated, and no hold is applied.
    • Disallow - The coupon is not applied, no violation is recorded, and no hold is applied.
    • Allow with approval - A hold is put on the order, a violation is recorded, and the coupon is applied pending approval
  • If validation overrides are not configured: The coupon is not applied, no violation is recorded, and no hold is placed.

Coupon minimum purchase is not satisfied

This validation is system-defined; it requires override rules only. One valid target item must be present in the order for the override rules for this validation to be evaluated.
  • Description: This validation is used when the minimum purchase amount condition is not satisfied. For example, a coupon specifies 10% off, providing that the customer spends $100. An override must be used if the customer spends only $99 and wants the coupon to be honored.
  • If validation overrides are configured as:
    • Allow - The coupon is applied, a violation is recorded if the validation rule is violated, and no hold is applied.
    • Disallow - The coupon is not applied, no violation is recorded, and no hold applied.
    • Allow with approval - A hold is put on the order, a violation is recorded, and the coupon is applied pending approval.
  • If validation overrides are not configured: The coupon is not applied, a violation is recorded, and no hold applied.

Too many coupons taken in a transaction

This validation requires a validation rule and override rules.
  • Description: This validation is used to limit the number of coupons that can be applied to an order. If the number of coupons is greater than the number configured in this rule, then override rules for this validation are evaluated.
  • If manager overrides are configured as:
    • Allow - All coupons are applied, no violation is recorded, and no hold is applied.
    • Disallow - All coupons are applied, no violation is recorded, and a hold is put on the order.
    • Allow with approval - All coupons are applied pending manager approval, a violation is recorded, and a hold is put on the order.
  • If validation overrides are not configured: All coupons are allowed. A violation is recorded and a hold is put on the order.

Coupon expired

This validation requires a validation rule. In this case only, it is not necessary to define an override rule.
  • Description: This validation defines a grace period and approval conditions (if any) for when to allow a coupon that is outside the grace period. If a coupon is expired or not yet in effect, it requires a manager override for the coupon to be evaluated against an order.
  • If validation overrides are configured as:
    • Allow - The coupon is applied, a violation is recorded if the validation rule is violated, and no hold is applied.
    • Disallow - The coupon is not applied, no violation is recorded, and no hold is applied.
    • Allow with approval - A hold is put on the order, a violation is recorded, and the coupon is applied pending approval.
  • If validation overrides are not configured: Coupons dated within the grace period defined in the validation are honored; those dated outside of the grace period are not. No violation is recorded and no hold is put on the order.

External coupon validation disallows coupon

This validation is system-defined; it requires override rules only.
  • Description: This validation is used to allow, disallow, or allow with manager approval any coupons that are not allowed by external validation. If a coupon is disallowed by this validation, then override rules are evaluated.
  • If validation overrides are configured as:
    • Allow - The coupon is applied, a violation is recorded if the validation rule is violated, and no hold is applied.
    • Disallow - The coupon is not applied, no violation is recorded, and no hold is applied.
    • Allow with approval - A hold is put on the order, a violation is recorded, and the coupon is applied pending approval.
  • If validation overrides are not configured: The coupon is not applied, no violation is recorded, and no hold is put on the order.

Coupon excluded by mutual exclusivity

This validation is system-defined; it requires override rules only.

  • Description: This validation is used to define approval conditions when mutual exclusivity rules prohibit the use of a coupon. For example, a customer might have two coupons that cannot be used with each other.
    • If validation overrides are configured as:
      • Allow - The coupon is applied, a violation is recorded if the validation rule is violated, and no hold is applied.
      • Disallow - The coupon is not applied, no violation is recorded, and no hold is applied.
      • Allow with approval - A hold is put on the order, a violation is recorded, and the coupon is applied pending approval
    • If validation overrides are not configured: The coupon is not applied, a violation is recorded, and a hold is put on the order.