Despatch Advice Message Introduction

The Despatch Advice is send from a Seller to a Buyer.
Despatch Advice is an alternative spelling for dispatch advice and mostly used in Electronic Data Interchange (EDI).

Process

The Despatch Advice is received from the Seller. Onetrail TPN™ will translate the Seller specific format and make the Despatch Advice available to the Buyer.

Process management

During the translations required by Onetrail TPN™ platform, the Despatch Advice is monitored. If some technical exception occurs, Onetrail will take action by contacting the Seller to clarify the problem.

For more detailed information about supported despatch advice processes we refer to the second section of this page.

Content

The companies and addresses used in the desadv are referenced by Global Location Numbers (formerly known as EAN/ILN address codes). These codes can be supplied by Onetrail unless your company already has GLN's numbers. These given GLN's can only be used to communicate with Onetrail.

The following GLN's are relevant to the Order Request:

• To identify the Buyer: XML: fromRole EDIFACT: UNB020, S002, 0004
• To identify the Seller: XML: toRole EDIFACT: UNB030, S003, 0010
• Where the goods are shipped to in case of Warehouse Shipment: XML: ShipTo EDIFACT: NAD+ST
• Where the Invoice needs to be send to: XML: BillTo EDIFACT: NAD+IV

Syntax

• XML

For default values, multiplicity of elements, attributes and an overview for mapping design purposes.

• EDIFACT

Besides XML Onetrail also supports a standard EDIFACT D97A DESADV besides a lot of other industry standards.

Format

The format of the messages is XML version 1.0. The encoding must be UTF-8.
Or EDIFACT D97.A DESADV

Communication

Examples

Supported processes by Onetrail TPN™ in the Despatch Advice Message

In this section we describe the various supported processes in the Despatch Advice Message. 

. The availability of each individual Onetrail TPN™ supported process for each Seller depends on their capabilities as shown in table Overview Supported Processes Despatch Advice. Each process is described in the subsections below.

• Remark: For Proof of delivery see last subsection. 

Despatch Advice Types

Buyers and Sellers can agree upfront which schedules they prefer for their deliveries. For example every day, once a week, every Wednesday etc. Multiple Despatch Advice's in one message are allowed; however, in Onetrail TPN™ every Despatch advice is handled separately. We distinguish two types of Despatch Advice's. The most used is the regular shipping/delivery notification.
In addition to this we can offer the Proof of Delivery Despatch Advice message. Recognition is done by a statement in the "GlobalDocumentFunctionCode" XML element. A significant difference between regular and the Proof of Delivery message (POD) is that there will be no "ShippingContainerItem" in the Proof of Delivery 

Additionally there will be a remark and a "DeliveryStatusCode" element in the "ShippingContainer" element.

XML usage:

Fixed values : "Notification" with Regular DESADV and with POD "Confirmation"
Variable values POD: i.e. "2017" : "Delivered".

EDIFACT usage:

No difference

Transporter Code

Sellers are using more than one Transporter for their delivery process. The Buyer knows which delivery type is used based on the specific Transporter. Onetrail maintains a table of available Transporters with corresponding GLN’s. The Seller can add a (internal) code or the GLN into their Despatch Advice Message. Onetrail will convert the internal code to a GLN or will use the GLN already delivered to inform the Buyer which Transporter is used by the Seller. Onetrail is able to receive a Track and Trace Code of a delivery from the Seller. The combination of the Track and Trace Code with the Transporter GLN makes it possible for the Buyer to get hold on the delivery process to their Warehouse, or in case of a Drop Shipment the delivery process to their Customer. Based upon the GLN a fixed URL can be used to Track and Trace the given code.

XML usage:

Fixed values:
<:transportedBy><:PartnerRoleDescription><:GlobalPartnerClassificationCode>: "Carrier"
Variable values
<:transportedBy><:PartnerRoleDescription><:BusinessDescription><:GlobalBusinessIdentifier>: i.e. "8713783712788"
<:transportedBy><:PartnerRoleDescription><:BusinessDescription><:businessName><:FreeFormText lang="EN">: i.e. "DHL"

EDIFACT usage:

Include:  Segmentgroup: 6
             Composite: C040
             Tag: 3127

Track and Trace

Tracking references can be added on Shipment level or Shipping container level. We distinguish two types of Tracking references: Shipper and Carrier. The first one is from the Sender. The second one is from the Transporter. Multiple Tracking references are possible. The XML tag "ProprietaryShipmentTrackingIdentifier" might contain a Track and trace URL.

XML usage:

Variable values

<TrackingReference><GlobalTrackingReferenceTypeCode>: "Shipper" or "Carrier" 
<TrackingReference><GlobalTrackingReferenceTypeCode><ProprietaryShipmentTrackingIdentifier>: i.e. "CC2S-DKY55"

EDIFACT usage:

Include: Segment group: 15
             Identity number qualifier: BN

Packaging of the Products

The Despatch Advice Message offers information to the Buyer about how the products are pre-packed by the Seller (Pallet, Carton, Box etc.). Depending on the Seller, information is provided on product level similar to the Purchase Order or the full packaging hierarchy (i.e. from pallet to box, to individual products in the box).

SSCC

Onetrail supports the use of the SSCC Barcode. This barcode offers information about the products included in a pallet delivery. The Serial Shipping Container Code (SSCC) is an 18-digit number used to identify logistics units. In order to automate the reading process, the SSCC is often encoded in a barcode, generally GS1-128, and can be encoded in a RFID tag too. The SSCC is used in electronic commerce transactions. The SSCC comprises an extension digit, a GS1 company prefix, a serial reference and a check digit. The digits are all numeric. It is applicable to tertiary level of packing. The SSCC is commonly used in the Advanced Shipment Notice (ASN) EDI transaction.

XML usage:

Fixed value:
<GlobalShippingServiceLevelCode>: "Regular"
Variable values:
<numberOfShippingContainers><CountableAmount>: Highest level packaging number
<ShippingContainer><shippingContainerIdentifier><ProprietarySerialIdentifier>: Identification of the package ( i.e. EAN SSCC)
<PackageType>: Identifies type of packaging i.e. "PALLET/UNIT LOAD", "CARTON"
<numberOfShippingContainers><CountableAmount>: Number of packaging Type

EDIFACT usage:

Include: Segment group: 15
             Identity number qualifier: AW

Purchase Order Line Number included in the Despatch Advice Message

Onetrail is able to add the Purchase Order Line Number on the received Despatch Advice Message from the Seller. This enables the Buyer to match the Despatch Advice Line Numbers with the used Line Numbers on the Purchase Order.

• Remark: Not all Sellers can offer this functionality!

Supported Product Codes in the Despatch Advice Message

Onetrail supports different product codes in the Despatch Advice Message:

• Seller Product Codes: Stock Keeping Unit number (SKU).
• Manufacturers / Vendor Product Codes: Manufacturer Part Number (MFPN) / Vendor Part Number (VPN).
• GTIN / EAN Product Codes: Global Trade Item Number (GTIN) / European Article Number (EAN) a unique product code supplied by GS1.
• Buyer Product Codes: own product code for Buyers.

Shipping and / or Delivery date

Different dates can be provided by the Sellers indicating the different types of deliveries. Sellers can provide the day and time of delivery at the Buyer and/or the moment a shipment leaves the Seller's warehouse. A window of delivery can also be provided by both Earliest and Latest delivery dates. Not all Sellers can give an estimate of the arrival date or departure date of the shipped goods.

XML usage:

Generic Variable value:
<ShipmentTransportationEvent><confirmedEvent><TransportationEvent><DateStamp>: Date of arrival or departure of the shipment i.e."20181025T000000"
Variable value direct from Sellers:
<ShipmentTransportationEvent><confirmedEvent><TransportationEvent><DateStamp><GlobalTransportEventCode>: "Ship" When the goods leave the Seller's warehouse or "Delivery" when the goods should arrive at the Buyer’s warehouse.
Variable value possibly added by Onetrail:
<ShipmentTransportationEvent><confirmedEvent><TransportationEvent><DateStamp><GlobalTransportEventCode>: "ShipCalculated" When the goods leave the Seller's warehouse or "DeliveryCalculated" when the goods should arrive at the Buyer’s warehouse. When a Seller can only provide either a shipping date or a delivery date and the Buyer insists on a receiving other values. When informed about the time it takes for the transporter to deliver the goods, Onetrail can provide a calculated delivery date from the actual shipment.

EDIFACT usage:

Include: Segment group: DTM
             DTM Qualifiers: 11 = Despatch date/time
             137 = Message date

Serial Number

Onetrail is able to receive the scanned serial numbers (and / or IMEI) in the Despatch Advice Message from the Seller. The Buyer can use this information to book the serial number for the End-Customer automatically. Especially for Drop Shipments this service is very helpful.

• Remark: Not all Sellers can offer this functionality!

End-User Reference

Onetrail is able to receive an End-User Reference originating from the Buyer’s Purchase Order and send back by the Seller. When the Seller sends the delivery as a Drop Shipment, the End-User Reference is needed on the Despatch Advice Message supplied by the Seller. Especially on the paper Despatch Advice.

Proof Of Delivery (POD)

Proof of delivery is a separate message inherited in the Onetrail TPN™ DESADV V3.2 format therefore mentioned here. Some Sellers, often in combination with their Transporter, offer the possibility to send a POD message after receipt of the goods by the recipient. The message can contain Despatch Advise number, delivery address, delivery date / time, the name of the recipient and with possibly a (link to) digital scan of the signature for receipt.

The minimal information a POD message should contain:
* Sender / Recipient Identification (Seller / Buyer)

• Transporter Identification
• Despatch Advise number Seller
• Transport ID Seller / Transporter
• Order number Buyer
• Package ID(Box number, Package ID / Serial number SSCC)
• Delivery Status Transporter
• Delivery Date / Time
• Name Recipient

Optional:
* Additional remarks like:

• • Delivered at neighbors house,
  • Planned new delivery moment (nobody home / answered),
  • Damage noticed upon delivery,
  • COD (Cash on Delivery)

• File name of the digital signature scan