Customer
Sees only their own returns.
- Pages
- Home, My returns, Uploads, My orders, Returns policy
- Can start
- New return, Upload a photo or receipt
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.”
My returns
In plain English
Pory gives every customer and returns team a sign-in of their own. Each customer sees only their own returns. It covers request → authorize → refund. Returns, photos and proof of shipping, orders, refunds and returns team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
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.
"Where's my refund?" landed in the inbox the moment the package was dropped off. In Pory each customer sees only their own returns, with a progress bar through Requested, Authorized, Received and Refunded, and the amount and date of each refund. When the warehouse marks the boots received, the customer can see it, and the follow-up email never gets written.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own returns.
Sees every return in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
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.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited customers.