Returns & RMA request portal for customers

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: Requests

Describe 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

My returns

My returns

Powered by Pory

In plain English

How Pory sets it up

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

01

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
02

The returns team authorizes or declines each return with a note

Deciding a return meant checking the order system, the photos in an email and the returns policy in a third tab. In Pory the team opens the return with its reason, delivery date and photos, and authorizes it or declines it with a note on the return itself. Customers get a clear yes or a reason, not silence.

Approve / reject with a reasonDone by: Returns team
03

Customers watch their return move from authorized to refunded

"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.

Status tracker for the submitterDone by: Customer

Who sees what in a returns & RMA portal

Every person signs in to their own view. This is what each role in the demo gets.

Customer

Sees only their own returns.

Pages
Home, My returns, Uploads, My orders, Returns policy
Can start
New return, Upload a photo or receipt

Returns team

Sees every return in the portal.

Pages
Home, Returns, Uploads, Refunds, Returns policy
Decides
Marks returns Authorized or Declined, with a reason

What’s in the returns & RMA portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Returns

  • Item (text)
  • Order number (text)
  • Reason (choice: Wrong size, Faulty, Not as described, Changed my mind)
  • Delivered on (date)
  • Photos (file)
  • Customer (link)
  • Requested on (date)
  • Ship back by (date)
  • What happens next (text)
  • Status (choice: Requested, Authorized, Received, Refunded, Declined)
  • Details (long text)
  • Team note (long text)

Photos and proof of shipping

  • What we need (text)
  • Return (link)
  • Needed by (date)
  • File (file)
  • Customer (link)
  • Status (choice: Requested, Uploaded, Checked)

Orders

  • Order (text)
  • Items (text)
  • Delivered on (date)
  • Return by (date)
  • Order total ($) (number)
  • Delivery (choice: Standard, Express, Store pickup)
  • Customer (link)

Refunds

  • Refund (text)
  • Return (link)
  • Amount ($) (number)
  • Refunded to (choice: Original payment, Gift card)
  • Refund date (date)
  • Customer (link)
  • Status (choice: Pending, Refunded)

Returns team

  • Name (text)
  • Role (text)

The parts behind this portal

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

Collect

1 part
  • Forms

    Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Decide

2 parts
  • 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.

Control

3 parts
  • Who sees which records

    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.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

A customer signs in with a link sent to their email and lands on Home. They see Home, My returns, Uploads, My orders and Returns policy, and only the returns that are theirs. From there they can use “New return” and “Upload a photo or receipt”.

Returns team decide: they mark each one Authorized or Declined and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your returns & RMA portal with Pory

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.

See pricing · How Pory builds a portal