EDI for Microsoft Dynamics (NAV / AX / GP) — pre-built integration with retailers
In short: EDIconnect provides a native, certified Microsoft Dynamics (NAV / AX / GP) integration for EDI: Microsoft Dynamics (NAV / AX / GP) sales orders, deliveries and invoices flow to and from EDIconnect through NAV: Web Services (SOAP/OData). AX: AIF (Application Integration Framework). GP: eConnect. All supported by EDIconnect legacy connectors. — no custom middleware, no batch files, no manual re-entry. Onboard your first retailer in 2-4 weeks.
Key capabilities
- Native Microsoft Dynamics (NAV / AX / GP) connector: NAV: Web Services (SOAP/OData). AX: AIF (Application Integration Framework). GP: eConnect. All supported by EDIconnect legacy connectors.
- Retailer templates included: 30+ pre-built retailer connections — Walmart, Target, Amazon, Costco, Kroger, Home Depot, Lowe's, CVS.
- All standard messages: EDIFACT (ORDERS, DESADV, INVOIC…) and X12 (850, 855, 856, 810, 820, 997) — no custom mapping per document type.
- Fits Microsoft Dynamics (NAV / AX / GP) update cycles: Cloud SaaS platform — Microsoft Dynamics (NAV / AX / GP) version upgrades don't break the integration.
How the Microsoft Dynamics (NAV / AX / GP) + EDIconnect integration works end-to-end
The pattern: a retailer PO arrives at EDIconnect via AS2/OFTP2/SFTP → EDIconnect validates and translates it → sends a sales order to Microsoft Dynamics (NAV / AX / GP) via NAV: Web Services (SOAP/OData) → Microsoft Dynamics (NAV / AX / GP) confirms availability and creates a delivery → the delivery flows back to EDIconnect as a DESADV/856 → invoice follows as INVOIC/810 → EDIconnect transmits everything to the retailer.
All of that happens in minutes, unattended, with full audit trail. Suppliers running Microsoft Dynamics (NAV / AX / GP) + EDIconnect typically handle 10-50× the EDI volume of a manual setup with the same headcount.
Frequently asked questions
How does EDI integrate with Microsoft Dynamics (NAV / AX / GP)?
NAV: Web Services (SOAP/OData). AX: AIF (Application Integration Framework). GP: eConnect. All supported by EDIconnect legacy connectors.
Do I need an ABAP developer / customization on Microsoft Dynamics (NAV / AX / GP)?
Typically no. EDIconnect uses Microsoft Dynamics (NAV / AX / GP)'s standard integration surfaces. Custom fields or special document types may require light configuration, but not custom code.
Can EDIconnect handle both inbound and outbound EDI in Microsoft Dynamics (NAV / AX / GP)?
Yes. Inbound: POs from retailers land as sales orders in the ERP. Outbound: ASNs and invoices are generated by the ERP and transmitted automatically to the retailer.
How long does Microsoft Dynamics (NAV / AX / GP) + EDI integration take?
Typical timeline: 1 week for Microsoft Dynamics (NAV / AX / GP) connector setup and item/partner master sync, 1-3 weeks per retailer for spec mapping and certification testing.
Does EDIconnect support hybrid Microsoft Dynamics (NAV / AX / GP) + non-Microsoft Dynamics (NAV / AX / GP) environments?
Yes. Many customers run Microsoft Dynamics (NAV / AX / GP) for HQ and lightweight tools (Excel, portals) for subsidiaries — EDIconnect connects both to the same EDI backbone.