Postnl.nl

Changelog

Updates Developer Center

[14-10-2024] Change ZPL output of Zebra printers for international labels

On October 30, we will implement a change in the ZPL output of Zebra printers for international labels. The ZPL output will include the command ^LH0,0. This command ensures the correct alignment of the label. Additionally, we will remove the command ^MD30 from the ZPL output. This command was responsible for darkening the label output but did not always have the desired effect.

[2-9-2024] New T&T status codes (G03 + V06) added to most common SFTP connection

Per 4th September 2024, two extra scan observations are added to the most common SFTP connection. These scan observations provide more insight into when a shipment is delayed during peak periods. This gives you the opportunity to proactively inform recipients or answer their questions. Below an explanation of the extra scans.

T&T status code / Observation: G03

Description: NL: “Door drukte duurt de bezorging wat langer dan normaal. We bezorgen je pakket zo snel mogelijk.” / ENG “It's very busy. Please allow for slightly slower delivery times. We'll deliver your parcel as soon as we can.”

Explanation: This scan observation indicates that a shipment that has been handed over at a PostNL drop-off point is not yet sorted and is currently in stock waiting for the first sorting scan.

We recommend to treat this observation as an indication that the parcel is delayed.

T&T status code / Observation: V06

Description: NL “Door drukte duurt de bezorging wat langer dan normaal. We bezorgen je pakket zo snel mogelijk.” / ENG “It's very busy. Please allow for slightly slower delivery times. We'll deliver your parcel as soon as we can.” 

Explanation: This scan observation also indicates a delay. It did not receive its first sorting scan yet. This scan often occurs during peak periods. We recommend to treat this observation as an indication that the parcel is delayed.

How can you act on this change?

Prepare for this change by storing the codes (G03 and V06) and corresponding descriptions in the appropriate (harmonization or definition) table. Check the complete list of PostNL T&T status codes. In addition, make sure that applications that convert the scan observations to information for your business processes recognize these scans and provide the correct information. 

[25-06-2024] Scheduled downtime Send & Track-API's

Please be informed that all PostNL-API's necessary for the creation of shipping-labels and pre-alerts will be unavailable due to scheduled maintenance between 01:00 AM and 02:00 AM (CET) on July 2nd. Be advised that this also applies to the Shipment-API.

[30-05-2024] Scheduled downtime Send & Track-API's

Please be informed that all PostNL-API's necessary for the creation of shipping-labels and pre-alerts will be unavailable due to scheduled maintenance between 01:00 AM and 01:30 AM on June 25th. Be advised that this also applies to the Shipment-API.

We apologize for any inconvenience this may cause.

[21-05-2024] Maintenance Notification for Labelling and Shipment API

On Wednesday, May 22, from 21:00-22:00, both the Labelling and Shipment APIs will undergo maintenance to address the incorrect handling of multiple shipment objects in one API-call. No downtime is expected for either service.

[02-05-2024] New validation process business reply numbers

On June 18, 2024, we will implement a new validation process for business reply numbers related to product codes 2285 and 3285, which will affect return shipments. This update is crucial to ensure accurate preannouncements and improve both billing and product quality.

Validation Activation:

  • For product code 2285, only business reply numbers can be used as recipient addresses.
  • For product code 3285, business reply numbers cannot be used as recipient addresses.

Impact:

  • This change has no impact if preannouncements are correct
  • Incorrect preannouncements will trigger an error.
  • Affected shipments will not receive a label or be pre-notified.

Required Actions:

If needed, adjust the recipient's address in AddressType 01 to align with the correct product code requirements.

Support:

  • For API adjustments or testing, contact us via the support form with "Business reply number validation" in the subject.
  • If you would like advice on which product codes or return options to use, please contact your account manager.
This update is part of our ongoing effort to enhance service accuracy and efficiency.

[28-02-2024] Upgrade generation of shipping labels

Per 10 april 09:00 AM, the application for the generation of shipping labels will be upgraded. As a result, Printertype-responses in the categy Zebra|Generic ZPL II have adjustments in the buildup of the ZPL-code. Users of this printer type output are advised to evaluate the ZPL-output on compatibility with application(s) and/or hardware.

Adjustments to the ZPL output are as follows:

  • The resolution command (^JM) is now set within a label format (^XA, ^XZ block)
  • The documentation command (^FX) containing the form name is no longer generated.
  • The ZPL header value in the default configuration file was changed to an empty value instead of "^MMT". If the original value (^MMT) is used, it is replaced by "^XA^MMT^XZ" to match the ZPL reference.
  • Some ZPL commands like (^LS, ^LT etc.) are now generated only once before the first label and no longer on every label.

The new Zebra|Generic output-types are retrievable via the sandbox-environment of either Labelling- or Shipment-API.

[09-01-2024] Update API-management portal

Per January 10th, the API-management portal has been deactivated and can no longer be used for retrieving your API-credentials. Please contact Chanel integrations via the support form and provide your customer number and username of the API-management portal for assistance.


If you use the API key for Data Solutions and you are unable to locate your API key in the module 'Manage API keys', please reach out to our support team at datasolutions@postnl.nl.

Changelog 2023

Changelog 2022

Changelog 2021

Changelog 2020

Changelog 2019