Use this article when a validation quote comes out higher, lower, or different from the reference quote in your matrix, and you need to find which part of setup is responsible. After this you will have located the first step on the price breakdown that diverges from your reference, identified the setup field behind it, and confirmed the corrected quote matches on Recalculate.
How to read the table
Validation quotes go wrong in a small number of predictable places: a wrong substrate cost, a press rate that does not match the shop floor, a finishing machine that picked up the wrong speed or a missing pretrim step, a category markup that fires when it should not, or a pricing rule that did not match. Work top-down: confirm the spec matches the matrix row, then walk the price breakdown step by step and stop at the first line that diverges. The table below pairs each customer-visible symptom with the surface where the cause shows up and the fix that resolves it.
Symptom | Check (where to look) | Fix (action) | Verify (what you'll see) |
The substrate line on the price breakdown is higher or lower than the matrix says it should be. | Open Substrates and find the row used on the quote. Read the Cost field and the unit next to it (per ton or per sheet). | If the unit is wrong, set it to the value that matches how the shop buys the paper. If the cost itself is out of date, update it. Apply Changes. | Recalculate the quote. The substrate line on the price breakdown moves to the value implied by the corrected cost and unit. |
The print line cost is wrong on a press run the matrix expects to be cheap. | Open Print machines and find the press the quote picked. Read the machine rate, plate cost, and speed for the sheet size on the quote. Open Issue analysis on the quote and read the Excluded machines section to confirm the expected press was not excluded. | If a press you expect is in Excluded machines for a setup reason (substrate Position, Tag, or sheet size), correct the matching field on the substrate or product part. If the chosen press has the wrong rate or speed, update it on the press record. Apply Changes. | Recalculate the quote. Issue analysis shows the expected press in use, and the print line on the price breakdown matches the matrix value. |
The cut, fold, or bind line on the price breakdown is wrong, missing, or priced twice. | Open Finishing and find the finishing machine the quote picked. Read its machine rate and output. Open the product category and read Production Steps. | If a step is missing, add it to the product category's Production Steps. If a step is priced twice, open the combined finishing machine and check Included Steps for overlap. If the rate or output is wrong, update it on the finishing machine. Apply Changes. | Recalculate the quote. Each finishing step appears once on the price breakdown with the line cost the matrix expects. |
The quote total is higher than the matrix says even though the production lines look right. | Open the product category used on the quote and read the default category markups. Open the price breakdown and read the Pricing rules applied section to see which rules fired. | If the category markup is too high, lower it on the category. If a customer or category rule fired when it should not have, open Pricing rules and adjust the condition that matched. Apply Changes. | Recalculate the quote. The Pricing rules applied section shows the expected rule set, and the quote total moves to the matrix value. |
A pricing rule the matrix expects to fire never appears in the Pricing rules applied section. | Open the price breakdown on the quote and read the Pricing rules applied section. Open Pricing rules and read the conditions on the rule the matrix expects. | If the rule's conditions do not match the quote's customer, category, or quantity, broaden or correct the conditions. If two rules conflict, set the priority so the expected rule wins. Apply Changes. | Recalculate the quote. The Pricing rules applied section now shows the expected rule, and the quote total reflects its action. |
Short runs match the matrix but long runs come out wrong, or the other way around. | Open the price breakdown for the failing run length and identify the first step whose line cost diverges from the matrix. Open Pricing rules and read any price-table rules that cover this product and customer combination. | Add or tune a pricing rule price table so the markup scales with run length as the matrix specifies. Do not change the press speed to fake margin on long runs. Apply Changes. | Recalculate quotes at both run lengths in your matrix. Each quote total matches its matrix row, and the Pricing rules applied section shows the price-table rule firing on the run lengths where the table applies. |
A new substrate, machine, or rule edit is not reflected on the quote. | Open Estimate Setup and look at the Pending Changes badge in the top bar. | Open Pending Changes, review the staged edits, and choose Apply Changes. | The Pending Changes badge clears. Recalculate the quote. The price breakdown now reflects the edit. |
Worked example 1 — A Stitched Book validation quote comes back too cheap on print
Northgate Press is validating a 5,000-run Stitched Book on Silk 100gsm SRA1 (the row shows as SRA1 in the Substrates table). The matrix says XL105 should print this job, but the validation quote came back about 30% under the matrix value, and the price breakdown shows HP Indigo on the print line.
Diagnosis: The operator opens Issue analysis on the quote and reads the Excluded machines section. XL105 is excluded because the SRA1 row is missing the offset compatibility Tag. The router therefore falls back to HP Indigo, whose digital click cost on 5,000 runs is lower than the offset make-ready it should have used. That is why the validation total comes in below the matrix.
Fix: Open Substrates, open the SRA1 row, and add the Tag the XL105 record requires for offset work. Apply Changes.
Verify: Recalculate the quote. Issue analysis no longer lists XL105 in the Excluded machines section. The price breakdown shows XL105 on the print line, and the print line cost rises to the matrix value for a 5,000-run offset Stitched Book.
Worked example 2 — A folded-leaflet validation quote totals too high
Northgate Press is validating a 2,000-run Folded Leaflets job on Silk 115gsm SRA1 (the heavier of the two SRA1 rows in the substrates table). The matrix expects this job to land at one total, but the validation quote comes in roughly 12% higher. The print, cut, and fold lines on the price breakdown all match the matrix value within rounding.
Diagnosis: The operator opens the price breakdown and reads the Pricing rules applied section. A general 10% margin rule is firing on top of the category's default markup, because the rule's conditions match every Folded Leaflets quote rather than only the customer segment the matrix assumes. The production lines are correct; the over-quote is in the commercial layer.
Fix: Open Pricing rules and open the 10% margin rule. Add a customer condition so the rule fires only on the customer segment the matrix expects, or lower its priority so the matrix-correct rule wins. Apply Changes.
Verify: Recalculate the quote. The Pricing rules applied section now shows the matrix-expected rule set. The quote total drops to the matrix value, and the production lines remain unchanged.
What if this didn't fix it?
If the spec on the quote matches the matrix row, the substrate cost and unit are correct, the expected press is not in the Excluded machines section, each finishing line appears once at the rate the matrix expects, the Pricing rules applied section shows the rule set the matrix assumes, and the quote total still does not match — the issue is in the calculation path itself rather than setup. Open a support request and include: the estimate ID, the matrix row the quote is being compared to, the first price breakdown step where the line cost diverges, the press and finishing machines named on the quote, and the Pricing rules applied section as shown on the price breakdown. If the chosen press is wrong, see Why a print machine is not selected for a quote before opening the request.
Related articles