Source mapping → ALDI
Map the file you already have to the ALDI EDI route
Use a confirm-once mapping rather than commissioning another format-specific import script.
Direct answer
Direct answer
ALDI EDI file mapping converts a stable internal export into the canonical fields needed by the route: purchase order, shipment reference, item, quantity, unit, container, carton count, weight and dates. Shipment Sentry analyzes CSV, TSV, Excel, JSON, XML, SAP IDoc, text and ASCII directly; PDF and images use schema-constrained AI extraction. Critical fields always require confirmation, and reuse is limited to the exact approved source format and heading signature.
Why mapping needs a controlled workflow
The mapping recipe is reusable; the ALDI guide is account-specific. Keeping them separate means a warehouse export can feed another partner route without copying parser code, while the ALDI EDIFACT DESADV still owns its identifiers, qualifiers and validation rules.
What the control should check
- 01Detect real file type and reject disguised or empty sources.
- 02Limit a mapping preview to 1–1,000 shipment rows.
- 03Expose source headings, proposed canonical targets and confidence.
- 04Require unique source columns for every mapped target.
- 05Expire and tenant-bind the confirmation draft.
- 06Apply the confirmed recipe only inside the intended ALDI workspace route.
Working example
CSV / XLSX / XML / JSON / IDoc / TXT / PDF
↓ confirmed mapping
purchase_order | shipment_reference | item_id | quantity | container_id
↓ ALDI route
EDIFACT DESADVThe canonical fields are stable; the receiving route still requires the current implementation guide and account identifiers.
Failure modes worth catching
- A stale recipe accepts an added or renamed source column.
- Two source columns target the same shipment field.
- AI output adds a field outside the fixed schema.
- An optional blank is converted into a quantity of zero.
Put it into the dispatch workflow
- 1Create the ALDI route and mark it guide-required.
- 2Upload a representative source file.
- 3Review the proposal and explicitly confirm every required field.
- 4Resubmit matching files in a partner-coded batch.
- 5Render and validate EDIFACT DESADV; quarantine changed layouts for a new confirmation.
Questions
Implementation answers
Is the ALDI pack production-ready without my implementation guide?
No. The starter route is explicitly partner-guide-required. It provides routing, canonical mapping and generic EANCOM / EDIFACT structure, but the current account guide and identifiers must be configured and approved.
Can I reuse an existing warehouse export?
Yes when it contains the required shipment truth. Analyze one representative CSV, spreadsheet, JSON, XML, IDoc, text, PDF or image and confirm its critical fields before automation.
How can files enter the gateway?
Use a partner-coded SFTP folder or filename, an authorized email recipient or attachment prefix, or the idempotent partner-batch API. Each channel supports independently routed results.
Sources and limits
Reviewed 2026-07-19. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.
Keep investigating