To start and identify an interchange of zero or more functional groups and interchange-related control segments
Belk X12 180 Return Merchandise Authorization and Notification
Plan X12 180 Return Merchandise Authorization and Notification for Belk.com (via Rithum). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 9
- Loops
- 1
- X12 180
- Partner references ↗
Implementation guide
Belk.com (via Rithum): 180 mapping and validation
X12 180 Return Merchandise Authorization and Notification is used when a return is requested, authorized or notified. Preserve return authorization, original order and returned item so the return authorization in your business system stays connected to the original document.
This document is listed for Belk.com (via Rithum). Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | return authorization return authorization, original order and returned item |
|
| Update the receiving system | Processing the return authorization ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the return authorization Original document reference and matching response |
|
The document reference includes 9 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a return is requested, authorized or notified. Name the operational owner of the return authorization and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map return authorization, original order and returned item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Belk guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic return authorization data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful return authorization processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 180 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic return authorization data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out return authorization without processing it twice.
Transaction context
Where 180 Return Merchandise Authorization and Notification fits on Belk.com (via Rithum)
- Belk channels
- 1 of 3
1 of Belk's 3 channels list 180
- Trading partners
- 5
partner references list 180
- Channels
- 5
channel entries list 180
Frequently listed alongside 180
The directory associates Rithum and 180 with 2 channels.
Document structure
X12 180 Return Merchandise Authorization and Notification at the element level
The X12 180 reference contains 22 segment entries and 75 data elements; 42 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Segment reference — 9 segments 1 loop · 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
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 specify pertinent dates and times
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Related references
Other transactions in Belk.com (via Rithum)
Other EDI documents listed on this channel.
Belk.com (via Rithum) EDI 180 questions
Common questions about 180 Return Merchandise Authorization and Notification on the Belk.com (via Rithum) channel.
What is X12 180 Return Merchandise Authorization and Notification used for?
180 is used when a return is requested, authorized or notified. It carries information for the return authorization. Match it to your business system using return authorization, original order and returned item.
Is 180 required for Belk.com (via Rithum)?
180 is listed for Belk.com (via Rithum). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 180?
Start with return authorization, original order and returned item and the target return authorization. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 180 error handling?
Test a return quantity larger than the original shipment and require review. Keep authorization separate from physical receipt so stock is not increased early. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 180 relate to other EDI messages?
Keep 180 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the return authorization workflow; confirm any required companion messages with your partner.
Connect Belk EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
