Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment not listed on Cole Haan PR
- 856 Ship Notice / Manifest (ASN) not listed on Cole Haan PR
- 810 Invoice not listed on Cole Haan PR
Channel
Plan a reliable EDI exchange for Cole Haan PR. Explore 2 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for Cole Haan PR. Use 2 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 850 Purchase OrderListed for Cole Haan PR | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 860 Purchase Order Change Request Buyer InitiatedListed for Cole Haan PR | buyer order-change request original purchase order, change revision and affected line |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Cole Haan PR. Compare other Cole Haan channels before reusing a mapping.
Start with purchase order or sales order, buyer order-change request. 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 Cole Haan production handoff and save the results of each approved test.
Match records between systems using buyer purchase order, order line and trading-party identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
2 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 2 of the 6Cole Haan document types; other entries appear on Cole Haan channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
X12 850 Purchase Order; X12 860 Purchase Order Change Request Buyer Initiated. Confirm which documents, directions and versions apply to your account.
Cole Haan PR lists 2 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 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 860 Purchase Order Change Request Buyer Initiated, use original purchase order, change revision and affected 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.
Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. 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 Cole Haan channels.
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.