Skip to content
EDI DELJIT — EDI TransactionPublished Nov 7, 2026

EDIFACT DELJIT: Just-in-Time Call-Offs

EDIFACT DELJIT explained: JIT and JIS call-offs, the SEQ group, Global DELJIT on D.04B, VDA 4915, 4985 and 4986, two full examples and the X12 862 map.

DELJIT is the call-off a supplier ships to, hour by hour. DELFOR tells you what to plan for the coming weeks. DELJIT tells you what the line needs tomorrow morning at 06:00, at which dock and line station, and sometimes in which order, vehicle by vehicle. Read it wrong and the result is not a planning error but a stopped assembly line.

This guide covers what DELJIT carries, how it relates to DELFOR, the directories and guidelines you will meet (Global DELJIT on D.04B, VDA 4985 and 4986), a just-in-time example, a sequenced example, the segments you will map, and how DELJIT compares with the EDI 862 shipping schedule.

What Is an EDIFACT DELJIT?

DELJIT is the UN/EDIFACT Delivery just in time message: it "provides the ability for a customer to convey precise delivery sequence and Just In Time schedule requirements to a supplier, and is intended to supplement the Delivery Schedule Message (DELFOR)." That definition, from the UN/EDIFACT directory, is the key to using it: DELJIT does not replace the plan in DELFOR. It narrows the near-term part of it to exact times, places and sequences.

Authoritative references for DELJIT work:

Who sends it? The customer's plant, usually from its production control or line-feeding system rather than central planning.

When is it sent? Much more often than DELFOR: daily, several times a day, or per sequence event. Volvo's guide, for example, describes sequence information sent once a day, 7 to 23 days before assembly depending on the plant.

Why does it matter? It is the instruction the line actually runs on. A missed or misread DELJIT means premium freight at best and a line stoppage at worst.

Directories and Guidelines

DELJIT is a UN/EDIFACT message but it is not part of the GS1 EANCOM subset, so retail suppliers rarely meet it. Automotive suppliers do, under these guidelines:

GuidelineDirectoryUsed for
Odette Global DELJITD.04BJIT, KANBAN and sequenced call-offs; SEG Automotive and Volvo publish profiles of it
VDA 4985EDIFACT DELJITJIT call-offs in German automotive, replacing part of VDA 4915
VDA 4986EDIFACT DELJITJIS (production-synchronous) call-offs, replacing VDA 4916
Older OEM profilesD.96A, D.97A and othersCustomer-specific implementations still in use

The examples in this guide use D.04B, because that is the directory of the published Global DELJIT guidelines we checked. The D.96A and D.04B layouts share the same backbone (SEQ group, then LIN group, then QTY and DTM), so the reading is the same; D.04B adds a transport group and a price group under each line.

The VDA list is clear that the old flat files have not gone away: it marks VDA 4915 and 4916 as replaced but still widely used. During a migration you may receive a VDA 4915 call-off and a DELJIT for the same parts, so agree with the customer which one you ship to.

JIT, KANBAN and JIS: Three Ways DELJIT Is Used

FlowWhat the call-off saysHow DELJIT shows it
JIT call-offDeliver these quantities at these timesOne SEQ group with LIN lines, each with QTY and DTM pairs
KANBANReplenish what the line consumedSame shape, often triggered per card or bin; SEG Automotive's guide covers it in the same profile
JIS (sequenced)Deliver one part per vehicle, in build orderOne SEQ group per vehicle or sequence position, with the vehicle identifier in GIR

The X12 world splits these between the 862 shipping schedule for timed call-offs and the 866 production sequence for build order. In EDIFACT both run through DELJIT.

Example 1: JIT Call-Off for Two Parts

The fictional axle plant Northbrook Axle calls off two cast parts from the fictional foundry Kestrel Castings for delivery on Thursday 12 November, in three-shift slots, against the DELFOR schedule it sent the previous week.

Live exampleEDIFACT DELJITGlobal DELJIT D.04B (Odette profile)

JIT call-off for two parts, three delivery slots

One SEQ group for unloading point D07; each LIN carries its DELFOR reference, line station and QTY+113 / DTM+2 pairs for each delivery time.

Structurally valid UN/EDIFACT
UN/EDIFACT · DELJIT · D:04B:UN · 30 segments · 1 message

DELJIT · Delivery just in time · ref 1

Document
242
Document number
NB-JIT-0005521
Message function
Original
Document/message date/time
2026-11-10 14:05

Parties

RoleIdentifierName and address
Buyer BY0410Assigned by buyer-
SE SE4471Assigned by buyer-
Ship to ST0410Assigned by buyer-

Lines (2)

#GTINCodesDescriptionQuantity to be deliveredPriceAmount
-
Supplier: KC-88120
Buyer: 7731-220-04
-240--
-
Supplier: KC-88135
Buyer: 7731-221-02
-180--

Interchange (UNB)

Sender
NBAXLE0410Mutually defined
Recipient
KESTRELCASTMutually defined
Prepared
2026-11-10 14:05
Control reference
NBJ0005521
Syntax
UNOC version 3
Messages
1
SegmentWhat it says
BGM+242+NB-JIT-0005521+9'Delivery just-in-time (242), call-off number NB-JIT-0005521, original
DTM+137:202611101405:203'Issued 10 November at 14:05
NAD+BY / SE / STBuyer, seller and ship-to plant, by codes the buyer assigned
SEQ+40'Opens the delivery instruction group. In SEG Automotive's KANBAN and JIT profile, SEQ is a trigger with code 40
LOC+7+D07::92'Place of delivery: unloading point D07
LIN / PIAThe buyer's part number (IN) and the supplier's (SA)
RFF+AAN:NB-DF-261106-01'The delivery schedule (DELFOR) this call-off belongs to
LOC+159+L2-STA14::92'Additional internal destination: line 2, station 14
QTY+113 / DTM+2240 to be delivered at 06:00, 14:00 and 22:00; 180 of the second part at 06:00 and 14:00

Times are in format 203 (CCYYMMDDHHMM). Whether DTM+2 means arrival at the dock or at the line station is set by the customer's guide, so confirm it before you plan transport.

Example 2: Sequenced (JIS) Call-Off

For a sequenced part, the plant sends one SEQ group per vehicle in build order. Each group carries the sequence number, the planned time, the vehicle identifier and the one variant that vehicle needs. This example follows the shape of Volvo Group's published Global DELJIT sequence examples, with fictional codes.

Live exampleEDIFACT DELJITGlobal DELJIT D.04B (Odette profile)

Sequenced call-off, one part per vehicle

Three SEQ groups in build order, each with a sequence number, start time, vehicle identifier in GIR and the variant that vehicle needs.

Structurally valid UN/EDIFACT
UN/EDIFACT · DELJIT · D:04B:UN · 31 segments · 1 message

DELJIT · Delivery just in time · ref 1

Document
307
Document number
NB-JIS-0005530
Message function
Original
Document/message date/time
2026-11-11 21:30
Date (194)
2026-11-18 06:40

Parties

RoleIdentifierName and address
Buyer BY0410Assigned by buyer-
SE SE4471Assigned by buyer-
Ship to ST0410Assigned by buyer-

Lines (3)

#GTINCodesDescriptionQuantity to be deliveredPriceAmount
-
Buyer: 7731-305-11
-1--
-
Buyer: 7731-305-14
-1--
-
Buyer: 7731-305-11
-1--

Interchange (UNB)

Sender
NBAXLE0410Mutually defined
Recipient
KESTRELCASTMutually defined
Prepared
2026-11-11 21:30
Control reference
NBJ0005530
Syntax
UNOC version 3
Messages
1
SegmentWhat it says
BGM+307+...'Sequenced delivery schedule (307), the code Volvo's sequence profile uses
SEQ+39+004417'Action code 39 (new) and sequence number 004417
DTM+194:202611180640:203'Start date/time for this sequence position: 18 November at 06:40
GIR+4+NB26-0044171:VV'The vehicle this part is for, in the identifier format the OEM's guide defines
LINThe variant needed: 7731-305-11 for the first and third vehicles, 7731-305-14 for the second
LOC+11 / LOC+159Unloading point and line station
QTY+113:1'One part per vehicle

You load the parts in sequence-number order, so the rack or trailer arrives with the variants in the order the line builds the vehicles. Volvo's guide lists the action codes it uses in SEQ: 39 new (preliminary), 40 agreed (firm), 38 replaced and 2 deleted. Other OEMs choose differently, so load the code list from your customer's guide.

DELJIT Structure at a Glance (D.04B)

AreaSegment or groupStatusWhat it holds
HeaderUNHMMessage reference and type
HeaderBGMMDocument code (242, or a sequence code), number, function
HeaderDTMMMessage date and time
HeaderFTXCFree text
HeaderRFF group (SG1)CReferences for the whole message
HeaderNAD group (SG2)CBuyer, seller, ship-to, with LOC and contacts
DetailSEQ group (SG4)MOne delivery instruction or sequence position: DTM, GIR, LOC
DetailPAC group (SG5)CPackaging, with PCI and GIN identification
DetailLIN group (SG7)COne part: PIA, IMD, ALI, GIR, FTX, PAC, DTM
DetailRFF group (SG8)CReferences for the line, such as the DELFOR number
DetailTDT group (SG9)CTransport for the line
DetailLOC group (SG10)CDelivery locations for the line
DetailQTY group (SG12)CQuantity, SCC and DTM
DetailPRI group (SG14)CPrice details
TrailerUNTMSegment count and message reference

There is no UNS and no CNT in DELJIT. The SEQ group is the only mandatory group in the detail.

Key Segments Explained

BGM: Beginning of Message

BGM+242+NB-JIT-0005521+9'
ElementNameExampleNotes
1001Document name code242Delivery just-in-time. 307 (sequenced delivery schedule) is also defined and used in Volvo's sequence profile
1004Document identifierNB-JIT-0005521The call-off number; quote it on your DESADV if the customer asks
1225Message function code9Original

SEQ: Sequence Details

SEQ+39+004417'
ElementNameNotes
1229Action request/notification description codeWhat to do with this group. The D.04B code list includes 39 new, 40 agreed, 38 replaced and 2 deleted
C286Sequence informationThe sequence number, used in sequenced flows; left out in simple JIT call-offs

QTY and DTM: What, and When

QTY+113:240'
DTM+2:202611120600:203'

QTY+113 is the quantity to be delivered. Each QTY is followed by its own DTM, so read them as pairs: the time belongs to the quantity directly before it. DTM+2 is the requested delivery date and time; DTM+194 is used for the start time of a sequence position. Some profiles add SCC between QTY and DTM to mark a quantity as firm or planned.

LOC: Where on the Customer's Site

LOC+7+D07::92'
LOC+159+L2-STA14::92'
Qualifier (3227)Meaning
7Place of delivery
11Place of discharge (unloading point)
159Additional internal destination, such as a line station
54Manufacturing department

Print the same location codes on your transport label as the call-off gives. The plant's receiving staff route parts by them.

GIR: Related Identification Numbers

GIR+4+NB26-0044171:VV'

In sequenced flows GIR carries the vehicle or build identifier that ties each part to one vehicle. The qualifier codes and the format of the identifier come from the OEM's guide, so map them from there rather than from this example.

DELJIT vs the X12 862 and 866

DataEDIFACT DELJITX12 862X12 866
PurposeJIT and sequenced call-offsNear-term ship or delivery scheduleOrder in which parts must arrive
Beginning segmentBGM (242 or a sequence code)BSSBSS
Plan it supplementsDELFOR830830 or 862
Delivery quantityQTY+113SHP and FSTQTY per sequence
Delivery timeDTM+2 with timeFST dates and JIT segmentsDTM per sequence
Sequence or vehicleSEQ and GIRNot usedThe sequence and vehicle references
Location on siteLOC+7, LOC+11, LOC+159N1 and REF per partnerN1 and REF per partner
Trailer countUNTSESE

One EDIFACT message covers the work of two X12 sets. If a customer moves you from 862s to DELJIT, expect the sequenced parts to arrive in the same message type as the timed ones, told apart by the BGM code and the SEQ content.

Where DELJIT Sits in the Flow

StepMessageDirectionX12 equivalent
1DELFORBuyer to supplier830
2DELJITBuyer to supplier862 or 866
3DESADV, at each shipmentSupplier to buyer856
4Self-billing by the buyer, or your INVOICEither810

The EDI 830 vs 862 article explains the plan-versus-call-off split in X12 terms, and the same logic holds here: DELFOR is the authority for what to buy and staff for, DELJIT for what leaves the dock today.

Common DELJIT Errors and How to Prevent Them

ProblemWhat happensPrevention
DELJIT quantities added to DELFOR demandDemand counted twice in MRPLet DELJIT consume the matching DELFOR window, using the RFF+AAN link
Time read as dispatch instead of arrivalParts arrive early or late by the transit timeConfirm in the partner's guide what DTM+2 means
Sequence loaded out of orderWrong variant at the lineLoad by sequence number, scan each part against the sequence at loading
Replaced or deleted sequences ignoredParts built for vehicles that changedProcess SEQ action codes for replace and delete, not only new
Unknown location codesReceiving cannot route the partsKeep the plant's dock and station codes in your master data and alert on new ones
Old VDA call-off and DELJIT both loadedDouble shipments during migrationAgree one authoritative source per part

DELJIT Implementation Checklist

  1. Get the partner's profile. Directory, Global DELJIT or VDA basis, and which flows it covers (JIT, KANBAN, JIS).
  2. Map the BGM codes the partner uses and what each means for your planning.
  3. Map SEQ action codes, including replace and delete.
  4. Agree what the delivery time means: arrival at the dock, at the line, or dispatch from your site.
  5. Load location codes for docks and line stations.
  6. Link each call-off to its DELFOR with RFF+AAN so the two do not double count.
  7. Set up labels and DESADV to carry the call-off and sequence references the plant expects.
  8. Test with real call-offs, including a changed sequence, a deleted sequence and a call-off sent late in the day.

Reading DELJIT With OrderSync

DELJIT is a scheduling message. The orders the rest of your business takes in, as EDI 850s, PDFs, emails and spreadsheets, still need someone to key them. OrderSync reads those inbound orders in any format, matches customers, items and units to your catalog, and outputs clean ERP data or valid X12, and it generates the outbound 856 ship notice and 810 invoice your US customers expect.

Paste any DELJIT into the free EDIFACT inspector to see it parsed segment by segment, use the free EDI inspector for X12 862s and 866s, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions

What is the X12 equivalent of DELJIT?

The 862 shipping schedule for timed call-offs, and the 866 production sequence for build-order deliveries. DELJIT covers both jobs in one EDIFACT message, and DELFOR plays the part of the 830.

What is the difference between DELFOR and DELJIT?

DELFOR is the rolling plan: firm and forecast quantities over weeks or months, with material and production authorisations. DELJIT supplements it with exact delivery times, places and sequences for the next hours or days. The UN definition says DELJIT is intended to supplement DELFOR.

What does BGM+242 mean?

242 is the UN/EDIFACT document code for a delivery just-in-time. The second element is the call-off number and the third is the message function, usually 9 for an original.

What does the SEQ segment do in DELJIT?

SEQ opens each delivery instruction group and is mandatory. Its action code says whether the group is new, agreed, replaced or deleted, and in sequenced flows it also carries the sequence number. In simple JIT profiles it can be a plain trigger, such as SEQ+40'.

What is VDA 4985?

VDA 4985 is the German automotive association's recommendation for JIT call-offs in EDIFACT DELJIT. Together with VDA 4984 for DELFOR, it replaces the VDA 4915 flat file, which the VDA notes is still widely used. VDA 4986 does the same for sequenced (JIS) call-offs.

Is DELJIT part of EANCOM?

No. DELJIT is a UN/EDIFACT message but not part of the GS1 EANCOM subset, so retail suppliers rarely see it. Automotive suppliers receive it under Odette and VDA guidelines.

Which directory does DELJIT use?

The Global DELJIT guidelines published by SEG Automotive and Volvo use D.04B. Older OEM profiles use D.96A or other directories. The version in UNH tells you which one you are reading.

Related guides

Sources

Check any DELJIT or DELFOR in the free EDIFACT inspector.

James Darby
Last updated: 11/7/2026

Related Resources