Skip to content

Channel

AldiALDI US (via OpenText)

Plan a reliable EDI exchange for Aldi / ALDI US (via OpenText). Explore 8 document references, map them to your business records and test the complete workflow before launch.

Book an EDI demo ← All Aldi channels
Documents
8 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Aldi / ALDI US (via OpenText): EDI implementation plan

Build a reliable EDI workflow for Aldi / ALDI US (via OpenText). Use 8 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 214 Transportation Carrier Shipment Status MessageListed for ALDI US (via OpenText) shipment status event

shipment reference, event code, event time and location
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
X12 990 Response To A Load TenderListed for ALDI US (via OpenText) load-tender response

original load reference, carrier and response
  • Associate acceptance with the correct version of the load tender.
  • Test a declined tender and ensure it returns to dispatch for reassignment.
X12 860 Purchase Order Change Request Buyer InitiatedListed for ALDI US (via OpenText) buyer order-change request

original purchase order, change revision and affected line
  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.
X12 850 Purchase OrderListed for ALDI US (via OpenText) purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 856 Ship Notice ManifestListed for ALDI US (via OpenText) shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 810 InvoiceListed for ALDI US (via OpenText) accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 210 Motor Carrier Freight Details And InvoiceListed for ALDI US (via OpenText) freight invoice

carrier invoice, shipment reference and charge line
  • Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate.
  • Test a second invoice for the same shipment and distinguish a revision from a duplicate.
X12 204 Motor Carrier Load TenderListed for ALDI US (via OpenText) load tender

load reference, pickup and delivery stop identifiers
  • Send an amended pickup appointment and retain the previous tender decision.
  • Test a multi-stop load whose stop sequence differs from address sorting.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for ALDI US (via OpenText). Compare other Aldi channels before reusing a mapping.

  2. Map records and assign owners

    Start with shipment status event, load-tender response, buyer order-change request. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Aldi production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using shipment reference, event code, event time and location. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for Aldi / ALDI US (via OpenText)

8 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on ALDI US (via OpenText)

This channel lists all 8 document types in the Aldi directory. Example relationships are shown below; confirm the required sequence in the channel guide.

Network onboarding

Plan the OpenText connection

The directory associates OpenText with 3 partner entries across 3 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.

Most frequently listed documents on OpenText
  • 810 2 ch
  • 850 2 ch
  • 856 2 ch
  • 860 2 ch
  • 204 1 ch
  • 210 1 ch
Other partner entries associated with OpenText

ALDI US (via OpenText) questions

Which EDI documents are listed for Aldi / ALDI US (via OpenText)?

X12 214 Transportation Carrier Shipment Status Message; X12 990 Response To A Load Tender; X12 860 Purchase Order Change Request Buyer Initiated; X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 810 Invoice; X12 210 Motor Carrier Freight Details And Invoice; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

How should I choose the Aldi EDI channel?

ALDI US (via OpenText) lists 8 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.

Which identifiers should the Aldi mapping preserve?

For X12 214 Transportation Carrier Shipment Status Message, plan around shipment reference, event code, event time and location. For X12 990 Response To A Load Tender, use original load reference, carrier and response. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Aldi accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Aldi / ALDI US (via OpenText) EDI?

Deliver an older status after a newer one and retain event history without moving the current status backward. Send one milestone twice and avoid duplicate customer notifications. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Related references

Other Aldi channels

Compare the document lists for other Aldi channels.

ALDI US (Legacy ISA ID: 0041498000097) 8 docs

Showing 1 of 1 references

Browse the full directory

Connect Aldi EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform