Use this article when Estimator picks an unexpected press, omits a finishing step, shows duplicate make-readies, or refuses to find any valid combination for a job. After this you will have identified whether the cause is in the substrate row, in a machine's compatibility constraints, or in tag wiring across substrates and machines, and you will know which per-cluster troubleshooting article carries the full fix.
Quick diagnosis table
Symptom | Check (where to look) | Fix (action) | Verify (what you'll see) |
Estimator selects an unexpected press (e.g., digital instead of offset). | Open View estimation path from the price breakdown and read which press the route uses. Open Issue analysis and read the Excluded machines section for the press you expected. | If Excluded machines says "no tag match" for the expected press, add the missing tag to the substrate or to the press. If it says "weight out of range" or "sheet size out of range", correct the value on the substrate or extend the range on the machine. Apply Changes. | Recalculate the quote. View estimation path shows the expected press. Excluded machines no longer lists it for the same reason. |
Unable to calculate estimate with "no valid combinations". | Open Issue analysis on the failed estimate and read the Excluded machines section for every press the shop runs. Confirm there is at least one substrate that fits the job's finished size and weight. | If every press is excluded for the same reason (e.g., "no tag match"), the substrate is missing a shared tag — add it. If presses are excluded for substrate-fit reasons, the substrate dimensions are too small or the weight is outside the machine ranges. See Troubleshoot missing substrate or product. | Recalculate. View estimation path shows a valid route and Excluded machines is empty or only lists machines genuinely outside the spec. |
Finishing step is missing from the route (no fold, no laminate, no bind). | Open View estimation path and read which finishing steps appear. Open the product category's part configuration and read which finishing operations are required. | If the operation is configured on the part but missing from the route, the finishing machine that provides it may be excluded — read Excluded machines for the finishing surface. Add the missing tag or adjust the substrate fit. Apply Changes. | Recalculate. View estimation path now lists the finishing step in the route, and the price breakdown shows the matching line. |
Make-ready appears twice on the same finishing line. | Open the finishing machine record under Estimate Setup → Finishing Machines and read the Included steps section. | If two related operations (e.g., crease and fold) run on the same machine in the same pass but are wired as separate finishing records, configure one as an Included steps entry on the other so Estimator uses the higher make-ready rather than double-counting. Apply Changes. | Recalculate. The price breakdown shows a single make-ready line for the combined operation. |
Route changes after a recent setup edit even though nothing on the quote changed. | Open Estimate Setup and read the Pending Changes count. | If the count is non-zero, open Pending Changes, review the staged edits, and Apply Changes. Recalculate the quote after applying. | The Pending Changes count returns to zero. The recalculated quote uses the edited machine, substrate, or category as expected. |
Example 1 — Stitched Book routes to HP Indigo instead of XL105
Northgate Press quotes a 5,000-run Stitched Book on Silk 100gsm SRA1 (the SRA1 row in the substrates table). The estimator expects the XL105 offset press to win because the run is large enough for offset to be cheaper, but the price breakdown shows HP Indigo instead.
Diagnosis: The estimator opens Issue analysis on the quote. The Excluded machines section lists XL105 with reason "no tag match". They open the SRA1 substrate row in Substrates and the XL105 record in Print Machines. XL105 carries the offset-ok tag in its tag list, but the SRA1 row has no offset-related tag — Estimator therefore excludes XL105 from any route the substrate runs through.
Fix: The administrator opens the SRA1 row in Substrates, adds the offset-ok tag, and selects Apply Changes in Pending Changes.
Verify: The estimator recalculates the quote. View estimation path now shows XL105 as the selected press. Excluded machines no longer lists XL105. The print-line cost drops from the per-impression Indigo price to the per-sheet offset price, and the price breakdown reflects the offset route.
Example 2 — Folded Leaflets route is missing the fold step
Northgate Press quotes a 2,500-run Folded Leaflets job on Silk 115gsm SRA1. The category specifies a six-page tri-fold layout, but the price breakdown shows only print and cut — no fold line at all.
Diagnosis: The estimator opens View estimation path and confirms the fold step is missing from the route. They open Issue analysis and the Excluded machines section lists Folder 1 with reason "no tag match". They open the Folder 1 record under Estimate Setup → Finishing Machines → Folding Step and read its tag list, which includes fold-coated. The SRA1 substrate row does not carry the matching fold-coated tag — so even though the category requires a fold, no folder is compatible.
Fix: The administrator opens the SRA1 substrate row, adds the fold-coated tag, and selects Apply Changes.
Verify: The estimator recalculates the quote. View estimation path now lists the fold step with Folder 1. The price breakdown shows a make-ready and run line for the folder, and Excluded machines no longer lists Folder 1.
What if this didn't fix it?
If Pending Changes is clear, Issue analysis lists no excluded machines for the expected route, the substrate's tags and dimensions match every machine's compatibility constraints, and the route still selects the wrong press or omits a finishing step, the issue is in the calculation logic rather than setup. Open a support request and include: the estimate ID, the expected route (press + finishing steps), the route Estimator actually picked, and the Excluded machines detail from Issue analysis if any. If the symptom started after a substrate import, see Troubleshoot missing substrate or product.