Who Pays for Shared Visibility?

A shared infrastructure needs a budget. So does the work that keeps its information useful. Supply-chain leaders should settle both before they count the benefits.

A supply-chain platform can balance its books while the cooperation behind it makes little business sense. Membership fees may cover software, security and support without covering the work needed to keep the information accurate. Paying for the platform does not settle who pays for that work.

Consider a forwarder correcting a shipment update so a customer can reschedule a warehouse appointment. Someone checks the record and resolves the discrepancy. The commercial test is what the forwarder has agreed to provide, what additional work is required and whether its return justifies that work.

The question is not simply who pays for the shared infrastructure. It is who sustains the participation that makes it useful. In a voluntary network, the reason to contribute must outlast the invitation to join.

Two costs that belong in one decision

The first cost is keeping the service available. The second is keeping its information useful: connecting systems, maintaining records, managing permissions and correcting errors. A business case that counts the infrastructure invoice but ignores additional work at partner companies is incomplete.

Where correcting information creates recurring work, allow for the staff time, training and support it requires, including shift cover and a clear route for resolving problems where needed. Do not assume existing teams have spare capacity. Before relying on a partner’s contribution, check that it has the resources to sustain the work.

The US Department of Transportation’s FLOW Program is voluntary, but companies must share their own data to access the aggregated, anonymised view. Access is a return for contributing, not proof that the return exceeds each participant’s costs.

RISE describes the Virtual Watch Tower (VWT) as a network in which participants control their data and share shipment-relevant information with authorised parties. Control does not remove the cost of contributing.

Rotterdam shows how the bill is shared

The Port of Rotterdam’s Secure Chain shows how charges can be shared. Companies digitally pass collection rights between authorised parties through an additional authorisation layer in Portbase’s services. This is a container-release process, not simply a visibility dashboard.

Secure Chain guidance specifies a €0.50 contribution per container from participating shipping lines/ship agents; Portbase’s published Secure Chain tariff dates the charge to 1 July 2025. Shippers and forwarders can choose free “Cargo Release Manager”, or paid “Cargo Controller Import”. Inland operators use “Hinterland Container Notification”; Portbase charges no additional fees for Secure Chain actions beyond that service’s subscription. 

Charges differ across the chain, and free access does not mean participation is costless. The Secure Chain’s guidance identifies separate software-vendor fees for required system connections.

The limit matters. When a shipping line releases a container through the Secure Chain, every party in that release chain must participate; an intermediate party cannot opt out while retaining the same collection process. This is a condition of collection. Voluntary networks face an additional test: their terms must keep essential contributors willing to participate. A tariff can allocate a bill; it cannot by itself secure that willingness.

The lesson is not to copy the tariff, but to separate service charges from participants’ work. Compulsory participation does not make that work costless. The published arrangement establishes neither who benefits most nor whether everyone earns a positive return.

Why pay for something already purchased?

A transport buyer has a legitimate objection. If timely shipment information is already part of a contract, why should it pay again? A supplier should not receive a second payment only because an agreed service is now delivered through a shared infrastructure.

Start by reading the agreement, not by designing a subsidy. Establish what information is owed, to whom, how often, and to what standard. Then identify what changes. Replacing repeated manual requests could reduce a partner’s workload; new checks or reporting requirements could increase it.

A powerful buyer may require additional work without increasing the price. A supplier may accept because the wider relationship remains worthwhile. You do not need equal gains or payment for every message.

But a contractual requirement does not create the capacity to fulfil it. Before relying on the information, check whether the agreed price, resources and processes support the required standard. Otherwise, procurement savings may leave essential work without the resources it needs.

Paying contributors can also reward avoidable manual work, encourage unnecessary messages or give an indispensable participant leverage to demand more. Pay for a defined, useful service, not continuing inefficiency. Simplify the process before negotiating how to share its cost.

Community ownership deserves no exemption from this discipline. If a commercial provider can deliver the required service more reliably and economically, use it. If the benefit does not justify the full cost, narrow the proposal or stop.

Four questions, not one

Asking who should pay risks collapsing four decisions into one price. Use the four-question framework below to review a proposed shared visibility service or an existing arrangement. For each question, make explicit the current arrangement, who is responsible, what remains unresolved and when it should be reviewed.

These questions interact, but should be answered separately. Free access does not make participation costless. An operating charge does not establish whether contributors’ additional work is covered. Paying more should not buy greater control. These are general principles, not a funding proposal for any named community.

1. Access

Who can use the shared service, and on what terms?

Access terms should encourage the participation the service needs. FLOW illustrates access conditional on contribution; the test is whether that return justifies the work.

2. Operating costs

Who commits to funding its availability, security, maintenance and support?

Members and backers must commit to funding the common service. Public support may be justified by demonstrable wider benefits.

Usage charges can recover identifiable costs, but usage is not a precise measure of value. Avoid rewarding the withholding of useful updates. Where benefits are spread across companies, agree who will fund the next operating period, the minimum commitment needed and a review date before incurring costs. Name the operator and rehearse a fallback if a major backer or contributor leaves. Promised collective value is not an operating budget.

3. Contributor work

Who does the work that keeps information useful, and what makes that contribution worth sustaining?

Those requesting information should agree its purpose and cost with contributors, then involve beneficiaries in supporting additional work. Options include service prices, help connecting systems, fewer duplicate requests or longer commitments. Credits against fees offer little to a contributor with no fees to pay. The return need not be a payment for data.

The publicly funded 2026 “Data Space Accelerator” study links payment for eligible companies to joining the Catena-X industrial data-sharing network, demonstrating actual data exchange and taking part in an accompanying survey. Funding entry is not the same as sustaining participation.

Assess each participant’s contribution and return over an operating period, not message by message. Access alone may not justify the effort; include benefits such as fewer enquiries or stronger customer relationships. Under contributor work, record the required tasks, responsible party, agreed return and correction process. If an essential contribution cannot be sustained, simplify the work or change the terms before relying on it.

4. Decision rights

Who can shape the rules and direction, and how are those rights agreed?

Backers should receive accounts and evidence that commitments are met. Agree who can change the rules, how decisions can be challenged and whether any special rights accompany funding. Make those rights explicit and reviewable, rather than an unspoken consequence of financial dependence.

Before the business depends on it

A workable bargain still needs a useful outcome. The IMO’s “Just In Time Arrival Guide” (2020) identifies contract terms that can prevent some voyage-chartered ships from adjusting speed, despite the opportunity to coordinate arrival. Earlier knowledge alone is not a saving.

Track selected alerts from checking the information to acting on it. Compare outcomes with a credible baseline, including the costs of providing and using information. Test readiness for rare disruption through explicit scenarios, not invented avoided losses. Use existing records where possible: measuring participation should not become another burden.

Make cooperation worth continuing

The objective is not to turn every exchange into an invoice. It is to make useful cooperation dependable: the service needs support, and its contributors need a reason to stay.

A clear bargain can protect that contribution while companies compete on price, reliability and service. Better standards may eliminate duplicate requests and repeated corrections. The best outcome is not a more elaborate way to divide the bill, but a smaller bill and stronger reasons to keep cooperating.

Funding the shared infrastructure is only the beginning. We have not secured visibility when we can see a shipment on a screen. We have secured it when the people who keep that picture reliable have a sound business reason to do so tomorrow.