X12
Inbound

Belk X12 180 Return Merchandise Authorization and Notification

Belk.com (via Rithum)
The EDI 180 (Return Merchandise Authorization and Notification) document is used by Belk for electronic data interchange. It enables automated processing and compliance with Belk's trading partner requirements.
10segments
1loops
5mandatory

Schema Reference

10 segments · X12 180 Return Merchandise Authorization and Notification

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BGN Beginning Segment
Mandatory Max: 1
BGN01 Transaction Set Purpose Code
M ID 2-2
BGN02 Reference Identification
M AN 1-30
BGN03 Date
M DT 8-8
BGN04 Time
C TM 4-8
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
PRF04 Date
O DT 8-8
BLI Loop
BLI Baseline Item Data
Optional Max: 1
BLI01 Product/Service ID Qualifier
M ID 2-2
BLI02 Product/Service ID
M AN 1-48
BLI03 Quantity
O R 1-15
BLI04 Unit or Basis for Measurement Code
O ID 2-2
BLI05 Price Identifier Code
C ID 3-3
BLI06 Unit Price
C R 1-17
BLI08 Product/Service ID Qualifier
C ID 2-2
BLI09 Product/Service ID
C AN 1-48
BLI10 Product/Service ID Qualifier
C ID 2-2
BLI11 Product/Service ID
C AN 1-48
RDR Return Disposition Reason
Optional Max: 1
RDR02 Return Request Reason Code
C ID 2-2
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
PRF04 Date
O DT 8-8
DTM Date/Time Reference
Optional Max: 15
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Belk EDI 180

Stacksync validates, transforms, and delivers your 180 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync processes Belk EDI 180 (Return Merchandise Authorization and Notification) documents automatically — syncing data to your system in real time with no manual intervention required.

Belk EDI 180 FAQ

Common questions about 180 Return Merchandise Authorization and Notification transactions with Belk.

How long does it take to set up Belk EDI with Stacksync?

Most suppliers are fully connected and processing live Belk EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Belk?

No. Stacksync handles the entire EDI transport layer. We connect directly to Belk's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Belk compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Belk?

Stacksync supports all EDI document types required by Belk — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Belk EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Belk's EDI network and your system in real time.

What happens when Belk updates their EDI specifications?

Stacksync monitors Belk's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.