Dockflow is launching a direct integration with Portbase. If you have a Portbase subscription, you’ll be able to connect it to Dockflow — cargo status, customs updates, and key port events all in a single dashboard alongside your carrier milestones. No exports, no tab-switching.
The integration is in beta. Join the waitlist today and we’ll reach out when it’s ready for your account.
What is Portbase, and why does every Rotterdam freight forwarder already use it?
Portbase is the Port Community System for Rotterdam and Amsterdam. It’s how the port runs digitally: shippers, forwarders, terminals, customs authorities, and carriers all exchange data through it.
Over 5,600 companies use it. 25,000 individual users. 145 million transactions a year. 95% of Rotterdam export documents now flow through Portbase digitally. If you move freight through either port, you’re in the system whether you think about it or not.
The issue is what happens after. Portbase data lives in Portbase. Container tracking lives somewhere else. You end up with two logins, two platforms, and a manual check every time the information doesn’t line up.
What the Dockflow × Portbase integration actually does
Dockflow is an official software supplier at Portbase, which is how we can pull Portbase data directly into your account. When you connect, six event types from the Cargo Controller come in automatically:
- Vessel visit updates (ETA, ATA, ETD, ATD) — so planned transport and warehouse resources can be adjusted before it’s too late
- Bill of Lading changes or deletions — when a carrier amends B/L data or pulls it from the manifest (usually meaning the cargo is not on board), you see it immediately
- Discharge terminal changes — if the unloading terminal switches, Dockflow flags it before it catches you at the gate
- Customs inspection notifications — when customs holds a container for inspection, it appears in your feed straight away
- Inspection releases — when customs clears the hold and pickup becomes possible again
- Discharge confirmations — container-level confirmation that each piece of equipment has been unloaded
Dockflow, a container tracking platform for freight forwarders, pulls all of this continuously without you triggering anything. It sits next to your carrier data in the same view.
One forwarding team on the beta told us it removed most of the back-and-forth with their port desk. When you can see cargo and customs status without logging into Portbase separately, the confirmations you were doing manually just stop happening.
Who this is actually for
The clearest fit is freight forwarders running 50+ shipments a month through Rotterdam or Amsterdam who currently check Portbase and a container tracking tool separately. One customer running a mid-sized import/export desk estimated their team was spending 3–4 hours a day on port monitoring — including extra staff dedicated specifically to watching import cargo — time the integration removes.
It also matters for teams handling both the port side and client-facing updates. Customs and inspection status are now visible inside Dockflow’s customer portal, so you can answer a shipper’s question without verifying it in Portbase first.
Why the right data in the wrong place is still a problem
Carrier data and port data answer different questions. Carrier data tells you where the vessel is and when it’s due. Portbase tells you whether the cargo is actually cleared to move once it arrives. When those two sources disagree, you need to know which one to trust.
Dockflow’s GraphTP algorithm handles this. When carrier ETAs and port status updates conflict, GraphTP determines which signal is more reliable and flags the discrepancy for your team. Portbase data runs through the same process as every other source.
So when something’s wrong, you see it. You don’t find out about a customs hold three days later because nobody checked Portbase that afternoon.
This is part of Dockflow’s container visibility module, which pulls carrier, port, and customs data into a single feed with exception-based alerting. Portbase is now one of those feeds.
How to join the beta waitlist
The integration is rolling out from April onwards. Join the waitlist and we’ll contact you directly when it’s ready for your account.
You’ll need an existing Portbase subscription to connect. Once live, setup is one step in your Dockflow account settings.
Not yet on Dockflow? Book a demo and we’ll walk through what the full setup looks like for your operation.
Three things before you go: the Portbase integration launches in April — join the beta waitlist to be first in line. Six event types from the Portbase Cargo Controller will flow into Dockflow automatically, sitting next to your carrier data in one view. All of it runs through GraphTP, so conflicts surface before they catch you off guard.
Frequently Asked Questions
Do I need a Portbase subscription to use this integration? Yes. This connects your existing Portbase account to Dockflow. Without a Portbase subscription it won’t be available — but Dockflow still tracks your containers across 200+ ocean carriers regardless.
Which Portbase events come into Dockflow? Six event types from the Portbase Cargo Controller: vessel visit updates (ETA/ATA/ETD/ATD), Bill of Lading changes and deletions, discharge terminal updates, customs inspection notifications, inspection releases, and discharge confirmations.
Does the Portbase data show up in the Dockflow Customer Portal? Yes. Once it’s in Dockflow, it’s part of the shipment record. Your shipper customers see it through the customer portal if you’ve set that up.
When is the integration available? The beta rolls out from April 2026. Join the waitlist to be contacted when it’s ready for your account.
