EDI 180 Return Merchandise Authorization Guide

The EDI 180 replaces the return authorization email thread. A distributor finds defective units, overstock or freight damage, asks the supplier if it can send them back, waits for an RMA number, ships, and then chases the credit. The 180 puts each of those steps into structured data: the items, the quantities, the reason for each line, and the supplier's decision on each line.

This guide covers what the 180 carries, the request and authorization flow, two live examples (a distributor's request and the manufacturer's answer), every segment you are likely to map, the reason and disposition codes, and how the 180 connects to the 810, 812 and 856.

What Is an EDI 180?

An EDI 180 is the Return Merchandise Authorization and Notification transaction set defined by the ASC X12 standards body. The X12 purpose statement says it supports customary business practice for returning merchandise to the vendor, and can serve as a request for a return, an authorization or disposition of the return, a notification of a return, or a notification of a consumer return. It travels in functional group AN (Return Merchandise Authorization and Notification).

Authoritative references for 180 work:

• The X12 transaction set catalog defines the 180 structure, its segment order and the return reason and disposition code lists
• The Healthcare Distribution Alliance publishes industry guidelines for the 180 and the 812 Credit/Debit Adjustment between pharmaceutical manufacturers and distributors
• The Stedi X12 4010 reference lists every 180 segment with its usage and repeat counts
• Each trading partner's 180 implementation guide decides which of the uses it supports and which segments and codes it requires

Who sends it? It depends on the use. The returning party (a retailer, distributor or pharmacy wholesaler) sends a request or a return notice. The supplier sends the authorization or denial. Some retailers send the 180 to drop-ship vendors to report that a consumer has returned an item.

Who receives it? The other side of the same relationship: the supplier's customer service or returns team for a request, the buyer's purchasing or returns team for an authorization.

When is it sent? A request goes out before anything ships back. The authorization comes back once the supplier has reviewed it. A notification is sent when goods have been returned, or when a consumer return has been received.

Why does it matter? Returns that move without an authorization tend to be refused at the supplier's dock, or accepted and never credited. A 180 exchange gives both sides the same record of what was approved, which is what the later credit is checked against.

The Four Uses of a 180

One transaction set covers several steps of the returns process. Your partner's guide will say which it uses.

The standard does not have one header flag that says "request" or "authorization" in every implementation. Partners tell them apart by which RDR elements are filled in (a request carries reasons, an authorization carries dispositions), by BGN06 pointing an authorization back to the request it answers, and in some guides by a transaction type code in BGN. Read the partner's guide before you build the map.

How a Return Authorization Flows

A typical distributor return to a manufacturer runs like this:

1. Identify the return. The distributor's warehouse or returns desk collects goods to send back: defective units returned by customers, damaged deliveries, excess or slow-moving stock under a stock rotation agreement.
2. Request. The distributor sends a 180 listing each item, quantity and reason, referencing the original purchase order and, where known, the invoice.
3. Review. The supplier checks each line against its return policy, the original sale and any agreement in place.
4. Authorize. The supplier sends a 180 back with an RMA number in N9*RZ, an expiry date, the address to return to, and a disposition for each line. Some lines may be authorized, some denied, and some marked for disposal in the field.
5. Ship. The distributor ships only the authorized lines, quoting the RMA number on the paperwork and cartons.
6. Receive and inspect. The supplier receives the return against the RMA and confirms quantity and condition.
7. Credit. The supplier issues the credit, as a credit memo, an 812 Credit/Debit Adjustment or a credit 810 invoice, depending on the relationship. Where the buyer has already taken a deduction, the credit closes it out.

Step 7 is where most return disputes land. If the credit does not match what the 180 authorized, both sides need the 180 exchange to work out why.

Interactive Example: Distributor Return Request

A hardware distributor asks a tool manufacturer to accept three lines back against purchase order PO-448812: six cordless drills returned by customers as defective (used), four circular saws of excess stock (unused), and two drill bit sets that arrived damaged. Each BLI line carries the vendor item number, quantity and UPC, a PID description, and an RDR with the request reason in RDR02 and whether the item was used in RDR05.

Use the Plain English tab for a readable summary, or click any segment to break it down element by element.

Interactive Example: Manufacturer Return Authorization

Two days later the manufacturer answers. BGN06 points back to the request, N9*RZ carries the RMA number, DTM*036 says when the authorization expires, and an N1*ST loop gives the returns center address. Line by line: the drills are authorized (RDR*RA), the saws are denied with a response reason (RT, return window exceeded) and a short note, and the damaged bit sets are marked DI (dispose, do not ship).

180 Structure at a Glance

The 180 has a heading, a detail loop per item (BLI), and nested loops for quantities, locations and serial or lot data.

Most commercial 180s use a small part of this: BGN, PRF, N9, the N1 loop, and BLI with PID and RDR. In the envelope, GS01 is AN.

Key Segments Explained

BGN: Beginning Segment

BGN*00*RA-55120*20261107***RR-20261105-01~

BGN06 is what ties an authorization to its request. If your system cannot match on it, you end up matching on PO and item, which breaks as soon as there are two returns against the same order.

N9: Reference Identification

N9*RZ*RMA-77310~
N9*IV*INV-77120~

N901 is the qualifier and N902 the value. RZ is the returned goods authorization number (the RMA), and IV is the seller's invoice number. The RMA number is the key the supplier's dock receives against, so it has to reach the shipping paperwork exactly as sent.

PRF: Purchase Order Reference

PRF*PO-448812***20261002~

PRF01 is the original purchase order number and PRF04 its date. At heading level it applies to the whole return. When lines come from different orders, the same segment goes inside each BLI loop instead.

BLI: Baseline Item Data

BLI*VN*RT-DRL-18V*6*EA****UP*081550200140~

BLI allows four item identifiers per line. Send the ones the supplier's guide asks for, and make sure they all describe the same unit: a case UPC with a quantity in eaches is a common cause of a line being denied as an unidentifiable item.

PID: Product/Item Description

PID*F****18V CORDLESS DRILL KIT~

PID01 = F (free-form) and PID05 the description. It helps the person reviewing the return, but suppliers match on the identifiers in BLI, not on the description.

RDR: Return Disposition Reason

RDR is the heart of the 180. It carries the buyer's reason for the return, the supplier's answer, or both sides of the decision, at heading level or per line.

RDR**DR***Y~
RDR*RD**RT*OUTSIDE STOCK RETURN WINDOW~

X12 allows only one of RDR02 and RDR03 in the same segment, so a single RDR is either the request side or the response side.

Common return request reasons (RDR02):

Dispositions (RDR01):

Response reasons (RDR03) explain a denial or a condition: NR (no record of original sale), RT (return time limit exceeded or beyond warranty), OS (out of season or discontinued line), IN (item not defective), QD (quantity difference), PC (pricing or cost difference), UI (unidentifiable item), MI (more information requested), PR (picture requested) and SR (sample requested), among others.

These code lists are the X12 4010 values. Partners use a subset, and the subset is in their guide.

DTM: Date/Time Reference

DTM*036*20261207~

DTM01 = 036 (expiration) and DTM02 the date. On an authorization it says how long the RMA is valid. On a notification, partners often use 050 (received) for the date the goods or the consumer return arrived.

N1 Loop: Parties and the Return Address

N1*ST*RIDGELINE RETURNS CENTER*92*RC01~
N3*88 FOUNDRY RD~
N4*DES MOINES*IA*50313~

The N1 loop names the buyer (BY), the vendor (VN), where the return ships from (SF) and where it ships to (ST). On an authorization, the ship-to is the address the returning party must use. It is often a returns center or a third-party processor, not the warehouse the goods first shipped from.

QTY and LX Loops: Serial and Lot Detail

When each returned unit has to be identified, the quantity moves out of BLI03 into a QTY loop, and an LX loop under it carries serial numbers, lot numbers and inventory data in N9 segments, with an optional N1 naming the manufacturer of that serial or lot. Electronics, medical devices and pharmaceuticals are the usual users. Which qualifiers carry the serial and lot numbers is set by the partner's guide.

Retail, Distribution and Healthcare Returns

The same transaction set behaves differently by industry.

• Wholesale and industrial distribution. The distributor requests, the manufacturer authorizes. Excess stock returns usually fall under a stock rotation or stock reduction agreement, which is why SR and EI exist as reasons. EDI for wholesale distribution covers the wider document set.
• Retail and drop ship. Some retailers use the 180 to notify a drop-ship vendor that a consumer has returned an item, with a reason code per line, so the vendor can restock or credit. Others run returns through a vendor portal and never send a 180.
• Healthcare distribution. Pharmaceutical manufacturers and distributors use the 180 alongside the 812 under the HDA guidelines, with short-dated, expired and recalled product as common reasons, and lot detail on each line. See EDI for pharmaceutical suppliers.

EDI 180 vs 812, 810, 856 and 824

Two confusions come up often. The 855 and 860 have no role in returns: rejecting a line on an 855 declines to ship it in the first place. And a 997 accepting your 180 request is not an authorization. Only the supplier's 180 response (or its returns portal) is.

Where the 180 Sits in the Order Lifecycle

1. Order. 850 purchase order, acknowledged on an 855.
2. Ship. 856 ship notice, goods received.
3. Bill. 810 invoice, paid with an 820 remittance.
4. Return request. 180 from the buyer, referencing the PO and invoice.
5. Authorization. 180 from the supplier with an RMA number and per-line dispositions.
6. Return shipment. The buyer ships authorized lines quoting the RMA.
7. Credit. 812, credit 810 or credit memo, matched to the authorization.

The full lifecycle is in our EDI order lifecycle guide.

Common 180 Errors and How to Prevent Them

Returns that go wrong usually show up later as deductions and chargebacks. The EDI inspector lays out each BLI and RDR element by name, which makes a 180 quick to check before you send it.

180 Implementation Checklist

• Confirm which uses the partner supports: requests, authorizations, notifications, consumer return notices
• Get its 180 guide and the subset of RDR codes it accepts on each side
• Confirm how it tells a request from a response (RDR content, BGN06, a BGN transaction type code)
• Confirm the item identifiers it wants in BLI, and whether quantity goes in BLI03 or a QTY loop
• Confirm whether serial or lot numbers are required, and in which N9 qualifiers
• Agree how the credit is issued: 812, credit 810 or memo, and what it references
• Make sure the RMA number flows to your shipping paperwork
• Test a full request, a partial authorization, a denial and a disposal

If you are mapping a new partner's document set, the EDI document types reference and EDI compliance guide show where returns fit alongside orders, ship notices and invoices.

Getting the Original Orders Right With OrderSync

Most returns trace back to the order: a wrong item, a wrong unit, a quantity keyed twice. Distributors and suppliers receive those orders as EDI 850s, but also as emails, PDFs and spreadsheets, and each one has to be matched to the right customer, item and unit before it ships.

OrderSync reads inbound orders in any format, matches customers, items and units to your catalog, and outputs valid X12 or clean data to your ERP. Paste any 180 into the free EDI inspector to see it parsed with a plain-English summary, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions