My returns
Returns & RMA portal
A returns and RMA portal is where customers request a return with photos and a reason, the returns team authorizes or declines each one with a note, and customers follow their return through to the refund.
Pattern: RequestsDescribe it to Pory
“Customers who want to return an order should request it with a reason and photos. Our team authorizes the return or declines it, and the customer can see when their refund is done.”
Viewing as
In plain English
What is a returns & RMA portal?
A returns and RMA portal is where customers request a return with photos and a reason, the returns team authorizes or declines each one with a note, and customers follow their return through to the refund. 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 returns team) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Customers request a return with the order number and photos
Returns started as an email saying "these don't fit", followed by three replies asking for the order number, a photo and a reason. In Pory the customer enters the item and order number, picks a reason, adds the delivery date and uploads photos in one go. The team has what it needs to decide, and the email tennis stops.
Forms to submit a recordDone by: Customer
Customers watch their return move from authorized to refunded
"Where's my refund?" landed in the inbox the moment the parcel left the post office. In Pory each customer sees only their own returns, with a progress bar through Requested, Authorized, Received and Refunded. When the warehouse marks the boots received, the customer can see it, and the chaser email never gets written.
Status tracker for the submitterDone by: Customer
The parts every portal is built from
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
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
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.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
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.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
More customer support portals
All customer support portalsSupport ticketing portalSubmit & triageWarranty claims portalSubmit → approve → replaceFeature request board portalSubmit → triage → plannedBug reporting portalReport → triage → fix statusBeta program portalSignups, feedback, releasesCustomer feedback & NPS portalCollect & actProduct reviews portalSubmit → moderate → publish
Your returns & RMA portal, live today.
Describe it in a sentence and send the invite. Unlimited customers, flat price.