SaaS costs a few hundred a month — why spend six figures on a custom build?

The difference is how many operating rules the tool can absorb. SaaS assumes one person per slot. Add shared equipment, staff qualification limits, or prepaid session deduction and you patch the gaps with labour, which usually costs more than half the build each year.

Do I have to charge deposits for online bookings?

Not necessarily. Start with a card authorisation without capture, or a NT$200 to 500 deposit, and state that cancellation is free up to 24 hours ahead. Volume typically dips 5 to 8% while no-shows fall from 12% to under 3%.

Can a booking system be built in phases?

Yes. Phase one is the slot engine plus LINE reminders, around NT$120,000 over eight weeks. Add deposit payments and reporting in phase two once the core is stable.

How to Build an Online Booking System: Slot Engine, No-Show Deposits, and LINE Reminders

1. When Phone Booking Becomes the Bottleneck

A salon with three stylists fields 40 calls a day: 18 bookings, 9 reschedules, 5 asking "anything free today?" At 2 minutes 40 seconds per call, that is 1.8 hours of labour burned daily. No-shows hurt more: a 12% weekend no-show rate means an empty 90-minute colour slot costs NT$2,800, and six a month is NT$16,800 gone. A booking system is not "a form on a page" — it answers who owns the slot, when it locks, and who pays for a no-show.

2. Good Fit vs Poor Fit

Custom fits when:

Resources are two-dimensional or more: staff x equipment x room, and any collision kills the booking
Service durations vary widely: a 40-minute cut versus a 180-minute perm needs dynamic slot calculation
You take 300+ bookings a month, or the front desk spends over an hour a day scheduling
You need deposits, prepaid session deduction, or a link to an existing membership or POS system

Do not build custom when:

You are a solo practitioner with simple slots — Google Calendar appointment scheduling is enough
You take fewer than 100 bookings a month with no deposit or conflict needs
Your service menu changes weekly and the business model is unsettled
Nobody checks the admin panel daily, so bookings arrive and go unanswered

3. Alternatives Matrix

Option	Annual cost NT$	Strengths	Weaknesses
Google Forms + spreadsheet	0	Live today	No double-booking prevention, no reminders, no deposits
Offshore SaaS (Calendly etc.)	6,000–30,000	Mature, zero maintenance	No Taiwan payment gateways or LINE binding, data held offshore
LINE Official Account + plugin	12,000–60,000	No app download needed	Thin conflict logic, shallow reporting, vendor lock-in
Custom build (ScriptWalker)	150,000–260,000 first year	Written to your rules, you own the data	High upfront cost, 8–12 weeks

The formula: (monthly hours handling bookings x hourly wage + monthly no-show losses) x 12 > 60% of first-year custom cost. For the salon above, NT$360,000 against NT$180,000 settles it.

4. The Build, Phase by Phase (8–12 Weeks)

Week 1 — Rules audit: interview front desk and stylists to capture invisible rules (15-minute cleanup buffer after a perm, apprentices cannot take colour jobs alone, two staff on Wednesdays). Tool: Notion. Deliverables: resource matrix and service duration table.
Weeks 2–3 — Flow design: map six steps — pick service, staff, slot, enter details, pay deposit, get confirmation. Tool: Figma. Deliverables: clickable prototype and mobile-first wireframes.
Weeks 4–7 — Slot engine: the heart of the project. Business hours, exception calendar, buffer times, resource conflict locks, on Laravel, with reminder queues following the official Laravel Task Scheduling docs. Deliverables: availability API and concurrency test report.
Weeks 8–9 — Payments and notifications: ECPay for deposits, LINE Messaging API for confirmations and reminders, SMS fallback, with optional sync via the Google Calendar API so staff see shifts on their phones.
Weeks 10–12 — Soft launch: release 20% of slots for real load, run the front desk in parallel for two weeks, monitor with UptimeRobot and Sentry. Deliverables: training recordings and a go-live checklist.

5. Full Cost Breakdown

One-time build (ScriptWalker Booking & Scheduling System Development starts at NT$120,000):

Requirements and rules audit: 15,000–30,000
UI/UX design including mobile: 20,000–40,000
Slot engine and conflict locking: 45,000–80,000
Deposit payment integration: 15,000–25,000
LINE binding and three-stage reminders: 20,000–35,000
Admin reporting and permissions: 15,000–30,000

Recurring costs people forget:

Card processing: around 2.75% per domestic transaction plus a per-order handling fee; see the official ECPay fee schedule
LINE Official Account: the mid-volume plan moves to NT$1,000 a month with 3,000 free messages from 1 November 2026, extras charged per message — see the LINE Biz-Solutions 2026 pricing announcement
SMS fallback: NT$0.8–1.2 per message, triggered only when LINE push fails
Hosting and backups NT$800–3,000 a month; domain about NT$500 a year, SSL free via Cloudflare
Annual maintenance: 15–20% of build cost, roughly NT$20,000–48,000

6. Client Expectation vs Reality

Clients assume	What actually happens
It is just a form, two weeks	The form takes two days; concurrency locks and exception calendars eat 40% of the hours
I explain the rules once and you get it	Front desk and owner differ on about 30% of rules; alignment takes three sessions
Customers will just start using it	Online share sits near 35% for two months; it needs front-desk prompting and a LINE rich menu
Deposits will scare customers away	Volume dips 5–8% while no-shows fall from 12% to under 3% — net revenue rises

7. Six Traps and How to Avoid Them

Front-end filtering as the safeguard: same-second submissions double-book. Fix: a unique index on (resource, start time) plus transactional locking.
No buffer time: the previous client is still at the basin while the next waits. Fix: per-service pre- and post-buffers.
Business hours hard-coded: a holiday closure needs an engineer. Fix: an exception calendar the manager edits directly.
One reminder on one channel: a missed message equals a no-show. Fix: three pushes — on booking, one day before, two hours before — LINE first, SMS fallback, automatic retry.
Manual edits with no audit trail: nobody can say who changed what. Fix: log user, timestamp, and before/after values on every change.
Cancelled slots never recirculate: gaps stay empty. Fix: a waitlist notifying the first in line within 60 seconds.

8. Success Metrics and the 90-Day Roadmap

Day 30: booking completion rate (target > 65%), share booked online (> 35%), source mix. Action: remove the field with the worst drop-off.
Day 60: slot utilisation, average lead time, cancellation rate. Action: off-peak discounts and opening the waitlist.
Day 90: no-show rate (< 5%), revenue per stylist, return rate. Action: automated follow-up when a package expires, and deposit fine-tuning.

9. Decision Checklist

☐ Do I need to lock staff plus equipment or a room at once?
☐ Do service durations vary by more than 2x?
☐ Do I take more than 300 bookings a month?
☐ Does the front desk spend over an hour a day on bookings?
☐ Is my no-show rate above 8%?
☐ Do I need online deposits or session deduction?
☐ Do I need to link an existing membership or POS system?
☐ Do two or more branches share one rule set?
☐ Can I write out my hours and exception rules in full?
☐ Have I named a daily admin-panel owner?
☐ Can my first-year budget reach NT$150,000?
☐ Am I comfortable with an 8–12 week build?
☐ Do I already have a LINE Official Account to bind?

Eight or more ticked and custom pays for itself. Fewer than five, run SaaS or a LINE plugin for three months first.

10. FAQ

I already have a LINE Official Account — do I still need a booking system?

LINE solves reach, not scheduling. It has no idea whether stylist three is free or who is using the equipment. Connect the two: LINE as entry point and reminder channel, the system as the slot authority.

SaaS costs a few hundred a month — why spend six figures on custom?

The difference is how many operating rules the tool absorbs. SaaS assumes one person per slot. Add shared equipment, qualification limits, or session deduction and you patch the gaps with labour — a year of which usually costs more than half the build.

Do I have to charge deposits?

Not necessarily. Start with a card authorisation without capture, or a NT$200–500 deposit, and state that cancellation is free 24 hours ahead. Volume dips slightly, no-shows drop sharply, and the net is positive.

Can this be built in phases?

Yes. Phase one is the slot engine plus LINE reminders, around NT$120,000 over eight weeks. Add deposits and reporting once it is stable, after validating that customers will book online.

11. Next Step

To check whether this is worth doing, take our free 30-minute consultation: we run the decision formula with you, map your resource matrix, and name the three traps you are most likely to hit. If it is not a fit, we will say so. ScriptWalker's Booking & Scheduling System Development starts at NT$120,000, covering requirements planning, the slot engine, LINE binding, and staff training.