Use this article when Estimate Setup is configured and you need to confirm the shop can quote real work before estimators rely on the tool for live customers. After this you will know what setup validation is, what "good enough" looks like, and how to walk a category through routing, production cost, and commercial price checks.
What setup validation is
Setup validation is the structured testing phase between completing Estimate Setup and using Estimator to quote production work. It is a check on three things together: that the route Estimator picks is the right press and finishing path for the spec; that production cost on each step is in an acceptable band against the shop's own reference; and that the commercial price after markups and pricing rules is one the team can stand behind. The surface for validation is the same Estimator quote screen the estimators use, opened from Manage Estimates in the sidebar.
Validation is not spreadsheet-parity with the shop's legacy MIS on every line. Spoilage, rounding, imposition, and pretrim logic differ between systems, so exact matches are uncommon and not the goal. Step-level agreement inside a documented percentage band is the goal.
What "good enough" means
Validation compares four things to a shop reference (an MIS export, a spreadsheet, or a printed sample quote):
Press and route — what production path Estimator picks; visible in the route options and the print lines of See price breakdown.
Paper cost — substrate cost on the breakdown vs the shop's expected paper cost for the chosen sheet.
Cut, fold, and bind times — the make-ready and run times Estimator computes vs the operator log on the equivalent job.
Total sell price — the price after markups and pricing rules vs the price the shop would have offered.
Each category gets its own acceptable percentage band, agreed with the finance lead. A band of ±3% on the total at the category level is typical; tighter bands are reasonable on simple flat work and looser bands on bound work where imposition and finishing logic differ more between systems.
A worked example
Northgate Press wants to validate the Stitched Book category before the estimating team uses the tool live. The agreed band is ±5% on the total at 1,000 / 5,000 / 25,000 copies. The reference is the shop's current spreadsheet price.
The validation sequence runs like this:
The implementation lead opens Manage Estimates → Create new estimate, picks the configured Volume Customer, and enters the Stitched Book spec for 1,000 copies (A4 portrait, Silk 100gsm SRA1 cover).
Estimator calculates. The lead opens See price breakdown and notes the route (XL105 offset), the substrate cost, the make-ready and run times on Print, Cut, Fold, and Stitch steps, and the bucket totals. Quantity is changed to 5,000 and then 25,000 and the same fields are recorded each time.
The lead opens the shop's reference spreadsheet for the same spec at the same three quantities and compares the totals. The 1,000 quantity is 4% high; the 5,000 quantity is within band; the 25,000 quantity is 7% high — outside the band.
The lead opens the price breakdown for the 25,000 quote and finds the Make-ready row on Stitch is twice the operator-log value. The Stitcher 1 configuration shows the wrong make-ready hours; the lead corrects the configuration, Applies Changes, and re-runs the 25,000 quote.
The 25,000 total now sits inside the ±5% band. The Stitched Book category passes validation at all three quantities.
The audit trail — what was queried, what diverged, what the fix was — lives in the validation comparison matrix the lead is keeping. See Create validation quotes for the matrix shape and Setup validation checklist for the per-category sign-off list.
What this affects
Confidence to go live. Validation is what tells the estimating team a category is safe to quote on live work.
Setup that needs follow-up. Categories that fall outside the band point at a specific layer to fix: substrate price, machine speed, conditional-step assignment, bucket markup, or a pricing rule.
The validation comparison matrix. This is the shop's record of what was tested and the outcome per quantity. It is the artifact the implementation team and the finance lead refer back to.
What this does not affect
Production routing or finishing logic. Validation reads the route but does not change it. If the wrong press is picked, the fix is in production setup or in tag compatibility, not in validation.
Live pricing rules. Pricing rules continue to fire on validation quotes. The lead can temporarily zero category markups to compare production cost in isolation (see step 3 in Create validation quotes) but the production rules stay live until the implementation team explicitly disables them.
Quote-level manual adjustments. A manual nudge on a single quote does not affect setup validation; validation is read against the default-configured price.