No shop is free of miswrites. A cashier fat-fingers a price, job items get swapped (a tune-up billed as a scheduled service), a payment is entered twice, a discount is forgotten. These mistakes are normal — what’s not normal is how many shops fix them: edit in place, delete-and-recreate, or leave it for “we’ll remember later.”
Why “just edit it” is expensive
At first glance, editing the wrong number is the fastest fix. The cost arrives later, in three forms:
First, history starts lying. A silently edited receipt no longer tells what happened — only its latest version. When a customer disputes (“yesterday you said 200, why 250 now?”), the shop can’t prove anything, even to itself.
Second, reports lose credibility. If numbers can change without traces, every report figure wears a question mark. Month-end cash gaps become untraceable: mistake, correction, or something else?
Third, a gap opens. The ability to edit without a trail is the same door used by honest error and dishonesty alike. The shop can’t tell them apart — which is unfair, above all, to honest staff.
The healthy standard: four questions answerable
A proper correction is a recorded event. After any correction, the system should answer four things:
- What changed? The old value and the new one — not just the final state.
- Who changed it? The account responsible — which is why one shared login ruins everything.
- When? Date and time.
- Why? The context: an input error, a negotiation, a new agreement with the customer.
With those four answered, corrections change character: from a credibility threat into evidence the shop is run seriously.
Correction ≠ return — and neither means delete
These words get used interchangeably, but the cases differ: a return means the goods came back (value corrected through the return path); a correction means the record was wrong (goods went nowhere). What they share: both resolve as recorded events — and no case is ever correctly resolved by deleting the receipt. The full family map is in returns as the real test.
How this looks in Automan
Important changes land on the activity trail (who-when-what), transaction corrections travel a correction path that recalculates the downstream effects — paid status, reports, even stock when goods are involved — and the right to correct can be limited per role, so not everyone holds an eraser.
The cultural effect is the most tangible one: the team stops fearing admitting mistakes. Because a miswrite corrected properly is finished — not a time bomb waiting to be found at month’s end.
See it alongside its siblings in returns, claims & corrections.