A supplier onboarding portal is where new suppliers upload their compliance documents, procurement approves or rejects each supplier with a reason, and suppliers get a reminder before a certificate expires.
Pattern: RequestsDescribe it to Pory
“We're a bakery manufacturer. New suppliers upload food safety certificates and insurance, our procurement team approves them, and we need a warning before any certificate expires.”
My compliance documents
| Document | Type | File | Supplier | Status | |
|---|---|---|---|---|---|
| BRCGS certificate – Leeds | Food safety certificate | 1 file | Bakare Packaging – Leeds | Uploaded | |
| Public liability insurance – Leeds | Public liability insurance | 1 file | Bakare Packaging – Leeds | Uploaded | |
| BRCGS certificate – Hull | Food safety certificate | 1 file | Bakare Packaging – Hull | Checked |
Showing 1–3 of 3
In plain English
A supplier onboarding portal is where new suppliers upload their compliance documents, procurement approves or rejects each supplier with a reason, and suppliers get a reminder before a certificate expires. 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 (supplier and procurement) that shows only what that role should see, and flat pricing with unlimited suppliers.
What it does
Compliance paperwork used to arrive as email attachments that someone saved to a shared drive under a new naming scheme each time. In Pory a supplier uploads each certificate or policy, says what it is, which site it covers and when it expires, and sees only their own documents. Procurement finds the file on the supplier's record instead of in an inbox.
Supplier approval used to be a spreadsheet row turning green, with no note of why. Procurement opens a supplier, reads the compliance documents linked to it, and approves or rejects it, writing the reason on the record. A rejected supplier knows exactly what's missing, and nobody has to reconstruct the decision before the next food safety inspection.
Expired certificates used to turn up during a customer's site visit, which is the worst possible moment to find one. Each document carries its expiry date, and the supplier gets a reminder in their portal inbox and by email ahead of it, naming the certificate and the date. Procurement stops keeping a diary of expiry dates for forty suppliers.
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, in its detail view, 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.
Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the records a viewer is allowed to see.
Control
Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up 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.
Describe it in a sentence and send the invite. Unlimited suppliers, flat price.
