EDIFACT DESADV / partner guide required
Generate a Carrefour EDIFACT DESADV from confirmed shipment evidence
Map purchase orders, shipment references, items, quantities, containers and dates before the partner-specific message is rendered.
Direct answer
Direct answer
The Carrefour EDIFACT DESADV path starts from a canonical shipment, not from a guessed message template. Shipment Sentry requires confirmed purchase-order, shipment, item, quantity and container fields, then uses the route's EANCOM / EDIFACT pack to render UNB/UNZ and UNH/UNT plus BGM, DTM, NAD, CPS, PAC, RFF, LIN and QTY. Because this route is partner-guide-required, production release also requires your current Carrefour qualifiers, situational rules and accepted/rejected fixtures.
Why mapping needs a controlled workflow
A syntactically valid DESADV can still describe the wrong purchase order, item, quantity or logistics unit. Separating source evidence, canonical mapping, partner rendering and final validation makes each defect attributable and prevents a visual or spreadsheet mapping guess from becoming an unreviewed dispatch.
What the control should check
- 01Pin the Carrefour pack to the guide version used by the account.
- 02Reconcile source purchase order and shipped item identifiers before rendering.
- 03Validate quantity, unit and date normalization.
- 04Build and recount every UNB/UNZ and UNH/UNT control after the message body is complete.
- 05Validate SSCC values and preserve package-to-item relationships.
- 06Hold output when a required route value or confirmed mapping is missing.
Working example
UNH+1+DESADV:D:VERSION:UN'BGM+351+SHIPMENT+9'RFF+ON:PURCHASE-ORDER'CPS+1'LIN+1++ITEM:QUALIFIER'QTY+12:QTY:UOM'The example is intentionally schematic. Do not copy its qualifiers or directory version into a Carrefour account without the current implementation guide.
Failure modes worth catching
- The shipment hierarchy is flattened and items attach to the wrong order.
- Leading zeroes disappear from a logistics-unit identifier.
- A partner qualifier is copied from a generic example.
- The complete message changes after it was validated.
Put it into the dispatch workflow
- 1Confirm the physical shipment source.
- 2Apply the exact approved source recipe.
- 3Render the Carrefour EDIFACT DESADV with route-owned identifiers.
- 4Run structural and configured partner rules.
- 5Release the exact validated bytes and retain their content hash.
Questions
Implementation answers
Is the Carrefour 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