The confusion that costs manufacturers money
DELFOR and DELJIT are the two EDIFACT messages at the heart of automotive supply chain management. They are related, they arrive from the same customer, and they both contain delivery information. But they serve completely different purposes, operate on different time horizons, and trigger different actions in your production system.
Getting them confused — or treating DELJIT as simply a more detailed DELFOR — is one of the most common mistakes in automotive EDI implementations. The consequences range from missed deliveries to penalty clauses.
DELFOR: the rolling forecast
DELFOR (Delivery Schedule / Delivery Forecast) is the long-range planning signal. An OEM sends DELFOR messages to its suppliers on a regular cadence — typically weekly — covering a rolling horizon of 4 to 26 weeks depending on the customer and commodity.
DELFOR tells you: over the coming weeks and months, this is approximately how much of your product we expect to need. It is a forecast. The quantities are indicative and will change. The purpose is to give you enough visibility to plan your material procurement, production capacity, and staffing.
Key characteristics:
- Sent weekly (or sometimes daily for fast-moving lines)
- Covers a rolling 4–26 week horizon
- Quantities are not firm commitments — they will be revised
- Used for capacity planning and material procurement
- Does not trigger a shipment
DELJIT: the firm call-off
DELJIT (Delivery Just In Time) is the firm delivery instruction. It tells you exactly what to ship, in what quantity, to which dock, at what time — typically within a 24 to 72 hour window. DELJIT quantities are commitments. When you receive a DELJIT, you ship against it.
Key characteristics:
- Sent daily or multiple times per day
- Covers a short horizon — typically 24 to 72 hours
- Quantities are firm — deviation triggers a discrepancy
- Specifies exact delivery time window and dock location
- Triggers production pick and shipment
- Must be responded to with a DESADV (shipping notice)
Why they must both feed your production system differently
The operational failure mode is when a manufacturer's ERP or production scheduling system treats DELFOR and DELJIT as the same type of message.
If your system creates production orders from DELFOR quantities, you will produce against forecasts that change weekly and end up with wrong inventory. If your system only processes DELJIT and ignores DELFOR, you will not have enough material visibility to plan procurement — and you will run out of components.
The correct architecture:
- DELFOR feeds your MRP run — it is the demand signal that drives material requirements planning, supplier orders for your own components, and capacity reservations
- DELJIT creates pick and ship instructions — it is the execution signal that drives warehouse picking, production final assembly, and transport scheduling
The penalty clause trigger
Most automotive supply contracts contain penalty clauses for late or short delivery. The clock starts when the OEM sends the DELJIT. If your system does not process DELJIT in near-real-time — or if there is a mapping error that causes DELJIT messages to be misclassified or delayed — you can be in breach of your delivery commitment before anyone in your organisation knows about it.
This is not a hypothetical. We have seen manufacturers receive penalty invoices from OEM customers for late deliveries that were, on investigation, caused by DELJIT messages sitting unprocessed in a queue for hours due to an integration issue.
Tolerance windows and rounding rules
Both DELFOR and DELJIT carry tolerance information — the acceptable range of delivery quantity that the OEM will accept without raising a discrepancy. These tolerances need to be reflected in your integration mapping and, in most cases, in your SAP scheduling agreement configuration.
The tolerances are not standard — they vary by OEM, by commodity, and sometimes by individual part number. They need to be negotiated during the trading partner onboarding process and maintained in your system as master data.
The implementation checklist
Before going live with DELFOR/DELJIT:
- Confirm your MRP run is configured to consume DELFOR quantities correctly
- Confirm your scheduling agreement tolerance windows match the OEM's requirements
- Build and test the DELJIT-to-pick instruction workflow end to end
- Test the DESADV response to DELJIT — the OEM's system expects a DESADV confirming shipment
- Agree the escalation process for DELJIT messages that cannot be fulfilled
- Confirm monitoring is in place to alert on unprocessed messages within your agreed SLA window
Related articles
For the foundational concepts behind EDIFACT message types, read our plain-language EDIFACT guide.
If your automotive EDI runs on SAP scheduling agreements, our EDIFACT and SAP integration guide covers DELFOR and DELJIT tolerance windows in detail.
Implementing automotive EDI for the first time? Read our vendor evaluation checklist before choosing a partner. Or speak to our team directly — we have delivered DELFOR/DELJIT implementations for Bulgarian Tier 1 automotive suppliers.