Supplement Registration, Notification, and Authorization Explained

Begin with the jurisdiction, not the badge

Words such as registered, notified, authorized, licensed, listed, and approved can describe different processes in different legal systems. The first research field should therefore be the market in which the product is offered and the public authority responsible there. Copy the exact claim from the label or seller page, including any number and agency name. Do not translate one jurisdiction's term into another jurisdiction's category merely because the words sound similar. A global comparison should preserve the original term and provide a jurisdiction-specific explanation.

The authority's own guidance is the source for what its process covers. Some systems focus on pre-market notification, some place responsibility primarily on the business, and some apply product-specific authorization to particular categories or ingredients. A public database can confirm that a record exists under defined search fields, but its presence does not answer every question about the package in hand. The record date, responsible company, product name, market, and current status all need to be matched before displaying a verification result.

Separate establishment records from product records

A company, facility, importer, or food business can hold a registration that is distinct from a product record. Marketing may display the organization-level number near a product in a way that invites readers to connect them. The comparison should create separate fields for responsible business, manufacturing establishment if disclosed, product notification or listing, and any other cited authorization. Confirm which entity and object the public record actually names. A valid company record does not by itself verify every product sold under that company's brands.

Likewise, a product name in a database may not identify every package version. Flavor, format, package size, market language, or responsible operator may have changed. Compare the record's identifiers with the current label and preserve uncertainty where a reliable match is unavailable. Never copy a regulator logo into a comparison badge unless its use is expressly allowed, and do not redesign a registration result to resemble an endorsement. Plain text such as record located, record not located after stated search, or package match unresolved communicates the evidence more accurately.

Understand what a public record does not establish

A notification or registration process is not automatically a review of every statement on a label, every production batch, or any claimed outcome. The exact limits depend on the authority and must be quoted or paraphrased from its current guidance. A comparison should never convert record located into clinically proven, regulator recommended, guaranteed safe, or superior quality. Those conclusions require different evidence and may be false even when the underlying record is genuine.

Absence from a search also has several possible explanations. The product may use another name, the responsible company may differ, the database may cover only part of the market, the record may be archived, or the search may be incomplete. Report the database, query fields, date, and result rather than declaring a product illegal. Legal status can require facts and expertise beyond a public search. Direct suspected noncompliance to the responsible authority's reporting channel without presenting MIHEN's database check as a legal determination.

Use a reproducible verification workflow

Record the product's market, full label name, responsible company, address, package identifier, claimed number, and source image. Open the authority's official database from its own domain rather than a link supplied only by a seller. Search the number exactly, then repeat with company and product names if the system supports those fields. Save the returned title, status, date, holder, and direct result URL when stable. Note spelling variants and filters used so a second reviewer can reproduce the search.

Match the record to the package using more than a similar name. Confirm the responsible operator and any identifiers available. If the database explains status codes, link that explanation instead of writing a new interpretation from memory. Screenshots can preserve results but should not replace the live official link. Recheck records on a defined schedule because databases, legal categories, and product responsibility can change. A verification timestamp is essential; a permanent verified badge is not justified by a search performed once.

Present cross-border differences without false equivalence

A product offered in several countries may have different labels, importers, claims, and regulatory records. Build one market-specific row for each package rather than applying the home-market record to every region. Language is not a reliable proxy for jurisdiction: the same language can serve multiple countries, and one country can require several languages. Hreflang pages should adapt links and explanations to the intended market rather than translating an agency name and leaving the underlying process unchanged.

The final page should show the authority, record type, subject of the record, package-match status, search date, and stated limitations. It can explain how a reader can repeat the public search. It should not provide a legal conclusion, predict regulatory action, or imply a health judgment. When MIHEN lacks current jurisdiction-specific research, the safe output is a general process guide with a clearly labeled gap, not a confident localized claim copied from another market.

• Identify the exact market and responsible public authority.
• Copy the claimed status term and number verbatim.
• Distinguish company, facility, importer, and product records.
• Search only the authority's official database or guidance.
• Match holder, product, package, and date fields.
• Record queries, filters, status wording, and search date.
• State what the record does and does not establish.
• Avoid endorsement-style badges and legal conclusions.