X12
Inbound

Road Runner Sports X12 870 Order Status Report

Road Runner Sports (via SPS Commerce)
The EDI 870 (Order Status Report) document is used by Road Runner Sports for electronic data interchange. It enables automated processing and compliance with Road Runner Sports's trading partner requirements.
13segments
5loops
6mandatory

Schema Reference

13 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
REF Loop
REF Reference Identification
Optional Max: 1
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
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
PRF04 Date
O DT 8-8
REF Loop
REF Reference Identification
Optional Max: 1
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
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
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
PO110 Product/Service ID Qualifier
C ID 2-2
PO111 Product/Service ID
C AN 1-48
PO112 Product/Service ID Qualifier
C ID 2-2
PO113 Product/Service ID
C AN 1-48
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
QTY Quantity
Optional Max: 4
QTY01 Quantity Qualifier
M ID 2-2
QTY02 Quantity
C R 1-15
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 Road Runner Sports 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 Road Runner Sports EDI 870 (Order Status Report) documents automatically — syncing data to your system in real time with no manual intervention required.

Road Runner Sports EDI 870 FAQ

Common questions about 870 Order Status Report transactions with Road Runner Sports.

What is a Road Runner Sports EDI 870 Order Status Report?

The Road Runner Sports EDI 870 Order Status Report is an X12 transaction set used to exchange Order Status Report data electronically between trading partners. As a inbound document, it standardizes the communication of Order Status Report information between Road Runner Sports and their suppliers, carriers, or partners. Stacksync processes Road Runner Sports 870 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Road Runner Sports's requirements in real time.

How does Stacksync automate Road Runner Sports EDI 870 Order Status Report transactions?

Stacksync handles Road Runner Sports EDI 870 Order Status Report transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 870 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Road Runner Sports 870 document meets their specific formatting requirements before transmission or after receipt.

What are common Road Runner Sports EDI 870 errors and how do I fix them?

Common errors in Road Runner Sports EDI 870 Order Status Report transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Road Runner Sports 870 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Road Runner Sports EDI 870 with Stacksync?

Most Road Runner Sports EDI 870 Order Status Report integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Road Runner Sports's 870 format and your system, running test transactions, and completing Road Runner Sports's certification process if required. Stacksync includes pre-built mappings for Road Runner Sports's most common 870 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Road Runner Sports EDI 870 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Road Runner Sports EDI 870 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Road Runner Sports updates their 870 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Road Runner Sports EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding