Restaurant Pre-order System for Group Bookings

The organiser of a Christmas party for fourteen forwards the festive menu as a PDF and asks each guest to reply with their choices. Replies trickle in over nine days, most by email, a few by text, one as a voice note. The restaurant receives a spreadsheet three days after the date it was promised. Two names are blank, and "no nuts" is typed beside the wrong person. The kitchen re-keys the list into its own prep sheet. Then three guests change their minds, one never answers, and the kitchen orders for the list it has, not for the table that will sit down.

Each of those slips is small. Together they decide what reaches the table: eleven portions of the wrong starter, a short main course, and somewhere on the list an allergy that was never checked against a dish. The Food Standards Agency (FSA) addresses exactly this case in its best-practice guidance on allergen information for non-prepacked food, published 24 February 2025 for England, Northern Ireland and Wales. Paragraph 50 covers food that has been pre-ordered, "for example, for a large group booking", and says:

The words "details been missed in the original order" describe an emailed spreadsheet with some precision. A list assembled by a third party, retyped by a second, and never shown to the guest it concerns is a list where details go missing. The same section of the guidance, headed "Distance selling and pre-ordering", sets the earlier duty in paragraph 46:

A pre-order collected by link, email or phone is a sale made at a distance, and this Journal reads the paragraph as applying to it. That is a reading of the guidance, not a quotation from it, and an environmental health officer is the right person to confirm how a particular venue is expected to apply it. Either way the practical point stands: written allergen information has to reach each guest before they choose, and the choice has to be recorded against the right person.

The FSA's commissioned research on adult food allergy gives the scale. Its Patterns and prevalence of adult food allergy (PAFA) final report, published 16 May 2024, estimates that "only around 6% of the UK adult population" have "a clinically confirmed IgE-mediated food allergy", which "equates to around 2.4 million people in the UK". The same report notes that a community survey in Greater Manchester "found that more than 30% of adults report having some type of adverse reaction to food".

The arithmetic on the 6% estimate is simple. A party of 14 contains 14 x 0.06 = 0.84 expected guests with a clinically confirmed allergy, so about one. That figure is arithmetic on an FSA estimate, not an observed rate at any restaurant, and it says nothing about how many guests will report an intolerance or a dislike. The survey figure of more than 30% suggests that dietary requirements of some kind are worth expecting at a large table. Across 252 guests, 252 x 0.06 = 15.12, or about 15 people.

Festive demand is concentrated, and that is what makes the email method fail specifically in December. Dojo, a payments company, reported from its own Dojo Bookings data across UK hospitality venues that Christmas party bookings had slipped 1% year on year, and that the week commencing 8 December accounted for 34% of all festive bookings (Morning Advertiser, 11 December 2025). It is one vendor's dataset, not a survey of the whole trade. The same report puts the average price of a three-course festive menu at £36.

Applied to an illustrative restaurant with 18 Christmas parties, 34% is 18 x 0.34 = 6.12, or about six parties in a single week. Six parties of 14 is 6 x 14 = 84 pre-ordered covers to reconcile in seven days, each with its own late changes and its own silent guest. This guide takes the restaurant owner's side of that week: what a pre-order system has to do, what the rules say, what it costs, and how to set one up.

The legal duty sits on the restaurant, not on the organiser who forwarded the list. The FSA's allergen guidance for food businesses (page updated 17 July 2026) is short on this point: "If you provide non-prepacked foods, you must supply allergen information for every item that contains any of the 14 allergens."

The guidance lists the 14: celery; cereals containing gluten; crustaceans; eggs; fish; lupin; milk; molluscs; mustard; peanuts; sesame; soybeans; sulphur dioxide and sulphites (above ten parts per million); and tree nuts. Paragraph 24 of the best-practice page says the same in a sentence: "There are 14 allergens that food businesses must tell consumers about if they are used as ingredients or processing aids in food." The guidance also marks the limit of the legal list: "Consumers may be allergic or have intolerance to other ingredients, but only the 14 allergens are required to be declared as allergens by food law." Paragraph 55 of the best-practice page adds that people "can be allergic or intolerant to foods outside of the 14 mandated allergens and therefore need to avoid eating those foods." A pre-order form that offers the 14 as tick boxes and also leaves a free-text box for everything else follows both statements.

For sales at a distance, the allergen guidance sets two stages in section 3.2: "If food is sold online or by phone through distance selling, allergen information must be provided at two stages in the order process." The first is "before the purchase of the food is completed", in writing or by phone. The second is "when the food is delivered", by stickers, an enclosed menu or by phone.

The guidance closes the loop with its own recommendation: "Our advice to food businesses providing non-prepacked food is that written allergen information, supported by a conversation, works best for consumers." A pre-order system supplies the written half. The conversation on the day remains with the people in the room.

Three shorter rules touch a pre-order contract. The first is cancellation. Regulation 28(1)(h) of the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 says the cancellation part does not apply to "catering or services related to leisure activities, if the contract provides for a specific date or period of performance", which describes a dated party booking. The second is the price on the page. The Price Marking (Food and Drink Services) Order 2003 requires that "any additional charge or minimum charge payable shall be indicated at least as prominently as the price of any food to which it relates", so a set-menu price and any service charge belong together on the form. The third is fairness. GOV.UK's guidance on unfair terms lists, as a sign of a term weighted in the seller's favour, "excessive cancellation charges and automatic loss of all upfront payments". The restaurant deposit system guide covers that point in depth; a pre-order system does not depend on taking deposits at all.

Most pre-order tools are described by their feature lists. The more useful test is a run of requirements, each one tied to a failure in the email method.

An organiser who fills in a form for thirteen other people is guessing at their allergies. A link for each guest means the person who is allergic is the person who ticks the box. It also moves the work. The organiser distributes links once instead of collecting and retyping fourteen answers. The resulting record is attached to a named place at the table, which the email method never achieves.

The order of the screens matters. If a guest sees every dish first and mentions an allergy afterwards, the system has to hope that the guest, the organiser and the kitchen all notice. If name and allergies come first, the dishes that follow can be filtered by what the guest declared. That single design choice changes the risk most.

The filter only works when each dish carries a recorded allergen list. A dish that contains a declared allergen should be locked, with the reason shown to the guest, so that nobody has to wonder why a starter is greyed out. A dish with no allergen information should never be presented as safe: it should be flagged as unchecked and held back from a guest who has declared an allergy until someone has confirmed it with the kitchen. This is the same duty the 14-allergen rule creates for every item on the menu, applied at the moment of choosing. The guide to adding allergens to an online menu covers building the dish-level data, and the wider restaurant allergen menu guide covers the menu itself.

A set menu with a starter, main and dessert section turns a free-for-all into three choices. Each section becomes one decision on the guest's page. That keeps the kitchen to a known set of dishes and the count to simple addition. A pre-order menu for large groups stays manageable when each course offers only a few options, because every extra option adds a line to the prep sheet and one more place for an allergen to hide.

The deadline is the restaurant's decision. No source read for this guide gives a standard figure, and the right number depends on how far ahead the kitchen orders. A restaurant that orders fish on Monday for a Friday party needs the count by Monday. The system should let the owner choose the number of hours before the booking when guest links close, and let staff edit any guest afterwards, so a late allergy or a change of mind after the cut-off is handled in the diary rather than by a text message to the chef.

People answer deadlines that are about to arrive. Automatic reminders to the organiser and to any guest who gave an email address, placed ahead of the cut-off, replace the chasing that otherwise falls on the person at the host stand. A manual reminder covers the party that has gone quiet.

Without a count, the owner learns who has not replied at the moment the kitchen needs the numbers. A tracker on the booking, showing "8 of 12 guests chosen", turns that into something visible days earlier, and a list of each place as chosen, part chosen or waiting says whom to chase.

The kitchen needs two views from the same data. The first is per guest, with each person's courses, allergies and notes in a printable sheet that works at the pass or at the table. The second is per dish: a total for each, so that the order and the prep match the choices. Both should export as a spreadsheet for suppliers or for a second pair of eyes.

Paragraph 50 asks for a discussion with individuals before food is served. A system supports that by putting the guest's declared allergens on the sheet that goes to the server, so the question at the table is specific: "You listed tree nuts, and your main is the bass, which has none." The system does not replace the conversation, and a venue that treats it as a replacement has misread the guidance.

An allergy note is personal data. The Information Commissioner's Office (ICO) defines "data concerning health" as "personal data related to the physical or mental health of a natural person, including the provision of health care services, which reveal information about his or her health status", and adds that health data "can therefore include a wide range of personal data", including "any information on injury, disease, disability or disease risk". The ICO page does not name allergies. This Journal's reading is that an allergy note collected to keep a guest safe reveals something about the guest's health and should be handled as health data. In practice that means limiting who can open the notes, keeping them in the booking record rather than in a group chat, and deciding how long to hold them. Clearing the notes once the event is over is a sensible default house rule for a one-off party.

Restaurants collect group orders in three ways, and the choice shapes everything after it.

The rest of this guide assumes the third method, which asks more of the system and less of the people.

A Christmas party pre-order form needs fewer fields than most owners expect: the guest's name, an optional email for reminders, the 14 allergens as tick boxes, a free-text box for anything else the kitchen should know, and one choice in each course of the set menu. A short note that the restaurant will check allergens again when the food is served sets the right expectation. Anything else, such as seating plans or place cards, is a second project.

A set menu pre-order depends on a set menu that is finished. Before any link goes out, check that each dish has a recorded allergen list, that the price is shown inclusive of VAT, and that any service charge is stated beside it. A guest who sees £45 on the form and £49.50 on the bill has a reason to dispute the difference. The Price Marking Order sets the standard. The form should meet it.

A corporate dinner changes three things. The organiser is often an assistant who is not attending, so the person who knows the guests' needs is not the person on the phone. The headcount moves more, because invitations go out to a department and acceptances arrive late. And the person paying may not be eating, which makes the question of who agrees to the terms a real one.

Three habits help. First, send the guest links to the guests themselves, not to the assistant, wherever that is practical, because the guests know their own allergies. Second, agree in advance a default dish for any guest who has not chosen by the cut-off, and put that rule in the booking confirmation so nobody is surprised. Third, state the cut-off in hours before the booking, because "a week before" is read differently by every department. A restaurant that takes corporate dinners regularly gains most from the tracker, since it shows at a glance how many of 40 invited guests have answered.

The figures in this section describe an illustrative restaurant and are not data from any real venue. The setting is a 70-cover restaurant with 18 Christmas party bookings, an average party of 14 and a festive set menu at £45 a head, inclusive of VAT. The wage figure is the National Living Wage for those aged 21 and over, £12.71 an hour from April 2026 (GOV.UK).

Start with the volume. Eighteen parties of 14 is 18 x 14 = 252 guests, and 252 x £45 = £11,340 of set-menu sales. That is the money riding on the lists.

Chasing and re-keying come next. At an illustrative 25 minutes a booking, 18 x 25 = 450 minutes, or 7.5 hours. At £12.71 an hour that is 7.5 x £12.71 = £95.33, rounded from £95.325. At an illustrative supervisor rate of £16.00 it is 7.5 x £16.00 = £120.00. These are wage costs only, without employer National Insurance, pension or overheads.

Over-preparation is the larger line. If the kitchen preps for an illustrative 5% more covers than are eaten, that is 252 x 0.05 = 12.6 covers. At an illustrative food cost of 30% of the £45 price, which is £13.50 a head, the waste is 12.6 x £13.50 = £170.10. A single party shows the shape of it: if the kitchen prepped 30 portions where 22 were ordered, 30 minus 22 is 8 spare portions, and 8 x £13.50 = £108.00 on one booking.

The on-the-day allergen check costs time as well, and no software removes it. At an illustrative five minutes of front-of-house time per party, 18 x 5 = 90 minutes, or 1.5 hours, and 1.5 x £12.71 = £19.07.

Added together on the National Living Wage basis, chasing (£95.33), over-prep (£170.10) and the on-the-day check (£19.07) come to £284.50. One failed party of 14 is a separate risk: 14 x £45 = £630 of sales at risk, and a lost margin of 14 x (£45 minus £13.50) = 14 x £31.50 = £441 if the food was already bought. A payment taken in advance is one way to narrow that exposure. A £140 online deposit payment, for example, would carry Stripe's published 1.5% + 20p for standard UK cards: 0.015 x £140 = £2.10, plus £0.20, makes £2.30.

The honest reading of these numbers is that the visible leakage is only part of the cost. One December of chasing and over-prep comes to £284.50 by the sum above, and that figure does not price the allergy risk, the group occasions across the rest of the year, or the hectic week in which a few staff hours turn into a count the kitchen can plan from. It also matters what the software replaces: a plan that already carries the website and the bookings adds pre-orders without adding a separate line to the bill.

Software for this job is sold in several ways: as a plan with add-ons, as a higher tier of a booking plan, as a starting price with the rest unstated, and as one plan that covers the work. Each page below was read on 28 October 2026. The question is the cost of a restaurant that needs a website, table bookings with deposits and per-guest group pre-orders in the first twelve months.

ResDiary's GBP pricing page lists Evo Connect at "£ 109" with "+ VAT/mo", described as "Up to 150 bookings per month", and states "A £99 set-up fee will apply." Its pricing page lists a Pre-orders add-on at "£35 per month" and an Event Manager add-on, for events, enquiries and large party bookings, at "£35 per month", with a footnote: "A surcharge of 1.2% applies for processing Deposits and Payments". The year-one sum is (109 + 35 + 35) x 12 + 99. That is 179 x 12 = 2,148, plus 99, which is £2,247 plus VAT. At the page's stated 20% VAT, 2,247 x 1.2 = £2,696.40. The surcharge sits on top: if all £11,340 of the example's set-menu sales were paid through it, 0.012 x 11,340 = £136.08, before any Stripe fees, which the page says "may apply". ResDiary's other pricing page reads "Your booking system price: tailored to your needs", so the two pages differ; the figures above come from the GBP page.

Favouritetable's pricing page places menu pre-ordering in FT Ultimo. The tier is shown at "£199per month" with "When billed annually in advance" and "Price exclude VAT", and its description reads "All the features of FT Pro plus menu pre-ordering, marketing, card payments and much more." The year is 199 x 12 = £2,388 excluding VAT, paid in advance.

Access Group's Collins Evo page says "Pricing starts from £149 per month." The lines read for this research show a starting price only. At that price the year is 149 x 12 = £1,788, and that is a floor, not a quote for any particular set of features.

TableSpark Growth is £39 a month excluding VAT, or £390 a year excluding VAT on yearly billing. It covers the restaurant website, table bookings with deposits and reminders, and group pre-orders with per-guest links, allergen checks and the kitchen sheet. Full, at £69 a month excluding VAT, adds online ordering. The difference in pounds against the year-one figures above is: £2,247 minus £390 = £1,857 against the ResDiary stack, £2,388 minus £390 = £1,998 against Favouritetable, and £1,788 minus £390 = £1,398 against Collins Evo even at its starting price.

These prices are not like-for-like. The providers charge for different things, in different ways, and each figure is the vendor's own published price on the day read, so they are separate charging structures and not a ranking of products. The point is narrower: on the pages read, a restaurant that wants group pre-orders as well as bookings is looking at a total built from a base plan plus add-ons (ResDiary), from a higher tier (Favouritetable) or from a starting price with the rest unstated (Collins Evo).

The card-fee side differs too. On TableSpark, 0% TableSpark commission applies to bookings, and Stripe's standard card-processing fees apply to online deposit payments, which was £2.30 on the £140 example above. On a stack with a payments surcharge, that surcharge comes in addition to the card fee.

Before the first link goes out, run through the list below. It combines what the rules ask with what the failure modes of the email method need.

The route depends on how many parties a year the restaurant takes and what else the same software has to do.

An add-on stack sits between the two. It can do the work, but the total depends on which base plan, how many add-ons and what surcharges apply, and that total is the figure in the previous section. For an independent restaurant that wants the website, the bookings and the pre-orders in one place, the arithmetic favours the single plan.

TableSpark's booking system carries group pre-orders on Growth and Full plans, from £39 a month excluding VAT. The steps below follow the take group pre-orders tutorial, which shows each click on a demonstration restaurant. The sample data in the screenshots belongs to that demonstration.

• Build and complete the set menu in Menu first. The allergen check on the guest page is only as good as the allergen data behind each dish.
• Choose a cut-off that matches your ordering day, not a round number.
• The kitchen management page shows how the day's sheet sits beside the rest of the kitchen workflow.
• For wider festive planning, the Christmas bookings guide covers capacity and staffing, and the group booking guide covers party size rules and table joining.

A pre-order page only helps if guests reach the restaurant before a directory or a marketplace. A website can be live at a working link and still be absent from Google, because robots or noindex directives, conflicting canonical addresses, orphaned pages, rendering problems, missing structured restaurant data or incomplete search verification can leave pages undiscovered, excluded or misunderstood. TableSpark packages crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant and LocalBusiness schema, internal links, mobile-first output and managed search-verification set-up into the plan, on every tier. Indexing and ranking remain decisions for Google. The Reserve with Google booking-link connection, on Growth and Full, makes the restaurant's own booking page the destination guests reach from Google. It is a booking-link connection: the guest completes the booking on the restaurant's own page.

Guest records are stored under the restaurant's TableSpark account, visible in the Inbox and the guest list, with CSV export, and each group booking keeps its guests' choices and declared allergens on the booking.

For an independent UK restaurant, TableSpark is the best-value and best overall choice for taking group pre-orders. The email method leaves allergy risk with the restaurant. An add-on stack prices pre-orders after the entry price has done its work. TableSpark Growth is £39 a month excluding VAT, or £390 a year excluding VAT, and includes the website, table bookings against real tables with deposits and reminders, per-guest group pre-orders with allergen checks, a cut-off you set, reminders, a tracker and the kitchen sheet with dish totals. The whole TableSpark range starts at £19 a month excluding VAT for the website, the enquiry forms and the Inbox, and online ordering arrives with Full at £69 a month excluding VAT. The pricing page shows each plan.

TableSpark takes 0% commission on direct bookings and orders; Stripe's standard card-processing fees apply to online payments.