AAFES, the Army & Air Force Exchange Service, is the Department of Defense's largest retailer. AIMS360 runs the full AAFES document set including the 753 routing request with carton-level detail, 754 routing instructions, 824 application advice and 860 changes, from one system.
AAFES EDI Integration
AAFES runs the 850, 856 and 810 like everyone else, then adds three things vendors are rarely ready for: a 753 routing request that is rejected unless it contains carton-level detail only, an 824 application advice that tells you whether your last document was accepted or refused, and direct AS2 connectivity with a stated refusal to cover anyone's VAN fees. AIMS360 handles all of it from the system that holds your inventory.
What is the best ERP for a brand selling to AAFES? The one that can produce the documents the Exchange actually requires without a middleware layer in between. AAFES is unusual in three ways. It requires a 753 routing request containing carton-level detail only, and rejects the file otherwise. It uses the 824 application advice to report whether your transaction was accepted, rejected or accepted with changes, which most retailers never send. And it offers direct AS2 connectivity while stating plainly that it will not pay VAN or EDI provider fees of any kind, so those costs land on the vendor. AIMS360 includes managed EDI in the platform and builds the 753 from the real carton record with weight, cubic feet, NMFC and commodity code attached, so the routing request is right the first time.
Who You Are Selling To
The Exchange is a retailer and a government organisation at the same time, and both halves show up in how it trades.
Thousands of facilities across more than 30 countries, five US territories and all 50 states, plus ecommerce at shopmyexchange.com. Ship-to destinations can be far outside the continental US, which makes routing and documentation matter.
AAFES, the Exchange, the PX and the BX all refer to the same organisation. Headquartered in Dallas, Texas, under the Department of Defense.
Exchange earnings support military quality-of-life programs, which is part of why compliance expectations are formal and documented rather than negotiated case by case.
The Exchange operates its own transportation management and favours consolidated, cross-docked movements. That is precisely why it controls routing through the 753 and 754 rather than letting vendors book their own freight.
Exchange Partners Online, known as EPOL, handles vendor administration and purchase order inquiry. EDI carries the transactional flow. The two run alongside each other.
Supplier requirements, the Business Terms Agreement and EDI specifications are published documents. What applies to you comes from the pack the Exchange issues, not from general practice.
AAFES EDI Documents
Every document below is generated from the same ERP records that run your inventory, warehouse and accounting.
| Transaction | What it does for the Exchange |
|---|---|
| EDI 850 purchase order | AAFES transmits the order. AIMS360 imports it against live inventory and routes it to the correct store or distribution center. |
| EDI 860 purchase order change | The Exchange uses the 860 to amend an 850 already transmitted, and the change updates the open order rather than arriving as a note. |
| EDI 753 routing request | Sent once the shipment is finalized, carrying total carton count and volume. Accepted only with carton-level detail, and it needs weight, cubic feet, NMFC and commodity code. |
| EDI 754 routing instructions | The Exchange decides how the shipment moves and returns the 754, which processes back into AIMS360 to update the existing shipment. |
| EDI 856 ship notice (ASN) | Carton-level shipment notice generated from the same record as the labels, transmitted as the shipment closes. |
| EDI 810 invoice | Bills the Exchange electronically with the order, shipment and terms already attached. |
| EDI 824 application advice | Reports whether a document you sent was accepted, rejected or accepted with changes, so errors can be corrected and resubmitted. |
The Exchange publishes its own supplier requirements and transaction specifications, and the mandatory set can differ by program. Confirm what applies to you against the pack AAFES issues.
The Rule That Stops Shipments
On a routed program you do not book the truck. You ask permission to ship, and the request has to be in exactly the right shape.
AAFES accepts the 753 only when it contains carton-level detail. Generate it at another level and the request is refused, which means no 754 comes back and the shipment cannot move. This is a file-type decision made at the moment the request is created, not something correctable later.
The request needs the date and time the shipment will be ready for pickup, total carton count and volume, plus weight, cubic feet, NMFC and commodity code. That is freight data most apparel systems never hold, which is why it usually gets assembled by hand for this account.
A Document Most Vendors Have Never Seen
Most retailers let you find out something failed when the money is short. The Exchange tells you.
An 824 reports a document as accepted, rejected, or accepted with changes. That third state is the interesting one, because the transaction went through but not as you sent it.
The 824 is mostly used to communicate what went wrong in a previous transaction, so you can identify the problem, correct it and resubmit rather than discovering it downstream.
An 824 is only useful if someone connects it back to the document it refers to. When that link lives in the same system as the original transaction, correction is straightforward. When it does not, it becomes an email nobody actions.
A Real Cost Decision
AAFES states this plainly in its own published guidance, which makes your connection method a budget line rather than an IT detail.
The Exchange does not require or recommend any particular EDI provider, and can trade documents directly with a company that has AS2 capability. Its guidance is explicit that it will not pay VAN or EDI provider fees of any kind, precisely because direct connectivity is on offer. Any such cost is the vendor's.
If your EDI runs through a third-party network, you are paying for a layer the retailer has already said it will not fund. With AIMS360 the managed EDI is part of the platform, so there is no separate provider to license, no per-document or kilocharacter fees, and no middleware to reconcile when an 824 says something failed.
Getting Started
The commercial path and the technical path run in that order.
| Step | What happens |
|---|---|
| 1. Submit through RangeMe | Prospective suppliers create a company and product profile, which routes the product to the relevant Exchange category buyer. |
| 2. Agree terms | With a buying relationship in place, the Business Terms Agreement is completed and you receive your vendor number and the Exchange's supplier requirements. |
| 3. Configure the trading partner | Account details, vendor number, ship via and FOB on the customer record, then the EDI configuration with document tagging for the 850, 810, 856 and 753. |
| 4. Load stores and DCs | Exchange store and distribution center codes are loaded in bulk through an import template rather than keyed individually. |
| 5. Test and certify | Communication testing and document testing each run to the Exchange's published windows. Suppliers using an established EDI provider rather than building their own maps get the shorter window. |
| 6. Go live | Documents move in production, with the 753 and 754 routing handshake exercised properly before volume starts. |
AAFES EDI FAQ
The one that can produce the documents the Exchange actually requires without a middleware layer in between. AAFES is unusual in three ways: it requires a 753 routing request containing carton-level detail only, it uses the 824 application advice to report whether your transaction was accepted or rejected, and it offers direct AS2 connectivity while declining to pay any VAN or EDI provider fees, which means those costs fall on the vendor. AIMS360 includes managed EDI in the platform and generates the 753 from the real carton record with weight, cubic feet, NMFC and commodity code attached, so the routing request is right the first time.
AAFES is the Army & Air Force Exchange Service, also called the Exchange, the PX or the BX. It is the Department of Defense's largest military retailer, headquartered in Dallas, Texas, operating thousands of facilities across more than 30 countries, five US territories and all 50 states, and selling online at shopmyexchange.com. Its earnings support military quality-of-life programs.
Prospective suppliers submit a company and product profile through RangeMe, which routes products to the relevant Exchange category buyer. Once a buying relationship exists, you complete the Business Terms Agreement, receive your vendor number and the Exchange's supplier requirements, and set up EDI before trading. Vendor administration then runs through Exchange Partners Online, the EPOL portal.
The core flow is the 850 purchase order in, with the 856 advance ship notice and 810 invoice back out. AAFES additionally requires the 753 request for routing instructions, the 754 routing instructions, the 824 application advice and the 860 purchase order change. Functional acknowledgments are expected promptly. Confirm the exact mandatory set against the supplier requirements the Exchange issues to you.
AAFES will only accept the 753 routing request if it contains carton-level detail only. If the file is generated at a different level of detail it is rejected, and the shipment cannot be routed. In AIMS360 the correct file type is selected when the 753 is processed, and the request carries total carton count and volume along with weight, cubic feet, NMFC and commodity code. The same 753 and 754 routing pattern appears at other routed retailers.
The 824 application advice reports the disposition of a document you already sent: accepted, rejected, or accepted with changes. In practice it is how errors get communicated, so you can identify what failed, correct it and resubmit. Most retailers never send an 824, which is why vendors new to the Exchange are often unprepared for it.
AAFES supports direct AS2 connectivity and does not mandate any particular EDI provider. Its published guidance is explicit that it will not pay VAN or EDI provider fees of any kind, because direct AS2 is available, so any such costs are the vendor's. That makes the connection method a real cost decision rather than an administrative detail.
Not with AIMS360. Managed EDI is part of the platform, with no separate EDI vendor to license, no per-document or kilocharacter fees and no middleware layer to reconcile. Since AAFES declines to cover VAN or provider fees, keeping the connection inside the ERP removes a cost the Exchange has already said it will not absorb.
Yes. Exchange orders, other retailer EDI programs, Shopify DTC and marketplace orders all allocate against one inventory pool with channel rules, so no channel promises units another has already taken.
The Exchange sets its own testing windows, with AS2 communication testing and EDI data testing each expected to complete within a defined number of business days, and shorter windows where a supplier uses an established EDI provider rather than building its own maps. In AIMS360 the mapping already exists, so the work is configuration and certification rather than development.
Get Started
Bring your program to a demo and we will walk through the 753 routing request, how the 824 gets actioned, and what onboarding looks like on your catalog.
