My reviews
A product review portal is where customers submit a rating and review for what they bought, a moderator approves or rejects each one, and approved reviews appear on a public page anyone can read.
Pattern: RequestsDescribe it to Pory
“Customers who bought our teas should be able to leave a rating and a review. We moderate each one before it goes live, and approved reviews show on a public page.”
My reviews
In plain English
A product review portal is where customers submit a rating and review for what they bought, a moderator approves or rejects each one, and approved reviews appear on a public page anyone can read. 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 (customer and moderator) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Reviews used to arrive as replies to the order confirmation email, which meant nobody else ever read them. In Pory a signed-in customer gives the tea a rating out of five, writes a title and a review, and adds a photo if they like. It lands as Pending for moderation instead of sitting in someone's inbox.
Without moderation, one spam review with a discount code for another shop could sit on the product page for a week. In Pory the moderator sees new reviews as cards, opens each one, and approves it or rejects it with a note on the review. Honest three-star reviews go through; the SAVE20 spam doesn't.
Good reviews got screenshotted into social posts and then lost. In Pory every review the moderator approves shows on a public page anyone can open without an account, photos and all; pending and rejected ones never appear. Shoppers get opinions from real tea drinkers, and the team stops curating screenshots.
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 customers, flat price.