---
title: "INTEGRATION - Portbase Secure Chain"
description: "This article explains how Secure Chain works in Qargo, how to recognise a Secure Chain shipment, and how to create or delegate a booking when Secure Chain applies."
url: https://help.qargo.com/en/articles/483948-integration-portbase-secure-chain
locale: en
updated: 2026-02-20
---

# INTEGRATION - Portbase Secure Chain

## Using Portbase Secure Chain in Qargo {#h_cbb41713e9}

Secure Chain ensures that only authorised companies can pick up or deliver a container at Dutch sea terminals. Qargo fully supports receiving and delegating these permissions so your workflows remain smooth and compliant.

* * *

### What is Secure Chain? {#h_c502a06e21}

Secure Chain is a security process in Portbase that gives specific companies the right to:

-   Create a pre-notification
-   Pick up or drop off a container

Two actions are possible:

1.  **Receiving Secure Chain permission**\
    → Another party nominates your company to handle a container.
2.  **Delegating Secure Chain permission**\
    → You transfer your permission to a subcontractor.

Qargo helps automate these steps where possible.

* * *

## 1\. Enabling Secure Chain in Qargo {#h_a3cb124490}

Secure Chain shipments in Qargo are identified with the **Secure Release** checkbox on the order.

![](https://help.qargo.com/media/2f54cf32d2a1-image.png)

This field can be:

-   Set automatically when a Secure Chain nomination arrives from Portbase
-   Set via **order import** or **API**
-   Checked manually if needed

**Important:**\
If you know the container is a Secure Chain shipment but the Secure Release box is _not_ checked, it means Qargo has not yet received the nomination from Portbase. You can check it manually to ensure correct processing.

* * *

## 2\. Receiving Secure Chain Permission {#h_3de9c9dc32}

When another party nominates you in Portbase:

1.  A Portbase user nominates your company for a specific container.
2.  Qargo receives the nomination with the shipment ID and container details.
3.  Qargo automatically matches it to the correct order.
4.  The Secure Release checkbox is automatically enabled.

### How this affects the **Status Request** task {#h_b6b974a8e6}

When you run a status request:

| **If Secure Release is…** | **Qargo will…** |
| --- | --- |
| **Checked** | Skip creating a pre-notification (already handled by the nomination). |
| **Not checked** | Create the pre-notification normally. |

This ensures you don’t create duplicate pre-notifications in Portbase.

* * *

## 3\. Creating a Booking (No Delegation) {#h_e26f9968d9}

For normal bookings where you keep the pickup rights:

1.  Create a booking in Qargo.
2.  Run the task **Create Container Booking to Portbase**.
3.  Qargo sends the booking to Portbase using the Secure Chain shipment details.
4.  Portbase returns the booking confirmation.

This flow works the same as a regular Portbase booking, except Secure Chain ensures your permissions are valid before pickup.

* * *

## 4\. Delegating Secure Chain Permission {#h_f4ff411ef4}

You can delegate your permission to a subcontractor in two ways.

### Delegating from Qargo {#h_9fe58c2dc9}

1.  Create a booking in Qargo.
2.  Select **Delegate to subcontractor** and enter the subcontractor’s **EAN reference**.

![](https://help.qargo.com/media/e7331bf0f5da-image.png)

1.  Run **Create Container Booking to Portbase**.
2.  Qargo automatically:

    -   Confirms the shipment was found
    -   Checks that Secure Chain applies
    -   Sends the delegation command to Portbase

The subcontractor now receives the rights to pick up the container.

### Delegating via Portbase UI {#h_5ebe3a3e23}

Alternatively, delegation can happen directly in Portbase:

1.  A Portbase user delegates the container to the subcontractor.
2.  Portbase sends the update to Qargo.
3.  Qargo continues to show pickup status, even after delegation, so you can monitor progress.

* * *

## 5\. Timeslots and Portbase {#h_25ae105dd5}

Portbase does **not** provide an API to share available or updated timeslots.\
This means:

-   **Timeslots in Qargo do not update automatically** after changes made in Portbase.
-   If Portbase assigns or changes a slot, you need to **manually verify and update** the timeslot:

    -   On the stop in Qargo
    -   Or in the Portbase booking view in Qargo

### Best practice {#h_b3fd382dd7}

Always double-check the confirmed timeslot when:

-   First creating the booking
-   Receiving updates from Portbase
-   A subcontractor has been delegated rights

* * *

## Summary {#h_2fc6254e55}

Qargo makes Secure Chain simple by:

-   Automatically detecting and handling Secure Chain nominations
-   Skipping unnecessary pre-notifications
-   Allowing easy delegation to subcontractors
-   Tracking pickup status even after delegation

If you need help configuring Secure Chain, adjusting your imports, or troubleshooting a Portbase flow, our support team is happy to assist.


## Related articles

- [Portbase: container terminal bookings](https://help.qargo.com/en/articles/171730-portbase-container-terminal-bookings.md)
- [PLANNING - Container Bookings: Linking External Bookings & Cancellation Handling](https://help.qargo.com/en/articles/580934-planning-container-bookings-linking-external-bookings-cancellation-handling.md)
- [CUSTOMER PORTAL - Creating and Planning orders shown in customer portal views.](https://help.qargo.com/en/articles/316497-customer-portal-creating-and-planning-orders-shown-in-customer-portal-views.md)
- [User roles: Permission and visibility](https://help.qargo.com/en/articles/180518-user-roles-permission-and-visibility.md)
- [INTEGRATIONS - Qargo API - What, Why & How](https://help.qargo.com/en/articles/865547-integrations-qargo-api-what-why-how.md)
