Products, categories and stock

Categories

“Entrance Tickets” is built in: products in it are TICKETS — they admit people, power check-in and can carry per-attendee forms.

Every other category is yours to create (the + next to the category selector): Food, Drinks, Bingo, Merch — whatever this event sells. Non-entrance items are collected at the counter by QR (see Food counter).

The public page groups products by category. Drag products up and down in the admin list to set the order inside each group — that order IS the public order.

The fields

• Name — what buyers see. Short description — one line on the card; Full description — details shown when the product is opened.
• Ingredients / Allergens / Portion — food-specific, all optional; shown to buyers so dietary questions answer themselves.
• Price (£) — 0 is allowed for free items (free kids’ entry, for example).
• Image — the product photo; upload or reuse.
• Active — unticked, the product is hidden from the public page and cannot be bought, without deleting it. Good for “not this year” items.

Stock

• Total quantity — how many exist. Leave BLANK for unlimited. When it runs out the page shows sold out and checkout refuses oversells.
• Low-stock alert — when remaining stock reaches this number, the dashboard shows a warning so you can restock or close sales calmly.

The list shows sold/total per product. Entrance tickets with a quantity also give the dashboard its “sold / capacity” reading.

Per-attendee forms (tickets only)

Entrance products can ask a form per attendee at checkout: contact fields (each can be off, optional or required), consent checkboxes you write yourself, and custom questions — short text, paragraph, or a choice list.

Answers are stored on the order, visible in the order detail and in exports. Ask ONLY what the event genuinely needs — avoid sensitive data (health, religion) unless you truly need it and know your legal basis; your organisation is responsible for what it collects.