Skip to main content
PandaCodeGen.

Booking / Small business websites

Adding Online Booking to a Small Business Website: Plugin, Builder or Custom

When a scheduling tool is enough, when your website builder's booking app is, and when a booking system has to be custom. With the real before and after from a training business we rebuilt.

By Hassan Jamal, Co-founder and Lead Engineer

Published

If you take one-to-one appointments, a scheduling tool such as Cal.com or Calendly is enough. If your site is on Wix, its own Bookings app is the shortest path. If a booking has to trigger fees, dates, a venue, certificates and staff records, it needs a custom build. The deciding question is what has to happen after someone clicks Book.

We build the custom kind, so we say where a cheaper route is the right one. Tool details below come from each vendor's own page, read on October 2026. Plans and prices change, so check the source before you buy.

Which booking route fits which business?

Online booking routes for a small business website, from each vendor's own page, October 2026
RouteFitsTaking payment, per its own page
Cal.comAppointments and calls with one person or a small teamFree plan accepts Stripe and PayPal; Teams is $12 per user per month on yearly billing
CalendlyThe same, with a wider set of integrationsNot on the Free plan; Stripe and PayPal from Standard
Wix BookingsSites already built on WixNeeds a Premium plan to accept online payments
WordPress booking pluginSites on WordPress that want booking inside the pageDepends on the plugin. Check its payment and email features before you install it
Custom buildClasses, courses or events where a booking sets off other workWhatever you build: we used Stripe on the page itself

When is a scheduling tool or builder app enough?

A scheduling tool is enough when the thing you sell is a time slot. A customer picks a time, you get a calendar entry and an email, and nothing else has to change. A hairdresser, a consultant and a tutor all fit. The tool books the slot and a person handles the rest.

Your website builder's own booking app is the next-simplest choice if your site already lives on that platform. You avoid a second login and a second bill, though you inherit the builder's plan limits, which is why the payment rules in the table matter.

When does a business need a custom booking system?

Custom starts to pay off when booking is the first step of a longer process. If each booking has a fee that depends on the course, a seat limit per class, a venue, a confirmation that states all three, and a record the team uses afterwards, a calendar widget can't carry it. You end up copying details by hand between tools, which is the cost you were trying to remove.

What does a real before and after look like?

A Step Above Medical, a medical training business, ran its old WordPress site with an enquiry form. The team replied by email and sent each student a Stripe payment link. Certificates were made by hand. The owner confirmed those details on 21 October 2026.

We rebuilt the site with Next.js and a Sanity editor, and built a separate operations portal on Supabase. Students now book a class and pay by Stripe on the website. The system sends the booking emails automatically with the fees, dates and venue, and the portal issues certificates from a PDF template we designed. The full case study has the before and after table.

The point for your own decision is the shape of the work, not the brand names. Before, every booking needed a person to read an enquiry, write a reply and send a payment link. After, the booking, the payment, the emails and the certificate follow from one action by the student. A scheduling tool would have covered the calendar part and none of the rest.

What should you ask before you pick a route?

  • Does a booking only need a time, or also a price, a seat count and a location?
  • Who sends the confirmation email today, and what does it contain?
  • What does your team do with each booking afterwards, and can the tool do that step?
  • Does payment happen through a processor such as Stripe, so card details never sit on your own site?
  • What do the plan and the payment fees cost each month at your booking volume?

Where we fit

If a scheduling tool covers you, use one. If your bookings feed fees, emails, certificates or staff records, we build that kind of system on custom engineering, and it can connect to the tools you already use. For the other costs around a site, see the monthly running cost guide. To talk through your own bookings, send us a note.

Common questions

What is the easiest way to add online booking to a website?
Use a scheduling tool such as Cal.com or Calendly and embed or link it from your site. It works for one-to-one appointments and calls, and it takes an afternoon rather than a project.
Can I take payment when someone books?
Yes, on most routes, but the plan matters. As of October 2026, Calendly shows payments as unavailable on its Free plan and lists Stripe and PayPal connections from the Standard plan, and Wix says you can add Wix Bookings for free but must upgrade your site to a Premium plan to accept online payments. Cal.com lists a free plan for one user with unlimited event types that can accept Stripe and PayPal payments, and a Teams plan at $12 per user per month on yearly billing.
When do I need a custom booking system?
When booking is only the first step: class seats, fees that depend on the course or location, confirmation emails with dates and venue, certificates, or staff records that must match what was booked. A scheduling tool books a time slot and does not know about any of that.
Is a booking plugin or app safe for a business that takes card payments?
Payments should go through a processor such as Stripe, so card numbers never touch your website. Whichever route you choose, check that the booking tool hands payment to the processor and does not store card details itself.

PandaCodeGen offers website and application development. Recommendations here reflect our delivery approach; the proposal for your project defines its scope. How we use evidence.