Retail integration
NEXCOM EDI integration and automation
A guide for suppliers connecting with NEXCOM, covering the documents exchanged, the main program rules, testing and ERP integration.
Overview
Understanding NEXCOM integration
Who this is for: Suppliers that sell to NEXCOM, and the EDI, logistics and finance teams that support them.
The Navy Exchange Service Command (NEXCOM) runs retail operations for US Navy communities. Suppliers that trade with NEXCOM electronically exchange documents such as the 850 purchase order, 855 purchase order acknowledgment, 856 ship notice/manifest, 810 invoice and 820 payment order/remittance advice. 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 4010 and 4030. Order types include distribution center and store, cross-dock, and drop-ship. 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. NEXCOM sets its own requirements and can change them, so treat your account contact and current guide as the final word.
Program summary
What NEXCOM asks of suppliers
A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with NEXCOM during setup.
- Standard
- X12 4010 and 4030
- Order types
- DC and store · Cross-dock · Drop-ship
Ship notices
- Routing runs through the 753 and 754, and carriers report status with their own 214, which is not a supplier document.
Testing
- Testing covers DC and store orders, cross-dock and drop-ship, and item data has its own scenarios.
Workflows
Typical NEXCOM business workflows
A typical flow built from the documents below; your own program may differ.
Order to invoice
- 1Receive 850 purchase order
- 2Send 855 acknowledgment
- 3Label and send 856
- 4Send 810 invoice
- 5Receive 820 remittance
Drop-ship order
- 1Receive the direct order
- 2Acknowledge with 855
- 3Ship to the end customer
- 4Send 856 with tracking
- 5Send the invoice
Documents and APIs
NEXCOM documents by program
Documents used in NEXCOM's EDI program, seen from the supplier's side. Which ones apply depends on your program, so confirm the list with NEXCOM.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Status | Purpose |
|---|---|---|---|---|
| 850 | Purchase Order | You receive from NEXCOM | Program document | Places an order for goods. |
| 855 | Purchase Order Acknowledgment | You send to NEXCOM | Program document | Confirms, changes or rejects an order. |
| 856 | Ship Notice/Manifest | You send to NEXCOM | Program document | Describes a shipment before it arrives. |
| 810 | Invoice | You send to NEXCOM | Program document | Bills for what shipped. |
| 820 | Payment Order/Remittance Advice | You receive from NEXCOM | Program document | Explains what a payment covers. |
| 846 | Inventory Inquiry/Advice | You send to NEXCOM | Program document | Reports inventory available to sell or ship. |
| 852 | Product Activity Data | You receive from NEXCOM | Program document | Shares sales and on-hand activity by item. |
| 753 | Request for Routing Instructions | You send to NEXCOM | Program document | Asks how a ready shipment should be routed. |
| 754 | Routing Instructions | You receive from NEXCOM | Program document | Tells the supplier how to route a shipment. |
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 NEXCOM.
General guidance
EDI service provider
Many suppliers connect through an EDI provider or network that manages the connection with NEXCOM.
General guidance
Challenges
Common integration challenges
Keeping order types apart
Different order types can need different maps, locations and labels, so identify each NEXCOM 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 NEXCOM rules and retesting affected documents.
Automation options for NEXCOM suppliers
Four ways to automate. One foundation.
ECOM helps you automate them, meet NEXCOM's labeling and ship notice requirements, and see what needs action. NEXCOM sets its program's rules; ECOM confirms which options fit yours.
-
Fully Automated EDI/API
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/API -
WebEDI
Receive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDI -
SmartConvert
Convert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvert -
WebConnect
Automate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
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.
Connect NEXCOM documents to your ERP
ECOM can connect NEXCOM 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 NEXCOM program
Each request goes to an ECOM EDI specialist with NEXCOM's name attached, so the reply starts from your program.
-
Review NEXCOM's requirements
Send us NEXCOM's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements review -
Connect NEXCOM 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 NEXCOM document, then go live with monitoring from the first file.
Plan testing and certification -
Shipping labels and ASNs
Labels and ship notices that match NEXCOM's rules, to help avoid receiving problems and compliance deductions.
Review shipping compliance
NEXCOM integration FAQs
Which EDI documents does NEXCOM use?
The documents in this guide are the 850, 855, 856, 810, 820, 846, 852, 753 and 754. Which ones apply depends on your program, so confirm the list with NEXCOM during setup.
Which X12 version does NEXCOM use?
This guide reflects X12 4010 and 4030. Versions can differ by document and can change, so confirm the release for each document before you build your maps.
How long does NEXCOM 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 NEXCOM-approved provider?
This page is an integration guide and does not indicate an approval or partnership with NEXCOM. ECOM can help you build and test your connection.
Accuracy
This guide describes NEXCOM's program in ECOM's own words as of November 2026. NEXCOM sets its own requirements and can change them at any time; your NEXCOM implementation guide, supplier portal or account contact is the authoritative source for your program.
NEXCOM is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
More retail integration guides
Academy Sports + Outdoors EDI
What Academy Sports + Outdoors publishes in its SMART Guide about EDI, including the six X12 5010 documents, acknowledgment deadlines, ship notice and label rules, on-time-in-full chargebacks and onboarding through Academy's designated EDI program provider.
Agway EDI
A guide for suppliers connecting with Agway, covering the documents exchanged, the main program rules, testing and ERP integration.
Albertsons Companies EDI
What Albertsons Companies publishes for suppliers about EDI, focused on direct store delivery invoicing with the 894 and 895, plus the supplier contacts and the warehouse details that are not public.
ALDI EDI
What ALDI US publishes for suppliers about EDI, advance ship notices and license plate number labels, how its 26 divisions are organized, and what to confirm during onboarding.
Best Buy EDI
What Best Buy publishes on its Partner Portal about EDI, which documents must be in production before the first purchase order, how ship notices and labels work, and how Canada testing runs.
Buc-ee's EDI
A guide for suppliers connecting with Buc-ee's, covering the documents exchanged, the main program rules, testing and ERP integration.
Request NEXCOM integration assistance
Tell us about your NEXCOM program, documents and ERP. We will outline the connection, mapping and testing plan.