To start and identify an interchange of zero or more functional groups and interchange-related control segments
Road Runner Sports X12 870 Order Status Report
Plan X12 870 Order Status Report for Road Runner Sports (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 12
- Loops
- 4
- X12 870
- Partner references ↗
Implementation guide
Road Runner Sports (via SPS Commerce): 870 mapping and validation
X12 870 Order Status Report is used when order progress is reported. Preserve purchase order, status time and order line so the order-status response in your business system stays connected to the original document.
This document is listed for Road Runner Sports (via SPS Commerce). 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 | order-status response purchase order, status time and order line |
|
| Update the receiving system | Processing the order-status response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the order-status response Original document reference and matching response |
|
The document reference includes 12 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice Manifest
shipment notice (ASN): shipment contents are known before the agreed notification deadline.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when order progress is reported. Name the operational owner of the order-status response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map purchase order, status time and order line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Road Runner Sports guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic order-status response 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 order-status response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 870 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic order-status response 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 order-status response without processing it twice.
Transaction context
Where 870 Order Status Report fits on Road Runner Sports (via SPS Commerce)
- Road Runner Sports channels
- 1 of 1
1 of Road Runner Sports's 1 channel list 870
- Trading partners
- 18
partner references list 870
- Channels
- 24
channel entries list 870
Frequently listed alongside 870
The directory associates SPS Commerce and 870 with 1 channel.
Document structure
X12 870 Order Status Report at the element level
The X12 870 reference contains 24 segment entries and 59 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 24
- Data elements
- 59
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| BSR | 4 | 4 |
| REF | 2 | 1 |
| N1 | 2 | 1 |
| HL | 2 | 2 |
| PRF | 1 | 1 |
| ISR | 2 | 1 |
| PID | 2 | 1 |
| QTY | 2 | 1 |
| CTT | 1 | 1 |
Key identifiers in 870
- Status Report Code
- Order/Item Code
- Reference Identification
- Date
- Reference Identification Qualifier
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
Segment reference — 12 segments 4 loops · X12 870 Order Status Report
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 an Order Status Report Transaction Set
REF Loop Repeat: 1,000
To specify identifying information
HL Loop Repeat: 1,000
To identify dependencies among and the content of hierarchically related groups of data segments
To provide reference to a specific purchase order
PO1 Loop Repeat: 1,000
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify basic and most frequently used line item data
ISR Loop Repeat: 104
To specify detailed purchase order/item status
To specify quantity information
Related references
Other transactions in Road Runner Sports (via SPS Commerce)
Other EDI documents listed on this channel.
Purchase Order X12 850 Purchase Order Change Request Buyer Initiated X12 860 Ship Notice Manifest X12 856 Inventory Inquiry Advice X12 846 Invoice X12 810
No references match your search.
Showing 5 of 5 references
Browse the full directoryRoad Runner Sports (via SPS Commerce) EDI 870 questions
Common questions about 870 Order Status Report on the Road Runner Sports (via SPS Commerce) channel.
What is X12 870 Order Status Report used for?
870 is used when order progress is reported. It carries information for the order-status response. Match it to your business system using purchase order, status time and order line.
Is 870 required for Road Runner Sports (via SPS Commerce)?
870 is listed for Road Runner Sports (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 870?
Start with purchase order, status time and order line and the target order-status response. 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 870 error handling?
Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 870 relate to other EDI messages?
X12 850 Purchase Order; X12 856 Ship Notice Manifest are related documents also listed on Road Runner Sports (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
Connect Road Runner Sports 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.
