Skip to content

The customer portal

Last updated November 20, 2026

The customer portal is the self-serve page where your shoppers file return requests. It lives on your own domain (no third-party redirect, no iframe), uses your WordPress theme’s styling, and identifies customers by order number plus the email they used at checkout — guest checkouts work the same as registered users.

Where it lives

After the setup wizard, the portal is on a WordPress Page called Returns at /returns/. The page contains one shortcode: [gorilla_returns_portal].

That shortcode is embeddable anywhere. If you’d rather host the portal inside an existing Help Center page, a customer-service section, or on a custom URL, just paste the shortcode wherever you want it. Two optional attributes let you simplify the chrome if the surrounding page already shows your branding:

[gorilla_returns_portal hide_header=”1″ hide_footer=”1″]

The flow, step by step

Step 1 — Lookup

The customer enters their order number and the billing email they used at checkout. The portal looks up the order in WooCommerce, validates the email matches, and checks the order is eligible for a return (status check + return-window check).

If eligible, they proceed to Step 2. If not, they see a plain-English reason — “Your order is still awaiting payment,” “This order is outside the 30-day return window,” “This order status isn’t eligible for returns yet” — not a generic “sorry, try again.” The admin lookup log shows every failed attempt with the specific reason, so you can see at a glance what’s blocking customers.

There’s also a “Can’t find your order number?” recovery flow on the lookup form that walks them through finding it in their order confirmation email.

Step 2 — Select items

The portal shows every item on the order. The customer checks the boxes next to the items they want to return and enters a quantity for each. Items that aren’t returnable (digital, downloads, non-refundable products you’ve marked as such in WooCommerce) are grayed out with an explanation.

Step 3 — Reason + photos

For each selected item, the customer picks a reason from your configured list (“Doesn’t fit,” “Defective,” “Wrong item,” etc.) and optionally uploads up to three photos. Photo uploads are useful for defect claims — “defective” plus a picture of the damage saves a round-trip email later.

Supported image formats: JPG, PNG, WEBP, HEIC. Max 5 MB per image. The prompt text shown to customers is configurable at Portal settings → Customer photo uploads.

Step 4 — Resolution

The customer chooses how they’d like the return handled:

  • Refund — refund to original payment method
  • Store credit — a code they can use on a future order. If you’ve enabled the bonus multiplier (e.g. 110% store credit for the refund amount), the bonus is shown here as an incentive.
  • Exchange — pick a different variant of the same product, or a different product entirely via the “Something else” escape hatch.

The resolution page notes that a return shipping fee may apply to refunds and store credit (exchanges typically ship free). It does not show a specific dollar amount at this stage — you set the exact fee per-RMA before approving — because the fee varies by item weight, destination, and your judgment call on who’s absorbing the cost.

Step 5 — Confirmation

Summary of everything they’re requesting. They click Submit request and the portal creates the RMA record, sends them a confirmation email with their RMA number, and emails you the new-request notification.

What customers see after submitting

The confirmation email gives them an RMA number and explains what happens next. When you approve the request from the admin, they get a second email with (if applicable) the prepaid USPS label attached as a PNG they can view inline on their phone — no app download, no printable PDF requirement, though a printable copy is included too for anyone who wants it.

Customers never need to create an account or log in. The RMA number plus their email is enough to check status at /returns/ any time.

Theme compatibility

The portal is a real WordPress page using the standard page template, so whatever theme you’re running — Flatsome, Astra, Divi, GeneratePress, Blocksy, Kadence, the default block themes — provides the page chrome. The plugin’s CSS is scoped to .gorilla-returns-portal to avoid clashing with your theme’s own styles.

Tested compatible themes include Flatsome, Astra, GeneratePress, Blocksy, Kadence, Divi, OceanWP, Elementor-based themes, and every default WordPress block theme. If you find a theme that breaks the portal, let us know — this is the kind of thing we fix quickly.