Skip to content

Channel

Core-MarkCORE-MARK US, LLC

Plan a reliable EDI exchange for Core-Mark / CORE-MARK US, LLC. Explore 3 document references, map them to your business records and test the complete workflow before launch.

Book an EDI demo ← All Core-Mark channels
Documents
3 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Core-Mark / CORE-MARK US, LLC: EDI implementation plan

Build a reliable EDI workflow for Core-Mark / CORE-MARK US, LLC. Use 3 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.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 850 Purchase OrderListed for CORE-MARK US, LLC purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • 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.
X12 855 Purchase Order AcknowledgmentListed for CORE-MARK US, LLC purchase-order response

original purchase order, response revision and order line
  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 810 InvoiceListed for CORE-MARK US, LLC accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for CORE-MARK US, LLC. Compare other Core-Mark channels before reusing a mapping.

  2. Map records and assign owners

    Start with purchase order or sales order, purchase-order response, accounts-receivable or accounts-payable invoice. 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.

  3. 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 production handoff and save the results of each approved test.

  4. 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 / CORE-MARK US, LLC

3 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on CORE-MARK US, LLC

This channel lists all 3 document types in the Core-Mark directory. Example relationships are shown below; confirm the required sequence in the channel guide.

CORE-MARK US, LLC questions

Which EDI documents are listed for Core-Mark / CORE-MARK US, LLC?

X12 850 Purchase Order; X12 855 Purchase Order Acknowledgment; X12 810 Invoice. Confirm which documents, directions and versions apply to your account.

How should I choose the Core-Mark EDI channel?

CORE-MARK US, LLC lists 3 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 mapping preserve?

For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 855 Purchase Order Acknowledgment, use original purchase order, response revision and order line. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Core-Mark 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 / CORE-MARK US, LLC 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 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.

Book an EDI demo Explore the EDI platform