OPTEL keg tracking needs separate asset and product-lot histories

Give the reusable asset its own identity

The direct answer is that each keg needs a stable asset identifier and lifecycle that survives repeated fills. Record the asset type, owner, manufacturer, material, capacity, serial or encoded identifier, commissioning date, current custodian and location, status, condition, permitted uses, inspection and maintenance requirements, and retirement evidence. Identifier replacement, duplicate tags, damaged marks, pooled ownership, and lost assets need explicit exception paths rather than a newly assigned history that conceals uncertainty.

Asset events should state what happened, where, when, by whom, under which business transaction, and with what source evidence. Issue, receipt, empty return, in-transit, cleaning, inspection, repair, filled, quarantined, lost, and retired are different states. A location scan can show that an identifier was observed; it does not prove custody, contents, cleanliness, condition, or successful return unless those facts were captured and acknowledged by the responsible party.

Create a new product-use link for every fill

Every fill should create a bounded relationship between the keg and the product lot or batch loaded into it. Preserve product and lot identifiers, formula or item version where relevant, production or packaging order, fill time, site and line, source or parent lots, quantity, unit, operator, cleaning and release evidence, label or code applied, destination, and any split, blend, rework, or transfer. The keg identifier should point to that use without becoming the product-lot identifier itself.

The separation matters because one keg can carry different products over time, while one product lot can fill many kegs and other package types. A return event for an empty asset does not prove which product was consumed, wasted, transferred, or remained in the container. Likewise, a complete lot genealogy does not establish where every empty keg is, whether it is serviceable, or who must return it. Joins between the histories should be effective-dated and cardinality-aware.

Govern custody, condition, and product disposition separately

Custody evidence should link dispatch and receipt events, sender and recipient, location, carrier or route, time, quantity of assets, discrepancies, damage, and acknowledgement. Forecasts and inventory views should expose unconfirmed movements, stale observations, unidentified assets, and disputed custody instead of counting every expected return as available stock. Maintenance should retain inspection criteria, findings, cleaning or sanitation evidence, repair, next due date, release authority, and any restriction on reuse.

Food disposition stays in the product history. A safety or quality hold may affect filled kegs, other packages, intermediate material, and later transformations based on lot and event links—not simply every asset at a location. Conversely, a damaged or unclean keg can require an asset hold even when its prior product lot was acceptable. Recall scope, regulatory notification, consumer action, recovery, and destruction remain accountable food-safety decisions; fleet return status is only one operational input.

Test one keg across two fills and a failed return

A representative evaluation should fill one keg from lot A, ship it to a retailer, record partial product disposition, return it with a damaged tag, clean and repair it, assign a verified replacement identifier, fill it from lot B, and then place lot B on hold while the keg is in transit. Reviewers should reproduce identity continuity, custody, quantity, condition, maintenance, both fill links, product genealogy, exceptions, asset availability, and product disposition without merging the histories.

OPTEL's official page supports the attributed positioning about digital traceability, reusable-packaging management, keg returns, fleet visibility, forecasting, inventory, location, maintenance, and related supply-chain uses. It does not establish identifier uniqueness, event capture, custody, condition, cleaning, product-lot genealogy, quantity reconciliation, return completion, asset availability, recall scope, regulatory compliance, or food safety. Qualified food-safety, quality, traceability, packaging, logistics, operations, information-technology, regulatory, and legal owners retain their decisions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.