Routing database for labels

First of all, for your labels, it's important that you use the correct routing. It can be found here:
For Belgian customers:
For Luxemburg customers:


EDI File description

The contents of the MPSEXPDATA file is divided into a header, several application records and an end.The header consists of 10 lines, one file definition header and 9 data record definition headers. For the application records the HEADER record must always be first followed by the corresponding detail records. Data records that are not provided
in the format described above cannot be processed. The tokens of optional fields must always be contained
in the definition line. The data line fields may remain empty (;;) unless they're mandatory fields.

There is no limit as to how many shipments you include in a single file. You can send us multiple files with one shipment each, one single file containing all your shipments of the day or any frequency in between.

MPSEXPDATA general structure summary

  • The #FILE line is unique for each MPSEXPDATA file. It contains your DelisID, the date (format YYYYMMDD) and time (format HHMMSS) and an ID of your file.
  • The #DEF files are definition files and also need to be mentioned only once per file. They're mandatory, but are pretty much the same every time. These contain the order and names of each field of each line type. 
  • The HEADER line contains the main info of your shipment. This contains the sender details, the receiver details, the total weight, references, the service code, etc. Basic details of the shipments. You can only have one HEADER line per shipment, obviously.
  • The PARCEL line contains the details of the parcel(s) of the shipment. You can have a single PARCEL line, which we call a mono-colli shipment, or you can have several PARCEL lines, one for each individual parcel within your shipment, which we call a mutli-colli shipment.
  • HEADER and PARCEL are the only two lines that are, without exception, always mandatory for each shipment. We will discuss these lines separately in the menu to the right. The other lines are for different service codes which are also discussed in the menu to the right. These include MSG, PERS, etc.
  • The SWAP line is a service that was discontinued so this can be ignored
  • The COD line is the same as SWAP: no longer in use
  • The DELIVERY line is also the same as SWAP and COD: it's not used.
  • The SHIPINFO line is yet another field we no longer use.
  • The MPSEXPDATA file must always end with an #END line. This line is, just like the #DEF and #FILE lines, also unique per file. The #END line contains the same ID you gave in the #FILE line.


MPSEXPDATA simplified construction

Lets assume your DelisID is mbvcr530, that your depot is 0530, that we create this file on the 13th of August 2018 and that we give it the unique ID 3.

#DEF lines




MPSEXPDATA file naming convention

The name of the EDI file needs to follow this logic:

MPSEXPDATA_<Delis ID>_CUST_<your depot code>_D<date>T<time>

Date format is YYYYMMDD, time format is HHMMSS. The date here must be the date on which you'll send this EDI file to DPD. This needs to be accurate. The time's accuracy is not as important: this is just a stamp we add to prevent the customer from accidentally overwriting files with the same name. You do need to make sure it has the correct format though and has a time value that is valid (for example 358500 would not be good, since 35h85 is impossible)

An example: lets say your DelisID is mbvcr530, your depot code 0530 and that you made this file on the 13th of August 2019, it could look like this:



Transferring EDI files to DPD

EDI files must be uploaded to the DPD SFTP: (port 2266)
Your username will be the same as your DelisID, which will be given to you by DPD IT. The password will also be given to you by DPD after validation of the files.


Further chapters can be found below.

Soumis par Dirk-Jan Dirix le mar 30/07/2019 - 14:58