Blog · Product Updates
Service Versions: Why a Price Change Shouldn’t Rewrite Your History
What happens to last year’s bookings when you raise balayage from $150 to $175? Here’s how service versions keep each visit at the price it was booked.
· Updated · 4 min read
It's a Tuesday afternoon and you raise balayage from $150 to $175. Your costs went up and your skills did too. What happens to the guests who booked at $150, and to last spring's numbers, depends on how your software stores a booking.
A link or a copy
Some software saves a booking as a link to the service. Change the service and every booking that points at it changes with it: last January's balayage now reads $175, and the totals built on it move too.
The other way is to save a copy of the service with each booking, as it was when the guest booked. Then a price change only touches what comes after it.
How loci does it
loci keeps service versions. Each edit to a service saves a new version holding its price, length, buffer and deposit. Each booking records the price, length and tax it was made with, and which version it came from.
January
Balayage is $150. Maya books for March.
February
You raise balayage to $175. loci saves it as version 2.
March
Maya comes in and her ticket says $150, the price she booked at. A new guest books balayage and sees $175.
Why it matters
- Guests pay what they were quoted. Nobody gets a surprise at checkout.
- The past stays put. Every booking keeps what it cost when it was made.
- You can see the history. Each version is kept, so you can see when a price changed and which bookings came before and after.
Ask your software
Raise a price on a test service, then open an old booking for it. If the old booking shows the new price, your history moves every time your prices do. See how it works in loci on the service versions page.