Certified pick up v4.9.0

We are pleased to announce the release of Certified Pick up version 4.9.0!

Release date

This version is released to UAT on 8th of June 2026.

CPu users must validate the changes in this version, along with each user's most important business scenario’s, as communicated during the CPu User Groups. For any help regarding demo data to test those scenario’s, this can be requested via support@nxtport.com.

This version is released to PRD on 21st of June 2026.

Improvements

API

Create/update commercial release (ref. Shipping Agent Integration Specifications): the value of the terminalCode attribute in the request body must be present on the following list: Terminalcodes.pdf (ref. CPu variables overview). This implies that a terminal code alias (for example “K1700”) is not allowed anymore for new commercial releases and update actions. In a following CPu release (4.10.0 or later), terminal code aliases won’t be allowed for all other API operations such as Terminal Release, Accept Release Right, Generate Pickup Right,…

General

The timestamp for a Greenlight (e.g. Commercial Release, Customs, Discharge,…) from this release onwards represents the original timestamp of the event (Commercial release, customs release, discharge,…). This applies for the timestamps shown underneath a greenlight in the CPu UI, as well as the timestamp in ReleaseLightChanged notifications (CPu notifications overview).
ReleaseLightChanged notifications (CPu notifications overview): identical originalValue and newValue are avoided (for example RELEASED to RELEASED or BLOCKED to BLOCKED), except for the PickupLight greenlight.
Security and technical improvements to ensure stability of the CPu application.

Bugs

Fix for missing validation error when a commercial release is created with a “release valid from” date in the past (UI).
Fix for transfer release right operation in the UI, where the equipmentNumber has a prefix such as for example “////1234567”.
Fix for retrieving release details via API as forwarder or transport operator, after the release right had been accepted by a next party. This implies that after the release right had been transferred and accepted by a next party, as forwarder or transport operator, you will still be able to fetch the release details (Release Party Integration Specifications and Transport Operator Integration Guidelines).