What is the EDI 180?
The EDI 180 (Return Merchandise Authorization and Notification) is the X12 transaction a buyer uses to ask a seller for permission to send goods back — and the message the seller answers with. Short answer: an 180 is not a credit memo and it is not a shipment. It is a negotiation, in a standard format, about what may come back, in what condition, and who pays for the trip.
That distinction is where most returns integrations go wrong. Teams model a return as a negative order. It isn't. An order is an instruction; a return starts as a request, and until the seller authorizes it, nothing should move.
Why does a return need authorization at all?
Because the seller has questions the buyer cannot answer for them. Is the item resalable, or is it damaged? Is it inside the return window? Should it go back to the distribution center, to a refurbisher, or nowhere at all — sometimes the cheapest correct answer is "keep it, credit issued." The 180 carries the buyer's side of that conversation: which items, how many, what condition, and why.
The reason codes are the heart of it. A return because the buyer over-ordered is a different financial event from a return because the product arrived defective, and both differ from a recall. If your integration collapses every return into one generic bucket, your partner's deductions team will happily reclassify them for you — at their rates, on their timeline.
What does an 180 actually contain?
At the header level, the transaction identifies the return authorization request itself: who is asking, which seller location or returns center is involved, and the references that tie the return back to the original business — the original purchase order, the original invoice, and the shipment the goods arrived on. Lose those references and the seller is matching cartons to orders by hand, which is exactly the labor the standard exists to eliminate.
At the line level, each item states the product identifier (usually the same UPC or buyer part number used on the original 850), the quantity proposed for return, the condition, and the reason. Quantities deserve care: the quantity requested, the quantity authorized, and the quantity actually received back are three different numbers, and a healthy returns flow tracks all three instead of overwriting one field.
The seller's response can authorize all, part, or none of the request, and can direct disposition — return to stock, repair, scrap in field, or hold for inspection. That partial-authorization case is the one homegrown integrations most often forget to build.
How does the 180 fit with the rest of the returns flow?
The 180 does not travel alone. The physical return shipment is usually announced with an 856 (Advance Ship Notice) so the receiving dock knows what is coming and can match cartons against the authorization. Money settles later: an 812 (Credit/Debit Adjustment) or the credit side of an 810 handles the financial correction once the goods are received and inspected. The acknowledgment discipline is the same as everywhere else in X12 — a 997 confirms the 180 arrived and parsed, not that anyone agreed to anything.
Sequencing matters. If the credit is issued when the 180 is requested rather than when the goods are received and inspected, you have built a machine for giving away product. If the 856 for the return references no authorization number, the dock cannot tell an approved return from a random box, and random boxes sit. Every returns dispute I have seen traces back to one of those two sequencing mistakes.
What breaks most often in 180 integrations?
Three things. First, condition and reason codes mapped loosely — your partner's guide enumerates the values they accept, and sending a plausible-but-unlisted code gets the line rejected or, worse, silently reclassified. Second, identifiers that drift from the original order: if the 850 said one part number and the 180 says another, matching fails. Third, treating the authorization as permanent. Authorizations expire; a return shipped against a stale authorization number is an argument waiting to happen.
Frequently asked questions
Is an 180 the same as an RMA number? No. The RMA number is the authorization reference the seller assigns; the 180 is the standardized message that requests it and, in the response flow, communicates it.
Does every retailer require the 180? No. Some partners run returns through portals or proprietary formats. But in grocery, general merchandise, and distribution, the 180 is the standard pattern, and partners who accept it expect the full request–authorize–ship–credit sequence.
When should the credit be issued? After the returned goods are received and inspected against the authorization — not at request time. The 812 or credit memo closes the loop the 180 opened.
Returns are the least glamorous flow in EDI and the one where sloppy sequencing costs real money, because goods and credits move in opposite directions and both can leak. If you are wiring up returns alongside your orders and invoices, that end-to-end view is what we built SignalEDI to handle. I'm Chris, founder of SignalEDI — if your 180s keep coming back as deductions, I'd genuinely like to hear where the match breaks.
Top comments (1)
The point about tracking requested, authorized and received quantities as three separate numbers is the part I see skipped most. A practical way to model it: store each as its own column on the return line, plus a status enum (requested, authorized, in transit, received, inspected, credited), and make transitions append-only events rather than updates. Then disputes become a query over history instead of an archaeology project. I'd also key every return line to the original PO line and shipment, not just the order header, otherwise partial returns of a split shipment can't be reconciled. Reason codes deserve a controlled vocabulary mapped to financial treatment (resalable, damaged, recall), since that mapping drives who absorbs the freight.