The backlog outlasts the stoppage by a multiple
A 48-hour strike does not cost 48 hours. ECT Rotterdam indicated it would take at least several days to clear the resulting container backlog, and that is before the compounding effect of vessels arriving on their original schedules into a terminal that is behind.
Northern European gateways were already operating at high utilisation with little flexibility to absorb additional disruption. A stoppage into a constrained network does not produce a delay proportional to its length. It produces a queue, and queues clear slowly.
Demurrage is a daily meter
Demurrage and detention charges are the clearest example in shipping of a cost that starts small and becomes serious quickly. They accrue per container per day, they do not stop while a dispute is pending, and they frequently exceed the value of the underlying service.
The contractual question of who absorbs them — carrier, forwarder, shipper, receiver — is rarely resolved cleanly when the cause is industrial action or congestion rather than a party's own delay. Force majeure provisions vary. Free time allowances vary. Practice varies by terminal.
While that is litigated or negotiated, the charges sit somewhere. They sit with whoever has the least contractual leverage, which is usually the smallest party in the chain.
The weakest link fails first, and quietly
This is the part that matters for a credit book. A large carrier or a well-capitalised forwarder absorbs an unexpected six-figure demurrage bill and files it under cost of doing business. A small forwarder, a regional trucking operator or a mid-size trader does not.
What that party does instead is stretch its other payables. It pays its bunker supplier later. It pays its port agent later. It negotiates on an invoice it would previously have settled without comment.
Those are the first observable symptoms, and they appear on counterparties that are not obviously connected to the strike at all. The stress transmits through the chain rather than staying with the parties directly affected.
What granular visibility changes
Aggregate congestion statistics tell you a port is slow. They do not tell you which of your counterparties has forty containers sitting past free time in it.
Vessel-level and counterparty-level dwell data closes that gap. It identifies which specific parties are accumulating congestion cost, how much, and for how long — which is the difference between knowing there is a problem in Rotterdam and knowing which three names in the book are carrying it.
What CERTY does about this
Granular, vessel-level visibility into dwell times and port status flags which specific counterparties are absorbing the most congestion cost. Because that data feeds the same behavioural scoring as payment activity, the resulting payment stretch is visible as it develops rather than at the next reporting cycle.
