# 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.

<QuickAnswer>
EDIFACT DELJIT is the delivery just-in-time message, the counterpart of the X12 862. A manufacturing plant sends it to a supplier to call off exact quantities for exact delivery times, or parts in build sequence, against the longer plan already sent in DELFOR. In automotive it follows the Odette Global DELJIT and VDA 4985 and 4986 guidelines.
</QuickAnswer>

**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](/guides/edi/862-shipping-schedule).

<EDIGuideCTA
  badge="For EDIFACT DELJIT"
  transactionType="DELJIT"
  headline="Check a DELJIT call-off before the truck is loaded"
  body="Paste a DELJIT into the free EDIFACT inspector to see each sequence, part, quantity and delivery time, with UNT and UNZ counts checked. For the orders that arrive outside your schedules, as EDI 850s, PDFs, emails or spreadsheets, OrderSync matches customers, items and units and sends clean data to your ERP."
  secondaryHref="/edifact-inspector"
  secondaryLabel="Try the free EDIFACT inspector"
/>

## 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](/guides/edi/edifact-delfor). It narrows the near-term part of it to exact times, places and sequences.

Authoritative references for DELJIT work:

- The [UN/EDIFACT D.96A DELJIT message](https://service.unece.org/trade/untdid/d96a/trmd/deljit_c.htm) from UNECE gives the definition and segment table, and the [D.04B layout on EDIFACTORY](https://www.edifactory.de/edifact/directory/D04B/message/DELJIT) shows the directory the Global DELJIT uses
- The [VDA list of EDI recommendations](https://vda.de/dam/jcr:0f97444c-dc98-4216-8b5d-51ff7a3e9258/ListeDer%20EmpfehlungenEDIundWarenbegleitendePapiere-2024-08.pdf) (August 2024) records VDA 4985 (JIT call-offs with DELJIT) and VDA 4986 (JIS call-offs with DELJIT) as the replacements for the VDA 4915 and 4916 flat files
- Supplier-published guides such as [SEG Automotive's Global DELJIT D.04B guideline](https://www.seg-automotive.com/file/editorial-content/purchasing-documents/jit-delivery-instruction_deljitd04b_en.pdf) and [Volvo Group's DELJIT D.04B guidelines](https://www.edi.volvogroup.com/content/dam/volvo-group/markets/edi/specifications-and-guidelines/jit-jis/volvo-deljit-d04b-implementation-guideline.pdf) show complete messages for KANBAN, JIT and sequenced flows

**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:

| Guideline | Directory | Used for |
|---|---|---|
| Odette Global DELJIT | D.04B | JIT, KANBAN and sequenced call-offs; SEG Automotive and Volvo publish profiles of it |
| VDA 4985 | EDIFACT DELJIT | JIT call-offs in German automotive, replacing part of VDA 4915 |
| VDA 4986 | EDIFACT DELJIT | JIS (production-synchronous) call-offs, replacing VDA 4916 |
| Older OEM profiles | D.96A, D.97A and others | Customer-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

| Flow | What the call-off says | How DELJIT shows it |
|---|---|---|
| JIT call-off | Deliver these quantities at these times | One `SEQ` group with `LIN` lines, each with `QTY` and `DTM` pairs |
| KANBAN | Replenish what the line consumed | Same 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 order | One `SEQ` group per vehicle or sequence position, with the vehicle identifier in `GIR` |

The X12 world splits these between the [862 shipping schedule](/guides/edi/862-shipping-schedule) for timed call-offs and the [866 production sequence](/guides/edi/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.

<EdifactSample
  title="JIT call-off for two parts, three delivery slots"
  description="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."
  label="Global DELJIT D.04B (Odette profile)"
  raw="UNA:+.? '
UNB+UNOC:3+NBAXLE0410:ZZZ+KESTRELCAST:ZZZ+261110:1405+NBJ0005521++DELJIT'
UNH+1+DELJIT:D:04B:UN'
BGM+242+NB-JIT-0005521+9'
DTM+137:202611101405:203'
NAD+BY+0410::92'
NAD+SE+4471::92'
NAD+ST+0410::92'
SEQ+40'
LOC+7+D07::92'
LIN+++7731-220-04:IN'
PIA+1+KC-88120:SA'
RFF+AAN:NB-DF-261106-01'
LOC+159+L2-STA14::92'
QTY+113:240'
DTM+2:202611120600:203'
QTY+113:240'
DTM+2:202611121400:203'
QTY+113:240'
DTM+2:202611122200:203'
LIN+++7731-221-02:IN'
PIA+1+KC-88135:SA'
RFF+AAN:NB-DF-261106-01'
LOC+159+L2-STA16::92'
QTY+113:180'
DTM+2:202611120600:203'
QTY+113:180'
DTM+2:202611121400:203'
UNT+27+1'
UNZ+1+NBJ0005521'"
/>

| Segment | What 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` / `ST` | Buyer, 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` / `PIA` | The 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+2` | 240 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.

<EdifactSample
  title="Sequenced call-off, one part per vehicle"
  description="Three SEQ groups in build order, each with a sequence number, start time, vehicle identifier in GIR and the variant that vehicle needs."
  label="Global DELJIT D.04B (Odette profile)"
  raw="UNA:+.? '
UNB+UNOC:3+NBAXLE0410:ZZZ+KESTRELCAST:ZZZ+261111:2130+NBJ0005530++DELJIT'
UNH+1+DELJIT:D:04B:UN'
BGM+307+NB-JIS-0005530+9'
DTM+137:202611112130:203'
NAD+BY+0410::92'
NAD+SE+4471::92'
NAD+ST+0410::92'
SEQ+39+004417'
DTM+194:202611180640:203'
GIR+4+NB26-0044171:VV'
LIN+++7731-305-11:IN'
LOC+11+D07::92'
LOC+159+L2-STA22::92'
QTY+113:1'
SEQ+39+004418'
DTM+194:202611180644:203'
GIR+4+NB26-0044182:VV'
LIN+++7731-305-14:IN'
LOC+11+D07::92'
LOC+159+L2-STA22::92'
QTY+113:1'
SEQ+39+004419'
DTM+194:202611180648:203'
GIR+4+NB26-0044193:VV'
LIN+++7731-305-11:IN'
LOC+11+D07::92'
LOC+159+L2-STA22::92'
QTY+113:1'
UNT+28+1'
UNZ+1+NBJ0005530'"
/>

| Segment | What 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 |
| `LIN` | The variant needed: 7731-305-11 for the first and third vehicles, 7731-305-14 for the second |
| `LOC+11` / `LOC+159` | Unloading 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)

| Area | Segment or group | Status | What it holds |
|---|---|---|---|
| Header | `UNH` | M | Message reference and type |
| Header | `BGM` | M | Document code (`242`, or a sequence code), number, function |
| Header | `DTM` | M | Message date and time |
| Header | `FTX` | C | Free text |
| Header | `RFF` group (SG1) | C | References for the whole message |
| Header | `NAD` group (SG2) | C | Buyer, seller, ship-to, with `LOC` and contacts |
| Detail | `SEQ` group (SG4) | M | One delivery instruction or sequence position: `DTM`, `GIR`, `LOC` |
| Detail | `PAC` group (SG5) | C | Packaging, with `PCI` and `GIN` identification |
| Detail | `LIN` group (SG7) | C | One part: `PIA`, `IMD`, `ALI`, `GIR`, `FTX`, `PAC`, `DTM` |
| Detail | `RFF` group (SG8) | C | References for the line, such as the DELFOR number |
| Detail | `TDT` group (SG9) | C | Transport for the line |
| Detail | `LOC` group (SG10) | C | Delivery locations for the line |
| Detail | `QTY` group (SG12) | C | Quantity, `SCC` and `DTM` |
| Detail | `PRI` group (SG14) | C | Price details |
| Trailer | `UNT` | M | Segment 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'
```

| Element | Name | Example | Notes |
|---|---|---|---|
| 1001 | Document name code | `242` | Delivery just-in-time. `307` (sequenced delivery schedule) is also defined and used in Volvo's sequence profile |
| 1004 | Document identifier | `NB-JIT-0005521` | The call-off number; quote it on your DESADV if the customer asks |
| 1225 | Message function code | `9` | Original |

### SEQ: Sequence Details

```
SEQ+39+004417'
```

| Element | Name | Notes |
|---|---|---|
| 1229 | Action request/notification description code | What to do with this group. The D.04B code list includes `39` new, `40` agreed, `38` replaced and `2` deleted |
| C286 | Sequence information | The 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 |
|---|---|
| `7` | Place of delivery |
| `11` | Place of discharge (unloading point) |
| `159` | Additional internal destination, such as a line station |
| `54` | Manufacturing 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

| Data | EDIFACT DELJIT | X12 862 | X12 866 |
|---|---|---|---|
| Purpose | JIT and sequenced call-offs | Near-term ship or delivery schedule | Order in which parts must arrive |
| Beginning segment | `BGM` (`242` or a sequence code) | `BSS` | `BSS` |
| Plan it supplements | DELFOR | 830 | 830 or 862 |
| Delivery quantity | `QTY+113` | `SHP` and `FST` | `QTY` per sequence |
| Delivery time | `DTM+2` with time | `FST` dates and `JIT` segments | `DTM` per sequence |
| Sequence or vehicle | `SEQ` and `GIR` | Not used | The sequence and vehicle references |
| Location on site | `LOC+7`, `LOC+11`, `LOC+159` | `N1` and `REF` per partner | `N1` and `REF` per partner |
| Trailer count | `UNT` | `SE` | `SE` |

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

| Step | Message | Direction | X12 equivalent |
|---|---|---|---|
| 1 | [DELFOR](/guides/edi/edifact-delfor) | Buyer to supplier | [830](/guides/edi/830-planning-schedule) |
| 2 | **DELJIT** | Buyer to supplier | [862](/guides/edi/862-shipping-schedule) or [866](/guides/edi/866-production-sequence) |
| 3 | [DESADV](/guides/edi/edifact-desadv), at each shipment | Supplier to buyer | [856](/guides/edi/856-ship-notice) |
| 4 | Self-billing by the buyer, or your [INVOIC](/guides/edi/edifact-invoic) | Either | [810](/guides/edi/810-invoice) |

The [EDI 830 vs 862](/blog/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

| Problem | What happens | Prevention |
|---|---|---|
| DELJIT quantities added to DELFOR demand | Demand counted twice in MRP | Let DELJIT consume the matching DELFOR window, using the `RFF+AAN` link |
| Time read as dispatch instead of arrival | Parts arrive early or late by the transit time | Confirm in the partner's guide what `DTM+2` means |
| Sequence loaded out of order | Wrong variant at the line | Load by sequence number, scan each part against the sequence at loading |
| Replaced or deleted sequences ignored | Parts built for vehicles that changed | Process `SEQ` action codes for replace and delete, not only new |
| Unknown location codes | Receiving cannot route the parts | Keep the plant's dock and station codes in your master data and alert on new ones |
| Old VDA call-off and DELJIT both loaded | Double shipments during migration | Agree 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](/edifact-inspector) to see it parsed segment by segment, use the [free EDI inspector](/edi-inspector) for X12 862s and 866s, or [book a 15-minute walkthrough](/book-call) to see your own orders processed.

## Frequently Asked Questions

<div className="not-prose">

### 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.

</div>

## Related guides

- **[EDIFACT DELFOR](/guides/edi/edifact-delfor)**: the delivery schedule DELJIT supplements
- **[EDI 862 shipping schedule](/guides/edi/862-shipping-schedule)** and **[EDI 866 production sequence](/guides/edi/866-production-sequence)**: the X12 counterparts
- **[EDI 830 planning schedule](/guides/edi/830-planning-schedule)**: the X12 plan
- **[EDIFACT DESADV](/guides/edi/edifact-desadv)**: the despatch advice for each delivery
- **[EDIFACT explained](/guides/edi/edifact)** and **[EDIFACT message types](/guides/edi/edifact-message-types)**: syntax and the full catalogue

## Sources

- [UN/EDIFACT D.96A DELJIT message](https://service.unece.org/trade/untdid/d96a/trmd/deljit_c.htm), UNECE: definition and structure
- [DELJIT in directory D.04B](https://www.edifactory.de/edifact/directory/D04B/message/DELJIT), EDIFACTORY: D.04B segment groups
- [Liste der Empfehlungen: EDI und warenbegleitende Papiere](https://vda.de/dam/jcr:0f97444c-dc98-4216-8b5d-51ff7a3e9258/ListeDer%20EmpfehlungenEDIundWarenbegleitendePapiere-2024-08.pdf), VDA, August 2024: VDA 4915, 4916, 4984, 4985 and 4986
- [Global DELJIT D.04B JIT delivery instruction](https://www.seg-automotive.com/file/editorial-content/purchasing-documents/jit-delivery-instruction_deljitd04b_en.pdf), SEG Automotive: Odette-based JIT and KANBAN profile
- [Volvo Group DELJIT D.04B guidelines and examples](https://www.edi.volvogroup.com/content/dam/volvo-group/markets/edi/specifications-and-guidelines/jit-jis/volvo-deljit-d04b-implementation-guideline.pdf), Volvo Group: sequence profiles and SEQ action codes
- [Ordering message guidelines](https://www.odette.org/process/ordering), Odette

Check any DELJIT or DELFOR in the free [EDIFACT inspector](/edifact-inspector).