Before the RMA starts, there is still time to change the outcome.

What changes when a merchant gets one decision before the RMA

Pre-return resolution means you respond to a customer's return intent before they have started the normal return or RMA flow. Instead of treating every return request as identical, you verify the order, understand the reason, check risk signals, and decide whether the customer should continue to the standard return process or see another resolution first.

For merchants, that timing matters. Once a customer has entered the full return process, the reverse-logistics cost usually becomes much harder to avoid. Pre-return resolution creates room for better decisions earlier in the journey.

Five steps from return intent to resolved session

A strong pre-return workflow is narrow and clear. It should feel fast to the customer and disciplined to the merchant team.

1. The customer enters through a QR insert, email, store link, support handoff, or agentic entry point.
2. The system verifies the order using an order number and matching email or another approved identifier.
3. The customer selects a reason such as size, changed mind, late arrival, duplicate purchase, damage, or wrong item.
4. Eligibility rules decide whether that reason can receive a keep offer, must be reviewed, or should route to the standard return path.
5. The session outcome is written back so the merchant can measure saved returns, discounts issued, routed cases, and flagged sessions.

This is closely related to return intent interception, but pre-return resolution is the broader operating model. It covers the workflow, the economics, the trust logic, and the merchant reporting layer together.

Why a €12 offer can beat a €25 return

The financial logic is simple: if a full return costs more than a controlled future-order incentive, it can make sense to resolve an eligible preference case before reverse logistics starts. Merchants should compare the real cost stack, not just refunded revenue.

For many stores, the cost of a full return includes outbound shipping already lost, return shipping, support time, inspection, repackaging, possible markdown, payment-fee leakage, and inventory delay. That often produces a real per-return cost that is meaningfully higher than the face value of a one-time future-order discount.

If you want the deeper financial model, the closest supporting pages are cost per return in ecommerce, refund cost on Shopify, and calculating the cost of returns for Shopify stores.

Pre-return resolution vs a return portal

A return portal starts when the customer has already decided to return. Pre-return resolution starts when the customer is still expressing intent. That difference changes both the merchant goal and the economic result.

That is why a page like pre-return tool vs return portal matters. Merchants searching for return tooling often do not yet realize there is an earlier layer that can resolve some return requests before the usual process begins.

Return intent vs return initiation

Return intent is the moment a customer begins looking for a solution. Return initiation is the moment they enter the formal return process. If you miss the first moment, you usually lose the chance to influence the decision. Pre-return resolution exists to operate in that gap.

Incentive economics vs return logistics cost

A disciplined keep offer is not a blanket discount. It is a constrained merchant decision: single-use, future-order only, short expiry, and available only on eligible reasons. The question is never whether discounts are good in general. The question is whether a controlled incentive costs less than the return you are about to process.

That logic is explored further in keep offer strategy for merchants and next-order discount strategy.

Fraud controls and merchant trust

Pre-return resolution only works when merchants trust it. That means the system must separate preference-based opportunities from defect claims and suspicious behavior. A good implementation should never use discounts to suppress damaged or defective cases.

• Route damaged, defective, wrong-item, and policy-sensitive reasons to the normal return path.
• Flag repeated claims, duplicate submissions, and unusual session patterns for review.
• Limit incentives by order, session, and time window.
• Write outcomes back so teams can audit what happened later.

KeepCard’s product framing is built around that discipline. If you want the trust and methodology background directly, see Why trust KeepCard.

What happens when an LLM handles the return flow

Pre-return resolution also fits newer agentic commerce workflows. If an agent can help a customer search, buy, and resolve issues after purchase, the merchant still needs a decision layer before the formal return path begins. That is why KeepCard supports API and MCP-style entry points alongside QR cards, email, and direct store links.

The best example on this site is agentic returns with KeepCard, which shows a full WooCommerce flow from search and purchase to a post-purchase keep-offer resolution.

How merchants should implement it

1. Define eligible reasons clearly

Start with changed mind, duplicate purchase, low-severity sizing mismatch, or similar preference reasons. Do not start with defect-heavy or policy-heavy categories.

2. Compare real return cost against incentive cost

Use a realistic range. If your full return costs EUR 10 to EUR 20 and your future-order offer costs EUR 5 to EUR 8 in expected margin impact, the keep path may be rational. If the item is high resale value and easy to restock, the answer may differ.

3. Keep the customer path short

Ask only for the order verification and the reason you need. The more steps you add, the more likely customers will abandon or contact support instead.

4. Preserve the normal return path

Customers should always be able to continue when the case is legitimate, ineligible, or simply not a match for recovery.

5. Measure outcomes weekly

Track saved returns, recovered revenue, discounts issued, routed defects, flagged sessions, and the reasons that most often triggered the flow. Those numbers will help you decide what to improve and what to highlight in future case studies.