Back to Blog
Corporate Solutions

Returns Management Software (RMA): A Practical Guide

How do you set up returns management software? Return requests and approval, return shipping codes, receiving and inspection, resellable or damaged, line level refund calculation and the link to stock and accounting.

İade YönetimiE-TicaretDepo YönetimiKurumsal Yazılım

Returns management software, often called an RMA system, records every step from a customer's return request to the refund: request, approval, return shipping, receiving, inspection, stock movement and money back. The short answer is that a return is not an exception, it is an order running in reverse. It deserves the same rigour as an order, with clear statuses and allowed transitions. Otherwise the same return gets refunded twice, or a damaged item finds its way back into sellable stock.

Why can returns not be tracked by email and spreadsheet?

In e-commerce, B2B sales and electronics, returns arrive every day. At first customer service approves by email, the warehouse writes incoming parcels into a sheet and finance refunds from the bank screen. Three teams keep three records. To answer "was this customer refunded?", "did the parcel reach the warehouse?" or "can the returned item be resold?" you have to ask three people. When one of them is on leave the process stops, and the waiting customer writes a complaint.

The cost of a return is not only the refunded amount. A lost parcel, a double refund or reselling a damaged item often costs more than the product itself.

Features returns management software should have

  • Return request: the customer or an agent picks the order line, quantity and return reason; reasons are fixed codes, not free text.
  • Rule checks: return window, non returnable categories and partial return rules are applied at request time.
  • Return shipping code: an approved request gets a code from the carrier, sent to the customer.
  • Receiving: the parcel is scanned and compared with the expected lines; missing or extra items are flagged.
  • Inspection: each line is classified as resellable, damaged or return to supplier; photos can be attached.
  • Refund: the amount is calculated from what the customer actually paid for that line, and a refund request goes to the payment provider.
  • Reporting: return rate by product and reason, average return lead time, damage rate.

How should return statuses and transitions be designed?

The way to make a returns flow reliable is to keep allowed status transitions in a single table: requested, approved, in transit, received, inspected, then refunded or rejected. The code enforces rules such as "no refund until every line is inspected" in that table; it does not rely on hiding a button in the interface. The refund amount is calculated as an integer in the smallest currency unit, from the price actually paid on the line after discounts. The example below shows both rules:

type ReturnStatus = 'requested' | 'approved' | 'in-transit' | 'received' | 'inspected' | 'refunded' | 'rejected';

const NEXT: Record<ReturnStatus, ReturnStatus[]> = {
  requested: ['approved', 'rejected'],
  approved: ['in-transit'],
  'in-transit': ['received'],
  received: ['inspected'],
  inspected: ['refunded', 'rejected'],
  refunded: [],
  rejected: [],
};

type ReturnLine = { orderLineId: string; qty: number; unitPaidKurus: number; condition?: 'resellable' | 'damaged' };

// The refund is calculated from what the customer actually paid, line by line.
function refundKurus(lines: ReturnLine[], shippingRefundKurus: number): number {
  return lines.reduce((sum, l) => sum + l.qty * l.unitPaidKurus, 0) + shippingRefundKurus;
}

function move(current: ReturnStatus, to: ReturnStatus, lines: ReturnLine[]): string | null {
  if (!NEXT[current].includes(to)) return 'move not allowed: ' + current + ' -> ' + to;
  if (to === 'refunded' && lines.some((l) => !l.condition)) return 'every line must be inspected first';
  return null; // ok: store the move with user and timestamp
}

In practice you need a few more rules. The refund request sent to the payment provider carries a unique key, so a retry after a network error does not pay the customer twice. In promotional orders (for example "buy 3, pay for 2") the discount carried by each line must be stored when the order is placed; trying to work it out later during a partial return leads to disputes. Whether shipping is refunded is a setting tied to the return reason.

How do returns connect to stock and the warehouse?

A returned item is not added straight to sellable stock. It first enters a "returns receiving" area and, depending on the inspection, moves to a sellable shelf, a damaged goods area or a return to supplier zone. Without that split, the stock system puts opened or broken items up for sale as if they were new. We explained how the warehouse side carries this flow in our e-commerce warehouse management article, and how return shipping codes and tracking numbers are obtained in our shipping integration article. A return is also part of the order; showing return status next to the order in the customer portal cuts support tickets, which we covered in our order tracking software article.

What about marketplace returns?

For marketplace orders, the request and approval usually happen in the marketplace's own panel. The returns software pulls those returns through the API, runs them through the same receiving and inspection flow and reports the inspection result back to the marketplace. The warehouse team then works from a single screen regardless of channel. Since marketplaces have different return rules and windows, rule checks should be configurable per channel.

Off the shelf or custom software?

Most e-commerce platforms include a simple returns screen, which is enough at low volume. If you sell on several channels, run your own warehouse, have complex promotion rules, special return agreements with B2B customers or a return to supplier flow, a custom setup that joins returns, stock, accounting and payments in one flow means fewer compromises. Before starting, count the return reasons of the last three months; it shows clearly which rules need to be automated.

Conclusion

Good returns management software treats a return as an order in reverse, enforces status transitions from a table, never puts a returned item back into sellable stock without inspection, and refunds from the price actually paid in a way that is safe to retry. To build this flow on top of your e-commerce, warehouse and accounting systems, see our corporate solutions page or describe your returns process and request a quote.

Let's Build Your Project

Get a free consultation for your website, mobile app, or corporate software project.

Get a Free QuoteExplore our Corporate Solutions service