🚛 Freight and home delivery

This list is not complete as of today. For further carrier reach out to support@parcellab.com

Hermes Einrichtungs-Service

With Hermes Einrichtungs-Service (HES) we are using the StatusDepCSV interface as of 31.07.2014. Data is provided via FTP access, the credentials for this FTP server will be provided to the shipper and need to be forwarded to parcelLab.

We need both the confirmation files with the filename pattern <VersenderID>-YYYY-MM-DD-HH-mm.csv listing the tracking url and the status files with the filename pattern sdgstat-<VersenderID>-YYYY-MM-DD-HH-mm.csv.

DHL 2-Mann-Handling

We track DHL through the web interface. For this interface to be accessible, we need the DHL Freight-internal tracking number in the format 60<12 digits>.

BJS Home Delivery

The used interface is referred to as Events CSV. Data is provided via SFTP.

InntraLog

With InntraLog, our setup requires the transfer of status data with the event codes IMP, WEC, WED, WEP, VSF, WED, AVV, AVS, ABG, AKL, AVW, KNA via SFTP.

DB Schenker

At DB Schenker you need to request the following access via your contact person:

EDIFACT IFTSTA D.96A

Subsequently, you will receive access data to Schenker's FTP server, which usually consists of a server (usually edi-cc.dbschenker.com), path (usually/ out / iftsta), a user and password.

Dachser

We use the interface Statusdaten CSV Version 2.0.1 (2014-07-14). Data is provided via FTP by Dachser.

Kühne + Nagel

K+N provides status data according to the EDIFACT IFTSTA specification via SFTP, that can be used by parcelLab.

Hellmann

At Hellmann you need to request the following access via your contact person:

EDIFACT IFTSTA D.96A

Subsequently, you will receive access data to Hellmann's FTP server, which usually consists of a server (usually a CNAME on hellmann.net), path (usually/out/iftsta), a user and password.

IDS Systemlogistik

For freight forwarders being part of IDS, we use the standardized interface of IDS:

elix/IDS Flatfile Interface

Transfer is handled usually via FTP or SFTP.

CargoLine

CargoLine is like IDS a group of freight carriers who generally all support this interface for data transfer of status data (German name):

Datensatz für Statusberichte – Release 100 (Package-Header-Satz: ‘STAT512’)

Transfer is handled usually via FTP or SFTP.

Gebrüder Weiss

For shipments from "Gebrüder Weiss" from Austria, we access the following interface:

BORD512 via EDI including parcel numbers in RFF+CW with the parcelLab-Setup

This interface must be created for each customer individually, which may involve costs.

Please request this interface from your contact at "Gebrüder Weiss" and contact the parcelLab team.

Custom interface ✨

If there's a need for setting up a new interface, consider these guidelines. The following guidelines can be understood as a point of reference rather than strict requirements.

Data transmission

The preferred transfer channel is via SFTP, where either the data can be downloaded by parcelLab or is automatically uploaded to parcelLab servers. For more information on data exchange see:

We expect data to be sent at least every hour, but data can also be sent in real time for each individual scan event (preferred).

Supported file formats are XML (preferred), CSV or EDIFACT. There is no strict file name convention, but all files are required to have a unique name.

Scan events and data

Scan events have to hold a timestamp, location (optional) and one of the following event codes incl. reason code and details.

Event code

Description

Reasons / Details

Order data received

Delivery has been created electronically

Inbound complete

Delivery has been received by carrier

Arrived at depot/ in transit

Any intermediary scan in depot of the carrier

Arrived at destination delivery depot

Delivery has arrived in final depot before delivery

Scheduled delivery date

Delivery date has been scheduled/ optionally confirmed with the recipient

Date of delivery, start and end of estimated delivery time window

Out for delivery

Delivery has been loaded for last mile and is on the way to the recipient

Successfully delivered

Delivery has successfully been delivered

see below

Delivered with problems

Delivery has been delivered, but with issues

Free text

Recipient refused delivery

Delivery has been rejected by the recipient

see below

Failed delivery attempt

Delivery has been attempted but was not successful

see below

Contact request

Recipient required to get in touch with carrier

Free text

Exception

Any issue during delivery process

see below

Will be returned

Delivery will be returned to sender

Return picked up

Return delivery picked up at customer

Return delivered

A return delivery has been delivered to the sender

Successfully delivered (reasons)

Reason

Description

Details

To recipient

Accepted by original recipient

Name of recipient

To authorised person

Accepted by family/ household/ company member

Name of authorised person

Safe deposit

Delivered to safe location authorised by recipient

Description of location

Collection point

Ready for pickup by recipient at collection point

Address of collection point

Other

Free text

Recipient refused delivery (reasons)

The details can always be a free text.

Reason

Description

Not ordered

Not ordered as by authorised recipient

Damaged

Packaging or goods damaged

Other

Failed delivery attempt (reasons)

The details can always be a free text.

Reson

Description

Address not found

Address cannot be found

Recipient not there/ business closed

Address can be found, but recipient was not met

Recipient not found at address

Address can be found, but recipient is not listed at address

Identification failed

Delivery required identification of recipient, but failed

Delivery payment failed

Cash on delivery failed

Time issue

Tour had to be aborted, because driver exceeded working period

Operative disruption

Issue in operations, e.g. truck broke down

Act of nature

Delivery cannot be performed, e.g. severe weather conditions

Other

Exception (reasons)

The details can always be a free text.

Reason

Description

Failed contact attempt

Carrier tried to reach recipient unsuccessfully

Damaged

Packaging or goods damaged

Items missing

Not all listed items found

Lack of space

Delivery could not be loaded onto truck

Misrouted

Delivery has been routed to the wrong depot/ tour

Operative disruption

Issue in operations, e.g. truck broke down

Act of nature

Delivery cannot be performed, e.g. severe weather conditions

Other

Sample

sample-event-message.xml
<?xml version=1.0 encoding=UTF-8?>
<Events>
<Event>
<Shipment>Shipment identifier, e.g. barcode, order number, tracking number</Shipment>
<Timestamp>YYYY-MM-DD HH:mm:ss +-HH:mm</Timestamp>
<Location>Depot München</Location>
<EventCode>Scheduled delivery date</EventCode>
<Details>
<EstimatedDeliveryDate>YYYY-MM-DD</EstimatedDeliveryDate>
<EstimatedDeliveryTimeFrom>HH:mm</EstimatedDeliveryTimeFrom>
<EstimatedDeliveryTimeTo>HH:mm</EstimatedDeliveryTimeTo>
</Details>
</Event>
<Event>
<Shipment>Shipment identifier, e.g. barcode, order number, tracking number</Shipment>
<Timestamp>YYYY-MM-DD HH:mm:ss +-HH:mm</Timestamp>
<Location>Depot München</Location>
<EventCode>Successfully delivered</EventCode>
<ReasonCode>To recipient</ReasonCode>
<Details>Julian Krenge</Details>
</Event>
</Events>