Returns portal: up to five photos per item

The returns portal takes up to five photos per item.

The customer can add them one at a time or several at once, and remove one to swap it. The portal counts them as they go in and says when five is reached. Photos are resized before upload, so five stay quick on a mobile connection.

The whole chain carries them. The ticket shows up to five photos per line, and the claims report gives each photo its own column.

Reason codes that require a photo still require at least one, and nothing else in the flow changes.

Stadium, Icebug, Nilson Group, HFN, Nordic Nest, Royal Design and Nordic Knots all asked for five.

What this means:

• Customer service can decide the claim without emailing for more photos
• The customer documents the claim once, while still in the flow
• Five photos per item, through to the ticket and the claims report
• Shorter time from claim submitted to claim resolved

Shopify connector: exchanges

Shopify stores can offer exchanges.

When a customer picks a replacement, Inretrn reads variants and stock straight from your store, so they only see the sizes and colours you actually have.

It uses the same exchange setup as Centra, Brink, Omnium and Viskan. Nothing new in the portal, and nothing to configure beyond connecting the store.

If Shopify is your platform, exchanges are yours to offer.

What this means:

• Live variants and stock read from Shopify before anything is promised
• More returns kept as exchanges instead of refunds
• The same exchange flow and the same portal screens as every other connector
• Nothing new for your team to learn

The portal:
More pages on the new foundation

As we have shared in earlier product updates, we are rebuilding the merchant portal step by step around one simple idea: you should always know where you are, what is going on and what to do next. This month we have taken another step in that direction.

For you, this means a cleaner and more consistent interface for Product groups, Reason codes, Carriers, Digital returns, API keys and Users.

We continue to make these changes gradually, so that nothing changes overnight. Each release moves a little more of the portal onto the new foundation. Same data, same actions, nothing to relearn.

After all, when things just work, everyone is happy.

What this means:

• Six more settings pages running on the new foundation
• The same flows underneath, with nothing to relearn
• Changes you can use each release instead of one big switch
• A foundation that lets the rest of the portal follow faster

The portal:
Clearer in both directions

Alongside the look, we have worked on what the portal says. Pages state more plainly what a setting does and what changes when you turn it on.

There is also a feedback button in the portal. It is what we go through when we decide which pages to take next.

What this means:

• Settings that explain what they do, where you change them
• Fewer support questions about what the portal just did
• A direct route from what annoys you to what we build next
• Feedback that reaches the people building the next release

Coming soon

The rest of the portal keeps moving onto the new foundation, in steps you can use right away rather than one big switch at the end. Expect it to arrive gradually across the coming releases, and expect your day to carry on uninterrupted while it does.