A product crosses a border. It carries documentation: a phytosanitary certificate confirming it is free of certain pests, a lab report showing compliance with maximum residue limits, a trade invoice listing quantity, price, and origin, a certificate of conformity from an accredited body, and a traceability record that can locate the product at every point in its supply chain.
Each of these documents answers a question. Is this product safe to import? Does it meet the destination market's threshold? Where has it been? Can it be recalled if necessary? The answers are correct. The systems that produce them are well-designed and, in most cases, well-functioning.
None of these documents answers a different question: what is this product?
Not what category it belongs to. Not whether it is permitted. What it actually is — what variety, what practices, what inputs, what season, what producer, what distinguishes it from the next shipment in the same category at the same price.
That question is increasingly asked. By procurement bodies comparing suppliers. By trade agencies promoting origin products. By institutional buyers building sustainable supply chains. By health authorities assessing what populations are actually consuming. By regulators trying to understand not just whether a product is compliant, but whether the information about it is complete enough for the decisions that depend on it.
The systems that would answer this question do not, for the most part, exist. Not because the information is absent — producers often know a great deal about their products — but because the information that exists at source does not travel in a form that these institutional readers can use.
What each system was designed to do
The documentation that accompanies a product through trade, regulation, and procurement was built for specific, bounded purposes.
Nutrition labels were designed to give consumers a summary comparison at the point of purchase. They compress multiple dimensions of a product's composition into a format that fits a package. Different jurisdictions compress differently: Nutri-Score in France, Health Star Rating in Australia, traffic-light labels in the United Kingdom, warning labels in Chile. Each system is internally coherent. None was designed to carry the product's full nutritional story to an institutional reader comparing products across regulatory contexts.
Certification systems — organic, fair trade, geographic indication, halal, kosher — were designed to confirm that a product meets a defined threshold. They answer an admissibility question. They were not designed to explain what distinguishes one certified product from another within the same scheme. Two products carrying the same organic certification may differ significantly in variety, practice, input, and provenance.
Trade documentation — phytosanitary certificates, certificates of conformity, bills of lading, customs declarations — was designed to move goods across borders. These documents answer clearance questions. They were not designed to carry product-level meaning to a buyer who wants to understand what they are sourcing.
Traceability systems were designed to answer a logistics and recall question: where has this product been? They were not designed to carry what the product is — only where it went.
Geographic indication systems were designed to protect the legal relationship between a product's name and its place of origin. Two producers operating under the same GI may have very different practices, inputs, and qualities. The GI record does not carry that difference.
Each of these systems does what it was designed to do. The difficulty is that none of them was designed to do what is increasingly being asked of them: carry a portable, structured account of the product that can be read across institutional contexts.
The gap
The gap is not a failure of any individual system. It is a structural condition that arises between systems.
A product may be fully documented and still arrive at its destination as a category and a price. The buyer knows it is organic. The buyer knows it originated in a particular country. The buyer knows it passed inspection. The buyer does not know what variety it is, what practices the producer uses, what inputs were applied, what the producer's testing history shows, or what distinguishes this specific product from the commodity average.
That information often exists. The producer knows it. But this information is not structured in a way that travels with the product beyond the first transaction. It is captured, but it is not portable.
The consequence is a persistent asymmetry. Products from regions with sophisticated export documentation infrastructure arrive in markets with their attributes readable. Products from regions with less developed documentation infrastructure arrive with their compliance intact but their distinction invisible. They are not rejected on the merits. They are passed over before the merits are assessed.
Why health comes first
Every product must answer a health question before it becomes a trade, procurement, or market question. Does this product support human wellbeing? Is its composition understood? Are its inputs documented? Has its safety been assessed?
Health is the first benchmark because it is the one question that every governance system — in every jurisdiction, in every language, in every regulatory tradition — asks about every product. It is universal in a way that trade preferences, sustainability standards, and procurement criteria are not.
The same information infrastructure that would allow a product's health-relevant attributes to travel clearly would also support trade documentation, procurement comparison, sustainability assessment, and institutional decision-making. Health is not a separate domain. It is the entry point. The documentation that serves health also serves everything that follows.
The pattern across systems
Altibbé's research programme — Structural Gaps in Product Information Systems — has examined this pattern across multiple systems: nutrition labels, certification, trade documentation, geographic indication, traceability, and India's product-information stack.
Each paper studies a different system. Each system performs a valid and often well-designed function. Yet across all six, the same structural pattern appears: information is captured for a bounded purpose, but it rarely accumulates into a portable account of the product itself.
Three distinctions recur across the research:
Meeting a standard is not the same as being understood.
Knowing where a product has been is not the same as knowing what it is.
Documentation does not automatically become product understanding.
These are not failures of any individual system. They are structural features of a documentation landscape that was built one requirement at a time, each system solving its own problem well, without a layer that connects them into a portable product account.
What this means
The gap between information that exists and information that travels has practical consequences for every institution that makes decisions about products.
Trade agencies promoting origin products cannot currently send the producer's full story with the product. Heritage products, artisan products, and origin-rich products compete on category and price rather than on the attributes that distinguish them.
Procurement bodies comparing suppliers receive compliance documentation but not product-level understanding. Two suppliers may both be certified, both be traceable, both be compliant — and still differ significantly in practice, quality, and suitability.
Health authorities assessing what populations consume can access safety data and nutritional summaries, but not the structured product-level information that would allow a more complete picture of what is entering food systems.
Standards bodies developing new frameworks encounter the same structural condition: existing documentation carries what it was designed to carry, but the layer that would make product information portable across institutional contexts has not been designed.
What Altibbé studies
Altibbé is a research-and-standards organisation for product information. It studies the gap described in this note — the structural space between information that exists at source and information that travels to the institutions, buyers, and markets that need it.
Its current research programme focuses on food and agriculture, where health is the first benchmark and the documentation gap is most consequential. The programme has published a growing catalogue of papers, each examining a different system, each finding the same structural pattern.
From this research, Altibbé develops standards for structuring what existing systems do not carry. HEDAMO — a disclosure standard for producer-declared product information — is one applied output of this broader work.
The gap is structural. It was not created by the failure of any individual system. It emerged from the success of many systems, each solving its own problem well, without a connecting layer. Studying that gap — and developing standards for what belongs in the missing layer — is the work Altibbé was created to do.
Institutional Note · Altibbé Inc. · May 2026
Altibbé studies how product information travels across health, trade, procurement, and institutional decision-making.
altibbe.com