Catering website design: the minimum guest count

A caterer may set a minimum headcount because a small order can cost nearly as much to set up as a large one. The rule is sensible, but it often sits on a terms page the visitor never opens before the form. A visitor with eighteen guests opens the quote form, reaches the headcount field and finds a dropdown that starts at a larger number. There is no lower option and no line that says why. They assume the form is broken or the caterer will not take small parties, and they leave. The minimum that protects the caterer turns into a lost inquiry.

• Is the minimum headcount written above the quote form, not only on the terms page?
• Can a visitor type any guest count, or does a dropdown start at your minimum with no lower option?
• Does the menu open in the same window, or does a PDF take over a phone screen?
• Is the time to a reply stated next to the send button?

The minimum is the first thing a small-party visitor needs, and often the last thing the page shows. Check it on the page itself. Open the quote form on a phone and try the smallest party you take, then one just under it. If the form refuses the number without saying why, the visitor is guessing. A short line above the form, in the same words as the terms page, lets a visitor with a smaller party go elsewhere at once, and it saves you a form you would have turned down anyway.

A menu attached as a PDF opens full screen on a phone, and the way back to the quote form can be a small arrow or nothing at all. A visitor comparing menus with a guest list ends up on the document, scrolls for the vegetarian options and loses the form they were filling. Test it: tap the menu link on a phone, then try to return to the quote with your thumb. If that takes more than one tap, put the three or four main options in the page and keep the PDF as the full list.

Look at the date and dietary fields too. A required date field that rejects a date a few weeks out, or a required dietary box with no option for none, stops a visitor who is still deciding. A line under each field that says what it is for, and an option labeled not decided yet, keeps the inquiry moving. Walk the form with a visitor who has no dietary needs and no firm date, and see which field they cannot get past.

Give a simulated visitor a plain task: request a quote for a seated lunch for eighteen guests, which is under your minimum. Use an invented name, an email inbox and an invented event. The run shows the screen where the visitor stopped, the text they could read on the form, and whether they reached the menu. Run it twice, once with a party above your minimum and once below it. If the two runs look the same, the page is not telling small parties why they are not welcome, and they will assume the worst.

Landing page testing

Caterers change their minimums for peak season, new venues and large bookings, and each change moves the headcount field and the rule. A higher minimum set for weddings can hide the small-party path, and a new menu PDF can change how the page opens on a phone. After any change, rerun the small-party visitor and check the rule above the form. Then run the wedding visitor, since a fix for small parties can make the large order harder to find.