Implementation Pricing Docs
Government & MilitaryPart of EDI in Fulfil, the ERP for Shopify brands

Navy Exchange Service Command

Supply Navy Exchange stores on bases worldwide using Fulfil ERP's native EDI integration. Automate purchase orders, advance ship notices, and invoices for exchange stores and distribution centers.

EDI requirements

Navy Exchange (NEXCOM) EDI requirements.

NEXCOM buys for Navy Exchange stores and distribution centers, and runs a separate drop ship program where you ship to the customer. Every PO needs routing before it ships, and the address routing gives you replaces the one on the PO. Testing runs on SPS Commerce's platform against three of your items.

NEX stores and distribution centers

You ship cases and pallets to NEX distribution centers on bulk and cross dock POs, and NEX moves them on to the exchanges, including overseas.

  • 850
    Purchase Order
    Navy Exchange (NEXCOM) → You
  • 856
    Advance Ship Notice
    You → Navy Exchange (NEXCOM)
  • 810
    Invoice
    You → Navy Exchange (NEXCOM)
  • 820
    Remittance Advice
    Navy Exchange (NEXCOM) → You
  • 852
    Product Activity Data
    Navy Exchange (NEXCOM) → You
  • 997
    Functional Acknowledgement
    Both directions

NEXCOM also takes routing requests on a 753 and answers on a 754. Fulfil's native EDI doesn't carry those two, so plan on requesting routing in NEX TMS.

NEX drop ship

You ship single orders from your own warehouse or 3PL to the customer's address, the way you ship your Shopify orders.

  • 850
    Purchase Order
    Navy Exchange (NEXCOM) → You
  • 855
    PO Acknowledgement
    You → Navy Exchange (NEXCOM)
  • 856
    Advance Ship Notice
    You → Navy Exchange (NEXCOM)
  • 810
    Invoice
    You → Navy Exchange (NEXCOM)
  • 846
    Inventory Advice
    You → Navy Exchange (NEXCOM)
  • 997
    Functional Acknowledgement
    Both directions

The 855 can accept the order, accept it with lines deleted or rejected, or reject it outright. NEXCOM wants the 846 to cover only the items it buys from you. Consumer returns that reach you are reported on a 180, which starts the credit.

Requirements and testing

  • Testing uses three of your items and covers a bulk PO, a cross dock PO, a routing request, a drop ship order, a drop ship acknowledgement with exceptions, a full rejection and an inventory feed.
  • Every test document is checked for the PO number, your vendor number, the ship-to location code and the item numbers (NEX's, yours, and the UPC, GTIN or EAN). Invoices are also checked on the total.
  • Request routing for every PO, whatever the freight terms, at least 24 hours before pickup and normally 48. Shipping to the PO address instead of the routed one is charged back.
  • Routing or bill of lading mistakes that cost NEX freight carry the excess freight plus a $300 processing fee each time.
  • Every carton carries an SSCC-18 label whose number is on the 856. Never reuse an SSCC; duplicates can hold up your payment.
  • A master carton is marked as one on all six sides and carries no SSCC. Inside it, each store gets its own carton, label and carton line on the 856.
  • New items, price changes and deletes go to NEXCOM as an item data file through SPS unless you use SPS's assortment tool. That test needs four items, with case and inner pack dimensions.

How Fulfil runs Navy Exchange (NEXCOM)

There is no NEXCOM profile in Fulfil yet, so the setup starts from NEXCOM's guides. Fulfil creates the 855 when you process the drop ship order, sends the 846 on a schedule, prints SSCC labels per carton once your GS1 Company Code is saved, files each 852 for reporting, and turns each 820 into a customer payment matched to your invoices.

Carton label

The Navy Exchange UCC-128 carton label, zone by zone.

NEX labels its zones A to I and skips G. The ship-to comes from routing, not the PO, and the store number goes on in at least 30 point bold so it can be read across a dock.

From ANorthside Goods
Reno, NV 89501
To BNEX Distribution Center
Norfolk, VA 23511
Carrier DExample Freight
BOL06141410000587120
E
PO16270418
Dept212
Warehouse4120
Label3 of 8
SSCC I (00) 0 0614141 000005871 6

Sample, 4 by 6 inches. The brand, numbers and company prefix are examples; the barcode scans.

  1. A
    Ship from Required

    Your company name and address.

  2. B
    Ship to Required

    The name and address routing gives you, which can differ from the PO.

  3. C
    Postal code Required

    The ship-to postal code.

  4. D
    Carrier When there is one

    The carrier and the bill of lading number.

  5. E
    PO and department Required

    The PO number, the NEX department number from the 850, and any promotion text the PO carries, in at least 20 point bold.

  6. F
    Carton count Required

    Which carton or pallet this is on the PO, such as 3 of 8.

  7. H
    Store or warehouse Required

    The NEX store or warehouse number from the PO's mark-for, in at least 30 point bold with no abbreviations.

  8. I
    SSCC Required

    The SSCC-18 barcode at least 3.02 by 1.25 inches with quarter inch quiet zones, and its 20 digits printed. Never reuse a number.

Fulfil prints SSCC carton labels for each package once your GS1 Company Code is saved on your company in Fulfil.

How to connect Navy Exchange (NEXCOM).

Connect with Navy Exchange (NEXCOM) in 3 steps.

01

Get set up in NEX TMS

Ask NEXCOM's traffic team for a TMS login and a five digit ship-from ID for each warehouse you ship from. Routing for every PO starts there.

02

Connect and load items

Fulfil connects natively over AS2, SFTP or a VAN. Send your item data with case dimensions so NEX can set up your items.

03

Run the SPS test scenarios

Pick three items. Return an 856, 810, label and 997 for the bulk and cross dock POs, then the 855s, 856 and 846 for drop ship, and fix whatever SPS flags.

Other retailers in Government & Military.

Explore other trading partners we integrate with.

View all trading partners →

FAQ

Navy Exchange (NEXCOM) EDI questions.

What EDI documents does the Navy Exchange require?
Store vendors take the 850 and send the 856, 810 and 997, and receive the 820 and 852. Drop ship vendors add the 855 and 846. NEXCOM's guides also include the 753 and 754 for routing and the 180 for consumer returns.
Do I need routing for every NEXCOM purchase order?
Yes. NEXCOM requires routing on every PO whatever the freight terms. On FOB origin orders NEXCOM picks the carrier; on FOB destination you book your own, but you still ship to the address routing gives you.
What does the NEX carton label need?
An SSCC-18 barcode, ship from and ship to, the postal code, the carrier and BOL when there is one, the PO and NEX department number, the carton count such as 2 of 5, and the store or warehouse number in large type.
How do NEX drop ship rejections work?
You answer the 850 with an 855. To drop some lines you acknowledge with exceptions and mark each line deleted or rejected. To turn down the whole order you send a rejection without line detail.
Who runs NEXCOM's EDI testing?
SPS Commerce runs the testing platform. It sends the test POs and checks what you send back field by field before NEXCOM moves you to production.
How long does Navy Exchange (NEXCOM) EDI setup take?
Typical setup takes 2-3 weeks depending on Navy Exchange (NEXCOM)'s testing requirements. Fulfil handles all technical configuration. You just need to provide Navy Exchange (NEXCOM)'s vendor guidelines and coordinate testing with them. Think of it like setting up a Shopify app, but it takes a few weeks instead of minutes because retailers have more rigorous testing requirements.
What do I need from Navy Exchange (NEXCOM) to get started?
You need Navy Exchange (NEXCOM)'s 'EDI Vendor Guidelines' document. This is usually a PDF that their vendor relations team provides. It contains technical requirements, testing procedures, contact information, and which EDI documents they require. Just forward this to Fulfil support and we'll handle the rest of the technical setup.
Does Fulfil charge extra for Navy Exchange (NEXCOM) EDI?
No. EDI integration is included with Fulfil. No per-transaction fees or additional charges for connecting with Navy Exchange (NEXCOM). Some retailers require specific EDI providers like SPS Commerce (which have their own fees), but Fulfil's native EDI works for most partners at no extra cost. It's like how Shopify includes basic integrations: EDI is just part of the platform.
Can I use my 3PL with Navy Exchange (NEXCOM) EDI?
Yes. Fulfil acts as the central hub between Navy Exchange (NEXCOM) and your 3PL. When Navy Exchange (NEXCOM) sends purchase orders via EDI, Fulfil routes them to your 3PL via integration. When your 3PL returns shipment data, Fulfil automatically generates and sends the required EDI documents back to Navy Exchange (NEXCOM). You get complete visibility while your 3PL handles fulfillment.
Is this different from selling on Navy Exchange (NEXCOM)'s marketplace?
Yes, very different. Marketplace selling (like Amazon or Walmart.com) means you sell directly to consumers through their website, similar to your Shopify store. EDI is for wholesale relationships where Navy Exchange (NEXCOM) buys your products in bulk and sells them in their physical stores or on their site. EDI is B2B (you to Navy Exchange (NEXCOM)), marketplace is B2C (you to consumers via Navy Exchange (NEXCOM)'s platform).
How does Fulfil match a retailer's part numbers on an EDI document to my SKUs?
On each trading partner you pick the product identifier the retailer uses on their documents, and Fulfil resolves it to the matching product. With Native EDI you can choose Buyer SKU, supplier SKU, EAN, or UPC, and set more than one qualifier so Fulfil checks them in order and falls back to the next if the first does not match.

Ready to connect with Navy Exchange (NEXCOM)?

Let Fulfil handle the technical complexity of EDI so you can focus on growing your wholesale business.