A customer account portal is where each business customer signs in to see only their own orders, invoices, contracts and documents, follow each order's status, and raise a support request against an order.
Pattern: Client hubsDescribe it to Pory
“We supply commercial kitchens. Each restaurant should see their own orders and invoices, the status of each order and their contracts, and raise a support request when something arrives damaged.”
My orders
| Order | Items | Ordered | Status | Invoice | |
|---|---|---|---|---|---|
| PO-2291 | Combi oven, 10-grid | 22 Sep 2026 | Shipped | 1 file | |
| PO-2274 | Chef's knives ×12, cutting boards | 9 Sep 2026 | Delivered | 1 file | |
| PO-2295 | Gastronorm pans ×40 | 24 Sep 2026 | Received | 0 files |
Showing 1–3 of 3
In plain English
A customer account portal is where each business customer signs in to see only their own orders, invoices, contracts and documents, follow each order's status, and raise a support request against an order. It follows the Client hubs pattern: one shared space per client: deliverables, documents, milestones. Pory generates it from a plain-English description, with a login for each role (customer and account manager) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Customers used to ring their account manager for anything about their account, because the only place it all lived was the back-office system. In Pory each customer signs in and sees only their own orders, invoices, documents and support requests. The account manager sees every customer's, and no restaurant ever sees another's price list.
Finding an old invoice used to mean emailing accounts and waiting a day for a PDF. In Pory each order lists what was on it, when it was placed, its value and the invoice file attached, in one table the customer can search and sort. The accounts team stops re-sending invoices at the end of every month.
"Where's my oven?" used to be a phone call in the middle of the lunch rush. Each customer sees their own orders move from Received to Picking, Shipped and Delivered, with the items listed on each. The warehouse answers fewer calls, and the head chef plans the week knowing what's on its way.
Contracts and price lists used to be attachments in someone's inbox, and which price list was current was a matter of opinion. In Pory each customer opens their own contracts and documents, with the file attached and the date it was added. Warranty claims start from the warranty itself, not a search for the right email.
Damaged deliveries used to be reported by phone, then photographed and texted to whoever picked up. In Pory a customer picks the category and the order, adds photos and a description, and watches the request move from Open to Resolved. The account manager has the order, the photos and the problem in one place.
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 customers, flat price.
