Booking
Attach a third-party booking link to events and event instances when your ticketing system isn't natively integrated
The Booking app is for organisations whose ticketing system isn't one of Basker's native integrations. It adds a booking-button label and URL to each event and event instance, and site-wide links for an external account, basket, and calendar. Your theme can use these values to send visitors to the right part of your booking journey.
Use it when:
- You sell tickets through a platform that doesn't have a Basker integration yet.
- Ticketing is handled outside Basker entirely: a venue's central box office, a partner's site, or a third-party event listing.
- You need a manual booking link as a stop-gap while a deeper integration is being set up.
The Booking app uses a link-based workflow, with events and event instances created and maintained in Basker.
Site-wide booking links
Open Settings → Apps → Booking to configure any of these links that your theme uses:
- Account Link: the external customer account page.
- Cart Link: the external basket or cart.
- Calendar Link: the external event calendar.
Leaving a value blank makes no change by itself. Your theme decides where configured links appear.
Attaching a booking URL
Once the Booking app is installed, events and event instances gain Booking Button Label and Booking Button URL fields. Open the event or instance, set the button text and destination, and save.
You can attach the URL at either level:
- On the event: use this when every performance of that event uses the same booking URL.
- On the event instance: use this when a specific date has its own booking URL (for example, a captioned performance on a separate ticketing page, or an opening night handled through a different supplier).
When both levels have values, your theme decides whether the performance-level values override or sit alongside the event-level button. Preview an event with several performances to confirm the result.
Creating events manually
Without sync, every event is one you create in Basker. See Create events for the full walkthrough: title, description, venue, season, dates, and the rest of the editorial detail.
Creating event instances manually
Each performance of an event is an event instance: a single dated occurrence that audiences see as a showtime. With Booking, you add each instance by hand:
Open the parent event
Open the event you want to add a performance to. Switch to the Instances tab where its existing instances are listed.
Create a new instance
Start a new instance. The parent Event should already be set; if you started from the Event Instances area instead, pick it.
Set the date and time
Fill in Start Date and pick its Timezone. These are the only required fields: most instances inherit everything else from the event.
Set any overrides
Override Title, Venue, Company, Duration, Season, Series, or Works if this performance differs from the event's defaults: opening nights, touring dates, and captioned performances usually need at least one of these.
Add the booking URL
Paste the booking URL for this instance, if it differs from the event-level URL. Use the Hide Start Time? toggle if you're not yet announcing the time, or Hide Event Instance? to keep it off the public site for now.
Save
Click Save. The instance appears on the event's listings, and the booking button on the live site routes to the URL you set.
For a production with many instances on a regular pattern, add the first instance and duplicate it to seed each subsequent date. Adjust the date and any per-night overrides on each duplicate.
Keeping booking information up to date
The Booking app focuses on links and button labels. Event details, cancellations, time changes, live availability, and basket or account journeys remain managed in Basker, your ticketing platform, and your theme as appropriate.
Keep changes aligned between Basker and the external ticketing system, and test booking links in preview before publishing.