Retail integration

Marine Corps Exchange EDI integration and automation

A guide for suppliers connecting with Marine Corps Exchange, covering the documents exchanged, the main program rules, testing and ERP integration.

Overview

Understanding Marine Corps Exchange integration

Who this is for: Suppliers that sell to Marine Corps Exchange, and the EDI, logistics and finance teams that support them.

The Marine Corps Exchange (MCX) is the retail operation serving US Marine Corps communities. Suppliers that trade with Marine Corps Exchange electronically exchange documents such as the 850 purchase order, 860 purchase order change, 856 ship notice/manifest, 810 invoice and 832 price/sales catalog. 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 4030, with 4010 for some documents. Order types include ship to distribution center, cross-dock, single store and direct store delivery. 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. Marine Corps Exchange sets its own requirements and can change them, so treat your account contact and current guide as the final word.

Program summary

What Marine Corps Exchange asks of suppliers

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

Standard
X12 4030, with 4010 for some documents
Order types
Ship to DC · Cross-dock · Single store · Direct store delivery

Ship notices

  • One ship notice is required per ship-to location, so multi-store orders need one notice per store.

Labels and pallets

  • Mixed-SKU pallets need every carton labeled, and the notice lists the same number of labels as were applied.

Invoices and payment

  • One invoice goes per purchase order, or per store on a direct store delivery order.

Testing

  • Direct store delivery vendors test either the 810 or the 894, not both.

Workflows

Typical Marine Corps Exchange business workflows

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

Order to invoice

  1. 1Receive 850 purchase order
  2. 2Label and send 856
  3. 3Send 810 invoice

Documents and APIs

Marine Corps Exchange documents by program

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

DocumentNameDirectionStatusPurpose
850 Purchase Order You receive from Marine Corps Exchange Program document Places an order for goods.
860 Purchase Order Change You receive from Marine Corps Exchange Program document Changes an existing order.
856 Ship Notice/Manifest You send to Marine Corps Exchange Program document Describes a shipment before it arrives.
810 Invoice You send to Marine Corps Exchange Program document Bills for what shipped.
832 Price/Sales Catalog You send to Marine Corps Exchange Program document Shares item and price information.
894 Delivery/Return Base Record You send to Marine Corps Exchange Program document Records a direct store delivery or return.
511 Requisition You receive from Marine Corps Exchange Program document Requests goods for a location.

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 Marine Corps Exchange.

    General guidance

  • EDI service provider

    Many suppliers connect through an EDI provider or network that manages the connection with Marine Corps Exchange.

    General guidance

Challenges

Common integration challenges

  • Keeping order types apart

    Different order types can need different maps, locations and labels, so identify each Marine Corps Exchange 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 Marine Corps Exchange rules and retesting affected documents.

Automation options for Marine Corps Exchange suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Marine Corps Exchange's labeling and ship notice requirements, and see what needs action. Marine Corps Exchange 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 Marine Corps Exchange documents to your ERP

ECOM can connect Marine Corps Exchange 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 Marine Corps Exchange program

Each request goes to an ECOM EDI specialist with Marine Corps Exchange's name attached, so the reply starts from your program.

  • Review Marine Corps Exchange's requirements

    Send us Marine Corps Exchange's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Marine Corps Exchange 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 Marine Corps Exchange document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Marine Corps Exchange's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Marine Corps Exchange integration FAQs

Which EDI documents does Marine Corps Exchange use?

The documents in this guide are the 850, 860, 856, 810, 832, 894 and 511. Which ones apply depends on your program, so confirm the list with Marine Corps Exchange during setup.

Which X12 version does Marine Corps Exchange use?

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

How long does Marine Corps Exchange 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 Marine Corps Exchange-approved provider?

This page is an integration guide and does not indicate an approval or partnership with Marine Corps Exchange. ECOM can help you build and test your connection.

Accuracy

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

Request Marine Corps Exchange integration assistance

Tell us about your Marine Corps Exchange program, documents and ERP. We will outline the connection, mapping and testing plan.