supply chain

Gas Bottle Tracking: How IoT Improves Cylinder Visibility and Utilization

Gas bottles and cylinders are valuable reusable assets, but they are frequently dispersed across filling plants, depots, vehicles, distributors, customer sites, construction projects, hospitals, restaurants, and industrial facilities. Once a cylinder leaves the filling plant, operators may have limited visibility into where it is, who is responsible for it, whether it is full or empty, and when it will return.

A gas bottle tracking system creates a digital record for each cylinder and follows its operational journey. By combining serialized identification with scanning, gateways, and connected devices such as NB-IoT trackers, operators can reduce manual reconciliation and make decisions using current asset data rather than estimates.[2][4]

Why gas bottle tracking matters

Cylinder fleets represent substantial working capital. A cylinder that remains at a customer site for months, is returned through the wrong distributor, or disappears from the circulation network cannot be filled and used to generate revenue.

Effective cylinder management is also closely connected with maintenance, inspection, filling, storage, handling, and distribution practices. World Liquid Gas publishes industry guidance covering these operational responsibilities across the LPG cylinder lifecycle.[1] Road transport of dangerous goods is separately governed by requirements such as ADR in applicable jurisdictions.[3]

Tracking does not replace these safety and regulatory processes. It provides a more reliable information layer to support them.

What information should be associated with each cylinder?

A useful digital cylinder record can include:

  • A permanent cylinder or asset identifier

  • Owner and responsible operator

  • Gas type and cylinder specification

  • Filled, issued, returned, quarantined, or empty status

  • Filling plant and most recent fill event

  • Distributor, vehicle, customer, or site currently holding the asset

  • Inspection, test, and maintenance dates

  • Delivery and return timestamps

  • Reported damage, loss, or abnormal handling events

  • Links to relevant documentation and certificates

The GS1 Global Returnable Asset Identifier, or GRAI, is specifically designed to identify reusable assets and can support standardized identification across companies and systems.[2] A company can also use its own serialized identifiers where that is more appropriate, provided every cylinder remains uniquely and consistently identifiable.

How an IoT gas bottle tracking system works

There is no single hardware configuration that is correct for every cylinder fleet. The architecture should reflect the value of the cylinders, their movement frequency, the surrounding infrastructure, and the level of visibility required.

1. Give every cylinder a digital identity

Each cylinder receives a durable identifier, commonly encoded in a barcode, QR code, RFID tag, or another machine-readable label. Scanning that identifier creates events such as filled, loaded, delivered, collected, inspected, or quarantined.

This is usually the most economical foundation for fleet-wide traceability.

2. Track movements at operational checkpoints

Readers, mobile devices, or IoT gateways can register cylinders as they pass through filling lines, warehouses, loading areas, trucks, distributors, and customer locations. Instead of reconstructing movements from paper records, the platform builds a time-stamped chain of custody.

3. Add active tracking where it produces value

High-value cylinders, cylinder cages, pallets, transport frames, or mobile collections can be equipped with active trackers. Depending on the deployment, these devices may report location, movement, temperature, or other telemetry through cellular or low-power networks.

Sensefinity's connected tracking approach combines IoT devices with a digital supply-chain management platform, allowing asset events and condition data to be viewed within the same operational context.[4][5]

An active location tracker does not automatically know how much gas remains inside a cylinder. Fill-level visibility requires an appropriate pressure, weight, flow, or level sensor and must be engineered for the specific cylinder, gas, and safety environment.

4. Turn events into operational workflows

Collecting data is only useful when the system can act on it. Business rules can identify:

  • Cylinders that have not returned within an expected period

  • Assets delivered to the wrong location

  • Unusually long distributor or customer dwell times

  • Missing delivery or collection scans

  • Cylinders approaching inspection or maintenance dates

  • Unexpected movement outside an authorized area

  • Disagreement between physical scans and inventory records

Teams can then investigate exceptions instead of manually checking every cylinder.

Operational benefits

Improve cylinder fleet utilization

Knowing which cylinders are available, filled, in transit, held by customers, or overdue helps operators understand the real capacity of the fleet. This can reduce unnecessary cylinder purchases and improve filling and distribution planning.

Reduce loss and unrecorded transfers

A time-stamped history makes it easier to determine where custody changed and where an asset was last recorded. This does not prevent every loss, but it narrows investigations and creates accountability across the distribution network.

Accelerate returns

Operators can identify customers or distributors with unusually long return cycles and introduce collection reminders, deposit rules, service-level agreements, or scheduled pickups based on actual dwell-time data.

Maintain accessible asset histories

Inspection, filling, repair, delivery, and return events can be associated with the same serialized cylinder. This creates a more complete operational history than disconnected spreadsheets and paper documents.

Improve customer service

Customer-service teams can answer practical questions such as whether cylinders were delivered, which assets remain at a location, and when a collection occurred. Disputes can be investigated using shared event records rather than memory.

LPG, industrial gas, and medical gas deployments are different

An LPG exchange network may manage very large numbers of standardized cylinders through distributors and retail points. An industrial-gas operator may need to track higher-value cylinders moving between factories, laboratories, workshops, and construction sites. Medical-gas operations can involve additional handling, quality, and availability requirements.

The same traceability principles apply, but the identification method, hardware, data retention, alerts, and operating procedures should be adapted to each use case. Equipment must also be selected and installed according to the relevant hazardous-area, transport, and safety requirements. An IoT project should never introduce unapproved equipment into a hazardous environment.

A practical implementation roadmap

A gas bottle tracking project can begin without instrumenting every cylinder with an active device.

  1. Map the cylinder lifecycle. Document filling, storage, loading, delivery, exchange, collection, inspection, repair, and retirement.

  2. Create a reliable asset register. Assign one persistent identity to each cylinder and remove duplicate or incomplete records.

  3. Instrument the main checkpoints. Start with fill, dispatch, delivery, and return events.

  4. Pilot active tracking selectively. Apply connected trackers to high-value assets, transport cages, routes, or customer segments where losses and delays are greatest.

  5. Define exception rules. Decide what constitutes an overdue return, unexpected location, missing scan, or maintenance risk.

  6. Integrate existing systems. Connect relevant events to ERP, inventory, customer-service, maintenance, or billing workflows.

  7. Measure operational outcomes. Track return-cycle time, lost assets, fleet utilization, scan completeness, and investigation time.

From cylinder inventory to a visible asset network

Gas bottle tracking is not simply a map showing dots. Its real value comes from connecting identity, custody, location, operational status, and lifecycle history.

Sensefinity can help gas suppliers and cylinder-fleet operators design a tracking architecture that combines serialized assets, IoT connectivity, gateways, and operational software. The objective is to begin with the most valuable visibility gaps and expand only where the resulting data supports a clear operational decision.

To discuss a pilot for LPG, industrial, or medical gas cylinders, contact Sensefinity and identify one route, depot, distributor network, or customer segment where missing assets or slow return cycles have a measurable cost.

Sources

[1] World Liquid Gas — Guide to Good Industry Practices for LPG Cylinder Management

[2] GS1 — Global Returnable Asset Identifier

[3] UNECE — ADR 2025

[4] Sensefinity — NB-IoT Trackers

[5] Sensefinity — Supply Chain Management Platform

The $647,420 Nike Pickup That Looked Legitimate — Until It Wasn’t

A driver arrived at a Memphis facility with documents that appeared sufficient to collect a Dallas-bound shipment of Nike merchandise. The cargo left the dock. But the driver was not completing the authorized movement, the paperwork was fraudulent, and the shipment headed towards the Chicago area instead.

The fictitious pickup happened on 21 August 2026. Nike contacted the Cook County Sheriff’s Police Organized Retail Crime Unit two days later, and investigators ultimately recovered approximately $647,420 in merchandise at a distribution facility in Des Plaines, Illinois, together with a stolen trailer. At the time of the report, no arrests or charges had been announced and the investigation remained active.[1]

This was not a failure of a lock. It was a failure of trust: the wrong person presented documents that looked right long enough for legitimate staff to release valuable cargo.

When a document looks right but custody is wrong

Traditional shipping documents describe an intended transaction. They do not necessarily prove that the person standing at the dock is the person currently authorized to execute it.

A convincing PDF, bill of lading or pickup reference can be copied, altered or generated from compromised information. The Nike incident is especially instructive because the shipment did not first disappear from an unattended parking area. It was handed over at origin after false paperwork made an unauthorized collection appear legitimate.[1]

It also sits within a wider pattern. In a separate Nike case, federal prosecutors alleged that unauthorized UPS labels were used to divert products from the company’s Memphis distribution operation. Reporting on that case describes “ghost labels” covering original shipping labels and redirecting packages to private addresses; those allegations have not been proven in court.[2]

The common weakness is clear: when operational truth lives only in editable labels, emails and documents, whoever can reproduce the appearance of authority may be able to redirect the physical goods.

Blockchain should verify the handover, not archive the fraud

Simply uploading a document to a blockchain is not enough. If false information is accepted at the start, an immutable database only preserves a false statement.

The useful model is different: create a verifiable digital chain of custody and require every physical handover to match its current authorized state. Before a warehouse releases a shipment, the system should be able to answer five questions:

  1. Which exact shipment is being collected? A unique digital identity binds the order, cargo unit, pallet or container to the operational record.

  2. Who is authorized right now? The approved carrier, driver, vehicle and pickup window are recorded by trusted parties, rather than inferred from a document presented at the gate.

  3. Has anything changed? A destination, carrier or collection instruction cannot be silently overwritten. A new authorization becomes a visible, time-stamped event.

  4. Is this handover happening in the expected place and time? A one-time release credential can be bound to the shipment, facility and pickup window.

  5. What happened after release? Independent IoT data confirms departure, movement and route exceptions instead of relying only on status messages from the party holding the load.

In that model, a counterfeit document is no longer the authority. It is merely a claim that must match the shared, verifiable record.

What the Nike pickup could have looked like

Imagine the same collection with digitally verified custody controls.

At the Memphis gate, the operator scans the shipment identifier and the driver’s one-time pickup credential. The system checks both against the latest authorization recorded for that shipment. If the driver, carrier, vehicle, destination or collection window does not match, the cargo is not released and the discrepancy is escalated through a known channel.

If all checks pass, the handover is signed as a new custody event. A cargo-level tracker then confirms when the load leaves the facility. A Dallas-bound shipment moving towards Chicago crosses a route or geofence rule, generating an alert while intervention may still be possible.

The incident report says investigators recovered the Nike merchandise after the diversion was identified.[1] A verified release process could have moved the decisive control point earlier—from recovery after the theft to refusal at the dock. No technology can guarantee prevention, but forged paperwork becomes much less useful when it cannot satisfy the digital authorization and physical-event checks required for release.

Sensefinity connects the record to the real cargo

The hard part of supply-chain blockchain is connecting digital claims to physical events. Sensefinity addresses that gap with IoT “oracles”: trackers and sensors that collect cargo location and environmental data, register it in the Sensefinity platform and can also write selected information to a logistics blockchain. Authorized partners can access the shared record without requiring direct access to one another’s internal IT systems.[3]

Our Blockchain solution provides the tamper-evident event layer. Our NB-IoT trackers locate assets on land and at sea and can issue alerts when an asset enters or leaves a configured geofence.[4]

Together, those capabilities support a stronger release and custody process:

  • digitally signed shipment and pickup authorizations;

  • an auditable history of instruction changes;

  • verified handovers between shipper, carrier, warehouse and receiver;

  • cargo-level location evidence independent of the truck or transport paperwork;

  • immediate alerts for unauthorized departure, route deviation or unexpected arrival;

  • a provenance record that follows the goods beyond a single logistics provider.

Trust the verified event, not the convincing document

Fictitious pickup succeeds in the gap between what a document says and what the operation can prove. Closing that gap requires more than checking logos, signatures and reference numbers. It requires a shared source of truth, a controlled handover and independent evidence from the cargo itself.

The $647,420 Nike recovery had a positive outcome. The more important objective for the next shipment is to make forged paperwork fail before the doors close and the truck leaves.

Talk to Sensefinity about combining IoT visibility, geofencing and blockchain-backed chain of custody for high-value cargo.

Sources

  1. $647K Nike cargo recovered near Chicago after fraudulent Memphis pickup — FreightWaves

  2. How Nike insiders were charged in a lucrative sneaker theft conspiracy — Los Angeles Times

  3. Sensefinity Logistics Blockchain

  4. Sensefinity NB-IoT Trackers

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