Elemental Amount vs Compound Weight on Supplement Labels

Read the full nutrient row before comparing numbers

A facts-panel row can name a nutrient, state a declared amount and unit, and identify a source compound in parentheses or nearby wording. These elements perform different label functions. Transcribe the entire row, including from or as language, indentation, symbols, and serving basis. Do not extract the compound name as though it were a second amount when no separate quantity is printed. Preserve the panel image so the relationship remains visible.

Marketing text may place a compound weight on the front while the facts panel declares the nutrient amount on its required basis. Record both statements with their source locations and exact wording. Do not silently select the larger number for a comparison. A retailer may also write a shorthand amount that cannot be matched to either printed field. Treat it as a seller claim until the package basis is confirmed.

Name the measurement basis explicitly

A numerical value is not comparable until its subject is known. Build fields for declared nutrient, declared nutrient amount, unit, source compound, separately stated compound amount, and serving definition. If the panel's amount is the nutrient quantity and another statement is the compound quantity, label those bases in every table heading. Do not use a generic amount column that makes unlike values appear interchangeable.

The same principle applies when labels use salts, chelates, complexes, hydrates, or other source descriptions. Similar-sounding compound names may have different compositions, and a compound name alone does not authorize a conversion. MIHEN's low-risk workflow does not calculate elemental fractions from chemical formulas, certificates, or reference tables. It records the values the identified package declares and stops when the comparison basis is not explicitly shared.

Avoid reconstructing one amount from another

It may be tempting to calculate a nutrient amount from a compound weight or the reverse. That operation can require exact chemical identity, purity, hydration state, formulation details, rounding conventions, and jurisdiction-specific labeling rules. Those facts are often absent from consumer packaging. A generic internet conversion can therefore create a precise-looking value that does not describe the finished product. The comparison should mark the missing basis instead of completing the arithmetic.

A certificate of analysis may report another basis again, such as a test result for a raw material or finished batch. Do not replace the label declaration with that result without matching the sample, unit, method, and specification. Store laboratory documents in a separate evidence layer. Label literacy asks what the package says; document literacy asks what a particular record reports. Keeping those questions separate prevents a result from one layer from being used to repair a gap in another.

Compare source wording without ranking forms

A table can align the declared nutrient amount, unit, source wording, separately declared compound quantity, other ingredients, and documentation status. It can identify exact text matches or differences. It should not describe one source form as better, more absorbable, gentler, stronger, or more effective without appropriately scoped evidence and qualified review. Those are not conclusions available from the label grammar itself.

Nor should the comparison infer that a higher declared nutrient amount is preferable. The amount is a factual label field. MIHEN can normalize compatible mass prefixes for a documentary calculation while retaining original units, but it should not combine International Units with mass values or apply nutrient-specific conversions in this guide. When panels use different bases, keep separate columns and explain why no single normalized figure is shown.

Publish the evidence chain and unresolved basis

For each record, show the exact package, panel image, verbatim row, serving definition, source location, access date, and whether the amount basis was explicit. Use states such as nutrient amount declared, compound amount separately declared, source compound named without quantity, seller basis unclear, and panel conflict. These states are more accurate than assuming every number beside the ingredient name means the same thing.

Have a second reviewer confirm punctuation, parentheses, and units. Automated validation can block a normalized comparison when amount-basis values differ. Corrections should preserve the previous label because a later redesign may clarify wording that was once ambiguous. A published comparison should also expose its field definitions so readers can see precisely which printed statement supplied each value and why an unresolved statement remains outside the calculation. The guide's conclusion remains limited: it explains how to keep nutrient and compound quantities from being confused. It does not calculate personal use, assess source-form performance, or recommend one declaration over another.

• Transcribe the full nutrient row, including source wording and symbols.
• Separate nutrient amount, source compound, and any compound amount into distinct fields.
• Label the subject and serving basis of every number.
• Keep front-label and retailer claims separate from facts-panel declarations.
• Do not reconstruct amounts from generic formulas or conversion tables.
• Store laboratory results in a separate evidence layer.
• Block normalization when the measurement basis differs or is unclear.
• Publish the panel source, package match, and review date.