AAFES EDI Integration for Military Exchange Suppliers

The Army & Air Force Exchange Service serves over 2 million active-duty military personnel and their families across 3,500+ retail locations worldwide. SBSA Technology handles full EDI compliance for all AAFES supplier types — merchandise vendors, food & beverage suppliers, and licensed brand partners.

Your AAFES Supplier Type

Select your fulfillment category to see requirements

1
Receive EDI 850 Purchase Order from AAFES

AAFES issues EDI 850 POs for all merchandise categories. The PO specifies the ship-to DC or store location and required delivery window.

2
Send 855 Acknowledgment within 24 hours

AAFES requires PO acknowledgment within one business day. Late or missing acknowledgments affect your vendor scorecard.

3
Ship complete to AAFES distribution center

AAFES expects orders to be fulfilled complete. Shortfalls must be reflected in the 855 with revised ship dates — do not cancel backorders silently.

4
Transmit 856 ASN before shipment arrives

The ASN must reach AAFES before the physical goods. Any shipment received without a prior ASN is subject to refusal and chargeback.

5
Invoice via EDI 810 — one invoice per PO

Submit one 810 per purchase order. GS1-128 carton labels required on all shipments to AAFES distribution centers.

1
AAFES Commissary & food service EDI 850

Food and beverage POs include additional data fields for lot numbers, expiration dates, and country of origin requirements.

2
Temperature and shelf-life compliance fields

Food suppliers must include handling codes and shelf-life data in the ASN. SBSA maps these fields automatically from your WMS or ERP.

3
Same 855 / 856 / 810 timing rules apply

Acknowledgment within 24 hours and ASN prior to shipment arrival are mandatory for food vendors as well as merchandise vendors.

4
Case-level pack configuration in the 856

AAFES requires case-pack quantities and UPC data to be confirmed at the line level in the advance ship notice.

5
SBSA handles food-specific data transformations

Our EDI mapping layer accounts for lot tracking, GTIN hierarchies, and food safety certification fields required by AAFES procurement.

1
850 PO routes directly to a base retail store

Direct delivery POs specify an individual AAFES store location on a military installation rather than a central distribution center.

2
Delivery appointment coordination required

Military installations require advance delivery appointments. SBSA's integration includes appointment scheduling data in the ASN workflow.

3
AAFES-branded packing documentation mandatory

Direct-to-store shipments require AAFES-compliant packing slips and labeling. SBSA generates these from your ASN data automatically.

4
Carrier tracking number required in the ASN

For parcel shipments, the tracking number must be embedded in the 856. For freight, include PRO or BOL number in the carrier routing segment.

5
SBSA bridges direct delivery to your ERP

Store-level order volume requires automation. SBSA connects AAFES store POs directly to your warehouse management or fulfillment system.

Which Type of AAFES Supplier Are You?

AAFES works with a wide range of vendor types. Understanding your supplier category is the first step to mapping the correct EDI workflow, carton labeling standard, and compliance scorecard metrics.

Retail & Hardline Products

Apparel, electronics, sporting goods, automotive, toys, home goods, and all standard retail categories sold in AAFES main stores and Express locations.

Merchandise Vendor

Commissary & Food Court

Shelf-stable groceries, beverages, snacks, and food court ingredients supplied to AAFES commissaries and food service concessions on military bases.

Food & Beverage

Franchise & Brand Concessions

National brand franchises operating within AAFES facilities — fast food, coffee, optical, auto services — with specific procurement and invoicing requirements.

Licensed Brand Partner
2M+ Active-duty military customers served
3,500+ Exchange retail locations worldwide
30+ Countries with AAFES installations
24hr Required EDI 855 acknowledgment window

AAFES EDI Connection Methods Connectivity

AAFES supports three EDI transmission protocols. SBSA Technology configures, manages, and monitors all three — including certificate renewal, partner profile setup, and failover handling.

SFTP

Secure File Transfer

SFTP file-based EDI exchange with AAFES's managed file server. A straightforward option for suppliers with existing SFTP infrastructure or moderate order volumes.

  • Transfer: Encrypted SSH file exchange
  • Polling: Configurable pickup intervals
  • SBSA manages: Key exchange and folder setup
  • Ideal for: Mid-volume or seasonal suppliers

VAN

Value-Added Network

Traditional VAN-based EDI through a third-party network mailbox. AAFES maintains VAN connectivity for legacy supplier setups and complex multi-retailer environments.

  • Networks: SBSA connects to all major VANs
  • Routing: ISA/GS qualifier-based routing
  • SBSA manages: Mailbox setup and routing tables
  • Ideal for: Multi-retailer supplier networks

AAFES EDI Integration EDI Transaction Set

SBSA Technology supports core and supplemental AAFES EDI Integration EDI documents. Critical transactions are highlighted because they carry the highest compliance risk when transmitted incorrectly or late.

850

Purchase Order

AAFES sends the 850 to initiate all purchase orders. It contains item, quantity, price, ship-to location, and required delivery window. The 850 is the start of every AAFES transaction cycle.

Inbound
855

PO Acknowledgment

You must return an 855 within 24 hours of receiving the AAFES 850. The 855 confirms acceptance, updates quantities or ship dates where needed, and is tracked on your vendor scorecard.

Outbound 24-hour acknowledgment window
856

Advance Ship Notice

The 856 ASN must be transmitted before your shipment arrives at the AAFES facility. It includes carton-level packing detail, GS1-128 label data, carrier information, and tracking or PRO numbers.

Outbound Shipment refused if ASN missing on arrival
810

Invoice

Submit one 810 invoice per AAFES purchase order. Invoice amounts must match the 850 PO exactly unless a change was acknowledged in the 855. One invoice per PO — no consolidated billing.

Outbound
997

Functional Acknowledgment

A 997 must be returned for every inbound EDI document received from AAFES. This handshake confirms the transaction was received and syntactically accepted by your system.

Outbound
860

PO Change Request

AAFES may issue an 860 to modify a previously sent PO — adjusting quantities, prices, or delivery dates. SBSA flags and maps all 860 changes back to your ERP automatically.

Inbound

Connect AAFES EDI to Your Business System

SBSA Technology integrates AAFES EDI directly with your ERP, WMS, or accounting software — eliminating manual order entry and ensuring AAFES compliance without changing how your team works.

QuickBooks Online

AAFES purchase orders flow directly into QuickBooks Online as sales orders. When you ship and invoice AAFES, the 810 is generated and transmitted automatically — no double entry, no manual uploads.

QuickBooks Enterprise

For larger merchandise suppliers using QuickBooks Enterprise, SBSA provides deep two-way integration — including inventory sync, advanced pricing rules, and multi-warehouse ASN support aligned to AAFES specifications.

SAP

SBSA provides certified SAP EDI integration for AAFES, mapping X12 transactions to SAP IDocs and business objects via RFC or middleware layer.

NetSuite

AAFES EDI transactions map directly to NetSuite Sales Orders, Item Fulfillments, and Invoices via SBSA's SuiteScript or REST API connector.

Microsoft Dynamics

SBSA integrates AAFES EDI with Dynamics 365 Business Central and Finance & Operations using native API connectors and Dataverse mapping.

D365 & BC

Using a WMS, 3PL platform, or custom system? SBSA integrates via flat-file, REST API, SFTP, or direct database connection to support your specific technology stack.

What SBSA Automates for AAFES Suppliers

Every AAFES compliance failure costs money — chargebacks, refused shipments, and vendor scorecard penalties. SBSA's automation layer removes manual touchpoints from the entire EDI workflow.

Automatic 855 Acknowledgment

Real-Time ASN Generation

GS1-128 Label Automation

Chargeback Prevention Monitoring

ERP Order Lifecycle Management

Compliance Scorecard Tracking

AAFES EDI FAQ

Common questions from suppliers beginning their AAFES EDI compliance journey.

AAFES (Army & Air Force Exchange Service) is the retail and services arm for U.S. military personnel and their families, operating over 3,500 retail locations on military installations in 50 states and 30+ countries. Any supplier selling merchandise, food, or licensed products to AAFES must comply with its EDI requirements to exchange purchase orders, acknowledgments, advance ship notices, and invoices electronically. Non-EDI suppliers cannot trade with AAFES at scale.

AAFES requires four core EDI transactions: the EDI 850 (Purchase Order, inbound from AAFES), the EDI 855 (PO Acknowledgment, outbound from you, required within 24 hours), the EDI 856 (Advance Ship Notice, outbound before physical goods arrive), and the EDI 810 (Invoice, one per PO). The EDI 997 Functional Acknowledgment is also required for every inbound document. Optional transactions include the EDI 860 (PO Change Request) issued by AAFES to modify existing orders.

AAFES enforces strict ASN compliance. Shipments arriving at an AAFES distribution facility without a prior or concurrent 856 ASN may be refused entirely, returned to the supplier at the supplier's cost, and recorded as a compliance failure on your vendor scorecard. A refused shipment is one of the most expensive outcomes in AAFES supplier compliance. SBSA transmits the 856 ASN automatically the moment your shipment leaves your facility, preventing this scenario entirely.

Yes. SBSA Technology is an Intuit Silver Partner and provides direct EDI integration with both QuickBooks Online and QuickBooks Enterprise. AAFES purchase orders flow automatically into QuickBooks as sales orders, and when you generate an invoice in QuickBooks, SBSA converts it to an EDI 810 and transmits it to AAFES automatically — no manual data entry or file uploads required. This is one of the most popular AAFES integration configurations we support.

Marine Corps Exchange (MCX), Navy Exchange (NEX), and Coast Guard Exchange (CGX) each operate as separate EDI trading partners from AAFES. They have their own ISA/GS qualifiers, trading partner IDs, and compliance specifications — though the underlying X12 transaction sets (850, 855, 856, 810) are the same. SBSA supports all four military exchange services simultaneously from a single managed integration platform, with separate compliance monitoring dashboards for each exchange.

Most AAFES EDI onboarding projects are completed in 2 to 4 weeks, depending on ERP complexity, the number of trading partner connections being established, and AAFES's own testing schedule. SBSA handles all AAFES-side communication, coordinates testing cycles, and manages ISA/GS qualifier setup on your behalf. You receive a dedicated onboarding manager and a clear project timeline from day one.

AAFES supports three EDI transmission protocols: AS2 (direct encrypted HTTPS connection, the recommended method), SFTP (secure file-based transfer), and VAN (Value-Added Network via a third-party mailbox). SBSA Technology configures, manages, and monitors all three protocols — including certificate rotation for AS2, key management for SFTP, and routing table maintenance for VAN. Most new AAFES suppliers use AS2 for its real-time delivery receipts and lower latency.

Ready to Become AAFES EDI Compliant?

Tell us your supplier type and ERP system — we'll build a complete AAFES integration plan tailored to your operation.