Channel
Core-Mark (via SPS Commerce)
Plan a reliable EDI exchange for Core-Mark (via SPS Commerce). Explore 9 document references, map them to your business records and test the complete workflow before launch.
- Documents
- 9 transactions
- Standards
- X12
- Implementation
- Mapping and launch plan
Implementation guide
Core-Mark (via SPS Commerce): EDI implementation plan
Build a reliable EDI workflow for Core-Mark (via SPS Commerce). Use 9 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 Core-Mark (via SPS Commerce) | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 875 Grocery Products Purchase OrderListed for Core-Mark (via SPS Commerce) | grocery purchase order purchase order, item and pack or unit basis |
|
| X12 855 Purchase Order AcknowledgmentListed for Core-Mark (via SPS Commerce) | purchase-order response original purchase order, response revision and order line |
|
| X12 856 Ship Notice ManifestListed for Core-Mark (via SPS Commerce) | shipment notice (ASN) shipment, order, package and item references |
|
| X12 810 InvoiceListed for Core-Mark (via SPS Commerce) | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 880 Grocery Products InvoiceListed for Core-Mark (via SPS Commerce) | grocery invoice invoice, grocery order and item |
|
| X12 852 Product Activity DataListed for Core-Mark (via SPS Commerce) | product activity report item, location, activity type and reporting period |
|
| X12 820 Payment Order Remittance AdviceListed for Core-Mark (via SPS Commerce) | payment or remittance record payment reference, invoice references and amounts applied |
|
| X12 812 Credit Debit AdjustmentListed for Core-Mark (via SPS Commerce) | credit or debit adjustment adjustment reference, original invoice and reason |
|
Implementation steps
-
Choose the trading account and channel
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Core-Mark (via SPS Commerce). Compare other Core-Mark (via SPS Commerce) channels before reusing a mapping.
-
Map records and assign owners
Start with purchase order or sales order, grocery purchase order, purchase-order response. 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.
-
Test a complete exchange
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 Core-Mark (via SPS Commerce) production handoff and save the results of each approved test.
-
Check results after launch
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.
Go-live checklist
- The required X12 documents, versions and sample files are agreed.
- Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
- Delivery receipts, document validation and business responses have monitoring and a named owner.
- Tests cover duplicates, partial processing and reconciliation with realistic business records.
Document catalog
EDI documents listed for Core-Mark (via SPS Commerce)
9 EDI transactions listed in this catalog.
- X12 850 Purchase Order View implementation guide →
- X12 875 Grocery Products Purchase Order View implementation guide →
- X12 855 Purchase Order Acknowledgment View implementation guide →
- X12 856 Ship Notice Manifest View implementation guide →
- X12 810 Invoice View implementation guide →
- X12 880 Grocery Products Invoice View implementation guide →
- X12 852 Product Activity Data View implementation guide →
- X12 820 Payment Order Remittance Advice View implementation guide →
- X12 812 Credit Debit Adjustment View implementation guide →
Document flow on this channel
Document relationships on Core-Mark (via SPS Commerce)
This channel lists all 9 document types in the Core-Mark (via SPS Commerce) directory. Example relationships are shown below; confirm the required sequence in the channel guide.
Grocery replenishment
All example steps listedCatalog & inventory
Some example steps listed- 832 Price / Sales Catalog not listed on Core-Mark (via SPS Commerce)
- 846 Inventory Inquiry / Advice not listed on Core-Mark (via SPS Commerce)
- 852 Product Activity Data
Network onboarding
Plan the SPS Commerce connection
The directory associates SPS Commerce with 74 partner entries across 94 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
- 850 92 ch
- 810 91 ch
- 856 90 ch
- 855 87 ch
- 860 56 ch
- 846 29 ch
Core-Mark (via SPS Commerce) questions
Which EDI documents are listed for Core-Mark (via SPS Commerce)?
X12 850 Purchase Order; X12 875 Grocery Products Purchase Order; X12 855 Purchase Order Acknowledgment; X12 856 Ship Notice Manifest; X12 810 Invoice; X12 880 Grocery Products Invoice; X12 852 Product Activity Data; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.
How should I choose the Core-Mark (via SPS Commerce) EDI channel?
Core-Mark (via SPS Commerce) lists 9 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.
Which identifiers should the Core-Mark (via SPS Commerce) mapping preserve?
For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 875 Grocery Products Purchase Order, use purchase order, item and pack or unit basis. Use the partner guide to locate these values and check their allowed formats.
Does a successful EDI receipt mean Core-Mark (via SPS Commerce) accepted the business document?
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.
What should be tested before launching Core-Mark (via SPS Commerce) EDI?
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.
Connect Core-Mark (via SPS Commerce) 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.




