Shipped in October 2026

A short round-up of everything that went live across Stampede in October 2026.

The 3D floor plan view now renders

The 3D view of your venue floor plan works. It opens by default when you load the plan, you drag to orbit and scroll to zoom, and table numbers and pool tables are drawn where you placed them. If the 3D scene cannot load, you get a message that says so and the flat plan takes over, rather than leaving you looking at an empty box. We had this wrong for a while. For some venues the 3D view rendered blank, with no tables in it, and the error state said nothing useful, so there was no way to tell whether the plan was broken, the browser was struggling or the tables had never been placed at all. Six changes went out together on 2 October 2026: the blank render, honest error messages, 3D as the opening view, the camera controls, and the missing table numbers and pool tables.

Nothing about your setup changes. Areas such as Main Floor, Terrace or Bar, tables with their minimum and maximum capacity and seating priority, and combinations for larger parties are the same records they were, and the day planner is still the live view for dragging pills, resizing durations and progressing a booking from arrived to seated to complete. What the 3D view is for is the room. At 19:15, with a party of 8 landing on a combination of two tables near the pool table, a manager checking the plan wants to see the space as it actually sits, including the non-bookable fixtures placed there for orientation. You will find it on the floor plan under table bookings, beside areas and tables, on any venue with tables placed.

Reviews reporting now reads like a report

Shipped 5 October. The Reviews report is now laid out as an article you read top to bottom rather than a grid of tiles, and Reports in the Reviews nav expands into two entries, Overview and Metrics. We had this wrong for a long time: one page tried to serve a head office reading six sites and a manager reading one, so the sentiment trend, the rating breakdown, the platform split and the NPS figure all sat at the same weight with no reading order. Nothing told you which number to start with, and the organisation view and the single venue view were the same page with a filter dropped on top of it. Metrics now exists at both levels, so the estate read and the venue read are separate pages rather than the same page pretending.

Overview carries the headline movement. Metrics carries the detail: rating and platform breakdowns, rolling sentiment and rating trends you can filter by venue and time period, the NPS figure, and the keyword lists grouped into customers like and needs improvement. Here is what that is for. It is Monday, and on the venue Metrics page needs improvement has pushed wait to the top across the last fortnight. You open the feedback inbox, filter to negative sentiment, and find three of them are from Friday, all parties of six or more seated after 19:45, all below the four star threshold so they came to you privately rather than landing on Google. That is a sitting problem on a specific night, not a vague feeling that the reviews have gone off. You can export the reviews report to CSV if the kitchen wants it in a spreadsheet. Find it at Reviews, Reports, Metrics, at organisation level and per venue, for any venue with Reviews turned on. It is a dependable daily read rather than a live ticker, so the heavier roll-ups catch up in the background.

Tidier workflow triggers

On 6 October we tidied the trigger step in the workflow builder. Booking count conditions now carry helper copy stating that the count includes the booking that just fired the trigger, and the field refuses a negative number instead of saving one. Removing a trigger now asks you to confirm before it goes. We also fixed a save bug we got wrong for months: if a trigger was left in a broken state, saving it hid the trigger from the canvas entirely, so the step you had just configured vanished and you had no way to see what the workflow was waiting on. It is restored and it stays on screen (1791393235). Hiding a trigger you were actively editing is worse than showing it broken, and we should have said so sooner.

The practical difference is off-by-one. Say you want a thank-you email that only starts on a guest's third booking. A party of 6 books in for 7.30pm on a Saturday, and that booking is their third with you. Set the count condition to 3 and the workflow starts on that booking, because the one in front of you counts. Before the helper copy, marketers reasonably read it as three previous bookings, set 2, and sent the message a visit early to anyone whose second booking happened to be a table of 6 on a Saturday. The confirmation on delete covers the other mess: triggers sit at the top of the canvas, they are easy to click past, and losing one meant the workflow stopped starting for anyone without an obvious reason why. You will find all of this in Workflows under Marketing, on the trigger step of any workflow you open. There is nothing to switch on, and it applies to live workflows as well as drafts.

Enquiry-only events, prefilled

Shipped 9 October: an Enquiry only toggle on an event. Flip it and the event stops taking instant bookings. A guest who picks it goes straight to the enquiry form with the event, the dates and the party sizes already filled in. We got the halfway version wrong for a while. We put min and max party size across the enquiry form, its validation and its settings back on 10 and 11 June, and events already carried their own menu, deposit, party-size limits and capacity, but the two did not hand anything to each other. A guest who clicked your Christmas sitting then re-typed the date and the covers into a blank form, and whoever picked the card up could not be sure the enquiry was even about that event.

Now the registration lands on the enquiry board as a card with the guest, party size, date and budget on it, moves through pending, in-progress, tentative and booked with the usual triage, qualified, negotiation and closed sub-stages, and carries an owner so it is clear who replies. Say a party of 22 registers interest in a 7pm sitting on 12 December. It arrives as an enquiry, not a confirmed table, so nobody has sold 22 covers before you have checked the room. You send a deposit link from the card, it chases itself and auto-cancels the hold if it goes unpaid, and once you mark it booked it becomes a booking on the day planner with the guest, requirements and any pre-orders attached. The toggle sits on the event itself, alongside its menu, deposit, party-size limits and capacity, in Bookings settings, and the registrations feed the same enquiry pipeline and inbox as every other enquiry.

Pre-order food with tickets

Shipped 13 October 2026: an event running in ticket mode now puts an Order food ahead section on the guest's ticket confirmation page, with a Start your pre-order button. Until now, ticket mode stopped at the ticket. A guest bought an adult or child ticket against the event capacity, got their confirmation, and that was the end of the conversation, so the kitchen for a ticketed supper club was still working off a spreadsheet someone emailed round on the Friday. The other half of this was worse and entirely our fault: a guest who started a pre-order, got interrupted, and came back to the same link had no route back into it. They either began again or gave up, and the errors they hit on the way told them very little. The confirmation page now shows continue or view depending on where they got to, and the error states say what actually went wrong.

The checkout behind it is the v2 one we rebuilt in June, so modifier selection comes with it. A guest picks medium, no onions, extra cheese against items you have set up under the Modifiers and Modifier Groups tabs on the Menus page, and your team sees it itemised, base plus each modifier plus total, in every order view including the live Square order dialog. Pre-order payments run through Stripe, separately from deposits you may be taking through Square. One thing it does not do yet: the lead booker cannot pay for everyone. On a party of six holding tickets for a 7pm Thursday sitting, each of the six opens their own confirmation page and orders for themselves, and the host confirms on behalf of anyone who stalls or removes them from the group pre-order so the rest can go through. That is a real limitation and we know who it annoys. Find it on any event with ticket mode on, under Bookings, as part of Table Bookings, where reservations stay unlimited with no per-cover commission.