To start and identify an interchange of zero or more functional groups and interchange-related control segments
NEXCOM (Navy Exchange Service Command) X12 180 Return Merchandise Authorization and Notification
X12 180 (Return Merchandise Authorization and Notification) is the EDI transaction exchanged between NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 13
- Loops
- 2
- X12 180
- All partners ↗
Transaction context
Where 180 Return Merchandise Authorization and Notification fits on NEXCOM Trans
- NEXCOM (Navy Exchange Service Command) channels
- 1 of 1
- Trading partners
- 5
- Channels
- 5
1 of NEXCOM (Navy Exchange Service Command)'s 1 channel carries 180
partners across the Stacksync network trade 180
channels network-wide carry 180
Most common alongside 180
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.
When it fires: 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.
Common 180 rejection causes
- Ambiguous use-case designation: because one 180 can be a request, an authorization, or a notification, a missing or wrong purpose designation leaves the receiver unable to route the document.
- Missing original purchase order reference (PRF segment), which breaks matching of the return to the original sale.
- Missing or invalid return reason codes, delaying the supplier's disposition decision.
- No 997 functional acknowledgment returned for the transaction, so the sender cannot confirm receipt and the return sits unresolved.
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 |
Key identifiers in 180
- Transaction Set Purpose Code
- Reference Identification
- Date
- Purchase Order Number
- Date/Time Qualifier
- Reference Identification Qualifier
- Description
- Entity Identifier Code
Full segment guideline — 13 segments 2 loops · X12 180 Return Merchandise Authorization and Notification
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a transaction set
To provide reference to a specific purchase order
To specify pertinent dates and times
To transmit identifying information as specified by the Reference Identification Qualifier
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
BLI Loop
To specify basic item data: item identification, quantity, and price
To indicate the disposition of the item, the reason for return by the returnee, the response to the reason for return, and whether the item was used
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
10+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Acknowledgment PR Product Activity Data PA Payment Order Remittance Advice IN Invoice RE Request For Routing Instructions RO Routing Instructions SH Ship Notice Manifest IN Inventory Inquiry Advice TR Transportation Carrier Shipment Status Message
No trading partner matches your search.
Browse the full directory
NEXCOM (Navy Exchange Service Command) NEXCOM Trans EDI 180 FAQ
Common questions about 180 Return Merchandise Authorization and Notification on the NEXCOM Trans channel.
What is X12 180 Return Merchandise Authorization and Notification?
X12 180 (Return Merchandise Authorization and Notification) is the EDI transaction set used to exchange return merchandise authorization and notification data. NEXCOM (Navy Exchange Service Command)'s NEXCOM Trans channel requires it from trading partners.
Does NEXCOM (Navy Exchange Service Command) NEXCOM Trans require 180 for trading partners?
Yes, NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) supports X12 180 Return Merchandise Authorization and Notification. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate NEXCOM (Navy Exchange Service Command) 180 with Stacksync?
Most companies go live with NEXCOM (Navy Exchange Service Command) 180 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 180 on NEXCOM Trans?
On NEXCOM Trans, X12 180 is typically exchanged alongside 850 Purchase Order, 856 Ship Notice Manifest, 846 Inventory Inquiry Advice, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your NEXCOM (Navy Exchange Service Command) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
