Apply
Apply → approve → stand assigned
An exhibitor and vendor application portal is where makers apply for a stand through a public form, the organiser approves or declines each application, and approved exhibitors see their stand and upload their insurance.
Pattern: RequestsDescribe it to Pory
“We run makers markets and want stallholders to apply for a stand through a public form, our team to approve or decline them, and exhibitors to see their stand and upload insurance documents.”
Apply
Apply → approve → stand assigned
In plain English
An exhibitor and vendor application portal is where makers apply for a stand through a public form, the organiser approves or declines each application, and approved exhibitors see their stand and upload their insurance. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (exhibitor and organiser) that shows only what that role should see, and flat pricing with unlimited exhibitors.
What it does
Stallholder applications arrive through an online form, Instagram DMs and emails with photos attached, and the organiser 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 stand type and which fair. Every application lands in one list, in the same shape, ready to review.
Choosing stallholders means a spreadsheet of colour-coded rows and a pile of "sorry, not this time" emails written from scratch. The organiser 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 organiser writes each reason once.
In the fortnight before a fair, the organiser's inbox is full of "have I got a stand?" and "which hall am I in?" Each exhibitor signs in to see their applications move from Submitted to Under review to Approved, with the stand number on the application once it's assigned. The questions stop arriving the week before bump-in.
Public liability certificates arrive as email attachments days before the fair, and someone matches them to stallholders late at night. Each exhibitor uploads their insurance, food safety certificate or risk assessment to their own documents list, with its type and expiry date. The organiser opens the file from the list instead of searching an inbox.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
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.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited exhibitors, flat price.