How to Manage Class Bookings and Ingredient Inventory for Cooking Schools

A cooking school is two businesses bolted together. One is a hospitality business: students book a 6-person knife-skills class for Saturday at 2 p.m., expect a glass of wine on arrival, and want to leave with a clean apron and a recipe card. The other is a tiny food-production operation: 144 ounces of chicken thigh, 18 lemons, 6 jars of capers, three different gluten-free flours, and a vegan sub for the one student in seat 4 who flagged a dairy allergy at checkout.

The school that gets both halves right is the school that fills its calendar at $95 a seat and posts a 4.9 on Google. The school that gets either half wrong has students standing around because the instructor ran out of shallots, or a 0-seat class on a Friday night because the booking page was broken on mobile.

This playbook walks through the seven steps that run a cooking school cleanly: class calendar and capacity, recipe library per class, ingredient lists and shopping, instructor assignments, dietary and allergen tracking, payments and gift cards, and post-class recipe sends. Deelo is the exemplar throughout — a single platform that handles the calendar, the inventory, the instructor schedule, the allergen flags, the payment, and the recipe email without stitching five SaaS subscriptions together.

Most cooking schools start on a Google Calendar plus a Squarespace booking widget. That works for the first 30 classes. By class 100, the school has overbooked a 6-station kitchen for an 8-student class, double-booked the chef instructor on a Tuesday, and accepted a corporate team-build for a date the school is closed.

The fix is a class calendar with three layers of capacity: seats, stations, and instructors. Each class type has a maximum seat count tied to the physical kitchen — a 6-station kitchen caps at 12 students paired up, or 6 students if every student gets a station. Each class also requires an instructor and (sometimes) an assistant. The calendar enforces all three at booking time.

In Deelo Bookings, every class is a service with a duration, a capacity, a resource (the kitchen), and a staff member (the instructor). When a student books, the system decrements the seat count, blocks the kitchen, and books the instructor in one transaction. No more double-booked Tuesdays.

Every class has a recipe set. "Knife Skills 101" runs the same five preparations every week. "Hand-Rolled Pasta" is two doughs, three sauces, one filling. The recipe set is the spine of everything downstream: the shopping list, the prep sheet, the post-class email, the allergen flags.

The mistake most schools make is keeping recipes in a shared Google Drive folder named "Recipes_FINAL_v3." Six months in, no one knows which version the chef instructor actually teaches, the egg quantities differ between the prep sheet and the handout, and a new instructor is left guessing.

The right answer is a recipe library where each recipe has a single source of truth: ingredients with quantities and units, method steps, allergens, dietary tags (vegan, gluten-free, nut-free, halal), and the class it belongs to. Update once, and every downstream artifact — shopping list, prep sheet, student handout — updates with it. In Deelo, recipes live as records linked to the class type, with structured ingredient rows that the inventory and shopping steps read from automatically.

If a Saturday Knife Skills class has 12 students, and each student debones one chicken thigh, the school needs 12 chicken thighs. If a Pasta Tuesday class has 8 students working in pairs, the school needs 4 batches of dough — which is 8 cups of flour, 12 eggs, and a pinch of salt.

The school doing this on paper is doing third-grade math four times a week and getting it wrong twice. The school doing this in software multiplies recipe quantities by booked seats, sums across all classes for the week, subtracts what is already on the shelf, and produces a single shopping list grouped by supplier (produce, protein, dry goods, dairy).

Deelo Inventory handles the math. Each ingredient is an inventory item with a current count, a reorder threshold, and a supplier tag. When the bookings for the week settle on Wednesday night, the school runs a "weekly shop" report: the system pulls every booked class, multiplies recipe ingredients by enrolled students, subtracts on-hand inventory, and outputs the shopping list. Receipts come back, the team scans them in, and the on-hand counts update.

Not every chef instructor teaches every class. The pasta specialist owns Pasta Tuesdays. The pastry chef owns Sunday Croissant Lab. The knife-skills instructor handles the foundations classes. A new sushi class needs the instructor who actually trained at a sushi bar — not the savory chef filling in.

Matching skills to classes is two things in software: a skills matrix on each instructor, and a constraint at booking time so an unqualified instructor cannot be auto-assigned to a class type they do not teach.

In Deelo, each staff member has tags for the class types they teach. When a class is booked, the system only offers instructors whose tags include that class. If the pasta specialist is on vacation, the system surfaces only the other instructors qualified for pasta — not the entire staff list. The school avoids the awkward Saturday morning when the booking page accepts a class no one on the schedule can actually teach.

Allergens are not a customer-service nicety. They are a liability issue. A student who flagged a tree-nut allergy at checkout and got served a pesto with pine nuts has a complaint that ends in a lawyer's office.

The school's job is to capture the allergen at checkout, surface it to the instructor before class, and make a substitution that the student approves. Most schools fail at the surface step: the allergen lives in a Stripe customer note, the instructor never sees it, and the substitution is improvised on the line.

The right pattern is a required allergens-and-restrictions field at checkout, attached to the booking, surfaced on the instructor's day-of class roster with the student's name and seat. The instructor sees "Seat 4: Maria — tree nut allergy, sub sunflower seed in the pesto" before the class starts, not when Maria asks at minute 35.

Deelo Bookings supports custom intake fields per service. Allergen and dietary fields are required at checkout, stored on the booking, and printed on the prep sheet the instructor reads while setting up. The recipe library's allergen tags also flag automatically: a class with a peanut-containing recipe shows a warning before a student with a peanut allergy can complete the booking.

Cooking schools sell three things: individual class seats, multi-class packages, and gift cards. Gift cards are 30-40% of December revenue at most schools and a meaningful share of every other holiday. The payments system has to handle all three plus a clean cancellation policy.

The cancellation policy needs to be enforced by the software, not by a tired front-desk person at 8 p.m. A typical policy: full refund up to 7 days before class, 50% credit between 7 and 48 hours, no refund inside 48 hours. The system should read the booking date and apply the rule automatically — a refund button that reads the policy and either refunds, issues credit, or refuses with a clear message.

For gift cards, the right pattern is a digital gift card that the recipient redeems at checkout, which decrements the gift card balance and accepts payment for the class. The school should be able to see outstanding gift card liability on the books — money owed to future students — without exporting a spreadsheet.

Deelo handles class seats, packages, and gift cards on a single Stripe-backed payments layer. Cancellation rules live as a setting on each class type. Gift cards are a balance ledger that decrements at redemption and shows up on the school's billing dashboard as a liability.

The class ends, the students leave with a glass of wine and a paper handout, and twenty minutes later half of them have lost the handout. The school that emails the recipes within two hours of the class ending gets two things: a tangible reminder of the experience, and the most-clicked email of the month — a reorder driver for the next class.

The email is automatic. When the class status flips to "completed," the system pulls the recipes attached to the class, formats them into an email, attaches a PDF, and sends to every student on the roster. The email also includes a discount code for the next class booked within 14 days — the single highest-converting upsell in the cooking-school playbook.

Deelo's automation engine fires this email on the class-completed event. The recipe content is pulled from the same recipe library used for the shopping list and the prep sheet — one source of truth, three artifacts. The discount code is generated per-student so the school can attribute the next booking to the recap email.

Deelo is the platform that ties the seven steps into one system. Bookings handles the class calendar, capacity, instructor assignments, allergen capture at checkout, payments, gift cards, and cancellation rules. Inventory handles the recipe library, ingredient quantities, shopping lists, supplier tags, reorder thresholds, and weekly reconciliation. The Automation app fires the recap email on class completion. The CRM tracks every student, their dietary flags, their booking history, and their lifetime value. One platform, one source of truth, $19/seat/month — instead of stitching Mindbody plus a separate inventory tool plus a separate email tool plus a separate gift-card vendor.

A cooking school running on Deelo books the Saturday Knife Skills class on Monday morning, places the produce order Wednesday night based on the booked seats, prints the prep sheet (with allergen flags) Saturday morning, runs the class, and sends the recap email Saturday at 6 p.m. — without anyone re-keying data between systems.

Run your cooking school on a single platform: bookings, inventory, payments, gift cards, instructor scheduling, and recipe-recap automation in one place.

[Start with Deelo Bookings — free to try, no credit card required.](/apps/bookings)