Skip to main content

Experience booking channels & add-ons

Two blocks on the Define step of the Experience builder (/admin/experiences/:experienceId/builder) decide how an experience is sold. Where it can be booked holds the channel switches: which of your website, booking widget and staff may offer it. What guests can add chooses the add-on sets, such as a cheese board or a bottle to take home, that are offered with it. Add-on sets themselves are built on the Storefront page at /admin/store, in the Add-ons tab.

This page covers those two blocks. For the rest of the builder, and for taking a booking, see Reservations & availability.

Who can use it​

  • See the channels and add-on sets on an experience — experiences.read. Without experiences.update the switches are replaced by ticks and crosses and nothing can be changed.
  • Change the channel switches — experiences.update: Manager, Admin.
  • Create add-on sets, change what is in them, and choose where they are offered — addons.update: Manager, Admin. This includes ticking a set on or off inside the builder.
  • Mark a product as usable as an add-on — products.update: Manager, Admin.
  • See add-ons while taking a booking — addons.read, as well as reservations.create. Manager, Concierge, Wayfinder, Host, Ambassador and Admins hold it. Server, Wine Associate and Viewer can create bookings but do not hold addons.read, so their Add-ons step is always empty.

Choose where an experience can be booked​

  1. Open the experience from Experiences and stay on Define.
  2. Find Where it can be booked — "Which channels sell this. Concierge and floor can always book an active experience; every other channel is a choice, and each one is tracked separately on the booking."
  3. Tick or untick the channels.
  4. Press Save channels. Avero confirms "Channels saved" — "Where this can be booked has been updated." Discard drops your unsaved ticks.

The switches are not saved as you type like the rest of the step. Nothing changes until you press Save channels.

ChannelWhat it is
Concierge & floor"Staff booking on the phone, at the desk, and on the floor." Marked always on; it has no switch.
A website rowOne row for each website you host on Avero, labelled with the site's name. "The hosted winery site."
Embedded widget"The widget on a page Avero does not host." It has its own switch and does not follow the website.
Point of sale"Sold at the till alongside wine."

Beside each switch is the number of bookings that came through that channel in the last 30 days, and its share of the total. Canceled bookings and no-shows are not counted. A channel with nothing shows "none yet".

If every guest-facing switch is off, Avero warns: "No guest-facing channel is on, so only staff can book this. That is right for a private buyout and a mistake for a tasting — it is a warning, not a block."

An experience whose channels have never been saved shows "These are inherited from the old Publish to Web setting. Saving here records them as choices for the first time." Until then the website and widget follow whether the experience is published, and the staff channels follow whether it is active.

The Publish step repeats your choice, read-only, under Where it will be bookable. Change the channels takes you back to Define.

What the switches control, and what they do not​

SwitchWhat it controls today
A website rowWhether the experience, and its times, appear on that site's experiences pages.
Embedded widgetWhether the experience, and its times, appear in the booking widget.
Point of saleNothing yet. The choice is saved and shown, but no screen or check reads it.
Concierge & floorNothing you can change. Staff can book any active experience from the booking wizard.

Each booking is also labelled with the channel it came through. Staff bookings are recorded as concierge, website bookings as website, and widget bookings as widget. That label is what the 30-day counts add up.

The switches hide an experience. They do not refuse a booking.

A website or widget switch decides whether guests are shown the experience on that channel. When a booking request arrives, Avero does not look at the switches again. It checks only that the experience is active and published.

In practice:

  • One guest channel off, another on. The experience disappears from the channel you turned off. A booking request for it that still reaches Avero, for example from a page a guest already had open, is accepted. The same is true between two websites: a site whose row is off no longer lists the experience, but does not refuse a request for it.
  • Every guest channel off, then Save channels. Saving with no guest-facing channel on also unpublishes the experience, so online booking requests are refused. This is the reliable way to stop online bookings.
  • Staff bookings are never affected by any switch.

The Publish step buttons do not move the ticks​

Publish to Web and Unpublish from Web on the Publish step change whether the experience is published. They do not change the ticks under Where it can be booked, so the two can disagree:

  • After Unpublish from Web, website and widget rows can still show as ticked. The experience is not shown or bookable online, whatever the ticks say.
  • After you save with every guest channel off, Publish to Web does not tick them back on. The experience stays hidden from your website and widget, but an online booking request for it is accepted again.

To put an experience back online, tick the channels you want and press Save channels. Do not rely on Publish to Web alone.

If you do not host a website on Avero​

The list has one website row for each website hosted on Avero. With none, there is no website row at all, only Concierge & floor, Embedded widget and Point of sale. Pressing Save channels in that state removes the experience from your online store's experiences pages, and there is no switch to bring it back. If your online store lists experiences and you have no hosted website, leave Save channels alone and use Publish to Web and Unpublish from Web instead.

What an add-on is​

An add-on is an ordinary product from your catalogue that staff can attach to a booking. Add-ons are grouped into add-on sets. A set has a name, an optional description and a list of products.

Three things must all be true before a product is offered on a booking:

  1. The product is in an add-on set.
  2. The set is offered against the experience, its location, or the seating area the experience runs in.
  3. The product itself has Can be a reservation add-on switched on.

A set that is offered nowhere is offered to nobody. Avero says so in both places you manage sets.

Create an add-on set​

  1. Open Storefront (/admin/store) and choose the Add-ons tab.
  2. Press Create Add-on Set. Enter a Name and, if you like, a Description, then Save. Avero confirms "Add-on set created successfully".
  3. On the set's card press Manage Items, then Add Product. Pick a Product, leave or change Default Qty, and press Add.
  4. Press Where it applies. Under Bind to choose Experience, Location or Surface (a seating area; pick its location first), choose the one you mean, and press Bind. Avero confirms "Add-on set bound".

Until step 4 is done the panel reads "This set is not offered anywhere yet." Bindings add up. A set bound to a seating area and a set bound to an experience are both offered when that experience runs in that seating area. Remove takes a binding away.

The pencil on a card opens Edit Add-on Set to change the name or description. The bin beside an item takes it out of the set. There is no button to delete a set or switch one off; to stop offering a set, remove its bindings.

Mark the product as well

The Add Product list on this page shows every active product, including ones that cannot be offered at booking. Open the product (/admin/catalogue/products/:productId), and in Basic Information switch on Can be a reservation add-on, then Save. It is off by default: "A product is only offered at booking if this is on AND it sits in an add-on set that is bound to the experience, location or surface being booked."

Offer add-on sets on an experience​

You can also work from the experience instead of from the set.

  1. Open the experience in the builder and stay on Define.
  2. Find What guests can add. Every add-on set in your company is listed, each with its item count, price range and where it is offered.
  3. Tick a set to offer it on this experience. Avero confirms "Offered here". Untick it and Avero confirms "No longer offered here" — the set itself is untouched. These ticks save straight away.
  4. Tap a set's name to see what is in it.

A set tagged only here is offered nowhere else, so you can change its contents on the spot: Add a product… adds one (only products already marked as add-ons are listed) and the cross beside an item removes it. A set that is also offered elsewhere is read-only here: "its contents are edited in the store rather than here — changing them would change those too."

The block ends with a count, for example "2 sets will appear at booking for this experience." Sets bound to the experience's location or seating area are offered too, even when they are not ticked here.

If the company has no sets, the block reads "This company has no add-on sets yet. They are created in Store → Add-ons." That is the Add-ons tab of the Storefront page.

How add-ons are priced​

An add-on has no price of its own. The price shown is the product's price in the catalogue, and it is the same in every set the product belongs to. To change what an add-on costs, change the product's price. See Products & inventory.

How add-ons are offered during booking​

Add-ons are offered in one place: the Add-ons step of the staff booking wizard at /reservations/new — "Anything to add?"

  • The step lists the sets that apply to the experience, location and seating area being booked, each under its own heading. A product that sits in two of those sets is listed once.
  • Each product shows its price with plus and minus buttons. Quantities start at zero. The Default Qty saved on the set is not used here.
  • The line under the list keeps count, for example "2 added · $48.00", or "Nothing added — that is fine".
  • The Estimated cost panel adds an Add-ons line and includes it in Estimated total. On the Deposit step each booking shows how many add-ons it carries.

Guests booking for themselves on your website or through the booking widget are not offered add-ons.

Add-ons are recorded, not charged

When you confirm, the products and quantities you picked are saved with the reservation, and that is all. They do not change the deposit, they are not shown on the reservation's detail page, and they are not added to a check or to Collect Payment. Put anything that matters to service in Notes for this booking, and ring the items up at the register when the guest is charged.

Reference​

ControlWhereWhat it does
Channel checkboxesBuilder → Define → Where it can be bookedChoose the channels. Nothing changes until you save.
Save channels / DiscardSame blockSaves or drops your ticks. Saving also sets whether it is published.
Change the channelsBuilder → Publish → Where it will be bookableReturns to Define.
Set checkboxBuilder → Define → What guests can addOffers the set on this experience, or stops offering it.
Add a product…An opened set tagged only hereAdds a product already marked as an add-on.
Create Add-on SetStorefront → Add-onsCreates a set with a name and description.
Manage ItemsA set's cardLists the set's products; Add Product adds one.
Where it appliesA set's cardBinds the set to an experience, location or seating area.
Can be a reservation add-onProduct → Basic InformationAllows the product to be offered at booking.

Troubleshooting​

  • A set is ticked but its products do not appear at booking — open the set in the builder. An item marked "Not add-on capable — turn that on in the product, or it will never appear at booking." needs Can be a reservation add-on switched on.
  • "Nothing to add on this booking" — "No add-on set is offered for this experience, location or surface." Either no set is bound to what is being booked, or your role does not hold addons.read.
  • "Nothing changed" — "The binding could not be updated." Ticking a set needs addons.update.
  • "Channels not saved" — "Nothing was changed." Try again; your ticks are still on screen.
  • The experience is ticked for the website but guests cannot see it — it may be unpublished or inactive. Check the Publish step.
  • A booking arrived through a channel you turned off — see What the switches control.
  • Two website rows show the same booking count — the count is for all websites together, not for each site.