DPDgroup GeoData

Download the GeoData guidelines  

  1. Download the GeoData specifications

    The data specifications last update : 08/2021

    In the sections below you will also find a more specific explanation of some of the commonly used non-standard service codes such as B2C Predict, B2C Parcelshop, etc.

  2. Encoding

    UTF-8 is the only allowed encoding of all data types sent towards DPD Belux from 2022 onwards.

    Please change all possible configurations away from ISO-8859-1 or other encoding type into UTF-8

  3. Correctly naming your EDI file

    Your EDI file’s name needs to have the correct format for our system to pick it up from our SFTP. An incorrect name format will result in the system not recognizing it and your data not being processed.

    The correct naming is as follows (bold parts are fixed, italic parts are variable):

    GEODATA_SHPNOTCUS_[YOUR DELISID]_0340[YOUR DEPOT CODE]_D[DATE]T[TIME]_[6 DIGIT COUNTER]

    • Your DelisID is assigned to you by DPD.
    • Your depot code is always 4 digits and is also assigned to you by DPD.
    • The data is in format YYYYMMDD
    • The time is in format HHMMSS
    • The counter exists only to make sure no file will overwrite the other if they’re created on the exact same second. It needs to be 6 digits.

    An example:

    • Your DelisID is BE2625
    • Your depot code is 0541
    • You create this file on January 22nd, 2025 at 16h51 and 32 seconds.
    • You have a new counter running

    Your file name would be
    GEODATA_SHPNOTCUS_BE2625_0340541_D20250122T165132_000001

    If you were to make another datafile on the exact same second, it would be named
    GEODATA_SHPNOTCUS_BE2625_0340541_D20250122T165132_000002

  4. B2C Predict shipment

    • Service code: 327 for normal parcel, 328 for small parcel
    • Extra required line: MSG line

    This service code allows you to have DPD send a Predict message to the receiver. For obvious reasons, this implies you need to know either the email address or phone number of the receiver. We usually advise using the email address.

    You also have to add a new line to your EDI: the MSG line. You can find the details of this line in the previously mentioned dataset

    In this line, 4 fields are mandatory:

    • MSGTYPE: use 1 if it’s an email, 2 if it’s a text message.
    • MSGDESTINATION: email or phone number to send the Predict to. If the type is 1, this must be an email. If the type is 2, it must be a phone number
    • MSGTRIGGER: this is an internal DPD code and can be hardcoded to 904 for these shipments.
    • MSGLANG: the language in which the Predict must be sent. Please note only English or the recipient country’s official language are accepted. This needs to be the official Two letter ISO language code

    You can have several MSG lines within your shipment. However, it’s worth noting that the MSG line is an “all or nothing” deal. This means if you add an MSG line to your data, you need to make sure all it’s mandatory fields are filled in. If, for example, you have an MSG line without the language code, the line will be considered faulty and be ignored, meaning the Predict will not be sent.

    Example:

    SHIPMENT;2;05368006612345;;0;1;;;;;;1;;18;0340536;20250131;183422;W;0100512;F311;20250131;183537;20250131;183537;0;;;;;L512;;;0;;;INS;0340530;20250131183423;+0100;
    SENDER;3;05360000000054321;;;DPDCP1254AZER;Sender Name BVBA;;Egide Walschaertsstraat 20;;;;;;;BE;;2800;Mechelen;;0;;;;;;;;B;;;;P;;
    RECEIVER;3;;Receiver Name;;;;;Teststraat 5;;;;;;;BE;;2920;Kalmthout;;Jean Durand;32471123456;;;;receiver_test@receiver.be;;;;P;;;;;;
    DELIVERY;3;;;;;;;;;;;;
    PARCEL;3;05368006612345;0;1;2281319S432153;2281319S432153;2281319S432153;Invoice reference;;358;;;;;040060030;18;;;;;0;;INS;2281319S432153;;;;;;0.000;;
    MSG;4;Sender Name BVBA;Sender Name BVBA;3;0;32471123456;904;NL;;
    MSG;4;Sender Name BVBA;Sender Name BVBA;1;0;receiver_test@receiver.be;904;NL;;

  5. Moving from Legacy Formats

    When moving from the DPD DE legacy format to Geodata, you can find help in:

    When moving from the DPD DE legacy format to API Integration, you can find help in:

  6. Heavy parcel regulation in Germany

    Rules will be applied for heavy parcels in Germany in 2025. This means that your GeoData must contain the correct weight of the parcel. Concretely, you need to ensure that the DECLAREDWEIGHT field in the PARCEL line is correctly filled in, with a value that matches the real weight of the parcel.

    Of course, the MPSWEIGHT field in the SHIPMENT line still needs to contain the total weight of the shipment: the sum of all weights of all your parcels within that shipment.

    There are also mandatory changes to the labels which are listed on this page.

Was this post helpful?(Required)