A Google Forms vendor application, step by step.

1. Create a new form in Google Forms and name it with your event and date, such as the event name followed by Vendor Application.
2. Add short answer questions for the business name, contact person, email, phone, website and Instagram.
3. Add the product questions: category, a description, and a link to photos or an upload question. Ask whether everything is handmade or resold.
4. Add space questions: booth size or type, power, tent and table needs. Use multiple choice so answers are consistent.
5. Add a section for documents and agreements: what they hold (insurance, licenses, food permit) and a required checkbox agreeing to your rules and refund policy.
6. In Responses, link the form to a Google Sheet so every application becomes a row you can sort and filter. Use sections and show-questions-based-on-answers logic so food vendors see food questions only.
7. Test it yourself, then share the link on your site, in your newsletter and in vendor groups. Set a clear application deadline in the form description.

Our vendor application form template lists every question worth asking, grouped the way the form above is. Copy it into Google Forms in a few minutes.

• It is familiar to nearly everyone, and vendors can fill it out on a phone.
• Responses can be stored in a Google Sheet, with charts of the answers, so you can sort and filter applicants.
• You can show different questions depending on earlier answers, add images and videos, and share the form for joint editing with a co-organizer.
• It suits a small one-off event with a handful of vendors.

A form collects answers. The rest of running an application happens around it, by hand.

• Payments: the form does not take booth fees. You send a payment link separately and match each payment to an applicant.
• Booth assignment: there is no map or inventory. You track who has which booth in a spreadsheet and keep booth limits yourself.
• Document review: uploaded insurance certificates and permits need to be opened and checked one at a time, and expiry dates tracked separately.
• Waitlists and statuses: approve, reject and waitlist are columns you maintain, and each vendor gets a hand-sent email.
• Refunds and cancellations: if you reject someone who has paid, you refund them yourself in whatever payment app you used.
• Limiting responses to one per person means asking vendors to sign in to a Google account, which some will not want to do.

If you spend more time matching payments, documents and booth spots than reviewing vendors, switch. A dedicated tool keeps the application, payment, documents and booth in one record. See how bzar compares with Google Forms and Square.

• Vendors apply online with your own questions, and you approve, reject or waitlist each one.
• Booth fees are paid by card through Stripe and paid out to you; if you reject a vendor, their booth fee is refunded.
• Require documents such as insurance certificates and permits with each application.
• Lay out your venue and assign vendors to booths on a map.

Facts on this page come from these sources, checked on 2026-10-10. Details change; tell us at hello@bzar.app if something here is out of date.

1. https://support.google.com/docs/answer/6281888
2. https://support.google.com/docs/answer/2839588