A price updated in one place and left stale in three others is a fault the customer finds first. A price update process with one source of truth and an effective date.
Key takeaways
- A price living in five places will diverge within two months, reliably.
- One source of truth is not "the system" but a defined file or field with an owner.
- Every price change needs an effective date, or there is no answer to what was correct yesterday.
- Open quotes are honoured to their expiry - decide that in advance, not during an argument.
- Consumer prices in Israel are displayed including VAT; mixing them with pre-VAT B2B prices is a permanent source of errors.
In a small business a price usually lives in five places: the website, the till, the price-list spreadsheet, the quote template, and the head of whoever answers the phone. An update happens in one or two of them and the rest stay stale - until a customer points at the gap, which is almost always how it gets discovered.
How to tell prices have already diverged
You do not have to wait for a customer. Three checks of a few minutes each will say so immediately: open the website and compare three items against the price list, open a quote sent this month and compare it, and ask whoever answers the phone what a given item costs without letting them look it up.
The third check is the most revealing, because it measures the price customers actually hear. In businesses where the price list is not easily reachable, the phone answer is the price from before the last update - and that happens even when every digital channel is immaculate.
Why it always diverges
Not because anyone is careless, but because the update is made from wherever the problem was noticed. Somebody saw the website price was too low and fixed the website; the till stayed. A week later the price list sent to customers was fixed; the website is now right, the till still is not.
The fix is not "be more careful" but reversing the order of operations: you do not update a channel, you update a price - and then push it to every channel in the same action.
One source of truth: what that means in practice
A source of truth is the place every other place takes from. It needs three properties:
- Identified - everyone knows which it is, without asking.
- One owner - one person is allowed to change it.
- Logged - every change leaves a date and a name.
In a business without an ERP this can be a single Google Sheet, and that is perfectly fine - as long as nobody updates a price anywhere else. The problem is never the tool but the number of sources, as described in manual price lists versus website quotes.
Map the channels once
| Channel | Who updates it | How the price gets there | The risk |
|---|---|---|---|
| Website / store | Site owner | Export or manual | Most often forgotten |
| Till / POS | Store manager | Usually manual | Discovered in front of a customer |
| Customer price list | Sales | A file that is sent | Old versions sitting with customers |
| Quote template | Sales | Typed by hand | Easiest to get wrong |
| Marketplace | Whoever opened the account | Export or manual | Usually has no defined owner |
| Phone answers | Everyone | From memory | Only fixable by training |
The last row cannot be connected technically, which is precisely why the price list has to be reachable by whoever answers - one page, not a file somebody has to hunt for.
The effective date field saves most arguments
A price change with no effective date creates a question with no answer: an order that came in yesterday - at which price? So every change should carry the date it takes effect, and the previous price should stay recorded.
In practice that is a row in a sheet or a field in the system: item, old price, new price, effective date, who approved. Five columns that end the recurring "but I was quoted something else" conversation.
What happens to quotes already out
The right decision is to honour a quote to the expiry printed on it, which means every quote needs a written validity date in the first place. A quote with no expiry is an open-ended commitment, and it comes back months later exactly when prices have risen.
What a price change should trigger: pull the open quotes still in validity, decide whether to notify the customer, and make sure the system will not invoice at the new price against a quote accepted at the old one. The logic of generating quotes from the system rather than from Word is in quotes from the system, not Word.
VAT display: the quiet trap
A price shown to a consumer in Israel includes VAT, while a B2B price list is usually given before VAT. A business selling to both audiences is effectively holding two numbers for the same item, and most pricing errors come from somebody copying the wrong one between channels.
The way to prevent it is to store exactly one number in the source of truth - preferably pre-VAT - and let each channel compute its own display. The moment both numbers are stored by hand side by side, they will diverge. This is an operational description only; for tax liability questions, the Israel Tax Authority or your accountant is the source.
What a price update that works looks like
- Decide the price and record it in the source of truth with an effective date.
- Mark the channels from the map that need action.
- Update them all on the same day, not over a week.
- Check each one - open the website, scan at the till, open a new quote.
- Check open quotes and decide what happens to them.
- Record that it was done, so it can be audited later.
Step 4 is the only one that actually verifies anything. An update not checked in the channel itself is an assumption, and in accumulated experience at least one channel did not save.
Who should own pricing?
One person, even in a business of three. Not because others do not understand pricing, but because multiple updaters is exactly the mechanism that splits prices apart. Ownership covers three things: update the source, push to the channels, verify it landed.
Where the owner sets prices but does not touch systems, separate the two roles explicitly: who decides and who executes. Confusing them produces a state where the price was decided but exists nowhere - which in practice looks identical to a price that was never updated.
Sources
Frequently asked questions
How often should prices be updated?
It depends on the business, but a fixed window beats rolling changes. A quarterly or half-yearly update window lets you change every channel in one action and notify customers once, instead of a drip nobody tracks.
What if a supplier raises a price mid-month?
Update the cost immediately so margin stays accurate, and the selling price at the next update window - unless the gap wipes out the margin, in which case it is an exception and should be recorded as one.
Should customers be told about a price change?
Regular customers and subscribers, yes, and in advance. That is also what prevents the call where somebody discovers the new price from an invoice, and that call costs more than the notice.
How do you verify prices really are consistent?
Once a quarter, pick ten items at random and check them in every channel. A ten-minute check finds what broke, and in a business that has never done it, it almost always finds something.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.