Building a Spoilage Allowance Into the Quote, Not Just the Post-Mortem

The Reorder That Didn't Match the First Run

The first run of a 10,000-label job came in fine. Margin looked healthy on the estimated-vs-actual report, the customer was happy, and the job got filed as a reference price for the next order. Six months later the reorder landed — same label, same substrate, same press, same per-label number carried straight over from the original quote. It shipped at a loss.

Nothing on the floor had changed. What had changed was that the first run's actual material consumption — the substrate burned through three colour changeovers, a die adjustment mid-run, and a short web break on colour two — never made it back into the quoting logic. It lived in a job-cost report nobody reopened before pricing the next one. The estimator had measured spoilage perfectly. They just measured it in the wrong place: after the job, instead of before the next one.

This is the gap between tracking waste and pricing for it. A job-cost report tells you what happened on a specific run. A spoilage allowance in label quote form tells the next estimate what's likely to happen again — and prices for it before the press ever starts. By the end of this piece you'll have a method for turning your own waste history into a defensible allowance you can actually defend to a customer who asks why the price went up.

Why a Spoilage Allowance Belongs in the Quote, Not the Post-Mortem

Most small shops have some version of waste tracking. Someone totals up substrate used versus substrate billed at month-end, or a job-cost report flags a run that came in under margin. That's useful — it's the only way to know spoilage is a problem at all. But it's diagnostic, not predictive. It tells you a job lost money; it doesn't automatically change the number on the next quote for a similar job.

A spoilage allowance in label quote form closes that loop. Instead of pricing a job as if the press will run at theoretical efficiency and then absorbing the difference as a surprise, you build a reasonable waste percentage into the estimate itself — sized to the job's actual risk factors, not a flat guess. The job still gets tracked afterward. But now the post-mortem is checking the allowance's accuracy, not discovering a problem that already shipped.

The honest case for this isn't fear — it's recovered margin. A spreadsheet or a one-off quote form will hold whatever number you type into it, right up until a cell is wrong or a reorder inherits last year's assumptions unchanged. An allowance built from your own history is defensible precisely because it isn't guessed; it's observed.

Where Flexo Waste Actually Comes From

Before you can size an allowance, it helps to separate the waste that's structural from the waste that's variable — because they belong in the estimate differently.

Some waste is a fixed cost of starting the job at all: the makeready waste consumed getting registration, colour, and pressure dialed in before good labels start coming off the press. That portion scales with colour count and tends to be fairly predictable once you know your press and crew.

Other waste is variable and job-specific: a web break mid-run, a die that needs a mid-job adjustment, a substrate roll with more splices than expected, a colour that drifts and needs a re-registration partway through. This is the waste that doesn't show up the same way twice, and it's the category most shops under-price because it's genuinely hard to predict for any single job.

The spreadsheet remembers the price. It doesn't remember why the last run ran short.

Both categories belong in the quote. Makeready waste usually belongs as a near-fixed component tied to colour count and press setup. Variable spoilage belongs as a percentage allowance sized from your own run history — which is the part most quoting workflows skip entirely.

Turning Waste History Into a Defensible Percentage

The only honest way to size a variable spoilage allowance is to look at what your shop's jobs have actually consumed versus what was billed — broken down by cause, not just totaled. A single blended "we usually run 5% over" number feels precise but hides the real story: a shop's waste is rarely uniform across job types. Short runs with frequent colour changes spoil differently than long runs on a stable substrate. Jobs on a newer die behave differently than jobs on a die nearing end of life.

This is where a Pareto breakdown of waste causes earns its keep — it tells you which 20% of causes are driving most of the lost substrate, so your allowance can be sized against the actual risk profile of the job in front of you, not an average across everything you've ever run. A shop that's logged enough jobs to see "web breaks on narrow substrates" or "colour drift past 10,000 impressions" as a recurring pattern can price those jobs differently than a straightforward two-colour reorder on a stable stock.

If your shop doesn't yet have that history organized, that's the starting point, not a reason to skip the allowance. Even a rough log — cause, job type, waste quantity — run for a few months gives you more to price from than a number pulled from memory. For a structured way to start capturing waste by cause instead of just a monthly total, our Waste & Spoilage Tracker by Cause is built for exactly this: a worksheet that separates makeready waste from variable spoilage and tags each entry to a cause, so the pattern becomes visible before it becomes a lost-margin surprise.

A Worked Example: Building the Allowance Into the Per-Label Number

To make this concrete, here's a simplified worked example — round numbers, illustrative only, not a claim about what any shop should expect.

Suppose a 4-colour job quotes at a run length of 10,000 labels. The press-speed curve and per-colour plate cost produce a baseline cost per thousand labels of, say, $38.00 before any waste allowance. Say this shop's waste history shows that jobs with this colour count and substrate type have historically run with variable spoilage — beyond the makeready waste already built into the press-speed math — averaging somewhere in a 3-5% range of good labels produced, driven mostly by colour drift and the occasional web break.

Taking the midpoint of that range as a working allowance, 4%, the estimator adds a waste reserve: 10,000 labels × 1.04 = 10,400 labels' worth of substrate priced into the job, even though only 10,000 ship. That reserve is folded into the per-label number before the quote goes out — not discovered as a shortfall when the actual job consumes 10,380 labels of substrate to deliver 10,000 good ones.

The job still gets tracked against actual consumption afterward. If it comes in under the 4% allowance, that's useful data for tightening the next similar quote. If it comes in over, that's useful data too — maybe this substrate or this die needs a higher allowance going forward. Either way, the number in the quote was reasoned from history, not assumed from hope.

Putting the Allowance Where the Quote Can See It

None of this works if the allowance lives in a separate spreadsheet tab that the estimator has to remember to check. It needs to sit inside the same calculation that already builds the per-label cost from press speed, plate cost, and makeready waste — so it's applied consistently, every time, without relying on memory.

FlexoCommand's flexo quoting engine already builds the per-label number from a press-speed curve by colour count, per-colour plate cost, makeready waste, die amortisation, and MSI substrate pricing — the structural costs. A spoilage reserve sized from your own history is the natural next line to add on top, so the quote reflects not just what the press should do in theory, but what jobs like this one actually tend to do in practice.

If you're still pricing reorders off a remembered number from the last job, or discovering spoilage only when a margin report flags a loss, start with the label job estimating checklist to see where an allowance fits in the quoting sequence, and look at what's actually driving waste on the floor before you size the percentage. Then pull a copy of the Waste & Spoilage Tracker by Cause and start logging — a few months of cause-tagged entries is enough to turn a guess into a number you can defend. If you want to see how a structured allowance sits alongside the rest of the cost build, FlexoCommand's pricing page outlines what's included at each tier.