Returns for a newbrand: why the sistercompany's portaldidn't fit

In short

A new brand belonged to a company that already had a returns portal for another store. The obvious idea: just share it. The problem: the new brand's customers would have been sent to a page with someone else's name and logo for their return. We reviewed the options and, along the way, clarified that “returns portal” actually means three different tasks.

The case

The brand was deliberately built as independent: its own name, its own world, its own target audience. A customer who bought there doesn't know the sister company. If they land on its page for their return, they get confused, and the carefully built brand gets a crack, right at the moment when trust matters most.

Three levels of a return

When people say “we need a returns portal”, they often mean just one of these levels. For a solution, all three have to be in place.

The options we reviewed

• Shopify's own return requests: lean, in the store's look, well suited for the request step. Whether a label is created automatically depends on the shipping setup.
• A dedicated returns app: more convenience for customers, label included, in the brand's design.
• Sharing the existing portal: technically the fastest, but with the break in the brand.

What you can take away

• A returns portal isn't a returns process. Request, label and processing are three tasks, often with three tools.
• The brand doesn't end at checkout. A return is exactly where it's decided whether a customer comes back.
• Start with what Shopify can already do. For many stores, that's enough to get going.
• Factor in inventory management. A return that looks great in the store but never arrives in the warehouse solves nothing.

Looking for the right returns solution? We review all three levels and find what fits your store.