The Spektrix integration is a small, two-way bridge between Make a Rezzy and your Spektrix box office — sized for the theatre-plus-restaurant case, not a full data sync. This article spells out exactly what crosses the bridge in each direction, when it happens, and what stays on its own side.
From Spektrix to Make a Rezzy
Data only flows from Spektrix to Make a Rezzy when a guest is actively booking through your reservation widget, and only for pages that have the Spektrix integration switched on (see Customising the widget). Two pieces of data come across:
The guest's current basket
When a guest with a Spektrix basket on the page opens the reservation widget, the widget reads the basket and looks at the earliest event in it.
- What we read: the basket ID, the customer ID attached to the basket (if any), and the start date of the first event.
- What we do with it: we pre-select that date in the widget's date input, so a guest with a ticket for an 8pm show on Friday lands on Friday already selected. The slot list then comes from your normal Make a Rezzy availability for that date, so the times the guest can pick from naturally fall before or after the performance — no separate "around the show" schedule to maintain.
- Where it shows in Make a Rezzy: the pre-selection only — the basket itself is not stored against the guest record.
The Spektrix customer ID
When the booking is submitted, Make a Rezzy holds on to the basket ID. A background job then asks Spektrix who owns that basket and saves the resulting customer ID against the guest's Make a Rezzy profile. We call this verifying the link.
Until the link is verified, no data is written back to Spektrix — see Verified vs unverified below.
From Make a Rezzy to Spektrix
Make a Rezzy writes back to Spektrix at one moment only — when a booking is marked Completed. There is no periodic sync and there is no write on Confirmed, Cancelled, or No-Show. Two customer attributes are updated in Spektrix:
| Spektrix attribute | What Make a Rezzy writes | Type |
|---|---|---|
| Last Dined At |
The end time of the booking that just completed, in
ISO 8601 (e.g. 2026-05-28T21:30:00+01:00).
|
Date/time |
| Number of Restaurant Visits | The total number of this guest's bookings at this venue that are Confirmed, Completed, Pending, or Pending Payment. Cancelled and No-Show bookings do not count. | Number |
Both attributes have to be created on the Spektrix side before Make a Rezzy can write to them. See Setting up the sync for the admin steps.
Verified vs unverified guest profiles
The integration only writes back to a Spektrix customer profile that Make a Rezzy has verified — meaning we have asked Spektrix "who owns the basket this booking came from?" and got back a customer ID. Two cases stop a profile from being verified:
- The basket was anonymous. The guest had not signed in to Spektrix before opening the widget, so the basket had no customer attached. No customer ID to write back to.
- The basket's customer did not match. Very rare, but if the basket and the booker are different people (for example, the basket was shared on a kiosk), the safety check kicks in and we leave the link unverified.
Unverified bookings still live in Make a Rezzy as normal — they just are not mirrored back to Spektrix.
What does not sync
To save you guessing what the integration does not do:
- Restaurant bookings do not become Spektrix orders. A booking made through the Make a Rezzy widget stays in Make a Rezzy. Spektrix's order list will not pick it up.
- Spektrix tickets do not become Make a Rezzy bookings. Tickets sold through Spektrix stay in Spektrix. The bridge only carries the date and customer ID into the widget, not the ticket itself.
- Floor plans and seat plans are separate. Make a Rezzy's floor plans (which tables are where) are unrelated to Spektrix's seat plans (which seats are in the auditorium). Changing one does nothing to the other.
- Menus, opening hours, and business details do not cross. Everything diners see about your restaurant on Make a Rezzy comes from Business details, not from Spektrix.
Where to go next
- Setting up the sync — creating the API user and the two customer attributes.
- Troubleshooting — fixes for the most common sync problems.
- Spektrix integration documentation — Spektrix's own reference for everything on their side.