blockchain

A New Destination Is a New Custody Act

A freight destination is not just an address field. Changing it alters the authorised route, the intended consignee and the point at which custody passes to another party. When that decision lives only in an email, a phone call or an overwritten TMS field, a fraudulent redirection can look like routine administration.

Replace silent edits with signed events

We believe every destination change should create a new custody act tied to the lot: previous destination, new destination, reason, requesting organisation and person, timestamp, approval policy and a cryptographic reference to the preceding event. The old instruction remains visible. Revocations, refusals and corrections become additional events rather than rewritten history.

Strong authentication must come before signature. For sensitive loads, that means step-up or multi-factor authentication, explicit confirmation of what is being signed and dual approval when value, product or route justifies it. A valid login is not enough; the signer must also be authorised to redirect that specific lot.

Anchor proof, protect commercial data

With Sensefinity's blockchain layer, the signed document can remain access-controlled off-chain while its hash, version and timestamp are anchored in a tamper-resistant history. Authorised partners can verify that the instruction presented is the one that was signed and identify what came before it without publishing sensitive commercial details.

Blockchain cannot prove that a bad instruction was true or prevent a compromised credential. Its value is narrower and more useful: changes, sequence and conflicts become much harder to hide.

Connect authorised intent to physical movement

The signed act defines what should happen. Cargo telemetry shows what is happening. Sensefinity's Cargo Safety capabilities can detect unplanned stops and unauthorised access and support asset-level tracking. Comparing those signals with the latest authorised destination creates an actionable exception when a load leaves its approved route before a valid change exists.

Read the full Prova article

The full Prova analysis explains the event model, authentication and authorisation controls, blockchain anchoring, a seven-step operating workflow and how this approach aligns with the move toward authenticated, auditable freight data.

Read “A destination change is a custody act — and it should be signed” on Prova.

A destination change should never erase the past. It should add a signed, attributable and verifiable decision to the lot's custody history.

EPCIS in 2026: The State of Supply Chain Event Data

Supply chains have no shortage of data. They have a shortage of data that different companies can interpret in the same way.

That is the problem EPCIS was built to solve. GS1 describes EPCIS as its flagship standard for sharing the what, when, where, why and how of products and assets across organisations. EPCIS 2.0 extends that event model to sensor readings, certifications, JSON/JSON-LD, REST interfaces and GS1 Digital Link identifiers.[1]

This report assesses where the standard stands in 2026, what is driving implementation, and where projects still break down. It is a desk-research snapshot, not a vendor adoption survey. Our evidence comes from current GS1 specifications and public regulatory material.

The 2026 snapshot

Signal What the evidence says Industry implication Standard maturity EPCIS 2.0 was ratified in June 2022; its implementation guideline followed in March 2023 and the GS1 EPCIS Sandbox launched in February 2024.[1] The technical foundation is established. The main risk has moved from specification maturity to implementation discipline. Condition data EPCIS 2.0 can carry timestamped sensor data, including readings used in cold chains and industrial IoT.[1] Location events and temperature evidence can travel in one interoperable event stream. Certification data The standard supports certification details associated with products, organisations, locations, harvests and shipments.[1] Compliance evidence can be linked to the event where it matters rather than stored in an isolated document repository. API accessibility JSON/JSON-LD and REST capture/query interfaces are part of EPCIS 2.0.[1] Integration no longer has to start with XML-heavy, batch-only architecture. Regulatory pull The FDA Food Traceability Rule requires covered actors to retain Key Data Elements linked to Critical Tracking Events and provide requested information to FDA within 24 hours.[2] Regulated traceability is becoming an event-data problem, even where the law does not mandate EPCIS by name. DPP convergence The EU Digital Product Passport is being introduced progressively and will carry lifecycle, origin, material and environmental information for selected product groups.[11] Product master data and supply chain events will increasingly need a common identity layer.

Our finding: EPCIS covers five evidence layers, but governance remains outside the standard

We reviewed EPCIS 2.0 against five practical evidence layers required by modern cargo and product programmes.

Evidence layer EPCIS 2.0 coverage What still has to be designed Identity Native support through GS1 identifiers and Digital Link URI syntax.[1] Identifier ownership, granularity and partner onboarding. Business events Native event model for status, movement, transformation, aggregation and chain of custody.[1] A shared event vocabulary and rules for late or corrected events. Physical condition Native sensor-data support.[1] Device calibration, sampling frequency, alert thresholds and proof that a sensor remained attached to the cargo. Claims and certifications Native certification fields.[1] Who may issue a claim, how it expires and how it is revoked. Exchange JSON/JSON-LD and REST interfaces.[1] Access control, commercial permissions, retention and cross-company service levels.

The conclusion is useful because it separates a standards question from an operating-model question. EPCIS can express all five layers. It cannot decide which partner is trusted, how often a sensor should report, who pays for data retention or which event wins when two systems disagree.

Regulation is pushing companies toward event-level traceability

The strongest implementation pressure is no longer a generic promise of visibility. It is the need to reconstruct specific product histories quickly.

The FDA's Food Traceability Rule applies additional recordkeeping to foods on the Food Traceability List. Covered organisations must associate Key Data Elements with Critical Tracking Events and be able to provide the information to FDA within 24 hours or another agreed period.[2] GS1's own food-safety guidance maps GTIN, GLN and EPCIS event data to this need for product, location and movement records.[18]

The compliance date was originally January 20, 2026. FDA subsequently proposed a 30-month extension to July 20, 2028, and Congress directed the agency not to enforce the rule before that date.[2] That extension is preparation time, not a reason to postpone architecture. Partner identifiers, event semantics and exception workflows usually take longer than the API connection.

Europe is creating a second source of pressure. Under the Ecodesign for Sustainable Products Regulation, Digital Product Passports will be introduced through product-specific rules. The Commission lists batteries first, followed by product groups such as textiles, iron and steel, construction products and others.[8][11] A passport tells stakeholders what a product is and what must be known about it. EPCIS can supply the time-ordered operational evidence of what happened to it.

The adoption gap is not capture. It is continuity.

Most pilots can generate a shipping event. Far fewer can maintain a trustworthy history through repacking, consolidation, subcontracted transport and handover to another platform.

Four gaps appear repeatedly:

  1. Identity breaks at aggregation. A pallet identifier is recorded, but the link between item, case, pallet and container is incomplete.

  2. Condition data lacks business context. A temperature reading exists, but the system cannot say which shipment leg, custody holder or product lot it belongs to.

  3. Partners use different event meanings. "Received" may mean arrival at the gate, unloading, quality acceptance or ERP posting.

  4. Corrections are not governed. Event histories need a controlled way to handle duplicates, delayed data and amended records without erasing the audit trail.

EPCIS has the structures needed to address these problems. Implementers still need to agree on the operating rules.

A practical 90-day EPCIS readiness test

A company does not need a multi-year transformation programme to learn whether its data is ready. A useful first test follows one real shipment and asks five questions:

  • Can every tracked object and logistics unit be identified consistently?

  • Can the business record packing, shipping, receiving and transformation events using shared vocabulary?

  • Can sensor readings be tied to the correct object, place and time?

  • Can one external partner query only the events it is authorised to see?

  • Can the team reconstruct the shipment history without manually joining spreadsheets?

If any answer is no, the pilot has identified a concrete interoperability gap. That is more valuable than a polished dashboard built on ambiguous data.

Where Sensefinity fits

Sensefinity already supports EPCIS supply chain events and can combine them with location, temperature and humidity data. Our NB-IoT trackers create observations from the physical journey; EPCIS gives those observations a shared business context.

The result is not simply another track-and-trace screen. It is an event history that can be exchanged with customers, suppliers and compliance systems without forcing every participant into the same application.

What to watch next

During the next implementation cycle, three developments deserve attention:

  • convergence between EPCIS event histories and Digital Product Passport records;

  • practical use of sensor and certification fields beyond proof-of-concept projects;

  • partner governance, especially access rights, event correction and long-term availability.

The standard is ready enough. The differentiator in 2026 is whether companies can keep identity, condition and custody evidence connected after cargo leaves their own system.

Methodology and limitations

This report was prepared on September 5, 2026 from public GS1, FDA and EU sources. The readiness matrix is Sensefinity's analysis of features documented in EPCIS 2.0; it is not an adoption-rate survey. We found no authoritative global count of production EPCIS 2.0 deployments and have not invented one.

Sources

[1] https://www.gs1.org/standards/epcis — EPCIS & CBV | GS1 [2] https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods — FSMA Food Traceability Rule | FDA [8] https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R1781 — Regulation (EU) 2024/1781 (ESPR) [11] https://single-market-economy.ec.europa.eu/single-market/digital-product-passport_en — Digital Product Passport | European Commission [18] https://gs1.org/public-policy/leveraging-GS1-standards-to-meet-key-food-safety-challenges — Leveraging GS1 standards for food safety | GS1

From Tracking to Insurability: How Real-Time Cargo Data Changes Risk

Cargo insurance has traditionally relied on information collected before and after a journey. The shipper declares the goods and route, the insurer evaluates historical risk, and—if something goes wrong—the parties reconstruct the incident from documents, emails, photographs and testimony.

The most important part of the journey is often missing: reliable data from the cargo while the risk is unfolding.

Connected trackers and sensors change that model. They can report location, temperature, humidity, shock and other conditions in real time, generating alerts before an exception becomes a total loss. They can also preserve an evidence trail for claims, liability analysis and future underwriting.

This is the shift from tracking to insurability: using operational data not only to find cargo, but to understand and actively reduce the risk attached to it.

Insurance should help prevent the claim

Traditional insurance provides financial protection after a covered loss. Connected insurance can add a second layer: earlier warning while intervention is still possible.

Consider a refrigerated pharmaceutical shipment. A temperature alarm at the destination may confirm that the product is unusable. An alert during transport may allow the carrier to repair the refrigeration unit, move the cargo or protect the remaining shelf life.

The same principle applies to theft, route deviation, excessive humidity, impact and unexpected dwell time. The value of real-time monitoring is not simply that it records the event. It gives operators an opportunity to change the outcome.

Allianz Commercial has described cargo tracking as a risk-management tool that enables companies to act when goods are damaged or move off route. It also notes that real-time analysis of sensor data can support mitigation—for example, responding to excessive moisture or temperature before the damage becomes worse.[2]

At Sensefinity, this is the foundation of our Insurance of Things approach: connect the insured asset, detect harmful conditions and turn real-time data into preventive action.[3]

Better evidence can mean faster claims

When prevention is no longer possible, data still matters.

A cargo claim often raises difficult questions:

  • When did the damage begin?

  • Where was the shipment at that moment?

  • Was the temperature already outside specification before a handover?

  • Did a severe shock occur during loading, road transport or terminal handling?

  • Was the container opened outside an authorized location?

  • Which organization had custody when the event occurred?

Without an independent record, each participant may hold a different version of the journey. The result can be long correspondence, expert investigation and delayed settlement.

TT Club identifies specific insurance benefits from smart-container data. Real-time visibility can help insurers understand the volume and condition of units at risk, while an audit trail can help identify the origin of an incident or a potentially liable party. According to TT Club, this can reduce lengthy investigations or provide earlier corroboration of findings.[1]

Allianz Commercial likewise notes that IoT devices and telematics can help insurers assess risk, validate claims more efficiently and evaluate liability more accurately. Its analysis also connects real-time event data with stronger fraud detection and faster claims processing.[6]

A sensor record does not decide coverage by itself; policy terms and professional claims assessment still apply. But it can replace uncertainty with evidence.

From generalized assumptions to shipment-level risk

Cargo policies must often price risk using broad categories: commodity, route, mode of transport, packaging, claims history and security procedures. These factors remain important, but they do not always describe what happens on an individual journey.

Two identical shipments on the same route can have very different risk outcomes. One may remain continuously monitored, follow authorized geofences and stay within temperature limits. The other may experience an unexplained stop, a route change and a prolonged condition excursion.

Real-time operational data creates the possibility of evaluating those differences. Over time, insurers and cargo owners can identify patterns such as:

  • routes or handovers associated with repeated exceptions;

  • facilities where dwell time or temperature excursions are more frequent;

  • packaging configurations that experience excessive shock;

  • security procedures that reduce unauthorized movement;

  • operators that consistently maintain agreed conditions.

This does not guarantee lower premiums. Pricing and coverage remain decisions for insurers and brokers. It does, however, give a well-managed shipper better evidence of its actual controls and performance—and gives the insurer better information for approval, terms and risk engineering.

The cargo needs its own source of truth

Vehicle telematics is valuable, but the truck and the cargo are not the same insured asset.

A trailer may be found after the pallets have been removed. A vehicle can follow the correct route while the goods inside experience excessive heat or humidity. A container can arrive with no visible external damage even though its contents suffered a critical shock.

Cargo-level monitoring closes this gap. Sensefinity’s NB-IoT trackers and smart sensors can be attached to containers, pallets, crates or selected high-value packages. They support location reporting, configurable geofence alerts, environmental thresholds and datalogging across long journeys.[4]

The result is a journey record centred on what is actually insured: the goods.

Trusted sharing across multiple parties

Insurance claims involve organizations that do not necessarily share the same systems: cargo owners, carriers, freight forwarders, warehouses, terminals, surveyors, brokers and insurers.

Data must therefore be useful without requiring every participant to surrender access to its internal infrastructure.

Sensefinity’s logistics blockchain can register selected events collected by trackers and sensors, including location and environmental conditions. Authorized partners can access a shared, tamper-resistant record without needing direct access to one another’s operational systems.[5]

This is particularly relevant to chain-of-custody questions. A trusted event history can support audits, clarify handovers and reduce disputes over which version of the journey is correct.

The technology should not create a new data burden. The objective is to preserve the events that matter: threshold breaches, route deviations, custody changes and other exceptions connected to the insured risk.

A practical Insurance of Things model

A connected cargo-insurance program can be built in six steps:

  1. Identify the critical risk. Theft, temperature, humidity, shock, delay or unauthorized access.

  2. Instrument the insured asset. Select the container, pallet, crate or item that must remain visible.

  3. Define operational thresholds. Establish expected routes, geofences, condition limits and escalation rules.

  4. Act on alerts. Assign named responders who can intervene before the loss becomes irreversible.

  5. Preserve the evidence. Maintain a reliable timeline for claims, audits and performance analysis.

  6. Learn from repeated journeys. Use historical data to improve routes, packaging, partners and risk controls.

This model creates value for both sides. The cargo owner gains earlier warning and stronger evidence. The insurer gains better visibility into risk quality, loss-prevention measures and the circumstances surrounding a claim.

Insurance becomes part of the operation

The future of cargo insurance is not a policy document disconnected from the physical journey. It is a risk partnership supported by live information.

TT Club’s vision of smart containers includes real-time condition data, geofences, early alerts and better audit trails for insurers.[1] Allianz sees sensor information supporting loss mitigation, efficient claims validation and more accurate risk assessment.[2][6]

Sensefinity brings those capabilities to the cargo level. Through trackers, sensors, analytics, alerts and trusted data sharing, our Insurance of Things approach connects financial protection with operational prevention.

Because the best claim is not merely the one settled quickly. It is the loss detected early enough to prevent.

Explore Sensefinity’s Insurance of Things solution or talk to us about a connected risk program for your cargo.

Sources

[1] TT Club, “TT Talk — What can we get out of a box?”: https://www.ttclub.com/news-and-resources/news/article/tt-talk-what-can-we-get-out-of-a-box/

[2] Allianz Commercial, “Sensors could improve navigation, supply chain and cargo risk management”: https://commercial.allianz.com/news-and-insights/expert-risk-articles/sensors-supply-chain-and-risk-management.html

[3] Sensefinity, “Insurance of Things”: https://www.sensefinity.com/insurance-of-things

[4] Sensefinity, “NB-IoT Trackers”: https://www.sensefinity.com/nbiot-trackers

[5] Sensefinity, “Blockchain”: https://www.sensefinity.com/blockchain

[6] Allianz Commercial, “Edge computing and cyber security”: https://commercial.allianz.com/content/dam/onemarketing/commercial/commercial/reports/commercial-edge-computing-and-cyber-security-report.pdfCargo insurance has traditionally relied on information collected before and after a journey. The shipper declares the goods and route, the insurer evaluates historical risk, and—if something goes wrong—the parties reconstruct the incident from documents, emails, photographs and testimony.

The most important part of the journey is often missing: reliable data from the cargo while the risk is unfolding.

Connected trackers and sensors change that model. They can report location, temperature, humidity, shock and other conditions in real time, generating alerts before an exception becomes a total loss. They can also preserve an evidence trail for claims, liability analysis and future underwriting.

This is the shift from tracking to insurability: using operational data not only to find cargo, but to understand and actively reduce the risk attached to it.

Insurance should help prevent the claim

Traditional insurance provides financial protection after a covered loss. Connected insurance can add a second layer: earlier warning while intervention is still possible.

Consider a refrigerated pharmaceutical shipment. A temperature alarm at the destination may confirm that the product is unusable. An alert during transport may allow the carrier to repair the refrigeration unit, move the cargo or protect the remaining shelf life.

The same principle applies to theft, route deviation, excessive humidity, impact and unexpected dwell time. The value of real-time monitoring is not simply that it records the event. It gives operators an opportunity to change the outcome.

Allianz Commercial has described cargo tracking as a risk-management tool that enables companies to act when goods are damaged or move off route. It also notes that real-time analysis of sensor data can support mitigation—for example, responding to excessive moisture or temperature before the damage becomes worse.[2]

At Sensefinity, this is the foundation of our Insurance of Things approach: connect the insured asset, detect harmful conditions and turn real-time data into preventive action.[3]

Better evidence can mean faster claims

When prevention is no longer possible, data still matters.

A cargo claim often raises difficult questions:

  • When did the damage begin?

  • Where was the shipment at that moment?

  • Was the temperature already outside specification before a handover?

  • Did a severe shock occur during loading, road transport or terminal handling?

  • Was the container opened outside an authorized location?

  • Which organization had custody when the event occurred?

Without an independent record, each participant may hold a different version of the journey. The result can be long correspondence, expert investigation and delayed settlement.

TT Club identifies specific insurance benefits from smart-container data. Real-time visibility can help insurers understand the volume and condition of units at risk, while an audit trail can help identify the origin of an incident or a potentially liable party. According to TT Club, this can reduce lengthy investigations or provide earlier corroboration of findings.[1]

Allianz Commercial likewise notes that IoT devices and telematics can help insurers assess risk, validate claims more efficiently and evaluate liability more accurately. Its analysis also connects real-time event data with stronger fraud detection and faster claims processing.[6]

A sensor record does not decide coverage by itself; policy terms and professional claims assessment still apply. But it can replace uncertainty with evidence.

From generalized assumptions to shipment-level risk

Cargo policies must often price risk using broad categories: commodity, route, mode of transport, packaging, claims history and security procedures. These factors remain important, but they do not always describe what happens on an individual journey.

Two identical shipments on the same route can have very different risk outcomes. One may remain continuously monitored, follow authorized geofences and stay within temperature limits. The other may experience an unexplained stop, a route change and a prolonged condition excursion.

Real-time operational data creates the possibility of evaluating those differences. Over time, insurers and cargo owners can identify patterns such as:

  • routes or handovers associated with repeated exceptions;

  • facilities where dwell time or temperature excursions are more frequent;

  • packaging configurations that experience excessive shock;

  • security procedures that reduce unauthorized movement;

  • operators that consistently maintain agreed conditions.

This does not guarantee lower premiums. Pricing and coverage remain decisions for insurers and brokers. It does, however, give a well-managed shipper better evidence of its actual controls and performance—and gives the insurer better information for approval, terms and risk engineering.

The cargo needs its own source of truth

Vehicle telematics is valuable, but the truck and the cargo are not the same insured asset.

A trailer may be found after the pallets have been removed. A vehicle can follow the correct route while the goods inside experience excessive heat or humidity. A container can arrive with no visible external damage even though its contents suffered a critical shock.

Cargo-level monitoring closes this gap. Sensefinity’s NB-IoT trackers and smart sensors can be attached to containers, pallets, crates or selected high-value packages. They support location reporting, configurable geofence alerts, environmental thresholds and datalogging across long journeys.[4]

The result is a journey record centred on what is actually insured: the goods.

Trusted sharing across multiple parties

Insurance claims involve organizations that do not necessarily share the same systems: cargo owners, carriers, freight forwarders, warehouses, terminals, surveyors, brokers and insurers.

Data must therefore be useful without requiring every participant to surrender access to its internal infrastructure.

Sensefinity’s logistics blockchain can register selected events collected by trackers and sensors, including location and environmental conditions. Authorized partners can access a shared, tamper-resistant record without needing direct access to one another’s operational systems.[5]

This is particularly relevant to chain-of-custody questions. A trusted event history can support audits, clarify handovers and reduce disputes over which version of the journey is correct.

The technology should not create a new data burden. The objective is to preserve the events that matter: threshold breaches, route deviations, custody changes and other exceptions connected to the insured risk.

A practical Insurance of Things model

A connected cargo-insurance program can be built in six steps:

  1. Identify the critical risk. Theft, temperature, humidity, shock, delay or unauthorized access.

  2. Instrument the insured asset. Select the container, pallet, crate or item that must remain visible.

  3. Define operational thresholds. Establish expected routes, geofences, condition limits and escalation rules.

  4. Act on alerts. Assign named responders who can intervene before the loss becomes irreversible.

  5. Preserve the evidence. Maintain a reliable timeline for claims, audits and performance analysis.

  6. Learn from repeated journeys. Use historical data to improve routes, packaging, partners and risk controls.

This model creates value for both sides. The cargo owner gains earlier warning and stronger evidence. The insurer gains better visibility into risk quality, loss-prevention measures and the circumstances surrounding a claim.

Insurance becomes part of the operation

The future of cargo insurance is not a policy document disconnected from the physical journey. It is a risk partnership supported by live information.

TT Club’s vision of smart containers includes real-time condition data, geofences, early alerts and better audit trails for insurers.[1] Allianz sees sensor information supporting loss mitigation, efficient claims validation and more accurate risk assessment.[2][6]

Sensefinity brings those capabilities to the cargo level. Through trackers, sensors, analytics, alerts and trusted data sharing, our Insurance of Things approach connects financial protection with operational prevention.

Because the best claim is not merely the one settled quickly. It is the loss detected early enough to prevent.

Explore Sensefinity’s Insurance of Things solution or talk to us about a connected risk program for your cargo.

Sources

[1] TT Club, “TT Talk — What can we get out of a box?”: https://www.ttclub.com/news-and-resources/news/article/tt-talk-what-can-we-get-out-of-a-box/

[2] Allianz Commercial, “Sensors could improve navigation, supply chain and cargo risk management”: https://commercial.allianz.com/news-and-insights/expert-risk-articles/sensors-supply-chain-and-risk-management.html

[3] Sensefinity, “Insurance of Things”: https://www.sensefinity.com/insurance-of-things

[4] Sensefinity, “NB-IoT Trackers”: https://www.sensefinity.com/nbiot-trackers

[5] Sensefinity, “Blockchain”: https://www.sensefinity.com/blockchain

[6] Allianz Commercial, “Edge computing and cyber security”: https://commercial.allianz.com/content/dam/onemarketing/commercial/commercial/reports/commercial-edge-computing-and-cyber-security-report.pdf

Metro-Chef Olaf Koch: „Technologie ohne Kundennähe ist wertlos“

Metro-Chef Olaf Koch: „Technologie ohne Kundennähe ist wertlos“

Das Startup Sensefinity aus unserem Accelerator hat einen Sensor entwickelt, der beispielsweise an einer Shrimps-Box angebracht werden kann. Er zeichnet die Position, Temperatur, Feuchtigkeit und den Luftdruck entlang der gesamten Lieferkette auf. Wenn die Temperatur sinkt, sendet der Sensor sofort einen Alarm aus und das System ermittelt daraufhin den genauen Standort der Box. Dabei setzt das Startup Blockchain ein, um ein unveränderbares und prüffähiges Protokoll erstellen zu können.