Distribution integration

Core-Mark EDI integration and automation

A guide for suppliers connecting with Core-Mark, covering the documents exchanged, the main program rules, testing and ERP integration.

Overview

Understanding Core-Mark integration

Who this is for: Suppliers that sell to Core-Mark, and the EDI, logistics and finance teams that support them.

Core-Mark is a distributor to convenience retailers. Suppliers that trade with Core-Mark electronically exchange documents such as the 850 purchase order, 875 grocery products purchase order, 855 purchase order acknowledgment, 856 ship notice/manifest and 810 invoice. This page summarizes how that exchange works from the supplier's side, so your team can scope the work before mapping starts.

The program uses X12 5010. Order types include general merchandise, grocery, drop-ship (direct shipment), and distribution center and store. Each order type can change which documents apply and how locations, labels and invoices are handled, so it helps to confirm which ones you will supply before you build anything.

Most of the effort goes into keeping your ERP, warehouse and shipping data consistent with what each document says. Ship notices, labels and invoices need to agree with the original order, and any rule that applies only to one order type needs its own handling in your maps. Core-Mark sets its own requirements and can change them, so treat your account contact and current guide as the final word.

Program summary

What Core-Mark asks of suppliers

A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with Core-Mark during setup.

Standard
X12 5010
Order types
General merchandise · Grocery · Drop-ship (direct shipment) · DC and store

Orders and acknowledgments

  • General merchandise uses the 850 and 810, while grocery uses the 875 and 880, each with its own test plan.

Testing

  • Test plans include catch-weight items and a traceability scenario, plus separate billing-services tests.

Workflows

Typical Core-Mark business workflows

A typical flow built from the documents below; your own program may differ.

Order to invoice

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Label and send 856
  4. 4Send 810 invoice
  5. 5Receive 820 remittance

Drop-ship order

  1. 1Receive the direct order
  2. 2Acknowledge with 855
  3. 3Ship to the end customer
  4. 4Send 856 with tracking
  5. 5Send the invoice

Documents and APIs

Core-Mark documents by program

Documents used in Core-Mark's EDI program, seen from the supplier's side. Which ones apply depends on your program, so confirm the list with Core-Mark.

DocumentNameDirectionStatusPurpose
850 Purchase Order You receive from Core-Mark Program document Places an order for goods.
875 Grocery Products Purchase Order You receive from Core-Mark Program document Places a grocery order.
855 Purchase Order Acknowledgment You send to Core-Mark Program document Confirms, changes or rejects an order.
856 Ship Notice/Manifest You send to Core-Mark Program document Describes a shipment before it arrives.
810 Invoice You send to Core-Mark Program document Bills for what shipped.
880 Grocery Products Invoice You send to Core-Mark Program document Bills for grocery items that shipped.
812 Credit/Debit Adjustment You receive from Core-Mark Program document Records credits, debits and deductions.
820 Payment Order/Remittance Advice You receive from Core-Mark Program document Explains what a payment covers.
997 Functional Acknowledgment Both directions Program document Confirms each file was received and readable.

Connectivity

How companies connect

  • AS2 or SFTP

    Direct internet connections such as AS2 or SFTP are common ways to exchange EDI documents. Confirm the options with Core-Mark.

    General guidance

  • EDI service provider

    Many suppliers connect through an EDI provider or network that manages the connection with Core-Mark.

    General guidance

Challenges

Common integration challenges

  • Keeping order types apart

    Different order types can need different maps, locations and labels, so identify each Core-Mark order type before mapping.

  • Documents that agree

    Ship notices, labels and invoices need to match the order and each other, or they can cause receiving and payment problems.

  • Changes over time

    Requirements change. Keep a process for picking up new Core-Mark rules and retesting affected documents.

Automation options for Core-Mark suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Core-Mark's labeling and ship notice requirements, and see what needs action. Core-Mark sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Core-Mark documents to your ERP

ECOM can connect Core-Mark documents with ERP and warehouse systems, so ship notices and invoices are generated from your own order and shipping data.

Next step

Get help with your Core-Mark program

Each request goes to an ECOM EDI specialist with Core-Mark's name attached, so the reply starts from your program.

  • Review Core-Mark's requirements

    Send us Core-Mark's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Core-Mark to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Core-Mark document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Core-Mark's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Core-Mark integration FAQs

Which EDI documents does Core-Mark use?

The documents in this guide are the 850, 875, 855, 856, 810, 880, 812, 820 and 997. Which ones apply depends on your program, so confirm the list with Core-Mark during setup.

Which X12 version does Core-Mark use?

This guide reflects X12 5010. Versions can differ by document and can change, so confirm the release for each document before you build your maps.

How long does Core-Mark EDI setup take?

Timing depends on your systems, the number of documents and the partner test plan. Mapping and testing each document is usually the largest part of the work.

Is ECOM a Core-Mark-approved provider?

This page is an integration guide and does not indicate an approval or partnership with Core-Mark. ECOM can help you build and test your connection.

Accuracy

This guide describes Core-Mark's program in ECOM's own words as of November 2026. Core-Mark sets its own requirements and can change them at any time; your Core-Mark implementation guide, supplier portal or account contact is the authoritative source for your program.

Request Core-Mark integration assistance

Tell us about your Core-Mark program, documents and ERP. We will outline the connection, mapping and testing plan.