Returned Goods Authorization (RGA): What It Is + How It Works

A returned goods authorization (RGA) is a supplier's or seller's formal approval allowing a buyer to send a product back, issued before the item ships. It establishes that the return is expected, assigns a unique RGA number used to track and reconcile the return, and tells the receiving warehouse what is coming, why, and what to do with it. Without an RGA, a returned item arrives unannounced and unidentified, which is where most returns problems start.

If you handle returns at volume, the authorization is not paperwork. It is the control point that determines whether a return gets received cleanly or becomes a mystery box on a shelf. This guide covers what an RGA is, how it differs from an RMA, the full process step by step, and what the whole thing looks like on the warehouse floor, which is the part most explanations skip. For the customer-experience side of returns, our returns management best practices guide covers policy and post-purchase flow.

What is a returned goods authorization?

A returned goods authorization is permission, granted in advance, for a product to be returned. The seller or supplier reviews the return request, approves it, and issues an RGA number that travels with the shipment. That number is the thread that ties the inbound return back to the original order, the reason for the return, and the agreed outcome, such as a refund, replacement, or credit.

The RGA does three jobs at once. It controls what comes back, so you are not accepting returns you never approved. It identifies what is coming, so receiving knows the item, the order, and the reason before the box is opened. And it sets the expected outcome, so finance and the warehouse are working from the same agreement.

RGA vs RMA: are they the same thing?

In everyday practice, yes, they are used interchangeably. The mechanics are identical: a request, an approval, a tracking number, and a controlled return. The distinction is mostly about context.

RGA (returned goods authorization) is the term you will more often hear in vendor, wholesale, and B2B settings, where a buyer returns goods to a supplier or distributor. It carries connotations of purchase orders, restocking terms, and vendor credit.

RMA (return merchandise authorization) is the term more common in direct-to-consumer and retail, where a customer returns a product to a seller. It carries connotations of customer experience, refund policy, and shipping labels.

You will also see RA (return authorization) and RGA used for the same thing. The label your organization uses matters less than whether the underlying control exists. A return that arrives without an authorization number, by any name, is a return your warehouse cannot trust.

The RGA process, step by step

The RGA process has seven steps, from the moment a return is requested to the moment the books are reconciled.

1. Return request. The buyer or customer requests a return, stating the order, the items, the quantity, and the reason (defective, wrong item, no longer needed, damaged in transit, and so on).
2. Review and approval. The seller checks the request against return policy: is it within the return window, is the reason eligible, is the item one that can be returned. The request is approved, partially approved, or denied.
3. RGA number issued. An approved return gets a unique RGA or RMA number tied to the original order. This number is the tracking key for everything that follows.
4. Return instructions and label. The buyer receives instructions: where to ship, how to pack, what to include, and often a shipping label. The RGA number is referenced on the label and packing slip so receiving can match it.
5. Physical return shipment. The buyer ships the goods back. The package is now in transit, identified by its RGA number.
6. Receiving and inspection. The warehouse receives the package, matches it to the RGA, inspects the contents, and grades the condition of each item. This is the step that determines what actually happens to the goods.
7. Disposition and reconciliation. Based on inspection, each item is dispositioned (restocked, quarantined, refurbished, returned to vendor, or disposed), the financial outcome is triggered (refund, credit, or replacement), and the return is reconciled against the original order and the inventory ledger.

Steps 1 through 5 are what most articles describe. Steps 6 and 7 are where the operational reality lives, and where returns succeed or fail at scale.

What an RGA looks like operationally inside a warehouse

Here is the part nobody else writes down. When an RGA-tagged package hits the receiving dock, a sequence of operational decisions has to happen, and each one has a failure mode.

Match. The receiver scans the package or enters the RGA number and pulls up the authorization. The system shows the expected items, quantities, and the reason the buyer gave. If the contents do not match the RGA, that mismatch has to be flagged now, not discovered three weeks later during a count.

Inspect and grade. The receiver inspects each item against defined condition grades. A "defective" reason on the RGA tells the receiver what to test for. The grade is captured at the point of inspection, by the person physically holding the item, because that knowledge does not survive a handoff to whoever puts it away later.

Disposition. The condition grade drives where the item goes. New and sellable goes back to pickable inventory. Open-box might go to a markdown location. Defective gets quarantined or routed to a return-to-vendor flow against the original purchase order. Each disposition is a different physical destination and a different inventory consequence.

Post to the ledger. The inventory outcome has to hit the books. A restocked item has to become available to sell. A quarantined item has to be held out of available stock. A returned-to-vendor item has to decrement and track an expected credit. If this posting lags, your available-to-sell number is wrong, and at volume a wrong number means overselling or dead stock you cannot see.

The RGA number is what holds this entire sequence together. It is the link between the customer's reason, the receiver's inspection, the disposition decision, and the financial reconciliation. Lose the thread at any step and you lose the ability to answer basic questions about what came back and what it cost you.

Is an RMA legally required?

This is informational, not legal advice; consult counsel for your specific situation. In most US business-to-business and direct-to-consumer contexts, there is no general law requiring a seller to use an RMA or RGA process. The authorization is a business and operational practice, not a regulatory mandate.

That said, the rules around returns themselves vary. Consumer protection law differs by state, certain product categories carry their own requirements, and your obligations can be shaped by your own published return policy, your contracts with buyers, and platform or marketplace rules you have agreed to. An RMA process is how sellers operationalize those obligations and protect themselves, but the process is generally chosen, not legally compelled. Where your specific obligations are unclear, talk to a qualified attorney rather than relying on a general guide.

Who pays for shipping with an RMA?

Return shipping cost is a policy decision, not a regulation. Who pays depends on the reason for the return and the seller's stated policy.

In common practice: when the return is the seller's fault (defective item, wrong item shipped, damaged in transit), the seller usually pays return shipping and often provides a prepaid label. When the return is a buyer preference (changed mind, no longer needed, ordered the wrong size), the buyer frequently pays, or the cost is deducted from the refund as a return shipping fee. B2B and vendor returns often follow the terms written into the purchase agreement, which may include restocking fees on top of shipping.

The clean version is simple: define it in your return policy, encode the rule in your RGA workflow, and apply it consistently. Ambiguity here is what generates support tickets and disputes.

Common RGA mistakes that cost time and inventory

Accepting returns without an authorization. Unannounced returns arrive with no order link and no reason, and they sit. Require an RGA number on every inbound return.

Grading condition late or inconsistently. If condition is not captured at inspection by the receiver, it gets guessed at later or lost entirely, and damaged goods get restocked as new.

Letting the inventory ledger lag. A return that is received but not yet posted to available stock is invisible. At low volume you absorb it; at 50-plus RGAs a week it causes overselling and phantom stockouts.

Treating vendor returns and customer returns as separate worlds. When RTV lives in a spreadsheet and customer returns live in another tool, nobody can see total returned value or reconcile vendor credits cleanly.

No disposition rules. When every receiver decides ad hoc what to do with a graded item, the same condition gets handled five different ways across five shifts.

How software changes the RGA process at scale

At a handful of returns a week, an RGA process can run on a spreadsheet and a sharp warehouse lead. The mistakes above are absorbable. At scale they compound.

If your warehouse processes 50 or more RGAs a week and the inventory ledger is not catching up in real time, that is exactly the problem returns management software inside a WMS solves. Instead of authorization in one tool, receiving in another, and inventory in a third, the RGA, the scan-verified intake, the condition grade, the disposition, and the real-time inventory update all live in one system. The RGA number stays attached from request to reconciliation, and the available-to-sell number is right the moment a sellable item is dispositioned to restock. Vendor returns run on the same ledger, so total returned value is one view rather than a manual stitch-together. This is also where the warehouse management layer matters most, because receiving and inspection are warehouse-floor work.

Want to see RGA processing inside a WMS instead of bolted on after the fact? Talk to an operations engineer.

FAQ

What is a returned goods authorization?

A returned goods authorization (RGA) is a seller's or supplier's formal approval, issued before the item ships, allowing a buyer to send a product back. It assigns a unique RGA number that ties the return to the original order, the reason for return, and the agreed outcome, and it tells the receiving warehouse what is coming and what to do with it.

What is the difference between RGA and RMA?

In practice they are the same process and are used interchangeably. RGA (returned goods authorization) is more common in vendor and B2B contexts, while RMA (return merchandise authorization) is more common in direct-to-consumer and retail. Both involve a request, an approval, a tracking number, and a controlled return.

Is an RMA legally required?

This is informational, not legal advice. In most US contexts there is no general law requiring an RMA or RGA process; it is a business practice rather than a regulatory mandate. However, return rules themselves vary by state, product category, contract, and platform policy, so consult counsel for your specific obligations.

Who pays for shipping with an RMA?

It depends on the reason and the seller's policy, not on regulation. When the return is the seller's fault (defective, wrong, or damaged item), the seller usually pays and often provides a prepaid label. When it is a buyer preference (changed mind, wrong size), the buyer often pays or the cost is deducted from the refund. B2B returns typically follow the purchase agreement terms.