A festival vendor application sounds like a form. In practice it is a small compliance process: you collect money, collect documents, check permits, say yes or no, and keep a record in case the health department or your insurer asks later. Doing it online is worth it. Doing it badly online, with a form that emails a PDF to one overloaded volunteer, only moves the pile.
This guide covers what to collect, how to handle payment and insurance, where Washington food-vendor permits come in (and where they do not), how to design the approval step, and which tools can run it, with prices as listed in October 2026. For the rest of the event site, see our guide to festival website design.
Already know what you need? Request an estimate and we will reply with scope and a price range for a sensible first phase.
What the application should collect
Collect only what you will use. Every extra field lowers completion. Every missing one costs you a phone call in the week before the event. A workable set:
- Business basics: legal name, contact person, mobile number, email, mailing address, and a Washington business license (UBI) number if the vendor has one.
- Booth details: category (food, craft, commercial, nonprofit), requested size, electricity needs, vehicle or trailer, and number of staff on site.
- What they will sell: a product list or full menu. For food, this is what the health department will want to see.
- Photos: two or three images of the booth and products, so you can approve without guessing.
- Documents: certificate of insurance, and permit or permit-application confirmation for food.
- Agreements: a checkbox acknowledging your rules (setup times, cancellation and refund policy, no-generator zones) with date and name captured.
Keep a separate, shorter version for returning vendors. Nothing irritates a vendor who has attended five years like re-entering the same data.
Payment: when to take it, and how
The cleanest structure is two steps. Vendors apply and, if you approve them, receive a payment link; they are not charged until they are accepted. That avoids refund work for rejected applicants. If you prefer to charge at application (a non-refundable application fee, common for juried events), say so in the form before they click submit.
Card fees come from the processor. As of October 2026, Stripe lists 2.9% + 30¢ per successful domestic card transaction on standard pricing, so a $150 booth costs about $4.65 to collect (our arithmetic). Two choices worth deciding in advance: whether vendors cover the fee, and whether you allow checks. Some small festivals still take checks from long-time vendors. Your system should record them against the application so the books match.
Insurance certificates
Whether you need vendor insurance depends on your permit, your venue and your own policy. Cities that issue special event permits may require the organizer to carry liability coverage. For example, the City of Seattle’s special events insurance page requires a minimum of $1,000,000 general liability per occurrence, with the City named as an additional insured, and says certificates are rejected if they contain certain wording, such as “AS PER written agreement or contract.” Seattle also asks for documents at least 30 days before the event. Your city will differ, so ask your permit office what they require of you, then decide what you require of vendors.
On the form, this means a file upload for the certificate and a field for the expiration date. Do not accept a certificate that expires before your event. A custom workflow can check that automatically. In a basic form tool, someone checks it by eye at approval time.
Washington food vendors: permits are the health department’s, not yours
Your application cannot issue a food permit, but it can make sure a vendor has applied for one. In Washington the local health jurisdiction regulates temporary food booths under chapter 246-215 WAC. Under WAC 246-215-09200, the owner of a temporary food establishment applies at least 14 calendar days before serving food, unless the local regulator sets a different timeline, and the person in charge needs a valid food worker card. The local authority may add requirements.
Local practice varies, so read your own county’s page. A few examples:
- Snohomish County: requires an event coordinator checklist at least 30 days before multi-day events or events with four or more food vendors, and vendor applications 14 days or more before to avoid a late fee. At least one person in each booth needs a posted food worker card.
- Spokane County: permits food booths only at community-recognized events, wants applications at least 14 days ahead, and includes an interview with food safety staff.
- Clark County: tells organizers to ensure food vendors provide documentation of permit status and to provide restrooms with handwashing.
- Seattle and King County: the City of Seattle’s special events food page says the Seattle and King County public health department lets an organizer hold one blanket permit covering all vendors instead of each vendor applying alone. The coordinator applies 30 days before the event and sends every vendor’s menu 14 days before, so it means more work for you.
Build your form with two permit fields: the permit number or application confirmation, and the date they applied. Set your own internal deadline earlier than the health department’s, so there is time to chase. Fees and rules change, so link to your health jurisdiction rather than copying numbers into your form. This section summarizes public pages as of October 2026; it is not legal advice.
An approval workflow that does not live in one person’s inbox
- Submitted: application received, confirmation email sent with the date they will hear back.
- Review: a checklist: complete, insurance valid on event date, permit status, product mix (you probably do not want nine lemonade stands), booth fits the map.
- Decision: accepted, waitlisted or declined, each with a short, kind email.
- Payment: accepted vendors get a link with a deadline. Unpaid spots go to the waitlist.
- Pre-event: load-in time, booth number, map and rules sent in one message a week out.
The usual weak point is the middle: review lives in someone’s email and a spreadsheet nobody else can see. Whatever tool you use, give the reviewer a single status field and make that visible to your committee.
Tools that can run it
- Jotform. As of October 2026, Jotform lists a free Starter plan (100 submissions a month, of which 10 can be payments, and 100 MB of uploads) and paid plans from $39 a month on monthly billing, with 50% off for approved nonprofits. Its file upload field collects documents such as certificates, and it offers workflow tools for approvals.
- Cognito Forms. Lists a free plan with 100 entries a month, 100 MB of storage and payments included, and a Pro plan at $19 a month billed annually. Storage is the limit to watch on the free plan, since insurance PDFs add up.
- ZAPP. A platform where artists and art festivals connect, with a separate offering for organizers. Check their organizer page for fees. It is built around juried art shows, so it fits those better than a general vendor market.
- Eventbrite or a ticketing platform. Built around selling tickets rather than screening applicants. Workable for paid booths with no screening.
All of these can work for a first year. Where they strain: approvals tied to payment, automatic insurance expiry checks, a year-over-year vendor record, and putting vendor data in the same system as your tickets and volunteers. That is where a small custom system earns its keep, and where custom software for small business is worth a look. If you have not tried the off-the-shelf route first, do that.
The honest verdict
DIY or off the shelf if you have fewer than about 50 vendors, one person reviews applications, and you can live with a spreadsheet. A form tool with file upload, plus Stripe payment links after approval, is enough. Your time goes to the food-permit follow-up, not the software.
Custom work makes sense when you have several hundred applicants, multiple categories with different rules, approvals that must gate payment, document-expiry checks, or a vendor database you want to reuse every year and connect to your nonprofit or tourism site. If that is you, we are glad to scope it. If it is not, we will say so.
Frequently Asked Questions
What should a festival vendor application include?
Business and contact details, booth category and size, a product list or menu, photos, a certificate of insurance, and for food vendors a health permit number or application confirmation. Add a checkbox acknowledging your rules and cancellation policy. Request only what you will actually use, and offer a shorter form to returning vendors so repeat applicants are not retyping the same information each year.
Do festival food vendors in Washington need a permit?
Generally yes, unless the food is on your health jurisdiction’s exempt list. Temporary food establishment permits come from the local health jurisdiction under chapter 246-215 WAC, and the rule asks owners to apply at least 14 calendar days ahead unless the local authority sets another timeline. Some jurisdictions let an organizer hold a blanket permit. Rules and fees differ by county, so confirm with yours.
Should vendors pay when they apply or after approval?
Most organizers collect payment after approval, which avoids refunding rejected applicants. If you charge a non-refundable application fee at submission, which is common for juried events, state it clearly before the vendor submits. Either way, set a payment deadline for accepted vendors and release unpaid spots to a waitlist so the map stays accurate. Record checks against the application too, so your books and your vendor list match.
Can I use Jotform or Google Forms for vendor applications?
Yes. Jotform and Cognito Forms support file uploads and payments, which covers certificates and booth fees. Google Forms does not take payments by itself. All of them leave approval status, insurance expiry checks and year-over-year vendor records to you. That is fine at small scale and gets heavy as the vendor list grows. If you have fewer than a few dozen vendors, a form with a shared status column is usually enough for the first year.