Aldi EDI
across every channel.
Stacksync wires the full Aldi trading-partner footprint, ALDI US (Legacy ISA ID: 0041498000097), ALDI US (via OpenText), into your ERP, WMS, or warehouse from one workspace.
Adopted by fast-scaling companies moving mission-critical data in real time
Document catalog
EDI documents we support for Aldi
16 transactions across 2 channels.
ALDI US (via OpenText)
8 docsDocument flow
How EDI documents flow with Aldi
Where each document sits in its trading cycle, based on the 8 document types Aldi trades across 2 channels.
Order-to-cash
Partial cycle- 850 Purchase Order
- 855 Purchase Order Acknowledgment not required by Aldi
- 856 Ship Notice Manifest
- 810 Invoice
Logistics
Complete cycle- 204 Motor Carrier Load Tender — runs on 2 of Aldi's 2 channels
- 210 Motor Carrier Freight Details And Invoice — runs on 2 of Aldi's 2 channels
- 214 Transportation Carrier Shipment Status Message — runs on 2 of Aldi's 2 channels
- 810 Invoice — runs on 2 of Aldi's 2 channels
- 850 Purchase Order — runs on 2 of Aldi's 2 channels
- 856 Ship Notice Manifest — runs on 2 of Aldi's 2 channels
- 860 Purchase Order Change Request Buyer Initiated — runs on 2 of Aldi's 2 channels
- 990 Response To A Load Tender — runs on 2 of Aldi's 2 channels
Network context
Aldi trades through OpenText
EDI traffic with Aldi is routed over this network. Stacksync maintains certified connections to each, so one integration covers every partner reachable on them.
OpenText
3 channels · 3 trading partners on Stacksync
OpenText Trading Grid is the EDI messaging service of OpenText Business Network, which OpenText describes as the world's largest business network. Large buying organizations across retail, automotive, and logistics route purchase orders, invoices, ship notices, and transportation documents through it, and suppliers connect via a network mailbox or a direct connection. Documents follow ANSI X12 and EDIFACT standards, with both self-service and fully managed onboarding options.
Aldi channel on this network: ALDI US (via OpenText)
- 810 2 ch
- 850 2 ch
- 856 2 ch
- 860 2 ch
- 204 1 ch
How it works
Three steps to live Aldi EDI.
Stacksync handles the complexity of Aldi EDI so your team doesn't have to. Connect your ERP, WMS, or database through a simple API, we translate, validate, and deliver every transaction automatically.
- 01
Connect your systems
Plug Stacksync into your ERP, WMS, or database with a no-code connector. We handle authentication, schema discovery, and field mapping.
- 02
Map to Aldi guidelines
We ship pre-built mappings for every Aldi document type. Override any field, add custom validation, or extend with custom code.
- 03
Send & receive in real time
Stacksync translates, validates, and delivers every transaction over AS2, SFTP, or API. Watch every document flow live in the dashboard.
Why Stacksync
Built for EDI suppliers, not enterprise legacy.
From pre-built Aldi mappings to real-time compliance checks, Stacksync removes the friction from EDI, so you can focus on growing your business.
-
Pre-built mappings
Stacksync ships native mappings for every Aldi document type. No more 6-week field-mapping projects.
-
Real-time monitoring
Every transaction shows up in the dashboard the second it lands, with retry, revert, and replay built in.
-
No vendor lock-in
Your data lives in your ERP/WMS/database. Stacksync is the translation layer, not the system of record.
-
Days, not months
Most Aldi suppliers go live in under a week. We migrate from SPS Commerce, TrueCommerce, Cleo and IBM Sterling.
Still with a legacy EDI vendor? We cover the buyout.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundSecurity teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Trading partners
5,000+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
FAQ
Aldi EDI questions
How long does it take to set up Aldi EDI with Stacksync?
Most suppliers are fully connected and processing live Aldi EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.
What is Aldi EDI?
Aldi accepts EDI for 8 document types across 2 channels. Trading partners use EDI to exchange purchase orders, invoices, shipping notices, and acknowledgements with Aldi programmatically, Stacksync handles the entire EDI exchange, validation, and translation into your ERP, WMS, or database.
Which EDI standards does Aldi use?
Aldi uses X12. Stacksync supports both X12 (the dominant North American standard) and EDIFACT (the dominant European and global shipping standard) for every connected trading partner. Channel-specific implementation guidelines from Aldi are pre-built into the Stacksync connector and validated on every outbound transaction.
Which transaction codes does Aldi support?
Aldi supports 8 transaction codes in total. The most common include: 990, 850, 214, 210, 810, 856, 860, 204. Each code is mapped to its business-record equivalent (purchase order, ASN, invoice, etc.) inside Stacksync, so EDI exchanges land directly in your ERP or warehouse without manual translation.
How long does Aldi EDI integration take with Stacksync?
Most Aldi EDI integrations go live in 3 to 10 business days. The Stacksync team handles partner enrolment, channel certification, transaction-set mapping per Aldi's implementation guide, and end-to-end testing. Complex multi-channel deployments or custom transaction sets take 2 to 4 weeks. Cutover is zero-downtime and parallel-run validated.