Booking system acceptance checklist: 12 tests that tell you whether it actually works
Before a booking system goes live, the happy path always passes — what actually breaks is everything off it. This 12-item test checklist needs no technical background, takes just your phone, and works for both custom builds and monthly SaaS.
Whether you're commissioning a custom build or trialling a monthly system,the happy path will always pass. That's exactly the path the vendor demos for you: pick a service, pick a time, confirm, get a notification.
What actually breaks is everything off that path. And those problems don't show up on day one — they show up on your busiest day.
There are 12 items here. No technical background needed; grab two phones and run through them yourself. We recommend doing it before you pay the final invoice.
1. Race conditions and conflicts
Test 1: Two people tap the same slot at the same time
Take two phones, use two LINE accounts, get to the time-selection step and stop — then tap the same slotsimultaneously.
Correct result: only one goes through. The other immediately sees "this slot was just taken" and returns to the time-selection screen.
Wrong result: both say the booking succeeded. That means the system has no atomic slot locking — and you'll be calling a customer to apologise on the day you're busiest.
Test 2: A slot closes at the exact moment you tap it
Have someone close a slot in the admin panel while you tap it on the front end. The system should block the booking and explain why, rather than writing in a booking you can't actually honour.
Test 3: The same customer books repeatedly
Make three bookings from one account. Does your business allow that? If not, does the system block it? If it does, can you tell from the admin panel that it's the same person?
2. Cancellations and rescheduling
Test 4: When a customer cancels, does the slot go back on sale?
After cancelling, check that slot immediately on the other phone — it should be selectable again.
A system that doesn't release it loses you one slot of business for every cancellation.
Test 5: Does rescheduling create a duplicate?
Move a booking to another time, then check the admin panel: you should see one booking with a new time, not the old one still there plus a new one alongside it.
Test 6: Can an expired booking still be cancelled?
Try cancelling yesterday's booking today — the system should block it. This gap will skew every number in your reports.
3. Reminder notifications
Test 7: Do reminders actually fire?
Set a booking for one hour from now and wait for the reminder. This sounds like a given, but a misconfigured schedule, a wrong server timezone, or a scheduler that dies unnoticed — all three are common.
Test 8: Does it fire twice?
Two identical reminders for the same booking means the scheduler processed it twice. Customers will find your system noisy.
Test 9: Do reminders still fire after a cancellation?
A reminder going out the next day for a cancelled booking is the most awkward failure there is.
4. Your own day-to-day operations
Test 10: Can you change things without an engineer?
Change these yourself: opening hours, service pricing, an unscheduled closure on a given day.
If you can't, every small tweak to this system becomes a maintenance bill. Over time, that usually costs more than building a proper admin panel in the first place.
Test 11: Can you export your data?
Export your customer list and booking records, then open the file and check the fields: name, phone, service booked, time, notes — are they all there?
This matters especially for repeat-customer businesses (beauty, tutoring, aesthetics) —that list is your asset, not the vendor's。
Test 12: Whose name are the accounts registered under?
LINE Official Account, domain, hosting, payment gateway — check each one is registered to you, not to the developer or an agency.
This isn't a feature test; it's an ownership test. Pass the first 11 and fail this one, and you're effectively renting a system that just looks like yours.
Print it and use it as-is
| # | Test | Pass |
|---|---|---|
| 1 | Two people tap the same slot; only one goes through | ☐ |
| 2 | Tapping a slot the moment it closes is correctly blocked | ☐ |
| 3 | Repeat-booking behaviour matches your rules | ☐ |
| 4 | Cancelled slots return to availability | ☐ |
| 5 | Rescheduling doesn't create a duplicate | ☐ |
| 6 | Expired bookings can't be cancelled | ☐ |
| 7 | Reminders fire on time | ☐ |
| 8 | Reminders don't duplicate | ☐ |
| 9 | No reminders after a cancellation | ☐ |
| 10 | You can change opening hours and pricing yourself | ☐ |
| 11 | Customer list exports with complete fields | ☐ |
| 12 | All accounts registered in your name | ☐ |
Why these 12
Because every one of them is the kind of problem youonly discover after launch, and that hurts to fix.
How the screens look, how round the buttons are — you can change that any time after launch. But fixing slot-locking logic means touching the database, a broken reminder scheduler means a rewrite, and accounts registered to someone else means starting the applications over. None of these are "we'll deal with it later" problems.
When we build our own LINE booking systems , these 12 items are our standard internal acceptance process. Take them to any vendor — they apply just as well to systems we didn't build.
Further reading: if you're unsure whether to buy a monthly system or go custom, see six questions that will tell you; to understand where the money goes in a custom quote, see breaking a quote into seven parts; for how requirements differ by industry, see clinics, beauty, restaurants。