Returns portal: return or claim, asked up front

Return and claim are two different paths. Until now the customer told them apart inside one list of reason codes.

You can now turn on a step that asks first. A customer who arrives without a return type in the link, on a product where both paths are open, picks Return or exchange, or Claim, before any reason codes appear. From there they see only that type’s codes. The rest runs as it did: photo, comment, ticket.

The step stays out of the way where it would mean nothing. A return type already in the link, or a product with only one path open, and the question is skipped.

It is a setting per market, on or off, so you can run it where it fits and keep the current flow where it does not.

What this means:

• Return and claim separated before the reason code, not inside it
• The rest of the claim flow unchanged: photo, comment, ticket
• Skipped wherever only one of the two paths is open
• On or off per market, next to the flow you run tod

Brevo: the post purchase flow reaches one more CRM

Post-purchase communication belongs where your customer data already lives.

Brevo is a customer platform: email, SMS, automations, CRM, the templates your team has already built. Return events in Inretrn now reach it, the same way they reach Klaviyo, Emarsys, Marigold, Dotdigital and Voyado.

The mechanics are unchanged. Events in the flow fire a Send mail action: a ticket created, approved or rejected, a shipment created, received or approved, a return order created, received or approved. Per market you pick which provider delivers it and which template it uses. Brevo is now one of those choices.

If Brevo is your platform, your return communication can run from it.

What this means:

• Post-purchase messaging triggered from the return flow for retailers on Brevo
• Brevo selectable per market, next to Klaviyo, Emarsys, Marigold, Dotdigital and Voyado
• Same event action, same templates, same triggers as every other provider
• Return communication running from the system that holds your customer data

Viskan: exchanges for one more e-commerce platform

An exchange only holds up if the portal knows what is actually on the shelf.

Offer a size that is not there and a kept sale turns into an apology. So before a customer sees a single exchange option, Inretrn reads live variants and stock levels from the retailer’s own product system. That look-up runs on a shared exchange pattern that already supports Centra, Brink, Omnium and more.

Viskan now has its own connector, built to that same pattern, so the exchange flow behaves exactly as it does for every other platform.

If Viskan is your e-commerce platform, exchanges are yours to offer.

What this means:

• Live variants and stock read from Viskan before anything reaches the customer
• The same exchange flow already running on Centra, Brink and Omnium
• Nothing new to learn in the portal, the flow behaves as it does for every other platform
• Exchanges you can offer with confidence, which keeps more revenue in house

Coming soon

In the summer release we said the rest of the product would move onto the new back office foundation in steps you can use right away, rather than one big switch at the end. That still holds, and the next screens are on their way. Expect them to arrive gradually across the coming releases, and expect your day to carry on uninterrupted while they do.