What are you building?
What are you building?
Built for traffic and time
Members & CommunitySocial EntertainmentDigital EducationMember App DevelopmentMember cards, points and coupons, synced with POSBooking & Registration SystemsOnline booking, scheduling, check-in and eventsCustomers pick a time slot online, book classes with their packages, register and pay for events, join a waitlist when it is full and check in by scanning a QR code. Capacity, cancellation and no-show rules follow how you work, and booking and payment data stay in your own system, connected to membership, POS and payments.
Free requirements review · Reply within 1 business day · NDA available
JoinX experience
If your process is standard, you run one location and the rules are simple, an off-the-shelf booking SaaS gets you started quickly; a custom booking system pays off when the rules are complex, you have several locations or roles, or bookings must connect to your existing membership, POS and payments. Booking SaaS is billed monthly or per booking, capacity, package, waitlist, cancellation and no-show rules are limited to the platform's options, and the data lives on the platform. A custom system is built once: class scheduling, packages, waitlist promotion, cancellation and no-show deductions, QR check-in, and event registration with payments and refunds all follow how you work, the data lives on your own servers, and app or LINE entry points added later share the same admin. For small events or a first trial, LINE or a form can collect sign-ups, but lists and reconciliation are mostly manual.
Real projects Booking, check-in and event work
Below are projects we built and maintain, covering class booking and check-in, on-site scan redemption at events, staff meal pre-ordering, and a sports event app and a multi-brand member portal.
Since 2020Yoga studio operator
A yoga studio management system including class booking and check-in. We have worked together since 2020, releasing up to version nine and adding features such as discount codes.
Since 2025GoodParty
An event platform built around digital business cards. Merchants manage coupon claiming and redemption in the back office, with on-site scanning that verifies coupons in real time and prevents forgery; park tickets were added later.
2026Food-tech company
A meal pre-ordering app for company staff, with the app and web version sharing one back end.
2025Sports association
Development of a sports association's event app.
Automotive group
Rental, car-sharing, charging and other services brought under one membership, connected across brands with single sign-on (SSO).
Since 2020Logistics company
Development of a logistics company's dispatch system.
* Projects without a client name are described by industry under confidentiality agreements.
Features Common booking and registration features
Features can launch in phases. Settle the rules for capacity, packages, cancellations and refunds first, then choose web, LINE or an app as the entry point, so new features never change the rules.
Open slots by service, location and staff, with capacity per slot. Full slots close automatically, so nothing is overbooked.
Timetables and shifts for teachers, coaches or staff, plus class packages, points and expiry dates, deducted automatically on booking.
Customers show a QR code that is scanned on site for check-in or redemption, with attendance and no-shows returned to the admin in real time.
Registration forms, ticket types and capacity, with online payment, cancellations and refunds handled by your rules and attendee lists you can export.
Reminders by SMS, email or LINE before each booking. When someone cancels, the next person on the waitlist is promoted and notified.
Bookings, packages and payments sync with your existing membership system, payment provider and POS through APIs, with no extra copy of the data.
Compare Booking SaaS vs custom booking system vs LINE booking or forms
All three can take bookings or sign-ups. They differ in how detailed the rules can be, where the data lives and whether it connects to membership, payments and POS.
| Aspect | Booking SaaS | Custom booking system | LINE booking or forms |
|---|---|---|---|
| Getting started | Booking SaaS: Sign up and configure | Custom booking system: Built after a requirements review, about 3–8 months | LINE booking or forms: Set up a form or official account and start |
| Rule flexibility | Booking SaaS: Limited to the platform's options | Custom booking system: Capacity, packages, waitlists, cancellation and no-show rules designed around how you work | LINE booking or forms: Mostly simple time slots and fields |
| Cost | Booking SaaS: Monthly or per-booking fees | Custom booking system: One-time build, with a separate maintenance agreement after launch | LINE booking or forms: Often free or low monthly fees, with messages billed by usage |
| Data | Booking SaaS: On the platform, with export options set by the platform | Custom booking system: On your own servers and database | LINE booking or forms: Scattered across forms and chat history, tidied up by hand |
| Check-in and payment | Booking SaaS: Depends on platform features | Custom booking system: QR check-in, online payments and refunds, synced with capacity in real time | LINE booking or forms: Mostly manual roll calls and reconciliation |
| Membership, POS and payments | Booking SaaS: Depends on the platform's integrations | Custom booking system: Connects to your existing membership, POS and payments through APIs | LINE booking or forms: Mostly manual reconciliation |
| Best for | Booking SaaS: Single locations with a standard process | Custom booking system: Complex rules, several locations or roles, and connections to existing systems | LINE booking or forms: Small events or a first trial |
Process How we build it
The screens are not the hard part. Capacity, packages, waitlists and refunds must add up correctly in every exception. Every phase ends with something you can accept.
2–4 weeks
Agree on service and class types, capacity and time-slot rules, packages and points, how cancellations and no-shows are handled, refund conditions, and which system is the source of truth for membership, payments and POS.
Depends on scope
The customer side and the admin are designed together. A clickable prototype is tried by front-desk staff, teachers or event organisers before sign-off.
3–8 months
Front end, admin and APIs for booking, scheduling, check-in and payment are built together and connected to payments, membership and POS. Full slots, cancellations, waitlist promotion and refunds are tested case by case.
Ongoing
Monitor booking, payment and check-in errors, and adjust rules for new classes, locations and events. The same team stays responsible.
Pricing Price ranges
Estimates based on custom system projects in Taiwan in 2026. The final figure depends on the booking and registration rules, the number of entry points (web, LINE, app), the systems to connect and the roles and scope of the admin.
| Scope | Price range | Typical content | Timeline |
|---|---|---|---|
| Requirements review | NT$100k–300k | Review of booking rules, capacity, payments and data flows, producing a comparable spec | 2–4 weeks |
| Single workflow | NT$500k–1M | Either online booking or event registration, with an admin | 3–5 months |
| Mid-sized system | NT$1M–2.5M | Booking, class scheduling, check-in, payments, membership and a multi-role admin, with an app or LINE entry point | 5–8 months |
| Connect existing systems | NT$50k–200k per integration point | Data sync with payments, membership, POS or LINE | Depends on the other system's API |
Payment processing fees, SMS and LINE messages, and cloud hosting are billed by usage. Post-launch maintenance is a separate agreement.
FAQ Common questions
Based on custom projects in Taiwan in 2026: either online booking or event registration with an admin is about NT$500k–1M; booking, class scheduling, check-in, payments, membership and a multi-role admin with an app or LINE entry point is about NT$1M–2.5M; each existing system connected (payments, membership, POS, LINE) is about NT$50k–200k. Payment fees, SMS and LINE messages are extra.
A single workflow takes about 3–5 months and a mid-sized system about 5–8 months, after a requirements review of about 2–4 weeks. The schedule also depends on how complex the rules are, the number of entry points, and whether your payment, membership or POS systems have APIs.
Consider a custom system when the platform's options no longer fit your rules, for example when packages, waitlist promotion, no-show deductions or multi-location scheduling need manual workarounds, or when bookings must connect to membership, POS and payments. With a custom system the data lives on your own servers, and existing customer and booking records can be imported before launch.
Yes. Capacity limits, package and point deductions, expiry dates, waitlist order, cancellation deadlines and no-show deductions can all follow how you work. Each rule is confirmed during the requirements review, and every exception is run through in testing.
Yes. Bookings, packages and payments sync with your existing payment provider, membership system and POS through APIs. Without an API, file exchange or an intermediary database can work, but reliability and maintenance cost are assessed first. Each integration point is about NT$50k–200k depending on the other system's API.
No. Customers can book and register on the web, in LINE or in an app, and all entry points share one booking admin and one set of data. Most start with web or LINE and add an app when customers return often and push notifications are needed.
Related Related services
Get started Start with one booking workflow
No full spec needed. Tell us whether it is class booking, service appointments, event registration or internal booking, what tool you use today, your rules for capacity, packages and refunds, and whether it needs to connect to membership, payments or POS.