Add-ons let you link related services to a booking, so customers can upsell themselves before they even reach checkout. Instead of just booking your main experience, customers can add extras you've chosen to make available, like a guided tour, a bonus experience, or any other optional service. It's a straightforward way to increase the value of every order without adding manual work on your end.
You can link one or more related services to any main service as add-ons. Selections are specific to each service, so the add-ons you offer on one experience won't automatically appear on another. This lets you tailor what's offered based on what actually makes sense alongside each service.
Availability is checked in real time, so customers only ever see add-ons that can actually be booked with the main service and date they've selected. You don't need to manually manage which combinations are valid.
Important: a service that's marked as hidden (not normally visible in your shopping cart or booking tool) can still be linked as an add-on. When it's linked this way, it becomes visible to customers during the Add-ons step, even though it wouldn't otherwise appear on its own. This is useful if you want to keep a service out of general browsing but still offer it as an upsell on specific bookings.
Once you've set up add-ons on a service, customers see a dedicated Add-ons step right after they select that service. From there they can:
Dates automatically align with the main service, so there's no separate date entry and no risk of mismatched bookings.
Customers stay in control of their cart, and this reduces the number of support requests you'll need to handle:
The Manage Add-ons option (accessible from the cart] your customers (or you) adjust add-ons after a booking has already been made. If a change to the main booking's date affects an add-on's validity, the system flags it clearly and walks the customer through updating or removing it. An order can't be completed with an add-on that no longer works.
Because an add-on generates its own linked booking rather than just being an extra line on the main booking, it can carry its own ticket, QR code, and check-in requirement if you've configured the add-on service that way. That means:
This is worth keeping in mind when deciding what to offer as an add-on. If a service needs its own check-in or entry tracking (like a separate activity with limited capacity), configuring it as an add-on with check-in enabled will carry that requirement through automatically.
Both let you bundle related services together, but they serve different purposes and behave differently in the system.
Use a package when:
Use an add-on when: