X12 transaction code
X12 180 Return Merchandise Authorization And Notification
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 180
- Trading partners
- 5
Specification summary
X12 180 Return Merchandise Authorization And Notification at the element level
The X12 180 specification defines 22 segments carrying 75 data elements, 42 of which are mandatory.
- Segments
- 22
- Data elements
- 75
- Mandatory elements
- 42
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 5 | 3 |
| PRF | 2 | 1 |
| DTM | 4 | 1 |
| N9 | 3 | 1 |
| NTE | 1 | 1 |
| N1 | 2 | 1 |
| N3 | 2 | 1 |
| PER | 7 | 1 |
| BLI | 6 | 2 |
| PID | 3 | 1 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Purchase Order Number
- Date/Time Qualifier
- Reference Identification Qualifier
- Description
- Entity Identifier Code
Trading partners that support X12 180
5 partners, 5 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 180 Return Merchandise Authorization And Notification
180 is used most heavily in retail, building & hardware and e-commerce & marketplaces.
The 180 carries the merchandise returns workflow between retailers and suppliers: a request for return authorization, the authorization or disposition decision, and notification that merchandise is being or has been returned, including consumer returns. Trading partners require it to replace fax and email RMA handling and to keep return credits, dispositions, and inbound return shipments matched to the original sale. The document is bidirectional: a retailer or buyer typically sends the return request or return notification to the supplier, and the supplier sends back the authorization or disposition. Merchandise is found defective, damaged, or incorrectly shipped, or a consumer returns product in-store, prompting the retailer to request authorization or notify the supplier of the return.
By industry
- retail 3 channels
- building & hardware 1 channel
- e-commerce & marketplaces 1 channel
By network
- Rithum 2 channels
- CommerceHub 1 channel
FAQ
X12 180 questions
What is X12 180 Return Merchandise Authorization And Notification?
X12 180 (Return Merchandise Authorization And Notification) is an EDI transaction set defined by ANSI ASC X12 for exchanging return merchandise authorization and notification between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 5 Stacksync trading partners support this code across 5 channels.
Which trading partners use X12 180?
5 Stacksync partners accept X12 180: Belk, Costco, Fanatics, HD Supply Holdings, Inc., NEXCOM (Navy Exchange Service Command). Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 180 with my ERP?
Stacksync handles the full X12 180 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
