Add-on Products and Upgrades

Add-on products are extras a customer can attach to a booking — an upgrade tier, party catering, branded merchandise, parking, drinks, photo packages. They show up as options on the booking flow and on the check-in screen, and their revenue lands in your reports separately so you can see how each performs. This guide covers creating them and tying them to rooms.

Opening the products page

Go to Settings → Products. You'll see every product with its name, price, type, and the rooms it's offered with.

Creating a product

1. Click Create.
2. Fill in:
   • Name — what customers see (e.g. "Photo Package", "Premium Game Master", "Party Bags × 10").
   • Short description — one-liner explaining what's included.
   • Price — flat amount per unit.
   • Type — Per booking (one charge regardless of player count) or Per player (multiplied by attendees).
   • Stock — optional. If physical merchandise, set a stock count and the system stops selling once it's gone.
   • Active — toggle to show/hide on the booking flow without deleting.
3. Save.

Tying products to rooms

Some products fit specific rooms — "Premium Game Master" for escape rooms, "Catering Package" for function rooms. Others are universal — "Parking Pass". You can scope each product to specific rooms or leave it global:

1. On the product detail page, find the Rooms field.
2. Tick the rooms this product should appear with. Leave blank for "all rooms".
3. Save.

Per-booking vs per-player

Pick the type that matches how you actually charge for the item. Mixing them up gives customers (and you) a surprise at checkout.

Customer flow

On the booking widget, after a customer picks their slot, an "Add extras" step shows the products available for that room. They tick what they want, the price recalculates live, and it carries through to payment.

At check-in, staff can add extras the customer didn't pre-order — useful for upgrades sold at the front desk.

Reporting

Product sales appear in:

• The booking modal — under "Add-ons" alongside the room price.
• The Daily Revenue report — broken out by product.
• A dedicated Products column in the bookings list, so you can filter for "bookings that included Catering Package".
• Stock levels (if you set them) update automatically as products sell.

Refunding a product

If a customer paid for an add-on but didn't use it (e.g. the catering wasn't needed), refund just the product portion:

1. Open the booking.
2. In the products section, click the trash icon on the line you're removing.
3. The booking total drops by the product price; the difference appears as a balance the system suggests refunding.
4. Process the refund per Processing Refunds.

Common patterns

Tiered upgrades

Create products for "Standard Experience" (free, default), "Premium" (+$30), "VIP" (+$60). Customers pick their tier on the booking flow. Use stock to cap premium availability if your VIP capacity is limited (e.g. only one VIP host per shift).

Merchandise

Create products for branded T-shirts, mugs, photo prints. Use stock to track inventory; reorder before you run out.

Bolt-on services

Photo packages, video recordings, custom decorations. Often per-booking type since they apply to the whole group.

Common pitfalls

• Wrong type. Per-player priced as per-booking under-charges large groups. Per-booking priced as per-player over-charges small groups. Test on at least one booking each way.
• Stock not tracked. If you sell merchandise without enabling stock, the widget will keep selling after you're physically out. Always enable stock for finite items.
• Products on rooms that don't make sense. A "Birthday Cake" probably doesn't apply to corporate escape-room bookings. Use room scoping rather than offering everything everywhere.
• Duplicates. If the same product appears under different names ("Photo Pkg" and "Photo Package"), reports split the revenue. Pick one canonical name and stick with it.

Going further

For complex add-on logic (conditional products, bundles, time-of-day pricing) the standard product system has limits. Talk to support — some scenarios need custom configuration we can do for you, others are pipeline items.