How to prevent food vendors running out before your festival ends

It's early evening, the next act is about to start, and your most popular food stall has stopped taking orders. The trader has ingredients somewhere, but the delivery van can't get through the site. Another stall is still open, although it has sold out of the only main meal some visitors can eat. You have food businesses on site. You no longer have the food offer you advertised.

To reduce the chance of this happening, agree each trader's demand forecast and replenishment plan before you confirm the pitch. During the festival, check how many complete meals remain and whether replacement stock can reach the stall before those meals sell. Buying more food is only useful when the trader can store it safely, prepare it and serve it at the time people want it.

You can't guarantee that every dish will last until closing. You can make the assumptions honest, identify shortages early and have an agreed response. That's what festival vendor stock planning needs to achieve. We'll work through a fictional festival, including a delayed delivery, then turn the method into a brief you can use with your traders.

Start with the food offer people are relying on

The first thing you want to check is what you've actually promised. Is food bought separately from independent traders? Does admission include a meal or a tasting? Are you advertising food throughout the day, or a particular lunch session? Your stock plan needs to support those words.

This guide assumes a paid festival where visitors buy meals separately from independent food businesses. The traders decide what stock to purchase and operate their food businesses. The organiser supplies accurate event information, agrees practical trading conditions and coordinates site services. If you've purchased an included meal for every ticket holder, start with your contractual meal obligation and our guide to calculating catering quantities per attendee.

Write down the minimum useful offer for each part of the day. That might mean substantial meals during the evening programme, rather than a requirement that every dessert remains available. Be specific about options your promotion has made important, including suitable choices for the audience you've invited. If you advertise meals until the final food hour, ask the traders how they will maintain that offer.

Consider how dependent visitors are on your site. An urban event with nearby restaurants and straightforward re-entry creates different practical consequences from a remote festival where leaving means missing the programme. Explain your actual food and re-entry policies before purchase, including arrangements for medical and dietary needs. Those policies affect what people can do if the on-site offer fails.

Then separate crew catering, artist hospitality and included guest meals from public trading. Tell traders about these arrangements because they affect potential purchases. Don't add every person with a wristband to the same customer forecast, then also tell the crew caterer to prepare their meals. Someone who has already eaten an included dinner may still buy a snack, but that's a different assumption.

The useful question is whether visitors can still buy an appropriate meal when they need one. Counting open stalls alone won't answer it. One may sell only sweets, another may be taking its final orders, and another may have lost the ingredients for most of its menu.

Forecast meal purchases by trading period

Share an attendance forecast that distinguishes confirmed facts from your judgement. Traders need paid tickets sold, expected additional sales, other admissions and the programme. They also need to know whether those people are expected together or across several sessions. A capacity figure describes what you can admit. It doesn't establish how many customers a stall will have.

Ticket information is a useful starting point. Loopyah's ticketing tools show ticket sales and let your door team scan QR tickets on their phones. Use that admission information when updating the event forecast, while keeping your assumptions about food purchases separate. A ticket sold or scanned doesn't tell you which meal that visitor will buy.

Here's our fictional example. A festival expects 1,000 public visitors across its trading day. For planning, the organiser and traders test 1,200 main-meal purchases, spread across lunch, afternoon and evening. Some visitors buy twice, some buy once and some don't buy a main meal. Snacks and drinks are excluded. These are invented assumptions for explaining the method, not festival consumption benchmarks.

The planning split is 300 main meals at lunch, 180 during the afternoon and 720 during the evening. That adds up to 1,200. The large evening assumption reflects this fictional programme and expected length of stay. Your own split needs evidence from comparable trading or an explicit discussion with the traders when you don't have it.

Ask what would make that split wrong. An early headline set could bring dinner forward. A hot afternoon could change the appeal of dishes. A revised re-entry policy could change how much people buy on site. Treat these as reasons to test alternatives, rather than assigning an invented uplift to every possible change.

For a first edition, show a lower and higher purchase assumption as well as the working forecast. Ask each trader what they could change under each version, and by when. A forecast becomes useful when it informs a purchasing deadline, a delivery booking or a menu decision. Three totals that lead to the same order haven't bought you any flexibility.

Don't distribute the expected meals evenly across stalls and call the job finished. Location, menu, visibility and service speed can produce very different demand. Work privately with each trader on its own forecast, using relevant evidence. Keep confidential purchasing plans and commercial information out of a group comparison between competing businesses.

Check whether each trader can sell complete meals

Once you have a working allocation, ask what actually limits the trader's available portions. Ingredients are only part of the answer. Containers, accompaniments, equipment and preparation time can determine whether the advertised meal can be sold.

Suppose a fictional bowl trader accepts a working forecast of 360 main meals. Its portion records show enough filling for 400 bowls, rice for 340 and serving containers for 380. With no accepted substitution or replenishment, it can produce only 340 complete meals. The smallest required component limits the offer. Reporting 400 because the filling is the expensive ingredient would overstate availability.

Now ask whether all those portions can be prepared during the relevant session. Raw ingredients in storage don't become ready meals instantly. The trader should explain its planned preparation batches, equipment and staff, and confirm that these fit its safe operating method. You need to understand the dependency without trying to run the kitchen yourself.

A useful opening check distinguishes complete meals ready to sell, additional meals that can be prepared from usable on-site stock, and confirmed replacement stock outside the stall. Keep those figures separate. A delivery booked for later is a future supply assumption until it arrives, passes the trader's checks and becomes usable.

Also identify ingredients shared across dishes. If the chicken and vegetable bowls both need the same rice, the rice total supports both options together. It cannot support the full reported quantity of each. Ask the trader to show how the available components divide across its actual menu.

This matters for dietary options too. Two menu names may depend on the same limited component, or a substitution may change which customers can eat either dish. The trader needs to check its current ingredient information and preparation controls. Don't describe a fallback as suitable merely because its main ingredient sounds similar.

Packaging deserves a line in the check because it is easy to overlook. Confirm what the trader will do if the planned container becomes unavailable, including whether an alternative is appropriate for the food and accepted under the event's waste arrangements. A tray of food without a usable serving method is still interrupted service.

For the wider offer, use our guide to coordinating food festival menus. Here, keep the stock report focused on the meals that can actually be sold under the agreed menu, rather than the most reassuring ingredient count.

Make restocking possible before you depend on it

Ask every trader to describe the full replenishment journey. Where is the stock now? Who releases it? Who transports it? Where does the vehicle stop? Who receives it, and how does it reach the stall? The journey ends when the trader can use the stock, not when a driver reaches the postcode.

Work through the journey with your site team. A delivery entrance may be available during setup but closed during public trading. A vehicle may be too large for the service route. A driver may have the correct address but no accreditation or contact. Resolve these details before a trader purchases stock on the assumption that a second delivery is straightforward.

Great Britain's Health and Safety Executive advises organisers to manage event transport risks, including separating people from vehicles and planning trade access without passing through public areas where possible. Check your site's actual transport arrangements with the responsible team. An urgent food delivery doesn't justify improvising vehicle movements through a crowd.

Agree a receiving point and a safe transfer method for deliveries that cannot approach the stall. Confirm the people, equipment and time required. A trader who expects to unload alone cannot also serve a busy queue unless someone else is covering service. Include that staffing conflict in the plan.

Ask what happens when the route is unavailable. A separately agreed safe alternative may work. Sometimes the realistic answer is earlier delivery into suitable storage. Sometimes replenishment during the event isn't feasible, and the trader needs enough safely stored opening stock or a different menu. Find that out while the booking can still change.

Storage has to be confirmed as a service. Check who supplies it, who can access it, how stock is identified and how failures are reported. If you're arranging shared storage, confirm the food-safety responsibilities and handling arrangements with the businesses involved. Don't assume an empty refrigerated vehicle can become a festival store without further assessment.

The New South Wales Food Authority's guidance for markets and temporary events explains local council notification, approvals and relevant food-business requirements in New South Wales. Elsewhere, check with the appropriate local authority. Adding storage, preparation or another food outlet can raise questions that your original site arrangement didn't cover.

A credible replenishment plan names the receiving person and says when the stock will be ready to use. "Our supplier is nearby" doesn't explain either. Ask the trader and site team to confirm the same version, with a clear contact if conditions change.

Set the restock trigger using time and remaining portions

The moment to request stock depends on how long replenishment takes and how quickly usable portions are selling. A fixed report that says "low stock" gives your team too little information. Ask for the remaining complete portions, the recent sales pace and the expected time until replacement stock is usable.

Here's a fictional calculation for one trader. It is selling 60 complete meals an hour during the period being assessed. A repeat delivery takes 90 minutes between the request and usable stock at the stall. At that steady pace, 90 meals would be sold during replenishment. That's 60 multiplied by one and a half hours.

For this example, the trader also chooses to allow another 30 meals for uncertainty. It would therefore request the next delivery with 120 usable portions remaining. These figures are illustrative decisions. They aren't a recommended buffer, service standard or claim that festival sales remain steady.

The interesting part is how the same stock count changes when the delivery changes. If replenishment now takes two hours, expected sales during that interval rise to 120. Keeping the same illustrative 30-meal allowance means requesting at 150 remaining portions. A delay can make the old trigger too late even when sales haven't increased.

Use the pace expected during the waiting period, rather than automatically extending the quietest recent hour. If a performance is about to finish, demand may change before the delivery arrives. Ask the trader to explain the assumption, and review it against the programme and what is happening on site.

Report timing matters as well. If nobody reads the request until much later, the supposed replenishment time is incomplete. Include the time needed to notice the threshold, approve any agreed action, contact the supplier, transport the stock, receive it and prepare it. Where those steps vary, show the uncertainty rather than presenting a precise promise you can't keep.

There may also be a last safe order time or delivery slot. Once that passes, the trader cannot use an ordinary restock trigger for the rest of the evening. Confirm the remaining meal requirement and available alternatives before the final opportunity closes.

This calculation is a prompt for an operational decision. It doesn't predict the exact minute a stall will sell out. Check the actual menu mix and complete portions, because the overall total can look comfortable while a particular meal is about to disappear.

Walk through a delayed delivery before festival day

Let's return to the bowl trader's fictional 360-meal forecast. After reviewing the limiting components, it revises its purchase schedule. It plans enough ingredients and containers on site for 240 complete meals, with a confirmed replenishment for another 120. The plan totals 360, provided the delivery becomes usable in time. The trader has agreed storage and preparation arrangements for both quantities.

By 4pm, the stall has sold 120 meals and has 120 complete portions remaining. Its current planning pace is 60 an hour. Under the original 90-minute replenishment assumption, it requests the replacement at 4pm, expects usable stock at 5.30pm and would have 30 opening-stock portions left at that point if the pace stays steady.

Now change one fact. At 4.10pm, the supplier reports that stock will not be usable until 6.30pm. That's two and a half hours after the original request. At 60 meals an hour, the 120 remaining portions would cover two hours, until 6pm. The revised plan therefore contains a half-hour interruption under these simplified assumptions.

That is the time to act. Waiting until the stall has only a few bowls left wastes the warning. The trader and event lead should check whether an already agreed alternative supply can become usable sooner, whether a suitable alternative dish can remain available, and how the wider food offer will cope if the stall pauses.

Suppose the trader has a pre-agreed option to collect suitable stock from an approved nearby preparation base. The site team still needs to confirm receiving access and timing. The trader still needs to check the food and its handling. A fallback only resolves the gap once someone confirms an earlier time when replacement stock will be ready to use, before the remaining portions run out.

If no safe replenishment is possible, the trader should revise availability honestly. That might mean closing one dish and continuing with another verified menu option. It may mean pausing orders. The organiser checks alternative food provision and keeps public information current, without promising that another stall has stock merely because it is still lit up.

Don't interpret the example as a reason to stretch holding times, reduce portions without telling customers or send a vehicle through an unsafe route. The useful lesson is that the delivery update gives you a decision before the shortage. The numerical timing assumes steady sales and immediately usable complete portions; the real trader must also assess preparation capacity and changing demand.

Check the whole food offer when one stall struggles

A popular trader selling out can shift demand elsewhere. That means the stock reports from the remaining stalls may become outdated at the same moment. Ask the food lead to check the affected options and trading periods, rather than only helping the original stall find ingredients.

Start with what people can buy now. Which substantial meals remain? Where are they? Can the traders serve additional customers, and do their remaining components support those dishes? A stall with plenty of ingredients may already be at its preparation limit. Sending everyone there could create a queue without increasing meals served.

Check the needs that have few alternatives. If you've promoted a substantial plant-based offer and only one trader still provides it, speak to that trader privately about remaining availability. Do the same for any specifically promised included meals. Keep statements about allergy suitability tied to the responsible food business's current information.

Ask the site and crowd teams to assess any changed customer movement. You don't want a food response creating a new obstruction. Our guide to food truck layout and access covers the space and service arrangements that should support these decisions before opening.

Keep drinking-water provision under its own event plan. A food stock report doesn't establish whether the site has adequate water or whether visitors need another welfare response. If the problem affects safe event operation, involve the responsible event manager and follow the event's arrangements instead of treating it as an ordinary trader delivery issue.

Decide who can approve extra event spending. A replacement purchase, additional transport or emergency food provision may sit outside the original trader agreement. Record who is buying, who receives the stock, who sells or supplies the food and who pays. Avoid an informal promise made under pressure that nobody can explain at settlement.

Sometimes an early intervention is a service decision rather than a purchasing decision. You might correct a misleading direction sign, ask the trader to update its available menu or improve the communication between the receiving point and stall. Check the cause before spending money. More ingredients won't fix a missing cook or a broken service appliance.

The organiser's role is to coordinate the response and protect the actual visitor offer. The trader remains responsible for its own food-business decisions and safe preparation, while the organiser remains responsible for the site services and duties it controls. Make those boundaries clear enough that neither team waits for the other to act.

Keep substitute ingredients connected to food-safety information

A substitute ingredient can solve a purchasing problem and create a different problem at the counter. A replacement sauce, bread or prepared filling may have different ingredients or handling requirements. The trader must check the actual product before using it and update the information staff rely on.

The Food Standards Agency's allergen guidance for food businesses, covering England, Northern Ireland and Wales, explains requirements for allergen information and handling. For loose food, it recommends written information supported by a conversation. Use the rules for your event's location and food type, rather than assuming a printed menu remains correct after a substitution.

Ask each trader to describe its change procedure in advance. Who checks the replacement product? Who updates the ingredient and allergen records? How do staff at the ordering point learn that the dish has changed? Who tells the event contact if the festival menu or dietary description must be corrected?

Don't ask an event steward to approve a substitute. They may help contact the trader's responsible person or direct a visitor to current information. They shouldn't assure someone that the dish is suitable based on its name, a previous recipe or an old photograph. Uncertainty needs an honest answer from the business that can assess it.

Transport and storage also remain part of the replenishment decision. Food Standards Australia New Zealand's food transport guidance explains contamination protection and appropriate temperature control during the journey. A local purchase is still a food transport operation; proximity alone doesn't establish safe handling.

Avoid writing your own universal temperature or time rule into a trader briefing. Confirm that the trader has an appropriate method for the product, journey and jurisdiction, with the relevant records and receiving checks. Ask how unsuitable stock is rejected and reported. Your remaining-portion count should exclude anything that cannot safely be sold.

Apply the same discipline to stock transferred between businesses. Don't casually pool ingredients because several traders appear to use the same product. Ownership, traceability, handling, recipe information and permission all need to work. If a planned shared supply arrangement is useful, agree it properly before opening and have the responsible businesses confirm the controls.

For the broader event process, our guide to dietary restrictions and food allergies explains what to establish with suppliers. During a shortage, keep the change specific and confirmed. A substitute that staff cannot accurately explain should not be presented as the unchanged dish.

Agree a stock report traders can maintain while serving

You need enough information to act without creating a second job for someone already serving customers. Agree the reporting method with each trader and the person who will read it. If their sales system already provides useful item counts, use those records where practical rather than asking them to retype the same information.

Keep sales and remaining stock distinct. A sales report can show completed purchases, but it may not include waste, staff meals, damaged packaging or a component that has run out. Ask the trader how the remaining complete portions will be checked, and who corrects the estimate when the menu changes.

Use a short standard update that names the stall, reporting time, meals sold, complete portions remaining by relevant option, current demand assumption, replenishment position and required action. An estimated count is fine when it is labelled and useful. An unexplained green status can hide a delivery that everyone assumes someone else has confirmed.

Here's a copyable fictional update. "Bowl stall, 4pm. Sold 120 main meals. Complete portions remaining 120, including 40 vegetable bowls within that total. Planning at 60 meals an hour for the next period. Requested 120-meal replenishment; usable stock expected 5.30pm. Trader supervisor contacts the supplier. Event food lead to confirm receiving access. Report immediately if the time stock will be ready changes."

That update doesn't ask the event lead to manage the trader's recipes or see another business's confidential sales plan. It tells the lead when receiving access is needed and who to contact about the delivery. Share commercially sensitive details only with the people who need them under the agreed arrangement.

Choose reporting points around decisions, such as before the main meal rush and before the final replenishment opportunity. Ask traders to report immediately when a delivery slips, sales accelerate or another change threatens availability. Don't impose a universal reporting interval because it looks tidy. The frequency should reflect the menu, demand changes and the time available to respond.

Also agree acknowledgement. A trader needs to know whether the event food lead has received a request and what action has been accepted. Silence shouldn't be interpreted as delivery permission or a spending approval. Nominate a deputy and a workable alternative if the normal communication channel fails.

At a shift handover, pass on the current stock concerns and outstanding actions. The incoming contact needs the latest confirmed time replacement stock will be ready, rather than a morning forecast copied into a new message. Ask them to confirm responsibility for anything still unresolved before the outgoing person leaves.

Put the restocking agreement in the trader brief

A good briefing conversation needs a written record the live team can use. Keep it short enough to find the relevant facts during trading, with supporting food-safety and contract information available separately. The brief should explain the accepted plan, rather than preserve every tentative version discussed during booking.

Include the event's public food hours and the trader's agreed service hours. Identify the menu version and any dish-specific availability. Record the trader's working meal forecast by period, the complete opening-stock quantities it has accepted and any replenishment on which it depends. Mark assumptions clearly so a forecast doesn't accidentally become an organiser sales guarantee.

Write the replenishment route and contacts in practical terms. Name the supplier or collection base, request deadline, agreed receiving point, approved access arrangements, receiving person and expected time until stock is usable. Keep the driver instructions accessible to the people arranging the journey. A supplier office number alone may not help during evening trading.

Then record the response rules. What remaining portions or changed conditions require a report? Who acknowledges it? What alternatives have been assessed? Who can approve additional event spending, and how does the trader report that a dish is unavailable? State the action that follows each warning rather than collecting status updates without a reader.

For example, the fictional bowl trader's brief could say that the supervisor requests replenishment at the agreed remaining-portion trigger and updates the event food lead immediately if replacement stock will be ready later than agreed. The event lead confirms site access with the transport contact. The trader checks the delivery and confirms receipt. Nobody records the replenishment as available until those checks are complete.

Keep the commercial terms consistent with the actual contract. Who owns unused stock? Who pays for an extra delivery? Is any minimum purchase or standby provision agreed? Our event vendor agreement guide covers the wider responsibilities. Don't introduce a new financial penalty or guarantee through an operational message on festival morning.

Before opening, walk through one interruption with the people who will handle it. Ask the receiving team what they do when a delivery arrives at the wrong gate. Ask the trader what happens if the replacement ingredient differs. Ask the event contact who updates visitors when the advertised dish disappears. Correct the brief while everyone has time to read it.

Budget for availability without buying unexplained surplus

A stock plan costs money, and someone carries that cost. Traders may reasonably hesitate to buy far beyond their own forecast when they bear the full risk of unsold ingredients. The organiser may still need a dependable late food offer. Discuss that tension explicitly rather than demanding that everyone simply bring more.

Compare the practical options. Earlier delivery into suitable storage might reduce access risk. An agreed standby purchase might preserve flexibility, if the supplier can actually honour it. A simpler late menu might require fewer ingredients. Each option needs a quote and a confirmed service, not an assumed saving.

Here's an invented USD comparison for the organiser. A shared, properly arranged storage service is quoted at $420, receiving support at $180, and an approved transfer service at $120. Together they cost $720. This is a fictional planning example, not a market rate or a recommendation that these services suit every site.

Assume the festival budget has a $4,500 surplus before that package, with all other income and costs unchanged. Paying the full $720 leaves $3,780. That shows the cost of this decision. It doesn't prove the package will prevent a shortage, generate extra ticket sales or pay for itself.

Check who receives the benefit and what the organiser has actually bought. If traders contribute under a negotiated arrangement, document the charge and responsibility. If the organiser funds the service, include it in the event budget. Don't count the whole value of independent traders' food sales as organiser income when your agreement only provides a pitch fee or a defined commission.

Likewise, describe uncertain losses carefully. A missed meal sale belongs first to the business that would have sold it. An attendee complaint might affect the organiser, but you can't turn that possibility into a precise future revenue loss without evidence. Evaluate the service against the visitor promise and the cost you can afford.

Extra food also needs an end-of-day plan. Ask traders what remains usable, what can be retained under their safe method and what must be discarded. WRAP's hospitality food-waste measurement guidance supports tracking waste so businesses can understand what was thrown away and why. Record enough to distinguish a sensible reserve from repeated over-ordering.

Keep tomorrow's stock separate at a multi-day festival

For a multi-day event, a strong first day can create a difficult second morning. Ask the trader to separate stock available for today's service from stock allocated to later sessions. The physical store may be shared, but the report needs to show which day the quantity supports. Otherwise, the evening team may use tomorrow's supply while believing another delivery will replace it.

Work through that decision with the trader before trading starts. Can the supplier increase the next order? When is the final request deadline? Is the product available, and can it arrive before preparation begins? If none of those conditions is confirmed, tomorrow's allocation cannot be treated as an unlimited reserve for tonight.

Suppose the fictional bowl trader has another 180 complete portions allocated to the following day. The supervisor proposes using 60 to continue tonight. That leaves 120 for tomorrow from that allocation. Tomorrow's report must show the reduced count until another 60 complete portions are confirmed as usable. Moving the stock changes when it is available; it doesn't increase the total.

Decide who needs to know. The trader owns the purchasing decision, while the event food lead needs to assess whether the next day's food offer still works. If extra receiving or transport is required, the responsible event contact must accept that arrangement. Don't let a night shift promise an early delivery to a receiving team that hasn't been told.

The physical handover also matters. Confirm who secures storage, maintains the agreed services and reports a failure overnight. The trader should identify what checks are required before food is used the next day. Stock that was present at closing isn't automatically available for sale in the morning if its condition or handling is uncertain.

Keep goods belonging to different traders identifiable under the agreed storage method. The incoming supervisor needs to know which supplies belong to the business, which have already been counted and which are awaiting checks. A handwritten total on a shared door can easily outlive the situation it describes.

Set a morning confirmation point early enough to change the offer if necessary. Ask each trader to confirm the menu it can actually operate, complete portions available and any outstanding delivery. Compare that with the coming programme and attendance assumption. Don't reopen public ordering solely because yesterday's plan said the stall would be ready.

Finally, record transfers between days in the same place as the original quantities. You want the closing report, morning count and supplier order to agree. That makes the next stock decision understandable without asking the previous supervisor to reconstruct what happened after a long trading shift.

Use the trading record to improve the next forecast

After the festival, compare each trader's accepted forecast with the trading record privately. Look at purchases by period, the time any dish became unavailable, replenishments requested and the time stock became usable. Include unsold usable stock and waste where the trader can report them consistently. The point is to explain the result, not produce a league table.

A stall that sold every planned meal by early evening hasn't necessarily demonstrated the full demand for its food. Once it stopped selling, later customers couldn't appear in its sales total. Record the sold-out time and any reliable evidence of unserved interest, without converting every person in a queue into a certain lost purchase.

A stall with surplus hasn't automatically overestimated the audience either. Its pitch might have been difficult to find, its service might have paused or its popular dish might have depended on a missing component. Find the cause before lowering next year's forecast. Otherwise, you could reduce stock for a problem that better access or a clearer menu would solve.

Keep delivery performance visible. Compare when stock was expected to be ready with what happened, and identify which step caused the delay. If the van reached the gate on time but stock waited for a receiver, choosing a different food supplier may leave the actual problem untouched. Assign the change to the team that can make it.

Then review your own information. Did you tell traders about included crew meals, revised attendance and programme changes? Did you describe a hopeful sales forecast as confirmed demand? Did a final delivery restriction reach everyone who depended on it? These are organiser decisions you can improve before the next booking round.

Update the assumptions you can explain, and retain the uncertainty where you still lack evidence. Your next edition should start with better period-by-period demand, a realistic replenishment journey and a clear record of which meals remained available. Before confirming the next trader, ask them to show how their stock will support the final public food hour. If that answer depends on a delivery, check the whole journey with them before accepting the plan.