Trading Partner

Trade EDI with NEXCOM (Navy Exchange Service Command)

NEXCOM (Navy Exchange Service Command) exchanges 11 EDI documents with its suppliers, listed below. Endless Commerce sends and receives every one of them natively, on the same record that holds your inventory and orders, so compliance never becomes a second system to reconcile.

Get a Demo

EDI documents NEXCOM (Navy Exchange Service Command) exchanges

Code	Transaction
850	Purchase Order
810	Invoice
856	Ship Notice/Manifest
855	Purchase Order Acknowledgment
846	Inventory Inquiry/Advice
852	Product Activity Data
820	Payment Order/Remittance Advice
214	Transportation Carrier Shipment Status Message
180	Return Merchandise Authorization and Notification
754	Routing Instructions
753	Request for Routing Instructions

Frequently asked questions

Which EDI documents does NEXCOM (Navy Exchange Service Command) use?

NEXCOM (Navy Exchange Service Command) exchanges 850 Purchase Order, 810 Invoice, 856 Ship Notice/Manifest, 855 Purchase Order Acknowledgment, 846 Inventory Inquiry/Advice, 852 Product Activity Data, 820 Payment Order/Remittance Advice, 214 Transportation Carrier Shipment Status Message, 180 Return Merchandise Authorization and Notification, 754 Routing Instructions, 753 Request for Routing Instructions. Endless Commerce sends and receives all of them natively, on the same record that holds your inventory and orders.

How long does it take to start trading with NEXCOM (Navy Exchange Service Command)?

Days, not months. Our team onboards the trading partner, maps the documents, and runs EDI for you, so there is no integration project and no separate EDI tool to staff.

Do I need separate EDI software to trade with NEXCOM (Navy Exchange Service Command)?

No. EDI is part of Endless Commerce rather than a tool bolted onto it, so trading documents read and write the same inventory and orders as the rest of your operation. There is no second system to reconcile and no VAN to buy.