A Wix Velo booking system uses Wix Bookings as the engine and Velo code to customize it. Your code checks availability, creates the booking, then hands payment to Wix eCommerce. Use it when standard Wix Bookings can’t handle your pricing, rules, or multi-step flow. Otherwise, the built-in app is cheaper.
Booking builds are the projects where I see the most outdated advice. Many online tutorials still show code that Wix has replaced. So before we get into how a Wix Velo booking system works, you need to know what changed this year.
What Changed for Wix Velo Booking in 2026?
Wix’s own documentation carries a deprecation notice for the old Bookings Frontend Velo API. It says Wix replaced that module with the Time Slots, Bookings, and eCommerce SDK APIs, and scheduled its removal for March 31, 2026. That date has passed.
In practice, tutorials that call getServiceAvailability() or checkoutBooking() from wix-bookings-frontend are out of date. If you inherited a site with that code, ask your developer to check it. I’d treat any custom booking code written before 2026 as suspect until someone confirms it still runs.
What Are the Three Service Types in Wix Bookings?
Every custom build starts with the service type, because each one behaves differently. According to Wix’s Bookings architecture documentation, the platform supports three types:
- Appointments: one-on-one or group sessions scheduled into open slots, based on staff and resource availability.
- Classes: recurring group sessions with a set schedule and capacity. Customers book individual sessions.
- Courses: multi-session programs with a fixed schedule. Customers book the whole course as one unit.
Pick the wrong type and you fight the platform later. For example, a six-week workshop belongs under Courses, not six separate Classes.
How Does a Custom Booking Flow Actually Work?
The flow is more logical than it sounds. Wix’s official sample flows describe it in a clear sequence, and here is the plain-English version:
- Check availability. Your code asks Wix for open slots for a specific service and date range.
- Show the options. The visitor picks a slot or class session on your custom page.
- Create the booking. Your code saves the choice. The booking starts with a status of CREATED.
- Create a checkout. Payment runs through Wix eCommerce, with the booking attached as the item.
- Send the visitor to pay. Once they finish, Wix creates the order and charges the customer.
Alternatively, you can run your own custom checkout. In that case, your code confirms the booking as paid after payment clears. That route gives you more control, but it also gives you more to maintain.
The Nuance That Causes Double Bookings
Here is the detail most guides skip, and it matters for anyone building a custom flow. According to Wix’s Bookings documentation, a booking with the CREATED status does not block availability. It also doesn’t appear on the business calendar until it’s confirmed.
That means two visitors can pick the same slot while one of them is still typing card details. Wix does re-check availability at several points: when showing slots, before creating the booking, and before confirming after payment. So the platform protects you from a true double booking. However, the second customer may pay and then get declined, which feels terrible.
That’s why I design a clear “slot no longer available” message and a fast retry path into every custom flow. A developer who never mentions this scenario probably hasn’t built one under real traffic.
What Can You Customize Beyond the Basics?
This is where Velo earns its cost. Wix’s Bookings APIs let developers extend far more than the visible calendar. Here are the pieces I use most:
- Custom pricing logic through service plugins, for example peak-hour rates or member discounts.
- Booking validation rules, such as blocking bookings under a minimum notice period.
- Resources and staff, so a room, a piece of equipment, or a specific therapist gates availability.
- Booking forms, since each service has its own form and Wix links the submission to the booking automatically.
If your needs stop at “let people pick a time and pay,” standard Wix Bookings already does it. Custom code only makes sense when a real rule doesn’t fit the dashboard. I’ve written about that same build-versus-configure question in how Velo API integrations actually work.
Why Does Booking Experience Matter So Much?
Customers judge your business by how easy it is to book. Salesforce’s State of the Connected Customer report, as compiled by SimplyBook.me, found that 48% of clients say a difficult or outdated booking experience would make them switch to a competitor. Vendor compilations like that vary, so treat the exact figure as directional. Still, the pattern is consistent across the data I’ve seen.
For tour and activity businesses, this matters even more. I cover the wider feature list in tour booking website features you actually need.
What Does a Custom Booking Build Cost?
I won’t quote a flat price, because scope drives everything. Wix Velo developers typically charge roughly $50 to $150 an hour for experienced work, and a custom booking flow is measured in hours of logic, testing, and edge cases. A simple slot picker takes far fewer hours than a multi-resource, multi-location system with custom pricing.
Before you request quotes, run your idea through my website cost calculator to get a grounded range.
[INSERT: a real booking project here, such as a specific client’s booking flow, the custom rule it needed, and how it changed their admin workload]
Mistakes I Would Avoid
- Skipping the plan requirement. Wix states a site needs a Premium Business Plan to accept bookings and payments. Check this before you promise a launch date.
- Copying an old tutorial. As covered above, pre-2026 code may call modules Wix has removed.
- Building custom when native works. Test the standard app first. Many “custom” requests disappear after an hour of configuring it properly.
- Ignoring the failure path. Plan for the full slot, the declined card, and the visitor who closes the tab mid-checkout.
Should You Build This Yourself?
If you’re comfortable with JavaScript and read API documentation for fun, a small custom flow is achievable. For anything involving payments, staff schedules, or custom pricing, hire someone who has built one under real traffic. I offer this as part of my Wix Velo development service, and I’ll tell you honestly if the native app is enough.
Frequently Asked Questions
Can Wix Velo build a custom booking system?
Yes. Velo lets developers use the Wix Bookings and eCommerce APIs to check availability, create bookings, and handle payment on custom pages. It suits businesses whose rules or design don’t fit the standard Wix Bookings dashboard.
Do I need a paid plan to take bookings on Wix?
Yes. Wix’s documentation states a site needs a Premium Business Plan to accept bookings and receive payments. Confirm your plan before development starts, since it affects both launch timing and ongoing monthly cost.
Why does my old Wix booking code no longer work?
Wix replaced the Bookings Frontend Velo API with the Time Slots, Bookings, and eCommerce SDK APIs, and scheduled the old module for removal on March 31, 2026. Code using getServiceAvailability() or checkoutBooking() needs updating.
What is the difference between appointments, classes, and courses in Wix Bookings?
Appointments are one-on-one or group sessions in open slots. Classes are recurring group sessions where customers book individual sessions. Courses are multi-session programs that customers book as one complete unit.
Can two people book the same slot in a custom Wix flow?
A booking with CREATED status doesn’t block availability, but Wix re-checks availability before confirming. So true double bookings are prevented, though a second customer may be declined after paying. A good build handles that case clearly.
How much does a Wix Velo booking system cost?
Cost depends on hours of custom logic. Experienced Velo developers commonly charge about $50 to $150 an hour. A simple slot picker costs far less than a multi-resource system with custom pricing and validation rules.
Want a Booking Flow That Fits How You Actually Work?
If you’re deciding between standard Wix Bookings and a custom build, message me on WhatsApp. I’ll tell you which one your business really needs, even if the answer is the cheaper one. Start the conversation here.