Skip to main content

Why a pricing rule did not apply

Use this article when a pricing rule you expected to fire is missing from the price breakdown, or fired with the wrong adjustment.

S
Written by Styrbjörn Holmberg

Use this article when a pricing rule you expected to fire is missing from the price breakdown, or fired with the wrong adjustment. After this you will know which condition or action caused the miss, and how to make the rule run as designed.

Symptom guide

Symptom

Check (where to look)

Fix (action)

Verify (what you will see)

No rule listed in Pricing rules applied on the breakdown

Open the quote's See price breakdown modal and scroll to the Pricing rules applied footer. Open the rule editor for the expected rule and compare each If condition to the estimate fields (customer, category, quantity, sheet size, dates).

Adjust the failing condition — usually a quantity threshold or a missing customer/category match. Apply Changes through Pending Changes.

Recalculate the quote. The rule appears in the Pricing rules applied footer and the adjusted bucket markup or target is reflected in the row above.

Rule exists but is inactive

Pricing Rules list — read the Status column on the rule row.

Set Status = Active. Apply Changes.

Recalculate the quote. The rule now appears in Pricing rules applied.

Wrong adjustment applied

Open Pricing rules applied and read which rule fired. Check the priority order in the Pricing Rules list.

Reorder rules so the intended rule runs first. Apply Changes.

The intended rule now appears at the top of the Pricing rules applied list and its action is reflected in the markup/target rows.

Expected rule shows in the list but a later rule is ignored

Open the earlier-listed rule and read its Action. A Set value action stops further pricing-rule processing for that target.

Split the actions across rules: use Increase/Decrease for nudges, reserve Set value for the final override. Apply Changes.

Both rules now appear in Pricing rules applied; each contribution is visible in the bucket-markup or target rows.

Price unchanged after rule activation

Open the quote totals area and look for a manual markup or manual price adjustment on the quote.

Clear the manual adjustment on the estimate.

Recalculate. The rule's effect is visible on the totals; manual adjustments no longer override the rule.

Expected price tier did not match

Open the rule editor and read the Price table thresholds (Min/Max quantity rows).

Edit the threshold values so the quote's quantity falls inside the intended row. Apply Changes.

Recalculate the quote. The Price table line matches the row whose range covers the quoted quantity.

Pricing Rules entry not visible in Estimate Setup

Estimate Setup sidebar — confirm the Pricing Rules section is visible.

Confirm the tenant entitlement for pricing rules. If the entitlement is enabled but the editor is missing, raise a support request.

The Pricing Rules section appears in the sidebar; the rules list is editable.

Example 1 — A volume discount rule never fires

Northgate Press has a rule that should decrease the Machine markup by 5 percentage points when a Volume Customer orders ≥5,000 copies of any Stitched Book. A 6,000-copy quote for a known Volume Customer shows the default markup; the rule does not appear in Pricing rules applied.

Diagnosis: open the quote's See price breakdown modal — the Pricing rules applied footer is empty. Open the rule editor and read the conditions. The Customer condition is set to the customer tag Volume Customer; the Quantity band is set to Min 5,000, Max blank; the Category condition is set to Stitched Book. Reading the quote, the customer carries the correct tag and the category is Stitched Book — but the quantity field reads 5000 on the quote (a number, not a band match), and the Min field on the rule was last edited as 5,001 by mistake.

Fix: open the rule editor, change Min to 5,000, Save, and Apply Changes through Pending Changes.

Verify: recalculate the quote. The rule appears in Pricing rules applied. The Machine bucket-markup row shows the nudged percentage. The Final price drops by the expected amount.

Example 2 — A second rule is silently ignored

Northgate Press has two rules. Rule A Set value sets VA per Press Hour = €150/h for one customer; rule B Increase by percentage adds 2% to the Labor markup for all quotes ≥ 5,000 copies. The customer's 5,000-copy quote shows VA per Press Hour = €150/h but the Labor markup is unchanged.

Diagnosis: open Pricing rules applied. Only rule A is listed. Rule A's Set value action stops further pricing-rule processing for the VA-per-press-hour target, but rule B adjusts a different target (Labor markup). The Pricing Rules list shows rule A above rule B; the priority and the Set action together suppress rule B.

Fix: open the Pricing Rules list, move rule B above rule A, Save and Apply Changes. Rule B is now evaluated first and increases Labor markup before rule A sets the VA per Press Hour target.

Verify: recalculate the quote. Both rule B and rule A appear in Pricing rules applied. The Labor markup shows the 2-point nudge and the VA per Press Hour target stays at €150/h.

What if this didn't fix it?

If the conditions match the quote, the rule is active, the priority order is correct, and no manual adjustment is in the way, the issue is in pricing calculation logic rather than setup. Open a support request and include: the estimate ID, the printhouse identifier, the rule ID (visible in the rule editor URL), the customer, the category, the quantity, and what you already tried. See Why a price model step is missing from a quote when the problem is a step that is not appearing rather than a rule that is not firing.

Related articles

Did this answer your question?