Cooking Classes Online: Dietary Needs, Seat Limits and Class Changes
Short answer: Sell a cooking class as an event with a fixed number of stations, not as a generic appointment. Cap seats by the number of cooking positions you physically have, and ask about allergies and diets in a required form field during checkout, so the answer is attached to each person and not buried in an email. Decide before launch who may swap a menu, who may move to another date, and what happens if you cancel for low numbers. The questions below are the ones owners usually need answered first.
How many seats should the page sell?
Sell stations, not chairs. A kitchen with four hobs and eight workbenches may teach eight people, but only if every pair has a hob within reach. Count what limits the class in the order it limits it: cooking positions, oven capacity, sink and handwashing space, then the tutor's ability to watch everyone.
Then decide whether the cap is a hard stop or a soft one. A hard cap prevents overselling by blocking checkout at zero. A soft cap lets you add a seat manually for a regular, which suits small schools. Whichever you choose, set a separate "minimum to run" number, because a class of two may not be worth the ingredients.
Couples and pairs
If the class is cooked in pairs, sell a pair ticket and a single ticket as separate products that both draw from the same seat pool. Otherwise a single booking leaves one half of a station empty while the page still says "full".
What should the dietary question look like?
Free text alone is risky, because "no nuts" can mean preference, intolerance or a serious allergy. Use a structured field first, then an open box.
- A required choice per attendee: none, vegetarian, vegan, coeliac or gluten-free, dairy-free, allergy, other.
- If the guest picks allergy or other, a required free text box that asks which food and how severe the reaction is.
- A tickbox confirming the guest understands that the kitchen handles common allergens, so cross-contact cannot be ruled out. The wording should be agreed with whoever is responsible for food safety in your business, and your local food authority's guidance should shape it.
Collect the answer per person, not per booking. When someone books four seats, three of them may eat everything and one may not.
Who sees the answers?
The tutor needs a one-page list for each session, sorted by diet, printed or on a tablet. The admin who buys ingredients needs counts: how many vegetarian portions, how many without gluten. Build both views from the same data so they never disagree.
Because this is health-related information, keep access narrow and delete old answers on a schedule you can state. Check the guidance of your data protection regulator on special category data rather than relying on a general rule of thumb.
Can a guest swap a dish or move to another date?
Decide the menu-swap rule per class, because it changes your shopping. For example, a class built around handmade pasta with a choice of two sauces can accommodate a vegan sauce easily. A class built around a whole fish cannot swap without a second ingredient order. Mark each class as "swap possible", "swap with notice of 72 hours" or "menu fixed", and show it above the dietary field.
For moving dates, offer a self-service change up to a cutoff you name, for example five days before, and treat later changes as a request. The seat released goes back to the pool instantly, so someone else can buy it.
What if you cancel the class?
Write the cancellation policy for your side first. Say how many days before the date you decide, what the minimum is, and what the guest receives: a transfer to another class, a voucher or a refund. Then build one automated message that goes to everyone booked, carrying the three options and a deadline. Doing this by hand for a Saturday class of ten is manageable. Doing it for a whole season of classes after a tutor falls ill is where owners lose evenings.
How should the class page be structured?
A good class page answers the same few things in the same order every time:
- Date, start and finish time, and the full address with a note on parking or public transport.
- What is cooked and what the guest takes home, whether a meal eaten there or boxed.
- The tutor, with one line on their background.
- Skill level and what to wear.
- Seats remaining, shown as a number when it is low and hidden when it is high.
- The dietary and swap rule.
- The cancellation rule.
Search engines read events from a page when it is marked up properly. Google documents the event structured data in its search documentation, and it is worth giving each dated class its own entry with a start date, location and ticket availability. Check the current guidance before copying any example, since requirements change.
What about gift vouchers and private parties?
Vouchers are common for cooking classes. Sell them as a value or as a named class, and be clear whether the recipient may redeem for any class or only that one. Private parties, like a birthday for twelve, are better handled by an enquiry form that asks the date, group size, dietary spread and budget, since they depend on your own diary. Keep them off the public class calendar.
What do you need to test before launch?
- Book the last seat twice at the same moment from two phones, and confirm one is refused.
- Choose "allergy" and see that the form will not progress without detail.
- Cancel a booking and check the seat returns.
- Print the tutor sheet for a class with mixed diets and read it as if you were standing at the bench.
- Cancel an entire class and watch the notification emails.
FAQ
Should the dietary question be on the product page or at checkout?
Put a summary on the product page so people see whether the class suits them, and ask the full question at checkout where it is attached to each person.
Can I refuse a booking because of an allergy?
You can decide that a particular class cannot be run safely for a particular allergy, but explain this kindly and offer another class. Check food safety guidance for your area and keep your reasoning consistent.
Do I need a waiting list?
If your popular classes sell out, yes. A waiting list that notifies the first person when a seat returns is a small feature with a large payoff.
Is a plugin enough for this?
Often yes for seat caps and add-ons. Per-person dietary data and tutor sheets are where plugins tend to run out.
If your classes need per-guest diet sheets and automatic cancellation notices, we can design the booking flow around how your kitchen really runs.