Vendor Registration Form Template
Curate your market or fair lineup — product descriptions for jurying, booth sizes, and a power question that expands only when a stall needs electricity.
Apply for a stall in about three minutes. Tell us what you'll sell and what your setup needs — booth assignments follow once the lineup is set.
A good market is curated, not just collected — six soap stalls in a row helps nobody, least of all the soap makers. Vendor registration is where curation begins, and this form is built to give the market team what jurying actually requires: a concrete picture of each stall's products, footprint, and power draw.
Why these fields. Stall name and contact name are split because they diverge exactly when it matters — "Willow & Wick Candle Co." cannot answer its phone, and on setup morning you need Maya, not the brand. The product description is required and coached toward specificity by its placeholder, because vague answers are what make product-mix planning impossible; "handmade jewelry" tells you nothing about whether it clashes with three existing vendors, while "hand-stamped silver rings" places itself. The website or social link does silent jurying work: five seconds on a vendor's product page answers the quality question that three more form fields never could. Stall size drives the site map — tables, booths, and food trucks are different shapes with different neighbors — and collecting it here means your layout drawing starts from data. The electricity question is a hard yes/no, and a yes reveals the what-will-you-plug-in follow-up through a logic rule; generator capacity and circuit runs are planned per amp, and the organizer who knows about the espresso machine in advance is the organizer whose market does not brown out at ten in the morning.
What we left out. Insurance certificates and permits as required uploads — most markets verify documents after acceptance, through a channel where a human checks them. (If you prefer collecting scans up front, add a file-upload block; PDFs up to 10MB work.) Stall fees are also absent by design: invoice accepted vendors after jurying, using the export as your billing list.
Who uses this. Farmers-market managers filling seasonal rosters, craft-fair and holiday-market organizers, food-truck rally coordinators, school fete committees, con and expo artist-alley teams, and flea-market operators replacing a paper waiting list.
Make it yours. Match the stall sizes to your actual site plan and rewrite the vendor-terms label to name your real rules — setup times, teardown, what stays overnight. Set a close date for applications in Settings, and turn on email notifications so each application lands with the market team while jurying is live. The responses view is your jury room: product descriptions and links side by side, ready to compare against the mix you already have.
Layout day. Export the CSV and sort by stall size, then by power needs. That two-column sort is nearly the whole site map — big footprints anchor corners, powered stalls cluster near circuits, and the walkway flow draws itself around what remains.
Frequently asked questions
Why does the power question sometimes grow a second field?
A logic rule reveals the what-will-you-plug-in question only after a vendor answers yes to electricity — no-power stalls never see it, and powered ones cannot skip it.
Can vendors send insurance documents through the form?
Add a file-upload block if you want certificates up front — files up to 10MB per upload. Many markets instead verify documents after acceptance through a controlled channel.
How do we handle stall fees?
Jury first, then invoice accepted vendors through your existing billing channel. The CSV export filtered to accepted stalls is your invoice run.
Can applications close on our published deadline?
Yes — set the close date and time in Settings, with a closed message telling late vendors about next season's application window.