Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment not listed on Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))
- 856 Ship Notice Manifest
- 810 Invoice
Channel
Plan a reliable EDI exchange for Saks Fifth Avenue & Saks OFF 5th / Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)). Explore 5 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for Saks Fifth Avenue & Saks OFF 5th / Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)). Use 5 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 856 Ship Notice ManifestListed for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) | shipment notice (ASN) shipment, order, package and item references |
|
| X12 810 InvoiceListed for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 846 Inventory Inquiry AdviceListed for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) | inventory availability record item, location, quantity type and snapshot time |
|
| X12 850 Purchase OrderListed for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 870 Order Status ReportListed for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) | order-status response purchase order, status time and order line |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)). Compare other Saks Fifth Avenue & Saks OFF 5th channels before reusing a mapping.
Start with shipment notice (ASN), accounts-receivable or accounts-payable invoice, 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 Saks Fifth Avenue & Saks OFF 5th production handoff and save the results of each approved test.
Match records between systems using shipment, order, package and item references. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
5 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 5 of the 7Saks Fifth Avenue & Saks OFF 5th document types; other entries appear on Saks Fifth Avenue & Saks OFF 5th channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
The directory associates Rithum with 23 partner entries across 25 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
X12 856 Ship Notice Manifest; X12 810 Invoice; X12 846 Inventory Inquiry Advice; X12 850 Purchase Order; X12 870 Order Status Report. Confirm which documents, directions and versions apply to your account.
Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) lists 5 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 856 Ship Notice Manifest, plan around shipment, order, package and item references. For X12 810 Invoice, use invoice number, purchase order and invoice line. 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.
Reconcile item quantities through shipment, order and packaging levels against the physical shipment. Test split shipments for one purchase order and prevent the second ASN from replacing the first. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other Saks Fifth Avenue & Saks OFF 5th channels.
Showing 9 of 9 references
Browse the full directorySee 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.