Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment not listed on SPS Stord
- 856 Ship Notice / Manifest (ASN) not listed on SPS Stord
- 810 Invoice not listed on SPS Stord
Channel
Plan a reliable EDI exchange for SPS Stord. Explore 4 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for SPS Stord. Use 4 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 945 Warehouse Shipping AdviceListed for SPS Stord | warehouse shipment confirmation warehouse order, shipment and shipped line |
|
| X12 850 Purchase OrderListed for SPS Stord | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 846 Inventory Inquiry AdviceListed for SPS Stord | inventory availability record item, location, quantity type and snapshot time |
|
| X12 940 Warehouse Shipping OrderListed for SPS Stord | warehouse fulfillment order warehouse order, owner, ship-to and item |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for SPS Stord. Compare other Stord channels before reusing a mapping.
Start with warehouse shipment confirmation, purchase order or sales order, inventory availability record. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Stord production handoff and save the results of each approved test.
Match records between systems using warehouse order, shipment and shipped line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
4 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists all 4 document types in the Stord directory. Example relationships are shown below; confirm the required sequence in the channel guide.
X12 945 Warehouse Shipping Advice; X12 850 Purchase Order; X12 846 Inventory Inquiry Advice; X12 940 Warehouse Shipping Order. Confirm which documents, directions and versions apply to your account.
SPS Stord lists 4 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
For X12 945 Warehouse Shipping Advice, plan around warehouse order, shipment and shipped line. For X12 850 Purchase Order, use buyer purchase order, order line and trading-party identifiers. Use the partner guide to locate these values and check their allowed formats.
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
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.