Selling to AAFES means shipping to a store network that spans continents — post and base exchanges across CONUS and OCONUS locations, supplied through exchange DCs and direct shipments, all on one program. The EDI documents are standard X12; what the Army & Air Force Exchange Service actually grades you on is discipline in two unglamorous places: location data and carton labels. That's why an AAFES setup budgets 3–5 days where a domestic retailer might take two. Here's where the time goes.
Build the location table like it's the product
Location-table discipline is everything in this program — those are the operative words for the 850 flow, where CONUS and OCONUS exchange facilities ride one program and orders arrive against facility codes your system must resolve without guessing. Military-style facility addressing follows its own conventions, and the rule on outbound documents is exact echo: ship-to codes reproduced precisely as transmitted, never normalized, abbreviated, or "cleaned up" by a helpful address validator. Audit every facility in your program scope into the table before testing, and disable any address-standardization logic in the path of these documents.
Connect the ERP and map the item file
Order lines arrive UPC-keyed with exchange item references, so the cross-reference is straightforward for anyone who has traded retail X12. Attach your business system — NetSuite, Dynamics 365 Finance & Operations, or another of the 30+ supported platforms — and route inbound orders into your standard order-to-cash flow. The distinctive work stays in the location layer; the item layer is familiar ground.
Treat the ASN and labels as one artifact
Exchange receiving scans every carton against the 856, and the labeling standard is strict UCC-128. The setup consequence: carton serials in the ASN's MAN segments and the physical labels must be generated from one pack-out record, with the ASN in place before freight reaches the exchange DC. Direct shipments and DC freight both flow through this discipline. Test with a multi-carton, multi-facility scenario — the combination of exact facility addressing and per-carton scanning is precisely where a worldwide program punishes improvisation.
Wire the 852 into forecasting
AAFES sends exchange-level sales and stock movement on the 852, and it deserves better than an archive folder: the activity feed is the demand signal for a worldwide store network. During setup, land it somewhere your planning process actually reads — replenishment forecasting, allocation planning, or at minimum a reviewed report. Demand patterns across a global exchange network won't resemble a domestic chain's, and the 852 is how you see them early enough to act.
Certify, go live, and monitor the edges
Certification with pre-built maps is routine; production health at AAFES is about the edges of the network. Track 997 acknowledgments on every exchange, watch ASN timing against freight arrival, and audit facility-code echo periodically — addressing drift is this program's version of the silent failure. Suppliers also serving other government-adjacent channels will find the discipline transfers; the partner directory covers adjacent programs.
Where the 3–5 days go
Budget honestly: roughly a day for connection and ERP attachment, a day or more for the location table and its verification (the OCONUS entries take the longest to confirm), a day for label-and-ASN lineage testing, and the remainder for certification and the 852 wiring. The location work cannot be compressed by working faster — it's verification-bound, not effort-bound — so start it first and let everything else proceed around it.
The commercial terms
AAFES documents meter like any other EDISQ traffic: the first 25 in a month are free, then per-document pricing from $0.50 stepping to $0.10 at the highest volume band, marginal-tier billed. Worldwide addressing complexity adds nothing to the rate — connectivity, certified maps, and sandbox are included, the model has no mapping or setup fees anywhere in it, and going live is a $100/month Production minimum applied in full to usage, AAFES included as your first live partner. Tiers at pricing.
FAQ
Who is AAFES?
The Army & Air Force Exchange Service — post and base exchange stores worldwide, supplied through exchange DCs and direct shipments.
Is AAFES EDI different from commercial retail EDI?
The documents are standard X12; the discipline is in labeling and addressing. UCC-128 accuracy and exact facility codes are what the program grades you on.
Why does the AAFES setup take longer than most?
Plan for 3–5 days. The worldwide location table — CONUS and OCONUS facilities with military-style addressing — takes more care than a typical retailer's DC list.
What is the AAFES 852 used for?
Exchange-level sales and stock movement. It is the demand signal for a worldwide store network, and it belongs in your replenishment forecasting.