One of the fastest ways for a small print business to lose money is to treat mid-run changes like harmless customer service.
A buyer asks for a color swap after parts are already started. Another wants a hole moved after the sample looked fine. Someone adds a quantity bump right as packaging begins. None of those requests sound huge by themselves, which is exactly why they do so much damage.
When you absorb change casually, you stop running orders. You start rescuing them.
Core idea
A mid-run change is not just a buyer note. It is a decision that can reset production, invalidate prior work, and spread confusion into packaging, counting, and reorders.
Why small favors become expensive
- the original quote may no longer match the work
- already-made parts may become scrap or awkward partial inventory
- the message trail becomes hard to interpret later
- your bench now has two versions of the same job alive at once
- you teach the buyer that late changes carry no process cost
The real problem is not the request itself. It is the uncontrolled branching it creates in the workflow.
Changes are not equal
A shipping-address correction is not the same as a geometry change. A quantity bump before production starts is not the same as a quantity bump after pack-out has begun.
Strong operators separate changes into clear buckets:
- administrative: contact info, shipping details, or other non-production corrections
- commercial: quantity, rush timing, or other changes that affect price or schedule
- technical: file, fit, material, finish, or hardware changes that can invalidate the baseline
Once you sort the change correctly, the response gets much cleaner.
What needs to happen before you say yes
- identify which work is already complete
- state what the current approved baseline was
- decide whether the requested change keeps or breaks that baseline
- state the effect on price, schedule, and already-made parts
- restart only from a defined new version, not from vague conversation drift
If you skip those steps, the order becomes a moving target and every later dispute gets harder to untangle.
A cleaner response pattern
When a buyer changes something mid-run, a controlled answer usually sounds like this:
The current order is based on version X, material Y, and quantity Z. Your requested change affects the approved baseline, so I need to separate completed work from revised work before I can confirm the updated cost and timing. Once I send that revision clearly, I can resume from the new version.
That is not rigid for the sake of it. It is how you stop one message from rewriting your whole day.
Where sellers get trapped
- they make the change first and price it later
- they do not freeze the prior version in writing
- they keep both old and new parts in the same physical area
- they promise speed before understanding the reset cost
All four feel helpful in the moment and expensive by the end of the job.
Lesson takeaway
Mid-run changes are not customer-service seasoning sprinkled on top of production. They are control events. If you do not isolate them, price them, and restart from a clear new baseline, the order stops being one job and turns into several unpaid ones.
Previous: Lesson 10
Next: Lesson 12
Back to module: Module 3
Back to hub: Masterclass Hub