Add-ons are workspace-owned optional purchases reused by Ticketing and Bookings;
there is no separate Add-ons module entitlement. Open either product's Add-ons
workspace to use Library, Collection and Sales as permitted.
Catalogue management uses bookings.pricing.manage or
ticketing.events.manage and checks every contributing Site. An Event or Booking widget adopts exact published item versions.
Catalogue, offers and customer purchase
- In the Library, create an item, its variants, Site availability, price/tax, quantity limits, uses per unit, sales quota and collection instructions.
- Choose the seller Payment Profile and publish the item version.
- In the Event's Optional add-ons or widget offer editor, select and order the eligible published versions, then publish that offer.
- A customer chooses add-ons after their tickets/activity and before payment. Nothing is preselected; no eligible catalogue means no extra step.
- Review the seller split and total, then complete checkout. Each required seller's payment must succeed before vouchers become usable.
Event managers can open Event → Tickets → Extras and its Optional add-ons
section, including a direct view=addons link, to manage the Event’s separate offer. Without Event-management
access that view falls back to an available Event page; its URL grants no access.
The web New add-on and Edit add-on dialog builds one item card: an optional cover image, title, category and description, followed by its price and quantities. New items start with one Standard option charged per item. A blank sales quantity is unlimited; zero total sales quantity remains a valid limit. Site availability, seller Payment Profile and tax treatment stay visible.
Sales category is a reporting label from the organisation's shared catalogue, separate from the Food/Drink/Merchandise/Other category used to organise the Library. The web Add-on and legacy Booking Extra editors require a category when publishing a priced definition. Choose a named category or create a missing one inline with Payments management access; Uncategorised is no longer a new selection. All variants use that version's sales category. A published meal package can retain the menu's category when no add-on override is supplied. Purchased snapshots and adopted offers retain their category after rename/archive; archive prevents new selection and does not close an otherwise valid published sale. Existing catalogue management permissions apply. It never changes the seller Payment Profile or collection policy. Native authoring has no category control.
The Add-on category choices and inline manager share the catalogue's current access check. Temporary connection loss keeps an open draft but blocks category commands until access is renewed. Losing Payments management closes the category manager and clears its unsaved category edits; an independently permitted Add-on draft and its category assignment remain available.
Pricing and variations opens the currency, charging basis, option labels, option prices and daily limits. Existing complex pricing opens this section for editing; closing it keeps every option and its values. Collection and purchase rules holds uses, collection instructions, minimum quantity and cancellation notice. Per-booking charging uses quantity one while retaining the other quantity draft for switching back. Invalid fields inside a closed section reveal it.
Guide beside New/Edit add-on explains the item, pricing/limits, availability/seller, collection and publication. Pricing guidance follows the charging basis and number of variations. Sales quotas apply across offers; purchase limits apply to one purchase. Uses per item describe redemption, not sale quantity. Publishing creates a library version; offering it through an Event or booking widget remains a separate step. Existing purchases retain their terms. Go to… opens required disclosures and focuses existing controls without changing the draft or triggering publication. Full help opens separately.
The optional guide shares the Event editor's per-user, browser-local Show/Hide behavior, stored separately for Add-ons. No business data enters that preference. At viewport widths of 1024px or more, the open guide expands the dialog to at most 960px; the 240px rail needs a content container of at least 896px. Smaller screens keep the compact dialog and an expandable guide above the form. The header/footer remain fixed, with one scrolling body and the existing focus trap. Pending-action and access restrictions still apply. This adds no native guidance or backend permission.
The image is optional: choose or drop a JPEG, PNG or WebP up to 4 MB. Uploading prepares the image for the draft; Publish version remains an explicit action. A failed upload retains the previous image, and failed publication retains the form with a neutral inline error. Pending publication or upload locks repeat actions and closing. Current access and source changes still retire private editors; a disclosure does not extend access or start publication. The same editor serves the Library and creation from an offer. Native screens are unchanged.

Optional purchases increase the total; included ticket benefits stay inside the ticket price. Lines with the same Payment Profile share one charge, while distinct compatible profiles use disclosed separate direct seller charges. Cross-seller Booking purchases require online collection. Historical Booking Extras retain their identity and share the same capacity authority after adoption.
Sales quotas count holds and sold quantities. They do not claim physical stock accuracy. Editing a catalogue price does not rewrite an adopted offer or sold terms; retiring/removing availability can close future sales while preserving existing purchases.

Guest Ticket QR collection
Published add-on versions can opt into
Allow collection with guest Ticket QR. In Collection, Assign guest Tickets
reserves purchased uses to individual active Tickets from that exact purchase.
The total includes already collected uses. Reducing it to the collected total
releases the unspent allocation. Management requires addons.fulfil.manage at
the collection Site. Ordinary manual/voucher handovers cannot spend reserved
uses; partial refunds require releasing affected allocations first. A full
cancellation revokes remaining allocations and preserves collection history.
Historical versions without the flag retain their voucher flow.
Collect with guest Ticket QR selects Assigned purchased add-ons or
Included Ticket items. A collection link opens that signed-in purpose and
Site; it grants no access. Scan the existing static or rotating Ticket QR,
review that guest's remaining items, enter a whole quantity and explicitly
confirm. Reading never admits a guest or consumes an item. Collection keeps
addons.fulfil; admission devices retain admission-only authority. Live and
Test mode remain separate, with practice confirmation in Test.
For Event-seller included items, enable Redeem with guest Ticket QR and set Uses per guest Ticket. New Tickets freeze that allowance when issued; later product edits do not refill sold Tickets. Descriptive historical inclusions create no allowance. Routed-seller included items stay on their existing flow. Existing package meal allowances keep their separate once-only record and Ticketing management command; this setting never converts that record.
A checked-in Ticket keeps its Web Wallet QR while source-valid assigned or included collection uses remain. Refunded, voided, resold, expired or revoked sources retain their existing refusal boundaries. Allocation never transfers a paid balance to a different guest, purchase or seller by matching an email. Native offline collection, anonymous collection devices and new native pass layouts are outside this change; physical device acceptance remains separate.
Included-item collection follows the current fulfilment Event after an Event swap, preserving the original booked Event as history. A Ticket with collected included items cannot be swapped to refill its allowance; the venue must review it. Inactive guest Tickets with unspent paid reservations remain visible to management for release only.
Hand over, correct and refund
Open the collection list or scan a voucher QR, review the exact item and remaining uses, enter the handover quantity and explicitly confirm. Scanning alone consumes nothing. A three-use drinks entitlement can be handed over in separate visits. The same atomic command powers list and QR redemption and preserves history.
With two or more collection Sites the list opens on All sites: purchases at every Site where you may collect, newest service date first, each named with its Site and handed over at that Site. The Site field narrows it and keeps the choice in the page link. Looking up or scanning a voucher and guest Ticket QR collection need the Site you are collecting at, so under All the screen asks for it first. All shows at most 500 purchases; choose a service date or one Site when it asks you to narrow the list.
Collection defaults to Live. Test mode must be selected explicitly and displays
a practice warning. addons.fulfil grants Site-scoped handover, while
addons.fulfil.manage governs corrections. These rights do not grant admission
or finance access. The Web Wallet projects the balance; Add-ons owns it.
An add-on-only refund reverses the selected purchased quantity and tax, revokes unused uses and retains completed handovers. Partly used packages need explicit manager review. Refunds use the original seller and frozen fee evidence. Whole Order refunds revoke all remaining uses; refunding a prepaid extra does not quietly remove the unpaid venue balance. Order detail checks add-on refund access only for an Order with purchased add-ons. In a multi-seller purchase the per-seller tools load when Refund specific add-on quantities is first opened and pause while it is closed.
Sales reporting separates base and optional revenue and applies complete Order finance access before counting a sale. Native add-on passes, offline redemption, shipping and stock-system integration are outside this implementation.