A wrong label, short fill, poor seal, color miss, or damaged finish can look like a small production mistake when the fix is “just redo it.” The visible replacement material may cost only a few dollars. The real bill can include extra labor, discarded packaging, lost product, another quality review, rush freight, delayed orders, and contribution from units that never become saleable.
Calculating the **cost of rework** turns an irritating exception into a business decision. It shows which problems are quietly draining product margins and which prevention step deserves time first.
Rework is not free just because the team fixes it
Rework is additional effort used to bring nonconforming output back to an acceptable condition. Removing and replacing labels, reopening and resealing packages, remelting a batch, refinishing a surface, correcting a blend, or inspecting every unit after one failure can all qualify.
The correction may preserve inventory, but it still consumes resources the original plan did not require. When owner time or spare materials absorb the work, the expense can remain invisible. A growing product business does not need complex quality accounting; it needs a consistent way to record what one failure consumed.
Use a three-part rework cost calculation
Start with three buckets:
**Direct rework cost = replacement materials and packaging + extra labor + outside fees, freight, disposal, or testing**
**Lost contribution = unsold units × expected contribution per unit**
**Total business impact = direct rework cost + lost contribution + documented delay or penalty cost**
Only include costs supported by what happened. A late batch does not automatically lose a sale. If the customer still buys every unit, record the extra handling or freight but do not invent lost contribution.
The same rule prevents double counting. If a rejected unit’s consumed materials are in direct cost, add its contribution—not its full selling price—to represent the remaining value the sale would have added.
Worked example: forty products with the wrong label
Imagine a 100-unit run. The team discovers that 40 units received an outdated label after the tamper seals were applied. Six containers are damaged during removal and cannot be sold. The other 34 units are corrected.
The incident record shows:
- replacement labels and seals: **$12**;
- consumed product and packaging in six lost units: **$24**;
- 1.5 hours of production labor at $24 per hour: **$36**;
- 0.5 hour of supervisor and quality review at $32 per hour: **$16**; and
- rush shipping for replacement labels: **$18**.
Direct rework cost is **$106**.
Each saleable unit normally provides $9 of contribution after its variable costs. The six lost units therefore represent **$54** in missed contribution.
**Total business impact = $106 + $54 = $160**
The labels themselves were only a small part of the loss. Most of the cost came from consumed work, damaged output, review time, and sales that could no longer occur.
This is a planning example, not a universal rate. Use actual pay rates, landed material costs, acceptable output, and channel contribution from your own operation.
Count time the business really consumed
Rework labor often disappears because the owner handles it after normal production. Include that time at a reasonable replacement or target labor rate. Someone must perform the work as the business grows, and those hours were unavailable for production, sales, purchasing, or rest.
Count all incident-specific work:
- stopping and containing affected units;
- diagnosing what happened;
- removing, cleaning, correcting, or repacking;
- repeating inspections or tests;
- updating inventory and batch records;
- contacting suppliers or customers; and
- restoring the workstation for normal production.
A broader [SKU profit check](https://resources.buildwithkerno.com/is-your-best-selling-product-actually-paying-its-way-a-practical-sku-profit-check/) can show whether recurring rework is weakening a product that otherwise appears healthy.
Record one page for every meaningful incident
A simple rework ticket should capture:
1. product, version, batch or lot, date, and operator; 2. requirement missed and where the problem was detected; 3. quantity affected, corrected, scrapped, held, and released; 4. materials, packaging, labor hours, outside costs, and lost contribution; 5. immediate disposition and approval; 6. likely cause and the earliest point where detection was possible; and 7. prevention action, owner, due date, and verification result.
Keep the original production record intact. Add the correction as an event rather than silently replacing the first result. That history helps the team distinguish a one-time exception from repeated **manufacturing waste**.
Fix frequent and expensive mistakes first
Do not rank problems only by the cost of the latest incident. Use two dimensions:
- **Impact:** direct cost, lost contribution, customer risk, safety or compliance significance, and schedule disruption.
- **Frequency:** how often the same failure or cause appears across runs.
A frequent $30 correction may deserve attention before a rare $200 event. A safety-critical or legally significant failure may require action regardless of the dollar amount. Money informs priority; it does not replace product-specific requirements or qualified judgment.
For ordinary operational problems, total the last 30 to 90 days by cause. Start with one recurring issue that has both meaningful impact and a practical prevention point.
Catch the error before more value is added
The cheapest correction is usually the one made before an entire run receives more labor and packaging. A formula-version check before weighing, first-piece label approval, fill-weight check after setup, seal check before case packing, or color reference before a full pour can contain the reach of a mistake.
Use [simple documented quality checks](https://resources.buildwithkerno.com/simple-quality-checks-every-product-business-should-document/) to place controls where an error becomes expensive if it continues. If the cause is an unclear handoff or judgment boundary, [standardize the dependable parts of production](https://resources.buildwithkerno.com/standardize-production-without-losing-craft/) without flattening intentional craft variation.
Frequently asked questions
What counts as rework?
Rework is additional effort used to correct output so it can meet an approved requirement. Reinspection caused by a failure can also belong in the incident cost.
Should owner time be included in the cost of rework?
Yes. Use a reasonable replacement or target labor rate. Unpaid owner time still consumes capacity and can hide a process that will become expensive when delegated.
How is rework different from scrap or normal yield loss?
Rework is corrected output. Scrap is output or material that cannot be recovered for the intended use. Normal yield loss is an expected, measured part of the process; a preventable mistake should not be hidden inside it.
Should lost revenue be added to the calculation?
Usually use lost contribution for units that will not be sold, because direct cost already includes consumed variable inputs. Add full lost revenue only under a carefully defined method that avoids counting the same cost twice.
What is an acceptable rework rate?
There is no universal percentage for every product. Establish your own baseline by product and cause, then prioritize trends by frequency, financial impact, customer risk, and applicable requirements.
Practical takeaway
Take the most recent meaningful correction and complete one rework ticket. Add replacement materials, packaging, incident-specific labor, outside costs, and only the contribution actually lost.
Then ask one question: **Where could we have prevented this mistake—or contained it before more value was added?**
That answer is more useful than treating rework as the unavoidable cost of a busy week. It turns production mistakes into visible choices and protects the margin your sales were supposed to create.
For a wider review, compare the incident with the [hidden operational costs that appear as a product business grows](https://resources.buildwithkerno.com/the-hidden-operational-costs-of-growing-a-physical-product-business/).
