Exhibitor
Sees only their own applications.
- Pages
- Home, My applications, My documents, Key dates, Booth fees, Exhibitor guide
- Can start
- Upload document
An exhibitor and vendor application portal is where makers apply for a booth through a public form, the organizer approves or declines each application, and approved exhibitors see their booth and upload their insurance.
Pattern: RequestsDescribe it to Pory
“We run makers markets and want vendors to apply for a booth through a public form, our team to approve or decline them, and exhibitors to see their booth and upload insurance documents.”
Apply
Apply → approve → stand assigned
In plain English
Pory gives every exhibitor and organizer a sign-in of their own. Each exhibitor sees only their own applications. It covers apply → approve → stand assigned. Applications, documents, booth fees, key dates, exhibitor downloads and market team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Vendor applications arrive through an online form, Instagram DMs and emails with photos attached, and the organizer copies them into one spreadsheet by hand. Anyone can apply here without an account: the business, what they sell, any power or space needs, the fair and the booth type. Every application lands in one list, in the same shape, ready to review.
Choosing vendors means a spreadsheet of color-coded rows and a pile of "sorry, not this time" emails written from scratch. The organizer opens each application, reads what they sell, and approves it or declines it with a note that stays on the application, or drags it to the waitlist. Applicants hear why, and the organizer writes each reason once.
In the two weeks before a fair, the organizer's inbox is full of "do I have a booth?" and "which hall am I in?" Each exhibitor signs in to see their applications move from Submitted to Under review to Approved, with the booth number on the application once it's assigned. The questions stop arriving the week before set-up.
General liability certificates arrive as email attachments days before the fair, and someone matches them to vendors late at night. The organizer asks each exhibitor for what their booth needs, and the exhibitor uploads their insurance, electrical inspection, health permit or risk assessment to that row, with its expiry date. Each one moves from Requested to Uploaded to Checked, and the organizer opens the file from the list instead of searching an inbox.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own applications.
Sees every application in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
An application page, a notice board, an open directory: pages and forms anyone can use without signing in, on your domain.
Upload and view files on the record they belong to, not in a folder named FINAL v2.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited exhibitors.