972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Planning and inventory

DELFOR Delivery schedule

The UN/EDIFACT message a customer sends to give suppliers short-term delivery requirements and medium- to long-term schedules.

Sent by
Customer planning the use of products
Received by
Supplier planning the supply
Standard
UN/EDIFACT · Batch message
X12 equivalent
830 Planning Schedule with Release Capability

What is the EDIFACT DELFOR message?

DELFOR is the UN/EDIFACT delivery schedule message. The directory describes it as a message sent from a party planning the use or consumption of products to a party that has to plan their supply, giving requirements for short-term delivery and medium- to long-term scheduling. The schedule can be used to authorize manufacturing or the provision of materials, based on the terms and conditions agreed between the parties.

DELFOR is central to automotive and industrial supply chains, where customers send updated schedules weekly or daily. The directory warns that the DELFOR structure changed from D02A, so versions before and after are not compatible.

How the EDIFACT DELFOR message worksDiagram of the UN/EDIFACT DELFOR Delivery schedule message. Customer planning the use of products sends it to supplier planning the supply. It usually starts the exchange. It is usually followed by DELJIT and DESADV. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT DELFOR message worksDelivery schedule: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDELFORSENDERCustomer planning theuse of productsRECEIVERSupplier planning thesupplyCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYDELJITDelivery just in timeDESADVDespatch advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage DELFORUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 4 conditional groups, starting with:RFFNADTDTGEIBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for DELFOR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT DELFOR message worksDiagram of the UN/EDIFACT DELFOR Delivery schedule message. Customer planning the use of products sends it to supplier planning the supply. It usually starts the exchange. It is usually followed by DELJIT and DESADV. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT DELFORmessage worksDelivery schedule: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDELFORSENDERCustomerplanning the useof productsRECEIVERSupplierplanning thesupplyCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYDELJITDelivery just in timeDESADVDespatch advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message DELFOR (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 4 conditional groups, starting with:RFFNADTDTGEIBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for DELFOR.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends DELFOR, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around DELFOR and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Sending rolling forecasts to suppliers
  • Releasing firm delivery requirements
  • Authorizing fabrication and raw material purchases

Where it fits in the message flow

This message DELFOR Delivery schedule
Usually followed by DELJIT Delivery just in timeDESADV Despatch advice

Structure

Mandatory segments in DELFOR (directory D.21A)

In UN/EDIFACT directory D.21A, the DELFOR message has 79 segment positions arranged in 32 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • UNT

Practical example

DELFOR in practice

A vehicle assembly plant sends each component supplier a DELFOR every week with firm requirements for the next two weeks, forecasts for the following months, the cumulative quantity received to date and fabrication authorizations. A seat supplier loads the schedule into its planning system to set production and to order foam and fabric.

Implementation

Implementation considerations for DELFOR

  • Confirm the version; DELFOR before and after D02A are structurally different.
  • Reconcile cumulative quantities between customer and supplier regularly.
  • Distinguish firm, planning and authorization quantities.
  • Follow industry guidelines such as Odette or VDA where the customer requires them.

How ECOM helps

Automate DELFOR with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related planning and inventory messages

All 6 planning and inventory messages

Need help with DELFOR?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us