How to coordinate trader menus and prices at a food festival

You've booked good food traders, sold tickets and promised an afternoon worth leaving the house for. Then the menus arrive. Half the stalls sell variations of loaded fries, the only substantial vegetarian meal needs a long explanation, and nobody has said whether the advertised price includes the container. These are problems you can catch before hungry visitors start asking your stewards.

To coordinate food festival menus, collect consistent information from each trader, check that the combined offer suits your audience, and agree how menus, prices and availability will be communicated. Independent traders should decide their own selling prices. Your job is to make the offer understandable, deliverable and honest without organising an agreement between competing businesses about what to charge.

That distinction matters commercially. You want visitors to find something they want, understand the cost and receive what they ordered. Traders need a viable day. We'll work through the menu submission, the service checks, the commercial boundaries and the changes that can otherwise turn a good lineup into a frustrating lunch.

Start with what your admission ticket promises

Before reviewing individual dishes, read your event page as if you were buying a ticket. Does admission include food, samples, a tasting credit or simply access to independent traders? Those are different purchases. If your advertising leaves room for buyers to assume lunch is included, clearer stall menus won't solve the disappointment at the gate.

Write the food arrangement in ordinary language wherever people decide to book. For example, admission might cover entry, demonstrations and entertainment, with food and drinks purchased separately from traders. If a particular ticket includes a tasting, name the serving, participating trader and redemption conditions. Don't describe a small sample in a way that makes it sound like a meal.

Next, describe the visit you're asking people to pay for. A lunchtime family event needs credible options for someone who wants a straightforward meal. An evening built around tasting unusual dishes may encourage smaller purchases across several stalls. Either can work, but the menus have to support the occasion. An impressive lineup of specialist names doesn't tell a parent whether their child can eat anything.

You also need to know the access rules. If visitors cannot bring their own food or leave and return, the choices on site become more consequential. Explain relevant policies before purchase, including any arrangements for medical or dietary needs. Don't let an admission restriction surprise someone after they've arrived.

Our broader guide to organising a paid food festival covers the admission offer and event budget. Here, we're dealing with the next decision: how the individual food businesses will deliver the eating experience you've described. Review the menus against that specific promise before accepting them for promotion.

Collect menus in a format you can actually review

A photograph of a chalkboard is useful for seeing a trader's style. It isn't a reliable menu submission. You may struggle to read it, identify the portion or tell whether the prices apply to this festival. Ask each trader to submit the same basic information privately to the person coordinating food.

For each item, collect the dish name, a plain description, the serving size and the trader's independently chosen customer price. Ask what comes with the dish and what costs extra. Record the currency and any compulsory charges. Include the planned service hours and whether the item is intended to be available throughout the event or only for a specified session.

Then collect the information the public menu can't carry in full. Who can answer ingredient and allergen questions? Where will the current written information be available? What equipment and staff does the dish require? How will the trader tell you about a recipe change or an item selling out? These answers explain whether a promising description can survive a busy service.

Keep public descriptions separate from private business information. You don't need a trader's recipe costing or profit target to publish an accurate menu. If you ask for commercially sensitive information for a genuine contracting purpose, explain why you need it, limit access and obtain appropriate advice about its handling. A shared folder accessible to every trader is the wrong place for confidential submissions.

Set a submission deadline that leaves time to resolve questions before printing or promoting dishes. Ask the named trader contact to confirm the final version you intend to publish. That confirmation should identify the actual menu, rather than simply saying that everything looks fine in a long email thread.

Work through one menu submission before collecting the rest

Imagine you're reviewing a fictional noodle stall for a paid afternoon food festival. Its initial submission says "noodle bowls, various toppings, prices on the day". That tells you the cuisine, but it leaves almost every useful decision unresolved. You can't publish a dependable offer or explain what a visitor should expect.

Ask the owner to describe the version they will actually serve. They return a menu naming a vegetable bowl, a chicken bowl and optional toppings, each with an independently chosen price. Both bowls include noodles, vegetables and sauce in the stated serving container. The descriptions identify which photographs show that serving. Now you can check the information without negotiating what another stall ought to charge.

The trader also confirms that the vegetable bowl is intended as a main meal. That helps you assess the overall offer, but you still need to ask about ingredients and preparation before making dietary claims. A vegetable dish doesn't automatically meet the needs of every vegetarian customer or someone avoiding a particular allergen. Copy only the descriptions the trader can support.

Next, consider delivery. Both bowls use the same cooking equipment, while the toppings require extra assembly. The trader proposes limiting custom combinations during the busiest service period and explaining the available options on the board. Ask them to confirm that this is the menu they're prepared to operate, then check that your event page doesn't promise a larger choice.

The owner says the stall can trade throughout the advertised food session but needs a planned staff break. You agree how service will continue and who will contact the festival team if it can't. This prevents your help desk from confidently directing visitors towards a stall that has temporarily closed.

Finally, send the actual public description back for confirmation. Include the dish names, portions, prices and service information together. Keep the trader's private operational notes out of the public version. If you're publishing a menu online, provide the approved link so the owner can check the same page visitors will read.

This example is deliberately ordinary. You're resolving a series of small ambiguities before they become customer complaints. Once you've worked through one submission properly, you can use the same questions with the other traders without forcing their food into identical menus or asking them to compare future prices.

It also shows why a deadline alone isn't enough. Someone has to read the answers, notice the missing information and follow up while changes are still practical. Reserve that review time in the production schedule. Otherwise, you'll collect a complete folder of menus without discovering whether the festival offer makes sense.

Check the confirmation identifies who supplied the information and when. If another employee takes over the stall, they should receive that confirmed version before they start serving customers.

Review the lineup as someone choosing lunch

Now read the menus together. Start with eating occasions: a substantial meal, something lighter, a snack, dessert and drinks. Then consider the audiences you've deliberately invited. Is there meaningful choice for them, or do your festival claims depend on one item at one stall?

A vegetarian visitor shouldn't have to make lunch out of optional side dishes if you've promoted a broad vegetarian offer. Similarly, a children's option should have a clear portion and description. Don't assume a small serving of an unfamiliar, heavily spiced dish solves the problem. Ask the trader what they're proposing and describe it accurately so families can decide.

Look closely at dishes that seem different on paper. Several traders might use different names for essentially the same fried base, toppings and sauce. That overlap can be fine where demand supports it. The issue is whether the combined menus give visitors a worthwhile choice and whether your site has enough service capacity for the likely favourites.

Be careful with exclusivity. A promise that only one trader can sell a whole cuisine, ingredient or food category may restrict your options far more than you expect. It can also create competition concerns depending on the arrangement. Don't casually offer exclusivity to resolve a menu discussion; define any proposed restriction precisely and have the contract reviewed.

If you need a different food offer, speak separately with prospective suppliers about what they can genuinely provide. Avoid asking competing traders to agree among themselves who will sell which dishes or serve particular customers. Your lineup decisions and their independent business decisions need proper boundaries.

Make a short list of unresolved visitor needs before confirming the food programme. That gives you a practical recruitment brief. "We need a substantial plant based meal available for the full lunch session" is more useful than adding another stall because its photographs look good.

Keep independent trader pricing independent

There's an important difference between requiring clear prices and arranging common prices. You can require traders to explain what their advertised price buys. You should not bring competing food businesses together to agree a standard meal price, minimum spend, discount policy or shared surcharge.

The UK's Competition and Markets Authority describes how associations have broken competition law by facilitating the exchange of confidential commercial information and coordinating rivals' decisions in its guidance on trade associations and competition law. The practical lesson for a festival is to avoid becoming the person who carries pricing intentions between competing traders.

Australia's ACCC also explains that price fixing can include components of a price and discounts. A friendly group conversation about keeping everyone's margins healthy doesn't make coordinated pricing acceptable. These are jurisdiction specific examples; get advice on your actual event arrangements where you need it.

Keep proposed menus and future prices out of trader group chats. Don't circulate a private comparison showing what everyone intends to charge and invite them to adjust. The fact that finished menus will eventually be public doesn't make exchanging future commercial plans a sensible coordination method.

If a trader complains that another stall is cheaper, don't promise to make the other business raise its price. Return to the service requirements and the agreed contract. Likewise, avoid telling traders that nobody may discount at the end of the day because someone else dislikes it.

Some events buy catering under a different contractual model and sell the food themselves. That changes the questions about who sets the customer price. Establish the real arrangement with your advisers first. Calling every participating business a partner doesn't explain who sells the meal or who bears the commercial risk.

Make the full customer price easy to see

A visitor should be able to understand the cost before ordering. Put the actual price beside the actual serving, with additions described clearly. If a meal price assumes the smallest portion or excludes something shown prominently in the photograph, correct the presentation before it reaches your event channels.

The CMA's price transparency summary, updated in January 2026, explains that UK businesses normally need to include unavoidable charges in the total price shown to consumers. That includes relevant taxes and compulsory fees. Treat a mandatory container charge as part of the pricing question, rather than a detail visitors can discover at the till.

The ACCC's guidance on price displays similarly explains Australian requirements for clear pricing and the minimum total cost, including applicable taxes and unavoidable fees. Check the rules where your event operates. Don't copy a tax or surcharge convention from an overseas festival and assume it applies locally.

Here's a fictional USD example. A board advertises a bowl at $12, but every buyer must also pay $1 for the only available serving container. The visitor needs to understand the unavoidable $13 total when considering the dish. A genuinely optional topping is a different decision and should have its own clear price.

Also separate refundable deposits from the food price in a way that accurately explains the upfront payment and return conditions. Ask the provider and your adviser how the arrangement must be displayed locally. Visitors need to know what leaves their account and what they must do to receive money back.

Require the stall board, online menu and payment system to agree. If any version changes, update the others before the changed price is used. A correct terminal total doesn't excuse a misleading board that persuaded someone to join the queue.

Explain portions without pretending every dish is comparable

A tasting portion, a side and a main meal can all be good purchases. Problems start when visitors have to infer which one they're buying from a photograph. Ask traders to describe portions in terms that help someone plan their meal, using an accurate size, quantity or serving description where appropriate.

Don't turn those descriptions into a festival wide claim that every main meal will satisfy every adult. Appetites vary, and dishes differ. Be specific instead. A description might explain that a serving includes a filled flatbread and salad, while another dish is a small tasting cup intended to be eaten alongside other purchases.

Check photographs against the version being sold. A trader may normally photograph a restaurant serving with several accompaniments, then offer a smaller festival version. If you publish that image, explain the difference prominently or use an accurate alternative. The same applies to promotional videos showing garnishes or drinks that cost extra.

Bundles need particular care. List what the buyer receives, whether substitutions are available and whether the components can be bought separately. Each trader should decide its own bundle prices. Your review should catch unclear descriptions, such as a meal deal whose advertised drink turns out to be a narrow choice that wasn't disclosed.

When people ask whether the festival is expensive, answer with verified public information. Link to current menus and explain what admission includes. Avoid defending the entire event through a headline "meals from" price when that option is a limited snack or unlikely to remain available.

Our guide to hiring food trucks for an event helps with supplier selection. Once you've chosen the businesses, portion descriptions are one of the simplest ways to make their offer understandable without telling them what their food should cost.

Check affordability through your own event decisions

You may discover that the independently proposed menus don't suit the audience you intend to attract. That's a problem to solve before launching tickets. It doesn't give you a reason to arrange common selling prices between the traders.

Start with the costs and conditions you control. A high pitch fee, expensive required equipment, long compulsory hours or an unnecessary reporting burden can make the day less attractive for a trader. Review whether those requirements are justified by the event you're actually delivering. Removing an avoidable cost may improve the opportunity, but don't promise that a trader will pass a saving to customers.

Give prospective traders accurate audience information. Separate paid tickets sold, expected complimentary admissions and your planning forecast. Explain the event hours, likely meal periods and any included catering elsewhere on site. A trader estimating food demand needs to know whether another supplier is feeding a large group before they arrive at the festival stalls.

Don't offer an unsupported sales guarantee. Attendance isn't the same as food purchases, and food purchases won't necessarily be shared evenly. The trader needs to make its own stock and staffing decision using the evidence available. Your responsibility is to describe that evidence honestly rather than making the pitch look safer than it is.

If you want to fund an affordable food offer, consider a separately negotiated catering purchase or subsidy with professional advice on the contract and competition implications. Specify the customer benefit, your cost and how delivery will be verified. Don't improvise a festival wide price agreement and describe it as affordability.

Put the commercial arrangement in writing. Our event vendor agreement guide explains the wider scope. Menu requirements should match the actual agreement on fees, trading hours and responsibilities, so nobody discovers a costly new condition after accepting the pitch.

Test whether the menu can be served at the busy time

A menu can be beautifully written and still fail during lunch. Ask how the trader will take orders, prepare food and hand it over when several customers arrive together. The slowest part may be cooking, assembling, answering questions or finding completed orders, rather than payment.

Use the proposed festival menu for this conversation. A trader's usual service speed may depend on different equipment, fewer choices or more staff than they'll bring to your site. Ask what preparation is permitted at the venue, what needs finishing to order and which dishes compete for the same cooking equipment.

If a supplier expects a compact festival menu, confirm the actual dishes before publishing the full restaurant menu on your website. Fewer choices may help service, but the trader needs to decide what it can deliver safely and commercially. Don't remove items yourself from their submission and assume you've improved the operation.

Consider the programme as well. A demonstration finishing immediately before a headline performance may produce a short, intense food rush. Ask whether the food offer and staff can handle that interval. Spreading activities or providing useful information before the rush may be more effective than adding another ordering terminal.

Keep ordering and collection clear where the stall arrangement allows it. People waiting for completed food shouldn't have to repeatedly cross the line of people deciding what to buy. Menu boards should be readable before the ordering point without creating a crowd in an access route.

Great Britain's HSE advises organisers to keep pedestrian routes clear of stalls and concessions. Review the real stall layout with the people responsible for site safety. Menu decisions affect space because an elaborate ordering conversation can create a queue in a location that looked adequate on an empty plan.

Keep dietary descriptions tied to current information

Dietary descriptions help visitors find possibilities, but they shouldn't turn your event team into people who guess whether a dish is suitable. The trader needs an accurate way to provide ingredient and allergen information, supported by staff who know where to check it.

The Food Standards Agency's allergen guidance for food businesses covers England, Northern Ireland and Wales. For nonprepacked food, it recommends written allergen information supported by a conversation. Check the requirements for your food type and event location before confirming the information each trader will provide to visitors.

Ask each trader how information follows a recipe change. If a sauce supplier changes, a finished menu icon may no longer describe the dish accurately. The person updating the recipe information also needs to tell the staff serving it and anyone publishing the event menu. A deadline for promotional copy doesn't justify keeping an inaccurate claim online.

Treat terms such as vegan and gluten free carefully. They don't answer every allergy question, and a dish description doesn't establish how cross contact is controlled. Avoid expanding a trader's specific statement into a broader festival promise. If the information is uncertain, direct the visitor to the responsible trader rather than offering reassurance yourself.

Also consider how someone finds help. A visitor may need information before joining a queue, especially if they are deciding whether there is anything suitable to eat. Make the route to that information clear in advance and on site. Don't make a phone signal or a single busy cashier the only practical route.

Our guide to dietary restrictions and food allergies at events develops the wider planning questions. For menu coordination, the crucial step is keeping the published description connected to the current dish and the staff who can explain it.

Agree how changes reach every public menu

Menus change for understandable reasons. A supplier misses a delivery, a dish sells faster than expected, or a trader discovers that an item cannot be served properly under the site conditions. Decide in advance how those changes will be reported and checked.

Nominate one event contact and a deputy. Traders should know how to reach them during setup and live trading. A message buried in a general supplier chat is easy to miss. Give the contact enough information to act, including the stall, item, change, effective time and whether visitors have already ordered or paid.

Separate a description correction from a change to what a buyer will receive. If someone has already purchased an included tasting or prepaid meal, a substitution may need their agreement or another remedy under the applicable terms and law. Don't quietly replace the description and assume that resolves existing orders.

For an ordinary sold out item, update the stall board first and any current digital menu promptly. Tell staff directing visitors to the stall. If the item is a major reason people booked, assess the effect on the wider offer and explain the position honestly. Keeping an attractive dish in promotion after you know it won't be available is avoidable.

Price changes require the same care across the board and till, while remaining the trader's independent decision within the actual lawful contractual arrangement. Don't make the change contact an approval meeting between competing businesses. Have your advisers review any proposed price control or restriction before it appears in the agreement.

Keep a simple record of confirmed changes and the people informed. This helps when a visitor shows an old screenshot or a staff member has the earlier menu. You can explain what happened without reconstructing the afternoon through conflicting messages.

Walk the stalls before opening

Before visitors arrive, compare the confirmed menu with what is actually displayed. Read it from the approach a customer will take. You should be able to identify the dish, serving and price without standing directly in front of the person taking orders.

Check a sample order with the trader's supervisor. Does the payment system show the correct item and total? Are optional extras genuinely optional? Does the team know how to handle a mismatch between the board and till? Testing these details while the site is quiet is easier than resolving them with a queue watching.

Confirm that current ingredient information is accessible and the staff know who can answer questions. Check the promised service hours and any planned breaks. If a trader has changed the menu during setup, make sure your published information reflects the version they can deliver.

Brief the event help team on useful facts rather than opinions. They need to know where to find current menus, which contact handles trader problems and how to report a blocked route or a concern about food information. They don't need to rank stalls or explain away prices on a trader's behalf.

Agree where ordinary customer complaints go. Usually the business that sold the food needs to address an order problem, while the organiser deals with event information and site arrangements. Explain the actual responsibility clearly so visitors aren't repeatedly sent between a stall and the information desk.

During trading, observe where decisions slow down. Are people discovering essential information only when they reach the cashier? Is the collection queue hiding the menu? Fix the specific problem with the trader and site team. Avoid changing several procedures at once when one poorly positioned sign explains the confusion.

Review the offer before booking the next edition

After the festival, review menu accuracy, availability and service alongside the overall event result. A popular stall can have a difficult trading day if its costs were too high. A queue can reflect strong demand, slow production or confusing ordering. Find out which explanation fits before copying the arrangement next time.

Ask traders separately what affected delivery and what information they needed earlier. Keep their confidential financial information private. Don't use a debrief to circulate margins, agree future prices or organise common discount rules. Review visitor feedback for specific failures you can fix, such as an undisclosed charge, an unclear serving or a promoted dish that disappeared early.

Then change the requirements you control. You might need clearer submissions, a different programme interval, better menu placement or a more realistic promise on the ticket page. Record the change and its owner before recruiting again. The next lineup should reflect what visitors could buy and traders could deliver, with independent prices and clear information throughout.