Marketplace and Own-Store Returns: Managing Them Under One Roof

If you sell on your own online store and on marketplaces such as Trendyol, Hepsiburada or n11, you are probably handling returns in several panels, each with its own flow. The short answer: bring all return data into one place, run a consistent policy and an exchange-first flow on your own store, and on marketplaces follow the marketplace's rules while improving your decision speed and data quality. Trying to run both channels the same way will either cost you opportunities on your own site or put you in breach of marketplace rules.

Two channels, two return logics

On your own store, you own the customer relationship. You decide what the returns page looks like, which options customers see, how you communicate and whether you use tools like store credit.

On a marketplace, the return process is largely controlled by the marketplace. In general, the customer opens the return request on the marketplace, the seller sees it in the seller panel and decides to approve or reject it. Contacting customers outside the platform or offering your own coupons is usually restricted.

Every marketplace has its own return windows, decision steps, rejection reasons and penalties, and they change over time. This article stays general; check each marketplace's current seller documentation for the details.

Step 1: Bring return data into one place

While channels stay in separate panels, basic questions become hard to answer. Which product is returned most? Which reason dominates in which channel? Is a sizing problem showing up only on one marketplace, or everywhere?

Build a shared reason vocabulary

Each platform presents return reasons with its own list and wording. Map them to a shared vocabulary, for example:

• size or fit issues,
• did not like it or changed their mind,
• ordered the wrong item,
• incompatibility,
• seller-side reasons such as defective, wrong item, missing parts and damaged in shipping.

When mapping, keep the platform's original reason code and text as well. You can analyse with the shared vocabulary without losing the detail you need when you go back to the marketplace.

Join by product

The same product may carry different identifiers on your store and on each marketplace. Once product matching is right, you get insights that feed sourcing and production decisions, such as "size S of this model runs small in every channel".

Step 2: Keep the policy consistent

Customers judge your brand, not the channel they bought through. Policies may not be identical everywhere, but the core principles should be:

• For seller-side problems, no customer is pushed around in any channel: offer a free exchange or the standard refund.
• The statutory right of withdrawal is fully honoured everywhere.
• Rejections rest on documented, explainable grounds.
• Your own store's policy should not be stricter than the marketplace experience, or customers will move future purchases to the marketplace.

Step 3: Where an exchange-first layer fits

Revenue-retaining offers such as exchanges and bonus store credit make sense where you own the customer relationship. That makes your own store the natural home for an exchange-first flow.

On your own store

• When a customer opens a return, you can offer an exchange for an in-stock option or bonus store credit.
• The standard refund stays visible and one click away at every step.
• Offers are driven by the merchant's rules and live stock.

On marketplaces

• Offering coupons or exchanges from your own store to a marketplace customer is usually not possible and may conflict with marketplace rules. Marketplace rules take precedence here.
• What you do control is the decision step: reviewing incoming requests on time and consistently.
• Approving routine requests quickly (for example, size returns opened within the window with a clear reason) and routing risky ones to a person shortens turnaround.

Step 4: Automating marketplace decisions carefully

As volume grows, approving every request by hand becomes difficult. Automation helps, but its limits must be clear:

1. Let automation only approve. A rejection can cause customer harm, marketplace penalties and legal risk; it should always come from a person.
2. Write explicit approval conditions. Criteria such as being within the window, below an amount threshold and having a clear reason should be written down.
3. Separate the unclear cases. Out-of-window, high-value or reasonless requests should land in a review list with the reason attached.
4. Record every decision. You should be able to see which rule decided, when and by whom.

Step 5: Track the right metrics

A handful of indicators is enough to look at all channels together:

• return rate by channel and by product,
• reason distribution (using the shared vocabulary),
• share of own-store returns resolved by exchange or credit,
• time from request to decision on marketplaces,
• share of seller-side reasons, an early warning for quality and packaging issues.

Quick checklist

• Are returns from every channel visible in one view?
• Are platform reasons mapped to a shared vocabulary, with the original code kept?
• Do exchange and credit offers on your own store use live stock?
• Is the standard refund one click away at every step?
• Does marketplace automation only ever approve?
• Does your team know each marketplace's current seller rules?

Where Revoop fits

On your own store, Revoop presents exchange and bonus credit offers based on live stock. On marketplaces it collects claims in one dashboard and proposes a decision. Automatic decisions are approvals only and are switched on by the merchant; rejections always come from a person. The platforms and marketplaces you can connect, and more answers, are in the FAQ.

Conclusion

The key to multichannel returns is to treat each channel on its own terms while keeping data and principles shared. Build an exchange-first experience on your own store, follow the rules and speed up decisions on marketplaces, and watch everything from one place.