Manufacturer, Distributor, and Contact Fields on Supplement Labels

Capture the complete business identification block

Record the business name exactly as printed, including legal suffixes, brand qualifiers, punctuation, and any nearby responsibility phrase. Preserve every address line, country reference, telephone number, website, email address, and customer-service wording that belongs to the block. A cropped company name without its surrounding phrase can lead a database to assign a role the package never states, so retain both a focused crop and the wider panel context.

A brand name on the front is not necessarily the legal business named elsewhere. Create separate fields for brand, labeled business, claimed role, and contact channel. Do not expand abbreviations or substitute a corporate parent found through search unless a cited public record establishes the connection. Even then, keep the external corporate relationship separate from the package declaration so readers can distinguish printed evidence from later research.

Let the responsibility phrase define the recorded role

Phrases such as manufactured by, manufactured for, distributed by, imported by, packed for, or another jurisdiction-specific formulation are not interchangeable. Quote the full phrase and map it to a controlled claim type without rewriting it. A manufactured-for statement does not identify the physical production site, and a distributed-by statement does not establish that the named company formulated or made the contents.

When no role phrase is visible, record company named on label rather than guessing manufacturer. Retailer category fields often use manufacturer as a generic database label, so treat them as seller metadata, not package proof. If two panels or official sources present different roles, version the evidence and show the conflict. A later corporate acquisition or name change should not silently alter what an older package actually printed.

Verify contact channels without transferring identity

A listed website or telephone number can help confirm that the contact block is current, but a working destination does not prove every product detail on a third-party page. Store the printed channel and, separately, the resolved official page checked by the reviewer. Note redirects, regional pages, and review date. Avoid publishing personal contact details that are not clearly presented as business information on the package or an official business source.

Domain ownership, trademark databases, and corporate registries may provide useful context, but each answers a different identity question. Do not merge them into one verified-manufacturer badge. If external verification is included, name the registry, record searched, jurisdiction, and date, then state exactly what it supports. MIHEN should not offer a legal conclusion about ownership or responsibility based on a label block alone.

Handle address fields as structured evidence

Transcribe locality, region, postal code, and country as printed, while retaining the original line breaks. A structured geographic field can support filtering, but it should not replace the verbatim address. Do not infer a manufacturing location from the business address. A headquarters, responsible-business address, mailing location, importer address, and production facility can be different places, and the label may identify only one of them.

Address formats vary across markets and change over time. Normalization should correct neither spelling nor jurisdictional abbreviations in the evidence layer. If a mapping service or postal reference suggests a standardized form, store it as an optional research value with provenance. When an address appears incomplete under a reviewer’s expectations, link to the applicable official rule or ask the responsible authority rather than declaring the label noncompliant.

Publish role confidence and source boundaries

A public record can show package wording, mapped role claim, address, contact channel, image source, market, package version, and capture date. Add confidence states such as role phrase visible, company name visible but role unstated, seller metadata only, official contact page matched, or source conflict. These labels are more informative than presenting every named business as the manufacturer.

Require a second reviewer for responsibility phrases and company names, especially on curved or low-resolution panels. Keep historical records when a business name, address, or web domain changes. When the package provides more than one company block, retain each block and its panel location instead of selecting one organization as primary without an explicit rule. A support contact can also differ from the business named in the identity statement, so the public display should avoid merging their roles. The guide helps readers locate and understand identity fields; it does not verify manufacturing conduct, assign legal responsibility, or endorse a business. Package-specific questions should go to the named contact or appropriate regulator using current information.

• Transcribe the full business name and every nearby responsibility phrase.
• Keep brand identity separate from the legally named business.
• Record contact channels and address lines exactly as printed.
• Do not infer a production site from a business address.
• Treat retailer manufacturer fields as seller metadata unless package-supported.
• Document external registry checks with source, jurisdiction, and date.
• Use an explicit role-confidence status for each record.
• Retain earlier package versions after company details change.