Describe your festival or market and get an application for vendor contacts, menus, permits, equipment, utilities, and booth needs.
Route vendor applications to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adapt it, or send it to the Makeform builder.
Audience
Food trucks and temporary food stalls
Format
Application with menu, permit, and utility sections
Prompt size
258 chars
Example form structure
Application with menu, permit, and utility sections
Business and primary contact
Menu items and prices
Permit and insurance files
Power, water, and propane needs
Booth or vehicle dimensions
Suggested routing tags
Ready for review
Permit follow-up
Power request
Ask for each appliance and its amperage so the site team can calculate total load.
Step 1
Apply
vendor, menu, documents, and booth plan
Step 2
Review
fit, duplication, permits, and site needs
Step 3
Confirm
placement, utilities, fee, and arrival slot
Step 4
Operate
setup details available to the event team
Why use one application
A promising menu can still be a poor site fit when a trailer blocks an aisle or several fryers exceed available power. One structured application gives programming and operations teams the same facts.
Collect item names, descriptions, prices, dietary options, and service style in a consistent format, making cuisine mix and duplicate offerings easier to review.
Request the permits, insurance files, and production details your own review process calls for, with follow-up fields based on vendor type.
Capture footprint, trailer access, appliances, amperage, fuel, water, refrigeration, and waste needs before booth placement begins.
Built for different events
Start with the closest scenario, then replace example policies, dates, fees, and document requests with the requirements set by your event team and relevant authorities.
Screen food trucks, tents, concessionaires, and nonprofit booths while collecting arrival, setup, and multi-day attendance details.
Collect recurring dates, product categories, production location, sampling plans, stall hardware, and seasonal availability.
Ask detailed questions about cooking equipment, holding methods, lighting, electrical load, staffing, and late teardown.
Review brand presentation, menu concept, prices, service speed, social links, and photos alongside practical space needs.
Application workflow
Build the application around the decisions your vendor committee and site team actually make, then keep responses structured for comparison.
State dates, venue, vendor types, fees, and available utilities.
Require menu basics, then reveal relevant fuel, sampling, trailer, or nonprofit questions.
Share one link, route applications, and tag follow-up.
Review answers, record decisions, and plan placement and arrival.
Form vs email vs generic template
Food vendor selection spans programming, document review, and operations. The useful format is the one that keeps those details connected for every applicant.
Field guide
These six sections turn a contact form into a useful intake for menu curation, document follow-up, booth planning, and vendor communication.
Vendor profile
Collect business and event contacts, then ask whether the applicant uses a truck, trailer, tent, cart, or packaged-goods stall.
Menu and pricing
Request item names, descriptions, prices, serving style, on-site preparation, and vendor-provided dietary labels for menu review.
Permits and records
Use labeled uploads and due dates for records your event requires. Requirements vary by location, event, and preparation method.
Booth and access
Capture occupied width and depth, including doors, hitches, awnings, tie-downs, queues, and serving windows, plus arrival constraints.
Utilities and equipment
Ask for each appliance, voltage, amperage, and plug type, plus water, wastewater, refrigeration, fuel, and cooking equipment.
Policies and scheduling
Present deadlines, fees, packaging, waste, arrival, and cleanup rules. Record acknowledgment while keeping selection and payment separate.
Related tools
Connect applications with general vendor intake, event registration, food-safety checks, catering requests, and post-event feedback.
Collect booth, product, staffing, and site needs from non-food and mixed vendor groups.
Open toolCreate a general vendor record for approved suppliers and event participants.
Open toolBuild an operational checklist for the food-handling checks your event team performs.
Open toolHandle attendee or participant registration alongside vendor planning.
Open toolGather headcount, menu, schedule, service, and venue details for catering inquiries.
Open toolAsk attendees, staff, or vendors what worked after the event closes.
Open toolFAQ
Practical answers for festival, fair, market, and pop-up organizers building vendor intake.
It helps an event evaluate food businesses by connecting vendor and menu details with documents, booth dimensions, equipment, utilities, waste, fees, and scheduling.
Include contacts, service format, menu and prices, preparation method, dates, uploads, footprint, appliances, power, water, fuel, waste, setup timing, fee category, and policy acknowledgment.
Yes. Add a labeled upload for each requested document so reviewers can spot missing items. Only request records relevant to your event's review.
Ask for each appliance's voltage, amperage, plug type, quantity, and operating schedule, plus any generator and fuel. This is more useful than one power checkbox.
Yes. Use conditional logic for vehicle dimensions and hitches, tent canopies and weights, or packaged-food production and display details.
Not automatically. Treat submission, review, selection, payment, document completion, and placement as separate stages, and explain the sequence in your confirmation message.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge, so you can build and run the application without a usage limit on the free tier.
Use consistent fields and tags such as ready for review, missing document, power request, or waitlist. Assign menu and site reviews, and keep internal notes separate.
Turn vendor interest into site-ready applications.
