Last-minute order changes: deciding where the cutoff is

A change request is not one thing. Changing the quantity a fortnight out is a note in a system. Changing it the night before, when the materials are bought and the work is half done, is somebody absorbing a cost, and that somebody is usually you.

What decides whether this is manageable is a line: the point in your own process after which a change stops being free. Most small businesses have that line and have never said it out loud, which is why the conversation happens under pressure with a customer who had no idea they were asking for anything difficult.

What we'll cover

• Every change has a cost point
• Finding your own cutoff
• Changes are not all the same size
• Making the cutoff visible before it matters
• Building it with CodeWords
• What an automation must never agree to
• The record of what changed
• Where consumer rights sit
• Preventing the changes you can
• Making it survive
• Limits worth knowing about
• What to decide first
• Frequently asked questions

Every change has a cost point

Trace one order through your process and mark where each cost becomes unrecoverable.

Materials ordered. Stock allocated. A slot in the schedule committed. Work begun. Something personalised. Something finished. Something dispatched.

Before the first of those, a change costs a few minutes. After the personalisation step, a change frequently means starting again. The interesting thing is that these points differ enormously by trade and by product, and customers cannot see any of them.

Which means a customer asking for a change the day before is not being unreasonable. They are asking a question they have no way to answer, and the business that has never told them where the line is has left them to guess.

Finding your own cutoff

It is not a single date. Different elements of the same order lock at different times, and being precise about that is what makes the policy fair rather than blunt.

For a made-to-order product the shape is typically: quantity and specification lock when materials are ordered, personalisation locks when it is applied, and the collection or delivery arrangement can usually move much later than either.

For scheduled work the shape is different: the slot locks when it starts displacing other bookings, and the scope locks when preparation begins.

Go through the last twenty changes you accepted and note which cost you something. The pattern is usually obvious within a few minutes and it is much more specific than a blanket "48 hours' notice" rule, which is either too strict for the easy changes or too lax for the expensive ones.

Changes are not all the same size

Sorting them into three groups makes the automation straightforward.

Free, always. Contact details, the collection time within your opening hours, adding a note. Accept these automatically and confirm. Sending these to a person wastes everybody's time.

Conditional. Quantity, date, specification. Whether they are free depends on where the order is, which the system can determine. Accept where the rules allow, and where they do not, explain what it would involve and get a person to decide.

Never automatic. Anything after a cost was incurred, anything involving a refund or a price change, anything on an order already in dispute.

Most change traffic is in the first group, which means most of it can be handled instantly, which is exactly what customers want and what a person answering on a busy afternoon cannot deliver.

Making the cutoff visible before it matters

Telling somebody about your change policy when they ask for a change is too late. They have already formed an expectation and you are now refusing.

The right moments are earlier and there are three.

At order confirmation. One line saying what can be changed and until when. Not terms and conditions, a sentence.

At the cutoff. A message saying the order is now being made, and that anything needing to change should be raised today. This single message is worth more than any policy wording, because it converts an abstract rule into a concrete prompt at the moment it is actionable.

In the reminder. Whatever you send before collection or delivery can carry the same line.

Businesses that send the cutoff message report the shape of their change requests shifting earlier, which is the entire objective.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which changes are always fine, which depend on the order's stage, and which must reach you.
3. Authorize the connections to wherever orders are recorded and your WhatsApp Business Platform account.
4. Describe the exceptions: an order already in production, one with a cost incurred, a change to something personalised, anything touching money.
5. Send the cutoff message from the start, since it is the part that changes customer behaviour rather than just handling it.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

What an automation must never agree to

Anything that changes the price, in either direction. A customer told a new figure by a system will hold you to it.

A refund or a cancellation with money involved. That is a decision and frequently a legal question.

A change after the cost was incurred, even a small one. Once you accept one without a person seeing it, the rule has no edges.

A date change that displaces something else. The system may not know what the alternative slot cost you.

Anything on an order already in dispute. Route it to whoever is handling that.

The general rule: an automation may accept changes that cost nothing and must escalate anything that costs something. Stated that plainly, it is easy to implement and easy to explain.

The record of what changed

Change requests are where memory and reality diverge, and the disagreement surfaces at collection when it is most expensive.

Record every change against the order itself, not in the conversation: what was asked, when, what was agreed, by whom, and what it cost if anything. Then confirm it back to the customer in a message that restates the order in full rather than just the change.

That full restatement is the part people skip and the part that prevents trouble. "Changed to six" is ambiguous a week later. A short confirmation of the whole order, with the change in it, is not.

Where a change alters the price, get an explicit acceptance before proceeding rather than assuming.

Where consumer rights sit

Worth knowing the shape of, because businesses often either promise more than they need to or refuse things they should not.

Most consumer cancellation rights attach to distance and off-premises contracts and are tightly bound up with whether goods are personalised or made to the customer's specification, which frequently changes the position. A change to an order is also not the same thing as a cancellation, and the two get conflated in these conversations.

What matters operationally is that your written terms say what happens, that the terms were available before the order was placed rather than after, and that anything genuinely in the territory of a cancellation or a refund goes to a person who can check the position rather than to a rule in a flow.

Preventing the changes you can

A share of change requests are caused by the original order being taken badly, and that share is larger than most businesses assume.

Confirm the specification in full at the start, in a message the customer can read back.

Ask the questions that get changed later. If quantity and date are your most changed fields, ask about them more carefully up front.

Flag the things people get wrong. Where customers routinely misjudge a size or a quantity, say so at the point of ordering.

Send the confirmation immediately, while they still remember what they wanted, rather than the next day.

Read your last twenty change requests and ask how many were the customer changing their mind versus the order never having been right. The second group is free to fix.

Making it survive

Keep the cost points current, since a process change moves them.

Send the cutoff message on every order, not just large ones.

Record changes against the order and confirm the whole order back.

Escalate anything touching money, without exception.

Count change requests by type, which tells you what to fix upstream.

Limits worth knowing about

A policy cannot recover an incurred cost, it can only decide who carries it.

Customers cannot see your process, so an unstated cutoff is not a rule they broke.

Blanket notice periods fit badly, being too strict for cheap changes and too lax for expensive ones.

Some changes are genuinely impossible, and saying so early is kinder than attempting them.

Automation does not make a bad policy fair, it just applies it consistently.

What to decide first

Your cost points. Walk one order through and mark where each cost stops being recoverable. Everything else here is downstream of knowing that, and most businesses have never written it down.

Two habits make the difference. Send the cutoff message on every order, because a prompt at the moment a change is still free does more than any policy wording does afterwards. And confirm the whole order back after any change, since the expensive disagreements are always about what the order was rather than about what changed.

Frequently asked questions

How do I set a change cutoff?

Walk an order through your process and mark where each cost becomes unrecoverable: materials ordered, stock allocated, schedule committed, work begun, personalisation applied. Those points are your cutoffs, and they differ by element.

Should there be one deadline for all changes?

No. Quantity, specification and collection arrangements lock at different times, and a single blanket notice period is too strict for the cheap changes and too lax for the expensive ones.

Which changes can be handled automatically?

Ones that cost nothing: contact details, collection time within opening hours, adding a note. Anything conditional on the order's stage can be automated where the rules allow, with escalation where they do not.

What must never be agreed automatically?

Anything changing the price, refunds and cancellations involving money, changes after a cost was incurred, date changes that displace other work, and anything on an order in dispute.

When should customers be told about the policy?

At order confirmation in one sentence, again as a message at the cutoff saying the order is now being made, and in whatever reminder precedes collection.

Does the cutoff message actually help?

It is the single most effective part of this. An abstract policy becomes a concrete prompt at the moment a change is still free, and change requests shift earlier as a result.

How should changes be recorded?

Against the order rather than in the conversation: what was asked, when, what was agreed, by whom and what it cost. Then confirm the whole order back rather than just the change.

What about consumer cancellation rights?

They depend on how the contract was formed and whether goods are personalised or made to specification, and a change is not the same as a cancellation. Make sure terms were available before the order and send anything in refund territory to a person.

How do I reduce change requests?

Confirm the full specification at the start, ask more carefully about the fields that get changed most, flag what customers routinely misjudge, and send the confirmation immediately rather than the next day.

What should I measure?

Change requests by type and by stage. The mix tells you which cutoffs are in the wrong place and which parts of your order-taking are producing avoidable changes.

Related reading

• Taking orders and keeping the record straight
• Keeping a price list true
• The edge cases that actually matter