---
title: "How to Manage the Returns Process in E-Commerce"
description: "How to manage the returns process in e-commerce? The difference between returns, cancellations and exchanges, the step-by-step flow, return reasons, payment refunds and store points, and returns management in Faprika."
url: https://www.faprika.com/en/blog/how-to-manage-the-returns-process-in-e-commerce
language: en
site: Faprika
---

# How to Manage the Returns Process in E-Commerce

> How to manage the returns process in e-commerce? The difference between returns, cancellations and exchanges, the step-by-step flow, return reasons, payment refunds and store points, and returns management in Faprika.

A customer received the product, didn't like it and wants to return it. If they can't find a return form, they will call you, write a message or leave a review; if they find one and the process is clear, they come back for their next purchase. The **e-commerce returns process**, that is, the flow from opening the request to inspecting the product and refunding the customer, is not where the sale ends but where customer loyalty is tested. The short answer: a good returns process collects the request in one place, shows the status to the customer at every step, inspects the product and returns it to stock correctly, and closes the payment with a record.

In this guide we explain the difference between returns, cancellations and exchanges, the steps of the returns process, return reasons and measures, the choice between a payment refund and store points, how to calculate the cost of returns, and how to manage returns and cancellations in the Faprika panel. Of the two tools in the article, one calculates the monthly cost of your return rate and the other audits your returns setup with eight questions. Legal time limits and consumer rights depend on legislation; for exact practice, work with your legal and financial advisors. This article provides general information and is not legal advice.

Key Takeaway

“A return is as much feedback as it is a loss. A store that keeps the process easy both retains the customer and, by seeing the reasons for returns, improves its product.”

## What Is the Returns Process in E-Commerce?

The returns process is the workflow that starts when a customer wants to send back all or some of the products they received, and ends with inspecting the product, updating stock and refunding the payment. The process is not just the product coming back; it also includes recording the request, making a decision, informing the customer and reflecting it in accounting.

### What Is the Difference Between Returns, Cancellations and Exchanges?

A cancellation ends an order before the product has been delivered. A return is when a delivered product is sent back and its price is refunded. An exchange is when another product or size is sent in place of the returned one. All three have different steps and different records.

| Concept | When does it happen? | Product movement | Money movement |
| --- | --- | --- | --- |
| Cancellation | Before delivery | The product never ships or comes back from transit | Payment is refunded |
| Returns | After delivery | Product comes back | Payment refund or store points |
| Exchange | After delivery | The old product comes back, the new one goes out | Any difference is collected or refunded |

We recommend reading

What Is a Distance Sales Agreement? A Guide to Pre-Contract Information, Right of Withdrawal and Returns for

E-Commerce

Sites (2026)

## Why Is Returns Management Important for E-Commerce?

Returns management is not just a customer service issue; it affects the profitability of sales, stock accuracy and brand credibility all at once:

- **Trust:** Customers look at the return policy before they buy. A clear and easy process supports the first purchase decision.
- **Profit:** Every return means reverse shipping, product inspection and sometimes unsellable stock. A store that doesn't calculate this cost loses margin without noticing.
- **Stock accuracy:** If a returned product doesn't go back to stock at the right time and in the right quantity, either the wrong stock is shown or sellable product disappears from the shelf.
- **Accounting:** Refunds that are paid out must be recorded consistently with invoicing and reporting.
- **Learning:** Return reasons are the most honest data on which product causes problems and why.

We recommend reading

How to Prepare a Profit and Loss Report in

E-Commerce

? A Guide to Net Profit by Product

## How Does the E-Commerce Returns Process Work, Step by Step?

A healthy returns process moves through six steps: request, review, decision, product return, payment or points, and closure. Recording the status at each step lets both you and the customer answer the question “where are we now?”.

*Görsel: Steps of the e-commerce returns process: request, review, decision, product return, payment or store points, and closure (The six steps of the returns process)*

### 1. How Do You Receive the Customer's Request?

The request should be opened in one place, preferably from the order screen in the customer's account. The customer selects the product and quantity they want to return, states the reason and chooses the return method. If requests arrive scattered by phone or message, they can't be tracked, and two separate returns may be opened for the same order.

### 2. How Do You Review the Request?

When a request arrives, the order details, delivery status and return conditions are checked. At this stage the request appears as “under review”. The customer should know the decision is pending, which is why it matters that the status is visible in the order details.

### 3. How Do You Make the Decision?

The request is approved, or rejected with a stated reason. When a request is rejected, giving the customer the reason in writing reduces objections and complaints. Every explanation written in the note field recalls the history in later conversations.

### 4. What Do You Do When the Product Comes Back?

When the product reaches the warehouse, it is inspected: is it used, damaged or missing parts? Adding a sellable product back to stock is necessary for stock accuracy. A product in unusable condition is not added to stock; it is important that this distinction can be selected in the system.

### 5. How Do You Process the Payment or Points?

Depending on the return method, the amount the customer paid is either refunded or credited to their account as store points. When the payment is completed, the payment status must be updated; otherwise the return still looks unfinished in the records.

### 6. How Do You Close the Request?

In the final step the request is closed and the customer is told the process is complete. Closure should happen when the stock, payment and note records are consistent. Requests that are never closed clutter the list over time and hide the work that is really pending.

Tip

Notify the customer when the status changes

Even four short notifications such as “request received”, “approved”, “your product has arrived” and “your payment has been processed” noticeably reduce calls and messages. When customers get information, waiting feels less burdensome.

## What Are the Return Reasons and How Can They Be Reduced?

Classifying return reasons in the system gives you not only reporting but also the ability to take preventive action. The customer selects a reason in the return form; these reasons should be simple, mutually inclusive and limited in number. A very long list of reasons tires the customer and makes reports harder to read.

*Görsel: Common return reasons in e-commerce and the measures you can take for each (Common return reasons and measures)*

| Return reason | Likely source | Measure |
| --- | --- | --- |
| Size or fit was wrong | Missing size information | Size chart, clear product specifications |
| Product differs from the photo | Misleading photo or description | Realistic photos, accurate text |
| Arrived damaged | Packaging or transport | Sturdy packaging, shipment tracking |
| Wrong product was sent | Picking error | Order verification and barcode check |
| Delivered late | Preparation or shipping delay | Realistic delivery time, suitable carrier |
| Changed their mind | Post-purchase regret | Clear terms, exchange and points option |

We recommend reading

How to Take Product Photos? A Phone-Based

E-Commerce

Product Photography Guide

### How Do You Prevent Returns Caused by the Product Page?

A significant share of return reasons begins before the purchase: the customer places an order without fully understanding what the product is. That is why product photos should be realistic, and dimensions, material and variants should be clearly stated, so the product page is treated as a tool for preventing returns. The clearer the product page, the fewer “different from the photo” and “not what I expected” reasons you will see.

### How Do You Prevent Returns Caused by Operations?

Sending the wrong product, missing parts and damaged deliveries are the visible errors of operations. Verifying by scanning barcodes during order picking, checking before packing and choosing carriers by delivery performance reduce these returns. A wrong-product return is both a loss of profit and an event that shakes customer trust.

We recommend reading

What Is Order Verification? Guide to Verifying Orders with Barcodes Before Shipping, Cost of Wrong Shipments and Returns, Verification Methods, Cost Calculator and Setup Audit

## How Do You Choose the Return Method: Payment Refund or Store Points?

The return method is how the customer gets the returned amount back. Faprika offers two options: payment refund and store points. With a payment refund, the amount the customer paid is paid back. With store points there is no cash outflow; the amount is credited to the customer's account as points, which the customer can use on the site whenever they like.

| Criterion | Payment refund | Store points |
| --- | --- | --- |
| From the customer’s side | Money comes back, builds trust | Used for repeat purchases on the site |
| From the seller’s side | Cash goes out | No cash outflow, revenue stays on the site |
| Best suited for | Damaged or incorrect product | Change of mind, didn't like it |
| Watch out | Processed according to the payment method | It should be explained clearly to the customer |

Store points should not be used to push the customer toward points. Offering a payment refund in cases where the seller is responsible, such as a damaged or incorrect product, protects trust. Leaving the return method to the customer's preference supports both satisfaction and repeat purchases.

Tip

Turn store points into a loyalty opportunity

Moving the refund amount to the customer's wallet or points brings the customer back to the site. Offering this not as an obligation but as an extra benefit (for example giving a small bonus of points to those who choose points) turns the returns process into a loyalty opportunity.

We recommend reading

How to Set Up a Loyalty Program? A Practical Guide to Points Systems, Tier Design and Cost Calculation in

E-Commerce

## How Is the Cost of Returns Calculated?

The cost of a return is not only the refunded amount; reverse shipping, inspecting and repackaging the product, the loss from unsellable products and the time your team spends are also part of the cost. By entering your monthly order count and return rate, the tool below shows the monthly total of your operational spend per return and calculates the monthly gain from lowering your return rate by one point.

Returns cost calculator

Monthly order count

Return rate (%)

Average order value (currency)

Operational cost per return (currency)

Monthly return count**80**

Refunded amount (currency)**48.000**

Monthly returns operations cost (currency)**4.800**

Monthly gain if the return rate drops 1 point (currency)**600**

Calculation: return count = orders × rate ÷ 100; refunded amount = return count × order value; operations cost = return count × cost per return. Values are examples; enter your own figures. Include reverse shipping, inspection and packing labor in the cost per return.

The number the tool gives is the visible cost of returns; hidden costs (unsellable products, lost customers, team time) come on top of it. To see the value of reducing returns, it also helps to think of the result per year rather than per month.

## Should Customers Be Able to Cancel Their Own Orders?

A cancellation ends an order before delivery, and letting the customer do it on their own reduces the returns and support workload. However, not every order can be cancelled at every stage: cancelling an order that has been prepared or handed to the carrier is a different matter. That is why you should define in which order status and with which payment method cancellation is allowed.

In Faprika, you enable the option that lets customers cancel their orders in Order Settings under the Configuration menu. You then select which order statuses and payment methods cancellation applies to. For example, for an order placed by bank transfer whose status is “awaiting confirmation” or “confirmed”, the customer sees the “cancel order” option in the order details. When the cancellation is completed, the stock of the relevant product is updated automatically and the order status becomes “cancelled”.

We recommend reading

How to Manage Bank Transfer (Havale/EFT) Payments? Havale vs. EFT, Matching Orders with Payments, Pending Payments and Time Limits, Stock Hold Risk, Bank Account Details, Fraud and Mismatches, Returns, Stock Hold Calculator and Setup Audit

## How Do You Manage Returns in the Faprika Panel?

Returns management in Faprika has two parts: first the returns system and its reasons are set up, then incoming requests, or returns the admin opens themselves, are managed from a single list.

### How Do You Activate the Returns System?

Go to the return request settings via Configuration, Settings and Order Settings, and activate the returns system. On the same screen you can set the format of the return number, edit the return reasons and add new ones. Once the returns system is on, customers can create return requests only for delivered orders, and they must be registered on the site to request a return.

### How Does a Customer Create a Return Request?

The customer clicks the “return request” button in their order details. In the form that opens, they enter the quantity of the products they want to return, leave the quantity at zero for products they don't want to return, select the return reason and the return method, and then create the request. Payment refund or store points can be selected as the return method.

### How Do You Track Incoming Requests in the Panel?

All requests are listed in the “return requests” tab under Orders in the panel. The list shows the return request number, order number, return date, request status, return method and return reason. You can quickly find specific requests by searching with criteria such as order number, date range or return reason. With the “Edit” button you can update the request status to “under review”, “approved” or “rejected” and add a note for the customer; the customer sees this status on the order details screen.

*Görsel: Returns list in the Faprika panel: columns for return no., order no., status, return method and return reason (Managing return requests in a single list (numbers and values are examples))*

### How Does an Admin Create a Return on Behalf of a Customer?

When a customer reports a return by phone or message without opening a request, the admin can start the return themselves. On the Orders page, open the details of the relevant order and click the button with the arrow icon. On the page that opens, enter the quantity of the product to be returned; tick the relevant option if you want the shipping fee refunded, and tick the option if you want the product added back to stock. Select the return reason and method and click “create return”. After the return is created, click the ID number next to the product to update the payment status; once the payment is completed and the status is recorded, the return is finalized.

| Step | Where in the panel? | Result |
| --- | --- | --- |
| Turning on the returns system | Configuration, Settings, Order Settings, return request settings | Customers can open a request for a delivered order |
| Reasons and number format | Same screen | Requests arrive with a common number format and reasons |
| Tracking requests | Orders, return requests | Status, method and reason in a single list |
| Status and note | The request's edit screen | The customer sees the status in the order details |
| Admin return | Order details, return action | Quantity, shipping refund and stock are selected |
| Payment status | By clicking the return ID | The return is complete once the payment is processed |

Recommended reading

What Is Back-in-Stock Notification? How to Set Up Stock Alerts for Sold-Out Products and Win Back Sales: Variant-Based Demand, Notification Channels and Threshold, Recovery Calculator and Setup Audit

## What Are the Ways to Reduce Returns?

Returns can't be eliminated entirely, but the preventable share can be reduced. The practical approach is to read the reasons regularly and take measures according to their source:

- **Enrich the product page:** Realistic photos, size information and an accurate description reduce the gap between expectation and reality.
- **Use reviews:** Genuine customer reviews show in advance whether the product meets expectations.
- **Verify during picking:** Barcode scanning and a check before packing reduce returns of wrong and missing products.
- **Choose the right carrier:** In regions with high damage and delay rates, choose a more reliable carrier.
- **State the policy clearly:** When return conditions are clear on the site, requests caused by uncertainty decrease.
- **Suggest exchanges:** For size problems, make exchanging easy instead of returning.

We recommend reading

How to Manage Product Reviews? A Guide to Collecting, Approving, Replying to Customer Reviews and Handling Negative Reviews in

E-Commerce

, with a Review Target Calculator and a Management Audit

## What Are Common Mistakes in Returns Management?

- **Hiding the return policy:** A customer who can't find the policy loses trust and starts calling.
- **Collecting requests in a scattered way:** When phone, messages and email get mixed, tracking becomes impossible.
- **Not showing the status to the customer:** A customer who gets no information asks again, and the support load increases.
- **Adding products to stock without inspection:** A damaged product appears as sellable stock.
- **Not processing the payment status:** The return has actually been made but remains open in the records.
- **Not reading the reasons:** The same problem repeats and the same product is returned again.
- **Forcing store points:** Ignoring the customer's preference damages trust.

Tip

Read the return reasons for the same product weekly

If the same reason appears several times in a row for one product, the problem is not with the customer but with the product. Reviewing the product page, the photo or the supplier prevents later returns before they happen.

## Returns Process Checklist

The list below summarizes the cornerstones of your returns setup. Until you can say “done” to every item, the process is considered incomplete.

*Görsel: E-commerce returns process checklist: returns system, cancellation setting, policy, product inspection, payment and reporting (Six checks for your returns setup)*

Returns setup audit

Return conditions are clear and easy to find on the site

Customers can open a return request from their own account

Return reasons are defined with a simple list

The request status is visible to the customer in the order details

There is an inspection and restocking rule for returned products

The status is updated after the payment or points are processed

The order statuses that can be cancelled are defined

Return reasons are reviewed at regular intervals

Items that apply**2 / 8**

Your returns setup doesn't seem to be in place yet. First write down the conditions and bring the request flow into one place.

The basic flow is there, but gaps remain. Complete the status notification, product inspection and reason analysis.

Your returns setup is solid. Now read the reasons regularly and take action on the product and operations side.

| Stage | Check | Done? |
| --- | --- | --- |
| Policy | Return conditions and time limits are clearly stated on the site | Yes / No |
| Setup | The returns system is on, the number format and reasons are prepared | Yes / No |
| Setup | Order status and payment method are defined for cancellation | Yes / No |
| Flow | Requests are received in one place, the status is visible to the customer | Yes / No |
| Product | There is an inspection and restocking rule for returned products | Yes / No |
| Payment | The return method is selected, the payment status is processed | Yes / No |
| Analysis | Return reasons are reviewed regularly | Yes / No |

## How Do You Manage the Returns Process with Faprika?

Faprika offers returns and cancellations as part of order management: requests sit in the same panel as the order, the status is shown to the customer, and stock and payment status are processed from the same place.

With Faprika returns management, you can use the following options:

- **Cancellation permission:** You define for which order status and payment method customers can cancel their own order; stock is updated automatically on cancellation.
- **Returns system:** You define the return number format and the return reasons yourself.
- **Customer request:** A registered customer opens a request for a delivered order by selecting the product and quantity.
- **Return method:** Payment refund or store points are offered as options.
- **Request list:** Request number, order, date, status, method and reason appear in a single list; you find them quickly with search.
- **Status and note:** You mark a request as under review, approved or rejected and leave a note for the customer.
- **Admin return:** You create the return yourself by choosing the quantity, shipping fee refund and adding back to stock.

You can see which features are included in which plan in the [e-commerce plans](https://www.faprika.com/en/pricing) comparison. For step-by-step usage, see the [cancellation and return operations](https://www.faprika.com/en/tutorials/cancellations-returns) training page.

We recommend reading

E-Commerce

Site Legal Pages: Which Agreements and Disclosure Pages Should You Have? Distance Sales, Privacy, Membership, Payment and Delivery, Warranty and Returns, Page Placement, Common Mistakes, Update Workload Calculator and Setup Audit

## Frequently Asked Questions

**How does the e-commerce returns process work?**

The customer opens a return request for a delivered order, the request is reviewed and approved or rejected, the product is inspected when it arrives and returned to stock, and then a payment refund or store points are processed. In the final step the request is closed and the status is shown to the customer.

**What is the difference between a return and a cancellation?**

A cancellation ends an order before the product is delivered. A return is when a delivered product is sent back and its price is refunded. With a cancellation there is no product movement or the product comes back from transit; with a return the product comes back from the customer.

**What is the difference between a payment refund and store points?**

With a payment refund, the amount the customer paid is paid back. With store points there is no cash outflow; the amount is credited to the customer's account as points, which the customer spends on the site. Offering a payment refund for damaged or incorrect products protects trust.

**How does a customer open a return request in Faprika?**

Once the returns system is activated, a registered customer clicks the return request button in the details of a delivered order. In the form they enter the quantity of the products they want to return, select the reason and the return method, and create the request. For guest customers, the returns system requires membership.

**How are return requests tracked in the panel?**

In the return requests tab under Orders in the panel, you can see the request number, order number, date, status, return method and reason. You can search by order number, date range or reason, edit a request, and update its status and note.

**How can the return rate be reduced?**

Read return reasons regularly and take measures based on their source: make the product page more realistic, verify orders during picking, choose a reliable carrier and state return conditions clearly. Repeated reasons on the same product usually come from the product or the supplier. For legal time limits, consult your legal advisor.

Manage your returns process from a single panel

With Faprika, manage return and cancellation requests from the order screen, show the status to your customer, and process stock and payment status from the same place. Let's plan your returns flow together with our experts.

Request a Demo

#### You May Also Like

- [**What Is a Distance Sales Agreement? A Guide to Pre-Contract Information, Right of Withdrawal and Returns for E-Commerce Sites (2026)**](https://www.faprika.com/en/blog/distance-sales-contract)
- [**What Is Order Verification? Guide to Verifying Orders with Barcodes Before Shipping, Cost of Wrong Shipments and Returns, Verification Methods, Cost Calculator and Setup Audit**](https://www.faprika.com/en/blog/what-is-order-verification)
- [**How to Manage Product Reviews? A Guide to Collecting, Approving, Replying to and Handling Negative Customer Reviews in E-Commerce, Review Target Calculator and Management Audit**](https://www.faprika.com/en/blog/how-to-manage-product-reviews)
- [**How to Set Up a Loyalty Program? A Practical Guide to Store Points Systems, Tier Design and Cost Calculation in E-Commerce**](https://www.faprika.com/en/blog/loyalty-program)