What is a DELFOR?
The EDIFACT DELFOR is a delivery forecast message used by buyers to communicate time-phased demand to suppliers, including item, quantity, location, and schedule details, enabling production planning, inventory optimization, and logistics coordination.
What is EDIFACT DELFOR used for?
EDIFACT DELFOR is used to communicate forecast demand from buyers to suppliers, allowing suppliers to plan production, inventory, and logistics based on future requirements rather than immediate orders.
Who sends EDIFACT DELFOR?
EDIFACT DELFOR is typically sent by buyers, OEMs, or retailers to suppliers to communicate forecasted demand and delivery schedules.
When is the EDI DELFOR sent?
EDIFACT DELFOR is typically sent on a recurring basis—weekly, daily, or monthly—depending on industry requirements and trading partner agreements.
Transaction Identity Block
| Attribute | Description |
| Transaction Name | Delivery Schedule Message |
| EDIFACT Message Type | DELFOR |
| Version | D96A |
| Industry Usage | Automotive, Manufacturing, Retail, Grocery |
| Primary Purpose | Communicate forecast demand and delivery schedules |
| Typical Sender | Buyer / OEM / Retailer |
| Typical Receiver | Supplier / Manufacturer |
| Common Preceding Transactions | ORDERS, INVRPT |
| Common Following Transactions | DESADV, INVOIC |
| Standard Authority | UN/EDIFACT |
What Does the DELFOR EDI message Do?
The Delivery Forecast EDI message communicates forecasted demand across defined time horizons, including: Item identification (LIN)
- Delivery location (LOC)
- Forecast quantities (QTY)
- Delivery timing (DTM)
- Forecast commitment status (SCC)
The DELFOR format enables suppliers to align production schedules, labor planning, procurement, and logistics execution with anticipated demand.
Who Uses the EDIFACT DELFOR?
Like the X12 830, the DELFOR message is most commonly used by buyers in Automotive (e.g., just-in-time (JIT) production), Retail & Consumer Goods (seasonal planning and replenishment), Manufacturing & Industrial (e.g., material requirements planning (MRP), and in Grocery & Foodservice (managing perishables and distribution).
| Industry | Use Case |
| Automotive | JIT production scheduling |
| Retail & Grocery | Demand forecasting and replenishment |
| Manufacturing | Material requirements planning |
| Consumer Goods | Distribution and inventory positioning |
What industries use EDIFACT DELFOR the most?
EDIFACT DELFOR is most widely used in automotive, manufacturing, retail, grocery, and consumer goods industries. It is especially critical in just-in-time (JIT) supply chains, where accurate demand forecasting is required to synchronize production, inventory, and logistics across trading partner networks.
When Is the EDIFACT DELFOR Required?
Organizations transmit DELFOR on a recurring cadence:
- Weekly (most common in automotive)
- Bi-weekly or monthly (retail and manufacturing)
Trading partner agreements typically define frequency and structure requirements.
How often should DELFOR be updated?
DELFOR is typically updated on a recurring basis—weekly in automotive environments and bi-weekly or monthly in retail and manufacturing. The update frequency depends on trading partner agreements, forecast volatility, and operational requirements for production and inventory planning.
Is the EDIFACT DELFOR Mandated Under Regulation?
No, the DELFOR is not directly mandated by regulation. Trading partner agreements, OEM requirements, and industry frameworks (e.g., automotive standards) commonly require its use.
How Does the EDIFACT DELFOR Work in the Business Workflow?
The EDIFACT DELFOR message integrates demand forecasting with procurement and supply chain planning
Upstream Transactions
Upstream transactions that support the DELFOR delivery forecast include PRICAT for product data, INVRPT for inventory visibility, ORDERS for contractual agreements, and ORDRSP for supplier confirmation, while organizational and location data are typically managed through NAD and LOC structures rather than a single dedicated transaction.
The following upstream transactions typically precede the EDIFACT DELFOR:
| EDIFACT Transaction | EDIFACT Message Name | Purpose | Why It Occurs Before DELFOR |
| PARTIN / NAD Structures / DIRDEB (varies) | Party / Organizational Information | Communicates corporate structure, trading partner identities, and location hierarchies using NAD/LOC constructs or dedicated messages depending on implementation | Ensures both parties share a consistent understanding of organizational structure and locations before forecast schedules are issued |
| PRICAT | Price/Sales Catalogue | Communicates product master data including item identifiers, pricing, packaging, and descriptions | Ensures both parties share a consistent product master before forecast schedules are issued |
| INVRPT | Inventory Report | Provides inventory availability, stock levels, and consumption data from supplier or distributor | Buyers use inventory visibility to refine forecast demand schedules communicated via DELFOR |
| ORDERS | Purchase Order | Establishes the contractual purchase relationship between buyer and supplier | DELFOR often releases or forecasts demand against an existing contract or order |
| ORDRSP | Order Response | Confirms supplier acceptance of a purchase order and validates terms | Ensures supplier commitment before forecast schedules are transmitted |
| PRODAT / PSS (varies by industry) | Product Data / Item Maintenance | Synchronizes item identifiers, packaging, engineering attributes, or product specifications | Prevents product identifier mismatches in forecast schedules |
Canonical Mapping Summary
| Canonical Function | X12 | EDIFACT |
| Organizational Structure | 816 | NAD / LOC / PARTIN |
| Product Master | 832 | PRICAT |
| Inventory Visibility | 846 | INVRPT |
| Purchase Agreement | 850 | ORDERS |
| Order Confirmation | 855 | ORDRSP |
| Item Maintenance | 888 | PRODAT / PRICAT |
What is the difference between DELFOR and ORDERS?
The EDIFACT DELFOR communicates forecasted demand for planning purposes, while ORDERS represents a firm purchase order that initiates a legally binding transaction. DELFOR provides forward-looking demand signals, whereas ORDERS triggers actual procurement, fulfillment, and financial processes within the supply chain.
What is the difference between DELFOR and INVRPT?
Where DELFOR communicates future demand forecasts from buyer to supplier, INVRPT provides current inventory levels from supplier or buyer environments. Together, they support supply chain planning by aligning projected demand with available inventory, enabling more accurate production, replenishment, and distribution decisions.
Downstream Transactions
Downstream transactions following DELFOR include DELJIT for short-term delivery execution, DESADV for shipment notification, IFTSTA for transportation visibility, RECADV for receipt confirmation, INVOIC for billing, and REMADV for payment reconciliation, collectively transforming forecast demand into physical and financial execution.
| EDIFACT Transaction | EDIFACT Message Name | Primary Purpose | Why It Follows DELFOR |
| ORDRSP | Order Response | Confirms supplier acceptance of forecast-driven order releases or commitments | Validates that the supplier can meet forecast demand communicated via DELFOR |
| DESADV | Despatch Advice (ASN) | Announces shipment contents, packaging, and delivery timing | Enables warehouse receiving preparation and inbound planning |
| DELJIT | Delivery Just-In-Time | Provides short-term, highly detailed delivery or shipping instructions | Refines the longer-term forecast communicated in DELFOR into executable delivery schedules |
| IFTSTA | Transport Status Message | Communicates in-transit shipment status updates | Provides visibility into shipment progress during transportation |
| RECADV | Receiving Advice | Confirms receipt and acceptance of goods | Validates that shipment arrival and quantities match forecast and delivery expectations |
| INVOIC | Invoice | Requests payment for delivered goods | Initiates financial settlement following delivery |
| REMADV | Remittance Advice | Communicates payment and settlement details | Completes financial reconciliation and closes the transaction lifecycle |
Canonical Mapping Summary
| Canonical Function | X12 | EDIFACT |
| Forecast Response | 855 | ORDRSP |
| Shipment Notice | 856 | DESADV |
| Short-Term Schedule | 862 | DELJIT |
| Shipment Status | 214 | IFTSTA |
| Receiving Confirmation | 861 | RECADV |
| Invoice | 810 | INVOIC |
| Payment | 820 | REMADV |
End-to-End Workflow Example
- Buyer establishes purchasing relationship
- Buyer generates demand forecast
- DELFOR is transmitted to supplier
- Supplier plans production and logistics
- Shipments are executed (DESADV)
- Financial settlement occurs (INVOIC)
Industry-Specific Workflow Variations
| Industry | Forecast Model |
| Automotive | Weekly firm + forecast schedules |
| Retail | Promotion-driven forecasts |
| Grocery | CPFR replenishment models |
| Industrial | Long-term capacity planning |
EDIFACT DELFOR vs EDI 830
| Feature | DELFOR (EDIFACT) | EDI 830 (X12) |
| Standard | UN/EDIFACT | ANSI X12 |
| Forecast Structure | SCC + QTY + DTM | FST + BFR |
| Location Handling | LOC | SDQ |
| Usage | Global | North America |
Can DELFOR trigger shipments directly?
No, DELFOR does not directly trigger shipments. It is a planning message used to communicate forecast demand. Execution is typically driven by downstream transactions such as DELJIT for scheduling and DESADV for shipment notification.
How is DELFOR different from a purchase order?
While a purchase order (ORDERS or EDI 850) is a binding commitment to buy goods, a DELFOR is a non-binding forecast message used for planning. The DELFOR message helps suppliers prepare for future demand, whereas purchase orders trigger actual production, shipment, and billing activities. In many instances, the DELFOR message goes a step further helping suppliers fulfil previous commitments to buy goods by detailing delivery expectations for certain god in industries like Automotive.
Cross-Standard Canonical Mapping
Canonical Function | X12 | EDIFACT | VDA | ODETTE |
Forecast Planning | 830 | DELFOR | 4905 | DELFOR |
JIT Delivery | 862 | DELJIT | 4915 | DELJIT |
How Does PartnerLinQ Use the EDIFACT DELFOR?
PartnerLinQ treats DELFOR as a core upstream planning signal within its execution control layer, where forecast data is:
- Ingested and normalized into a canonical model
- Classified (firm vs forecast via SCC)
- Distributed across partner networks
- Monitored for exceptions and variance
This transforms DELFOR into a controlled, visible, and actionable execution signal across multi-enterprise ecosystems.
Where Is the EDIFACT DELFOR Used?
The DELFOR is used in:
- Automotive manufacturing networks
- Retail supply chains
- Industrial production planning
- Grocery and foodservice distribution
What Is the Purpose, Key Features, and Business Use Cases of the EDIFACT DELFOR?
The EDIFACT DELFOR is used to communicate delivery forecasts from buyers to suppliers, providing time-phased demand by item, location, quantity, and schedule. It combines forecast quantities, delivery timing, location detail, and schedule commitment (firm vs forecast) to align supply chain execution with anticipated demand across multi-enterprise networks. It enables production planning, inventory optimization, and logistics coordination by distinguishing firm commitments from forecast demand and support efficient supply chain execution.
Operational Purpose
The primary purpose of the EDIFACT DELFOR is to synchronize buyer demand forecasts with supplier planning and execution processes.
The DELFOR enables organizations to communicate:
- Forecast demand across defined time horizons
- Delivery schedules tied to locations and products
- Resource planning signals (labor, materials, capacity)
- Schedule commitment levels (firm vs forecast via SCC)
The DELFOR functions as a forward-looking planning instrument, allowing suppliers to prepare for demand before orders are executed.
Key Features
| Feature | Description | Business Impact |
| Time-Phased Forecasting | Communicates demand across weekly, monthly, or custom time buckets (DTM + QTY) | Enables structured production and procurement planning |
| Firm vs Forecast | Uses the SCC to classify/distinguish committed demand from projected demand values | Prevents overproduction and reduces supply risk |
| Multi-Location Forecasting | Supports delivery forecasts by plant, warehouse, or distribution center (LOC) | Improves routing and fulfillment accuracy |
| Item-Level Forecasting | Uses LIN loop to define forecast per product | Enables granular planning and execution |
| Rolling Forecast Horizon | Supports continuous updates and revisions | Keeps suppliers aligned with demand changes |
| Reference Integration | Links contracts, purchase orders, or agreements (RFF) | Maintains traceability across transactions |
| Canonical Compatibility | Aligns with X12 830 and other standards | Enables multi-standard interoperability |
Business Use Cases
| Use Case | Description | Business Outcome |
| Supplier Production Planning | Suppliers use forecast schedules to plan manufacturing capacity and labor allocation | Improved production efficiency and reduced bottlenecks |
| Inventory Planning & Replenishment | Forecast quantities guide stocking strategies and replenishment cycles | Reduced stockouts and excess inventory |
| Logistics & Transportation Planning | Delivery timing and location data drive shipment scheduling | Optimized transportation and warehouse operations |
| Automotive JIT Scheduling | OEMs transmit rolling forecasts to Tier suppliers | Supports just-in-time manufacturing models |
| Retail & Grocery Forecasting (CPFR) | Retailers share demand forecasts for replenishment planning | Improves shelf availability and demand alignment |
| Supplier Managed Inventory (SMI) | Suppliers manage inventory levels based on forecast data | Enhances collaboration and reduces carrying costs |
| Capacity & Resource Planning | Forecast signals enable labor and material planning | Improves resource utilization and cost control |
What Information Is Required in the EDIFACT DELFOR?
The EDIFACT DELFOR requires structured forecast data including item identification, delivery location, quantities, scheduling dates, and schedule classification to ensure accurate supply chain planning and execution. These elements ensure that suppliers can accurately interpret demand, plan production, and execute deliveries.
The EDIFACT DELFOR message is built to communicate time-phased demand with full operational context, in context, an executable forecast generally requires gathering the following insight:
- Who → Party identification (buyer, supplier, ship-to)
- What → Product or item (LIN)
- Where → Delivery location (LOC)
- When → Delivery timing (DTM)
- How much → Forecast quantity (QTY)
- How firm → Schedule classification (SCC)
Quick DELFOR Segment Reference
| Segment | Name | Purpose |
| UNH | Message Header | Identifies message type and control number |
| BGM | Beginning of Message | Defines document type and reference |
| DTM | Date/Time/Period | Specifies forecast dates and validity |
| RFF | Reference | Links contracts or purchase orders |
| NAD | Name and Address | Identifies trading partners |
| CTA / COM | Contact Information | Defines communication contacts |
| UNS | Section Control | Separates header and detail |
| LIN | Line Item | Identifies product |
| IMD | Item Description | Describes item when needed |
| LOC | Location | Defines delivery location |
| QTY | Quantity | Specifies forecast quantity |
| SCC | Scheduling Conditions | Defines firm vs forecast |
| UNT | Message Trailer | Ends message and validates count |
What is the role of LOC in DELFOR?
The LOC segment in DELFOR identifies delivery locations such as warehouses, plants, or distribution centers. It ensures that forecast demand is allocated correctly across multiple locations, enabling accurate routing, inventory positioning, and fulfillment planning.
Required Segments (Must Use)
Based on a unified PartnerLinQ specification, the following segments define the minimum viable forecast structure, that is to say they are typically held to be mandatory for a valid DELFOR message:
| Segment | Role | Key Elements |
| UNH | Message start | Message type (DELFOR), control number |
| BGM | Document identity | Document code (241), reference number, function |
| DTM | Document date | Forecast issue date |
| RFF | Reference | Contract or agreement reference |
| NAD | Party identification | Buyer, supplier, ship-to |
| CTA | Contact | Communication contact |
| UNS | Section control | Separates header and detail |
| LIN | Item definition | Product identifier |
| QTY | Forecast quantity | Quantity values |
| UNT | Message end | Segment count and control |
Optional but Operationally Critical Segments
While optional in the standard, these are essential in real-world implementations:
| Segment | Purpose | Why It Matters |
| IMD | Item description | Clarifies product details |
| LOC | Delivery location | Enables multi-location forecasting |
| DTM (Detail) | Delivery timing | Defines schedule per quantity |
| SCC | Schedule classification | Distinguishes firm vs forecast |
| RFF (Line-level) | Item references | Links to orders or contracts |
Required Identifiers
| Identifier | Segment | Purpose |
| Message Reference | UNH | Unique transaction control |
| Forecast Document Number | BGM | Identifies forecast instance |
| Party Identifier | NAD | Buyer, supplier, ship-to |
| Product Identifier | LIN | SKU, GTIN, or internal item |
| Location Identifier | LOC / NAD | Delivery destination |
Required Dates
| Date Type | Segment | Purpose |
| Document Date | DTM (Header) | Forecast generation date |
| Forecast Period | DTM | Validity window |
| Delivery Date | DTM (Detail) | When goods are required |
| Schedule Window | DTM + SCC | Defines timing pattern |
Required Reference Numbers
| Reference Type | Segment | Example |
| Contract Number | RFF | Agreement ID |
| Purchase Order | RFF | Blanket PO |
| Release Number | RFF | Forecast revision |
Line-Level Forecast Detail
The DELFOR message supports granular forecasting at the item and location level where each LIN loop represents a complete forecast structure per item.
| Element | Segment | Description |
| Product ID | LIN | Identifies item |
| Quantity | QTY | Forecast amount |
| Timing | DTM | Delivery schedule |
| Location | LOC | Delivery destination |
| Schedule Type | SCC | Firm vs forecast |
Summary Table of Key Segments
| Segment | Function | Business Role |
| UNH | Message control | Identifies message |
| BGM | Document identity | Forecast reference |
| NAD | Party roles | Defines participants |
| LIN | Item | Product definition |
| LOC | Location | Delivery routing |
| QTY | Quantity | Demand signal |
| SCC | Schedule | Commitment classification |
| DTM | Timing | Delivery schedule |
| UNT | Trailer | Validation |
What Status and Reason Codes Are Used with the EDIFACT DELFOR?
The EDIFACT DELFOR uses the SCC segment to define schedule status (such as firm or forecast demand) and the BGM segment to indicate document status (original, replacement, or cancellation). Unlike some EDI transactions, DELFOR does not use a standardized set of reason codes, relying instead on contextual updates and trading partner rules.
What is a DELFOR forecast horizon?
A DELFOR forecast horizon defines the time span covered by the forecast, typically including short-term firm demand and longer-term forecast demand. It enables suppliers to plan production and resources over multiple time periods, balancing immediate commitments with future demand projections.
Status Codes (SCC Context)
The SCC segment is the most important status indicator in DELFOR, it defines how forecast quantities should be interpreted:
| Code | Meaning |
| 1 | Firm |
| 4 | Forecast |
Reason Codes
Unlike healthcare EDI or claims processing the DELFOR does not define standardized reason codes. Reasons for changes or exceptions are generally defined in trading partner agreements and communicated through references (RFF), occasionally free text (FTX), and external workflows. Reason codes are typically implementation-specific and defined by trading partners.
About FTX (free text, if used)
While the use of ‘free text’ persists within some trade relationships, PartnerLinQ does not recommend the use of the FTX segment, the FTX segment is a conditional segment used to convey unstructured or semi-structured free-form or coded textual information; supplemental details, general comments, instructions, or references to standard texts that that cannot be accommodated by other structured data segments and typically agreed upon by trading partners use the FTX segment.
What Are the Benefits of the EDIFACT DELFOR?
The EDIFACT DELFOR improves supply chain efficiency by providing forward visibility into demand, enabling production planning, inventory optimization, and logistics coordination. It reduces uncertainty, enhances partner collaboration, and supports cost control by aligning supplier operations with forecasted requirements.
Supply Chain Coordination Benefits
| Supply Chain Function | Impact of DELFOR |
| Procurement | Aligns supplier commitments with forecast demand |
| Manufacturing | Enables capacity and labor planning |
| Logistics | Supports transportation scheduling |
| Inventory Management | Balances stock levels with projected consumption |
Operational Benefits
| Benefit | Description | Business Impact |
| Forward Demand Visibility | Provides time-phased forecasts across defined horizons (weeks/months) | Reduces uncertainty and improves planning accuracy |
| Production Alignment | Enables suppliers to align manufacturing schedules with forecast demand | Minimizes bottlenecks and idle capacity |
| Inventory Optimization | Supports better stock positioning based on projected demand | Reduces stockouts and excess inventory |
| Improved Supplier Coordination | Synchronizes buyer and supplier planning processes | Enhances collaboration and responsiveness |
| Supply chain coordination | Synchronizes supplies with production and deliveries | Improved responsiveness |
| Multi-Location Planning | Supports forecasting by delivery location (LOC) | Improves fulfillment accuracy and routing |
Financial Benefits
| Benefit | Description | Business Impact |
| Trading Partner Compliance | Meets OEM, retail, and industry EDI requirements | Ensures continued partner participation |
| Standardization Across Networks | Uses global EDIFACT standards | Enables interoperability across regions |
| Inventory Stabilization | Reduces excess inventory | Reduces carrying costs |
| Demand Visibility | Improves working capital planning | Reduces capital costs |
| Auditability & Traceability | Links forecasts to contracts and references (RFF, BGM) | Supports governance and accountability |
| Structured Communication | Eliminates ambiguity in demand signals | Reduces disputes and errors |
Strategic Benefits
| Benefit | Description | Business Impact |
| Supports JIT & Lean Operations | Enables just-in-time production models | Reduces inventory and improves flow |
| Enables CPFR Collaboration | Facilitates collaborative planning with partners | Improves forecast accuracy |
| Scales Across Multi-Enterprise Networks | Supports large, distributed supply chains | Enhances global coordination |
| Drives Data-Driven Decision Making | Provides structured demand data | Enables analytics and forecasting improvements |
Compliance Benefits
- Supports trading partner requirements
- Aligns with global EDI standards
What Are the Benefits of Automating the EDIFACT DELFOR?
Automating the EDIFACT DELFOR improves supply chain performance by increasing accuracy, enabling real-time forecast processing, enhancing visibility, and supporting proactive exception management. It allows organizations to scale across trading partners while aligning production, inventory, and logistics with demand.
| Category | Benefit | Business Impact |
| Automation | Eliminates manual forecast processing for faster execution | Increases speed and efficiency |
| Accuracy | Reduces data entry errors | Improves data integrity and forecast reliability |
| Real-Time Visibility | Real-time tracking enables continuous forecast updates | Improves responsiveness |
| Exception Management | Identifies forecast deviations | Enables proactive resolution and better decisions |
| Scalability | Supports large partner ecosystems | Reduces onboarding friction |
What Automation Solves
| Challenge | Without Automation | With Automation |
| Forecast Processing | Manual, slow, error-prone | Fast and standardized |
| Data Consistency | Inconsistent interpretation | Unified logic |
| Forecast Updates | Hard to track | Version-controlled |
| Multi-Partner Scaling | Complex and fragmented | Seamless and scalable |
Operational Benefits of Automation
| Category | Benefit | Description | Business Impact |
| Processing Efficiency | Automated Forecast Ingestion | Eliminates manual entry of forecast schedules | Faster processing and reduced labor costs |
| Data Accuracy | Reduced Human Error | Ensures consistent parsing of LIN, QTY, DTM, and LOC | Improves reliability of planning inputs |
| Speed to Execution | Real-Time Processing | Enables immediate availability of forecast data | Accelerates production and logistics alignment |
| Standardization | Consistent Interpretation | Applies uniform rules to SCC (firm vs forecast) | Prevents misinterpretation across partners |
| Scalability | Multi-Partner Enablement | Supports onboarding and processing across many suppliers | Enables network growth without added complexity |
Visibility & Control Benefits
Category | Benefit | Description | Business Impact |
Forecast Visibility | Time-Phased Demand Views | Provides structured visibility into future demand | Improves planning accuracy |
Exception Detection | Automated Alerts | Identifies forecast spikes, drops, and inconsistencies | Enables proactive issue resolution |
Version Control | Forecast Tracking | Tracks changes across BGM updates (original, replace, cancel) | Prevents duplication and missed updates |
Location Awareness | Multi-Site Visibility | Aligns LOC-based demand across facilities | Improves routing and fulfillment |
Auditability | Traceable Transactions | Maintains history of forecast changes | Supports compliance and governance |
Supply Chain Execution Benefits
Supply Chain Function | Automation Impact |
Procurement | Aligns supplier commitments with real-time demand signals |
Manufacturing | Enables dynamic production scheduling |
Inventory Management | Optimizes stock levels using updated forecasts |
Logistics | Supports synchronized shipment planning |
Financial Benefits
Benefit | Description | Business Impact |
Reduced Inventory Costs | Aligns procurement with actual demand | Improves working capital efficiency |
Lower Expediting Costs | Reduces last-minute shipment changes | Minimizes premium freight expenses |
Improved Cost Forecasting | Enables forward-looking spend visibility | Enhances financial planning |
Reduced Waste | Prevents overproduction | Lowers obsolescence and write-offs |
Partner & Network Benefits
Benefit | Description | Business Impact |
Faster Partner Onboarding | Standardized DELFOR processing across partners | Reduces onboarding time |
Improved Collaboration | Shared visibility into demand forecasts | Enhances coordination |
Interoperability | Supports EDIFACT, X12, and API formats | Enables multi-standard environments |
Consistent Communication | Eliminates ambiguity in forecast interpretation | Reduces disputes and delays |
Advanced Benefits (Execution Control Layer Perspective)
Capability | Description | Outcome |
Canonical Normalization | Converts DELFOR into a unified data model | Eliminates mapping complexity |
Demand Classification | Interprets SCC into firm vs forecast signals | Improves execution accuracy |
Exception Intelligence | Detects forecast anomalies automatically | Enables proactive response |
Multi-Enterprise Visibility | Tracks demand across partner networks | Enhances decision-making |
Hybrid Integration | Supports EDI + API + cloud workflows | Future-proofs supply chain operations |
EDI DELFOR Technical Structure, Format, and Versions
Hierarchical Structure
- Header (UNH → NAD → CTA)
- Detail (LIN → QTY → SCC → DTM)
- Summary (UNT)
File Format and Delimiters
Using the following UNA Service string advice (UNA:+.? ') in the transaction to define the production delimiters on all EDIFACT transmissions sent to Vendors, Carriers, Trading and Solution partners will enable consistent EDI parsing across trading partners:
- UNA1 Component data element separator - 3A (:)
- UNA2 Data element separator - 2B (+)
- UNA3 Decimal notation - 2E (.)
- UNA4 Release indicator - 3F (?)
- UNA5 Reserved for future use - 20 (space)
- UNA6 Segment terminator - 27 (')
Version Differences
Version diversity is a core integration challenge. The most popular EDIFACT DELFOR versions are D96A and D97A, followed by EANCOM Syntax 3 for retail and Odette D.04A for European automotive. Newer UN/EDIFACT versions such as D01B, D00A, and D04A exist but are less widely adopted in production environments.
Manufacturers engaged in Multi-Enterprise Supply Chain Business Networks should expect companion guides which define implementation-specific partner requirements.
Common X12 EDI versions, ranked for convenience include:
| Rank | Version | Primary Usage | Why It Ranks Here |
| 1 | D96A | Automotive, Manufacturing (Global) | Most widely implemented; deeply embedded in OEM ecosystems and legacy EDI infrastructures |
| 2 | D97A | Automotive, Manufacturing | Natural successor to D96A; widely adopted but slightly less dominant |
| 3 | EANCOM® Syntax 3 (based on D96A/D01B) | Retail, Grocery, CPG | Dominant in GS1/EANCOM environments; standardized for retail supply chains |
| 4 | Odette EDIFACT D.04A | European Automotive | Strong adoption among EU OEMs and Tier suppliers; industry-specific dominance |
| 5 | D01B (Syntax 3) | Global (modern EDIFACT) | Used in newer implementations but limited compared to legacy automotive standards |
| 6 | D00A | Transitional / Limited Use | Exists in some implementations but not broadly dominant |
| 7 | D04A (generic UN/EDIFACT) | Modern / niche implementations | Less adopted than Odette-specific D04A; limited production footprint |
Version by Industry (adoption)
Industry | Most Common Version |
Automotive (Global) | D96A / D97A |
Automotive (EU) | Odette D.04A |
Retail / Grocery | EANCOM Syntax 3 |
Manufacturing | D96A / D97A |
Modern / API-Integrated | D01B / D04A |
Industry-specific guidance:
Industry-specific guidance models includes:
- AIAG (American Automobile Industry) EDI Guidelines
- VICS (CPFR) Retail EDI Standards
- VDA (Germany Industry) EDI Guidelines
What Are the Limitations of the EDIFACT DELFOR?
The EDIFACT DELFOR is limited by forecast volatility, complex interpretation, version fragmentation, and its batch-oriented nature. It does not provide real-time updates or standardized reason codes, requiring additional systems and processes to ensure accurate execution and alignment across supply chain partners.
Limitation | Description | Business Impact |
Forecast Volatility | Forecasts change frequently as demand shifts | Requires constant updates and re-planning |
Non-Binding Nature | Forecast quantities (SCC = forecast) are not contractual | Creates uncertainty for suppliers |
Interpretation Complexity | Requires correct pairing of SCC, QTY, DTM, and LOC | Misinterpretation leads to planning errors |
Version Fragmentation | Multiple versions (D96A, D97A, EANCOM, Odette) coexist | Increases integration and mapping complexity |
Limited Standardized Reason Codes | No universal reason codes for changes | Requires custom partner logic |
Batch-Oriented Communication | Typically transmitted on a schedule (not real-time) | Reduces responsiveness to rapid demand changes |
Dependency on Upstream Data Quality | Requires accurate master data (items, locations) | Poor data leads to incorrect forecasts |
Multi-Location Complexity | Forecasts across multiple locations increase complexity | Raises risk of routing and allocation errors |
Technical Limitations
Limitation | Description | Impact |
Rigid Structure | EDIFACT syntax requires strict formatting | Limits flexibility |
Mapping Overhead | Requires transformation across systems (e.g., X12 830) | Increases implementation effort |
Identifier Fragmentation | GLN, DUNS, Odette, internal IDs coexist | Causes identity resolution issues |
Lack of Native Real-Time Support | Designed for batch exchange | Requires API augmentation |
Operational Limitations
Limitation | Description | Impact |
Lag Between Forecast and Execution | Time gap between DELFOR and actual orders | Risk of misalignment |
No Direct Execution Trigger | DELFOR does not initiate fulfillment | Requires downstream transactions (DELJIT, ORDERS) |
Supplier Dependency on Interpretation | Suppliers must interpret forecast intent correctly | Variability across partners |
Exception Handling Outside Standard | Errors and changes handled externally | Requires additional workflows |
Financial & Planning Limitations
Limitation | Description | Impact |
Uncertain Demand Signals | Forecasts may not materialize into orders | Risk of overproduction |
Inventory Risk | Suppliers may build ahead of demand | Increased carrying costs |
Cost Planning Variability | Forecast changes impact budgeting | Financial instability |
Trading Partner & Ecosystem Limitations
Limitation | Description | Impact |
Trading Partner Variability | Each partner may implement DELFOR differently | Requires custom mapping |
Companion Guide Dependency | Implementation depends on partner-specific rules | Reduces standardization |
Onboarding Complexity | Requires setup per partner | Slows network expansion |
Are Implementation Guidelines and Sample Files Available for the DELFOR?
Yes. PartnerLinQ provides sample transactions and implementation guides. EDI DELFOR implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding.
Companion Guides
Trading partners frequently publish DELFOR implementation guidelines defining segment usage and validation rules. Customized specification documents for use in on boarding and technical development are available through PartnerLinQ Support and Guideline Management.
Trading Partner Requirements
Customized mapping, testing, and validation documentation are also available. Partners may specify:
- Specific schedule qualifiers
- Unique product identifiers
- Location codes
- Reporting frequency
- Distribution Model (full publication vs. changes ONLY)
- Identifier use (standards)
- Validation rules
EDI DELFOR Example File (EDIFACT)
What Are the More Common EDI Errors and Rejection Scenarios?
The most common EDIFACT DELFOR errors include missing message envelopes, incorrect segment counts, invalid party qualifiers, missing identifier context, item mismatches, incorrect scheduling logic, invalid date formats, and trading partner compliance violations, all of which can result in message rejection or incorrect forecast execution.
| # | Error Category | Scenario | Root Cause | Business Impact |
| 1 | Structural | Missing UNH/UNT envelope | Incomplete message structure | Immediate rejection |
| 2 | Structural | Segment count mismatch (UNT) | Incorrect segment count | Message validation failure |
| 3 | Mandatory Data | Missing BGM segment | No document identity | Forecast cannot be processed |
| 4 | Party Identification | Incorrect NAD qualifier (3035) | Wrong party role mapping | Misrouting or rejection |
| 5 | Identifier Context | Missing 3055 code list qualifier | Unknown identifier system (GLN, DUNS, Odette) | Partner mismatch |
| 6 | Master Data | Unknown item (LIN) | SKU not synchronized | Forecast rejected |
| 7 | Scheduling Logic | Missing QTY + DTM pairing | Quantity not tied to date | Forecast unusable |
| 8 | Scheduling Logic | Incorrect SCC (firm vs forecast) | Misclassification of demand | Overproduction or shortages |
| 9 | Data Format | Invalid DTM format (not 102) | Incorrect date formatting | Parsing or validation failure |
| 10 | Compliance | Trading partner companion guide violation | Missing required segments or qualifiers | Rejection at partner level |
Top 10 Real-World Rejection Scenarios
- Missing UNH/UNT envelope
- Invalid segment count (UNT)
- Missing BGM (document identity)
- Incorrect NAD qualifiers (3035)
- Missing 3055 code list qualifier
- Unknown item (LIN)
- Missing QTY + DTM pairing
- Incorrect SCC (firm vs forecast)
- Invalid date format (DTM)
- Companion guide violations
Key Validation Rules (Must Enforce)
Rule | Description | Outcome |
Envelope Validation | UNH ↔ UNT consistency | Prevents rejection |
Segment Presence | Mandatory segments required | Ensures completeness |
Data Pairing | QTY must align with DTM | Defines schedule |
Code Validation | Qualifiers must match standards | Prevents misinterpretation |
Identifier Resolution | NAD + 3055 must align | Ensures correct routing |
What Are the Basic Questions for EDI Integration with the EDIFACT DELFOR?
- Are there Samples and Specs available?
- What trading partner requirements apply?
- What version is supported?
- What is the general direction of the transaction?
- Are inbound or outbound orders required?
- Are AS2, VAN, or SFTP connections used?
- Are more than one trading partner exchanging the DELFOR?
- Are there other interested parties?
- What trading partner requirements apply?
- What version is supported?
- What other transactions might these interested parties be a party to?
- What response to the DELFOR is expected or sent?
- Is a response to DELFOR a timed event? Are notifications involved/needed?
- What system generates the response?
- What response time is contractually required?
- Are there samples and specs of the response transaction available?
- Are change orders supported?
- What identifiers are required (GLN, DUNS, Odette)?
- What validation rules apply?
- How are changes to the DELFOR business message managed today?
- Is there automation? (an internal systems trigger) or are DELFOR business message transactions triggered manually?
- How is automation managed (manual vs. system-triggered)?
- Are responses and changes automatically triggered? (an internal systems trigger)
- Are alerting systems configured for missed response deadlines?
- Do transactions require human intervention?
- What systems generate or consume the transaction?
- How are changes to the business message managed today?
- How are one-time addresses handled in ERP?
- Are SKU or UPC identifiers used?
- What identifiers are required (SKU, UPC, GTIN)?
- What testing process is required?
- What validation rules must be applied?
What Are the Best Practices for Using the EDIFACT DELFOR?
| Best Practice | Category | Description | Operational Benefit |
| Synchronize Item & Location Master Data (LIN, NAD, LOC) | Master Data Alignment | Ensure product and location identifiers are consistent across trading partners | Prevents rejections and routing errors |
| Use Correct Code List Qualifiers (3055) | Identifier Governance | Align GLN, DUNS, Odette, or internal IDs with proper qualifiers | Eliminates identity ambiguity and improves partner matching |
| Pair QTY with DTM | Schedule Integrity | Ensure every forecast quantity is tied to a delivery date or time period | Enables actionable demand planning |
| Apply SCC Correctly (Firm vs Forecast) | Schedule Classification | Distinguish committed demand from planned demand using SCC codes | Prevents overproduction or shortages |
| Maintain Clean LIN Loop Structure | Forecast Structure | Organize item → quantity → date → location consistently | Improves parsing and execution accuracy |
| Manage Forecast Lifecycle via BGM (1225) | Version Control | Use original, replace, and cancel codes correctly | Prevents duplication and outdated forecasts |
| Maintain Consistent RFF References | Reference Integrity | Link forecasts to purchase orders, contracts, or agreements | Improves traceability and reconciliation |
| Enforce Structural & Business Validation Rules | Validation & Compliance | Validate UNH/UNT, mandatory segments, qualifiers, and formats | Reduces rejection rates |
| Follow Trading Partner Companion Guides | Partner Compliance | Adhere to partner-specific DELFOR requirements | Ensures successful processing |
| Maintain Consistent Forecast Cadence | Forecast Governance | Send forecasts on a defined schedule (weekly/monthly) | Keeps suppliers aligned with demand |
| Monitor Forecast Changes & Variances | Exception Management | Track updates across forecast versions | Enables proactive issue resolution |
| Use LOC for Accurate Multi-Location Allocation | Distribution Accuracy | Assign demand to correct delivery locations | Improves fulfillment and routing accuracy |
| Normalize DELFOR Across Standards (DELFOR ↔ 830 ↔ API) | Interoperability | Maintain canonical mapping across formats | Enables multi-standard integration |
| Automate Forecast Processing & Validation | Automation | Eliminate manual handling and enforce rules programmatically | Improves speed, accuracy, and scalability |
What Transactions Are Associated with the EDIFACT DELFOR?
| Stage | EDIFACT Transaction ID | EDIFACT Transaction Name | Role in the Workflow | Operational Purpose |
| 1 | PARTIN (NAD, LOC) | Party & Location Identification | Master Data Alignment | Defines trading partners and locations |
| 2 | PRICAT | Product Catalog | Product Master Data | Synchronizes item, pricing, and packaging |
| 3 | INVRPT | Inventory Report | Inventory Visibility | Provides stock levels to inform planning |
| 4 | ORDERS | Purchase Order | Commercial Foundation | Establishes contractual agreement |
| 5 | ORDRSP | Order Response | Commitment Validation | Confirms supplier acceptance |
| 6 | DELFOR | Delivery Forecast | Forecast Planning (Core) | Communicates time-phased demand |
| 7 | DELJIT | Delivery JIT | Execution Scheduling | Converts forecast into short-term delivery instructions |
| 8 | DESADV | Despatch Advice | Shipment Execution | Provides shipment details and visibility |
| 9 | IFTSTA | Transport Status | In-Transit Visibility | Tracks shipment progress |
| 10 | RECADV | Receiving Advice | Receipt Confirmation | Confirms delivery and quantities |
| 11 | INVOIC | Invoice | Financial Settlement | Initiates billing |
| 12 | REMADV | Remittance Advice | Payment Closure | Completes financial reconciliation |
Ordered Transaction Workflow (Unified Cross-Standard View)
EDIFACT DELFOR and EDI 830 operate within the same ordered workflow, beginning with master data and product synchronization, followed by forecast planning, and concluding with execution and financial settlement. The transactions align stage-by-stage, differing only in format while maintaining identical business functions.
| Stage | EDIFACT Transaction ID | X12 ID | X12 Transaction Name | Operational Purpose |
| 1 | PARTIN (NAD, LOC) | 816 | Organizational Relationships | Defines trading partners and locations |
| 2 | PRICAT | 832 | Price/Sales Catalog | Synchronizes item, pricing, and packaging |
| 3 | INVRPT | 846 | Inventory Inquiry/Advice | Provides stock levels to inform planning |
| 4 | ORDERS | 850 | Purchase Order | Establishes contractual agreement |
| 5 | ORDRSP | 855 | Purchase Order Acknowledgment | Confirms supplier acceptance |
| 6 | DELFOR | 830 | Planning Schedule | Communicates time-phased demand |
| 7 | DELJIT | 862 | Shipping Schedule | Converts forecast into short-term delivery instructions |
| 8 | DESADV | 856 | Advance Ship Notice | Provides shipment details and visibility |
| 9 | IFTSTA | 214 | Transportation Status | Tracks shipment progress |
| 10 | RECADV | 861 | Receiving Advice | Confirms delivery and quantities |
| 11 | INVOIC | 810 | Invoice | Initiates billing |
| 12 | REMADV | 820 | Payment/Remittance Advice | Completes financial reconciliation |
Common Questions About EDIFACT DELFOR
What is the difference between DELFOR and DELJIT?
The EDIFACT DELFOR provides long-term, time-phased delivery forecasts used for planning, while DELJIT delivers short-term, detailed just-in-time (JIT) instructions for execution. DELFOR supports production and inventory planning, whereas DELJIT translates forecast demand into precise delivery schedules for immediate fulfillment.
Is DELFOR the same as EDI 830?
Yes, EDIFACT DELFOR and X12 EDI 830 serve the same business function—communicating forecast demand from buyers to suppliers. The difference lies in format: DELFOR uses EDIFACT syntax (e.g., SCC, QTY, DTM), while EDI 830 uses X12 structures (e.g., FST, BFR), but both represent the same planning process.
What segments are used in DELFOR?
The EDIFACT DELFOR uses segments such as UNH (message header), BGM (document identity), DTM (dates), RFF (references), NAD (parties), LIN (items), QTY (quantities), SCC (schedule conditions), LOC (locations), and UNT (message trailer) to define time-phased forecast demand across items, locations, and delivery schedules.
What is SCC in DELFOR?
The SCC (Scheduling Conditions) segment in DELFOR defines how forecast quantities should be interpreted, distinguishing between firm demand (committed) and forecast demand (planned). SCC is critical for execution, as it determines whether suppliers must fulfill demand immediately or treat it as a planning signal.
FAQs
What is EDIFACT DELFOR?
EDIFACT DELFOR is a delivery forecast message used to communicate time-phased demand from buyer to supplier.
What is DELFOR used for?
It is used for production planning, inventory management, and logistics coordination.
Who sends DELFOR?
Typically, the DELFOR is sent by buyers, OEMs, or retailers, the DELFOR message is most commonly used in Automotive (e.g., just-in-time (JIT) production), Retail & Consumer Goods (seasonal planning and replenishment), Manufacturing & Industrial (e.g., material requirements planning (MRP), and in Grocery & Foodservice (managing perishables and distribution).
When is DELFOR sent?
Typically, daily, weekly, or monthly on a rolling forecast basis.
Related Resources
Explore Our Integration Solutions
PartnerLinQ Integration Solutions
Connect Everything. Integrate Intelligently.
Future-Proof Your Business with Composable, AI Powered Connectivity.