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 · Shipping and logistics

INSDES Instruction to despatch

The UN/EDIFACT message that instructs a party controlling ordered goods to despatch them or put them on hold.

Sent by
Owner of the goods, buyer or seller
Received by
Warehouse, logistics provider or party holding the goods
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT INSDES message?

INSDES is the UN/EDIFACT instruction to despatch message. The directory defines it as a message from one party to another party that has control over ordered goods, instructing it to put a consignment on hold or to despatch it according to conditions in the message.

It is used where goods are stored by a third party, such as a logistics provider's warehouse, and the owner decides when and where they ship. The instruction names the goods, quantities, destination, date and transport arrangements, and the warehouse reports execution with a despatch advice.

How the EDIFACT INSDES message worksDiagram of the UN/EDIFACT INSDES Instruction to despatch message. Owner of the goods, buyer or seller sends it to warehouse, logistics provider or party holding the goods. It usually follows ORDERS. It is usually followed by 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) and end of message: UNS (Section control). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT INSDES message worksInstruction to despatch: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSORDERSPurchase orderINSDESSENDEROwner of the goods,buyer or sellerRECEIVERWarehouse, logisticsprovider or partyholding the goodsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYDESADVDespatch advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage INSDESUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFNADTODTDTEQDLINEND OF MESSAGEUNSSection controlBlue 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 INSDES. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT INSDES message worksDiagram of the UN/EDIFACT INSDES Instruction to despatch message. Owner of the goods, buyer or seller sends it to warehouse, logistics provider or party holding the goods. It usually follows ORDERS. It is usually followed by 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) and end of message: UNS (Section control). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT INSDESmessage worksInstruction to despatch: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSORDERSPurchase orderINSDESSENDEROwner of thegoods, buyer orsellerRECEIVERWarehouse,logisticsprovider or partyholding thegoodsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYDESADVDespatch advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message INSDES (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFNADTODTDTEQDLINEND OF MESSAGEUNSSection controlBlue 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 INSDES.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends INSDES, 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 INSDES 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

  • Instructing a third-party warehouse to ship an order
  • Placing a consignment on hold
  • Releasing held goods for despatch

Where it fits in the message flow

Usually follows ORDERS Purchase order
This message INSDES Instruction to despatch
Usually followed by DESADV Despatch advice

Structure

Mandatory segments in INSDES (directory D.21A)

In UN/EDIFACT directory D.21A, the INSDES message has 51 segment positions arranged in 15 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
  • UNS
  • UNT

Practical example

INSDES in practice

A cosmetics brand stores finished goods at a logistics provider's warehouse in the Netherlands. When a retailer's order arrives, the brand's ERP sends the warehouse an INSDES with the products, quantities, delivery address and requested delivery date. The warehouse picks and ships the order and sends the brand and the retailer a DESADV.

Implementation

Implementation considerations for INSDES

  • Distinguish despatch and hold instructions clearly.
  • Use product and location identifiers shared with the warehouse.
  • Confirm execution with despatch advices and stock reports.
  • Define how changes and cancellations are sent.

How ECOM helps

Automate INSDES with ECOM

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

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

Related messages

Related shipping and logistics messages

All 7 shipping and logistics messages

Need help with INSDES?

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

Request a Demo Contact us