What Core-Mark expects in the 856
Core-Mark trades on X12 4010 over AS2. Core-Mark's 856 follows the standard X12 layout — no partner-specific companion-guide quirks are curated for this document yet. The certified base map covers the standard requirements, and validation still runs against the 856 spec before anything transmits.
How EDISQ maps it
The certified Core-Mark 856 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against Core-Mark's spec before transmission, and the sandbox replays Core-Mark test scenarios until everything passes.
Common rejection reasons
Nearly all 856 rejections trace to reference data, not syntax: identifiers that don't match Core-Mark's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before Core-Mark ever sees the document.
Sample Core-Mark 856
A representative 856 interchange addressed to Core-Mark — envelope, shipment→order→pack→item hierarchy, and control totals:
1ISA*00* *00* *ZZ*ACMESUPPLY *ZZ*COREMARK *260101*1200*U*00401*000000001*0*P*>~ 2GS*SH*ACMESUPPLY*COREMARK*20260101*1200*1*X*004010~ 3ST*856*0001~ 4BSN*00*SHIP0001*20260101*1200*0001~ 5HL*1**S~ 6TD1*CTN25*3****G*180*LB~ 7TD5*B*2*UPSN*M~ 8REF*BM*BOL000123~ 9DTM*011*20260105~ 10N1*ST*CORE-MARK DC 5093*92*5093~ 11HL*2*1*O~ 12PRF*PO12345~ 13HL*3*2*P~ 14MAN*GM*00000123450000000017~ 15HL*4*3*I~ 16LIN**UP*012345678905~ 17SN1**24*EA~ 18CTT*4~ 19SE*17*0001~ 20GE*1*1~ 21IEA*1*000000001~
FAQ
Which 856 version does Core-Mark use?
X12 4010, delivered over AS2. The certified map tracks Core-Mark's current companion guide.
How do I test a Core-Mark 856?
The sandbox generates realistic Core-Mark 856 scenarios against your live mapping — free, unlimited, invisible to Core-Mark.
What does it cost?
Per document only: first 25/month free, then from $0.50, decreasing with volume. No partner or mapping fees.