X12
Inbound

URBN X12 870 Order Status Report

URBN Suppliers (via DSCO (dba Rithum))
The EDI 870 (Order Status Report) document is used by URBN for electronic data interchange. It enables automated processing and compliance with URBN's trading partner requirements.
12segments
4loops
6mandatory

Schema Reference

12 segments · X12 870 Order Status Report

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
BSR Beginning Segment for Order Status Report
Mandatory Max: 1
BSR01 Status Report Code
M ID 1-2
BSR02 Order/Item Code
M ID 1-2
BSR03 Reference Identification
M AN 1-30
BSR04 Date
M DT 8-8
HL Loop Repeat: 1,000
HL Hierarchical Level
Mandatory Max: 1
HL01 Hierarchical ID Number
M AN 1-12
HL02 Hierarchical Parent ID Number
O AN 1-12
HL03 Hierarchical Level Code
M ID 1-2
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
REF Loop
REF Reference Identification
Optional Max: 1
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
REF03 Description
C AN 1-80
PO1 Loop Repeat: 1,000
PO1 Baseline Item Data
Optional Max: 1
PO101 Assigned Identification
O AN 1-20
PO102 Quantity Ordered
C R 1-15
PO103 Unit or Basis for Measurement Code
O ID 2-2
PO104 Unit Price
C R 1-17
PO105 Basis of Unit Price Code
O ID 2-2
PO106 Product/Service ID Qualifier
C ID 2-2
PO107 Product/Service ID
C AN 1-48
PO108 Product/Service ID Qualifier
C ID 2-2
PO109 Product/Service ID
C AN 1-48
SLN Subline Item Detail
Optional Max: 100
SLN03 Relationship Code
M ID 1-1
SLN04 Quantity
C R 1-15
ISR Loop Repeat: 104
ISR Item Status Report
Optional Max: 1
ISR01 Shipment/Order Status Code
M ID 2-2
ISR02 Date
O DT 8-8
ISR03 Status Reason Code
O ID 3-3
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
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 URBN EDI 870

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

Validate
Transform
Route
Monitor
Stacksync processes URBN EDI 870 (Order Status Report) documents automatically — syncing data to your system in real time with no manual intervention required.

URBN EDI 870 FAQ

Common questions about 870 Order Status Report transactions with URBN.

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

Most suppliers are fully connected and processing live URBN 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 URBN?

No. Stacksync handles the entire EDI transport layer. We connect directly to URBN'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 URBN 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 URBN?

Stacksync supports all EDI document types required by URBN — 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 URBN 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 URBN's EDI network and your system in real time.

What happens when URBN updates their EDI specifications?

Stacksync monitors URBN'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.