Label Fields Across Capsules, Tablets, Gummies, Powders, and Liquids

Start with format as a packaging fact

Capsule, tablet, softgel, gummy, powder, and liquid are useful descriptors of the physical format presented by the package. Record the manufacturer’s wording rather than inferring a format from an isolated product photo. A pouch can contain packets, a bottle can contain a liquid or solid units, and a listing title can be abbreviated. Preserve the front panel, facts panel, net-quantity statement, and any included measuring-device information so the classification can be audited.

Format alone does not demonstrate faster absorption, greater effectiveness, easier use, or better quality. Those comparative claims require evidence beyond label structure and are outside this guide. MIHEN uses format only to decide which documentary fields deserve attention. A neutral record can help readers find serving form, package count, measurement language, and storage text without turning those factual differences into a product recommendation.

Match serving language to the physical form

Solid-unit labels may define a serving with a count, while powders and liquids may use volume, mass, scoops, teaspoons, packets, or another declared measure. Capture the complete serving phrase and do not shorten it to a bare number. If a powder states both a scoop description and a metric amount, preserve both. If a gummy serving contains multiple pieces, keep the piece count attached to every per-serving declaration.

Do not assume that one capsule, one scoop, one dropper, or one packet equals one serving. The label controls the documentary denominator. Similarly, do not divide a per-serving amount by unit count to manufacture a per-unit claim unless the page clearly labels it as arithmetic, all relevant units are identical, and the editorial method permits that narrow calculation. This content set defaults to the printed basis and identifies unmatched denominators rather than filling them in.

Separate net quantity from servings and ingredient amounts

Net quantity tells the consumer how much product or how many units the package contains under the applicable label convention. Servings per container is a different field, and a declared ingredient amount is different again. A format comparison should allocate separate columns to net contents, serving size, approximate or declared servings per container, and facts-panel amounts. Never use bottle size or package mass as a proxy for the quantity of a named ingredient.

Some packages combine count and mass or volume statements, and multipacks can add an outer-package count. Capture the hierarchy: retail package, inner container or packet, units within it, and serving definition. When only a retailer listing supplies one of those values, mark the source type. A discrepancy can result from a packaging update, bundle configuration, or transcription error, so the record should not resolve it without package-matched evidence.

Document format-specific supporting fields

Powders and liquids may include preparation, mixing, measuring-device, settling, shaking, or refrigeration language. Gummies and other flavored formats may have prominent flavor statements and a longer set of non-dietary ingredients. Capsules and tablets may identify shell, coating, color, or printing materials in the other-ingredients statement. Capture these as label text in the appropriate field, not as an assessment of convenience or desirability.

Storage and handling wording can depend on the container and product form, but MIHEN should reproduce it only as a package statement. Do not rewrite directions into new instructions or combine fragments from different panels. Record whether a measuring device is shown or mentioned without asserting its accuracy. If the product image set does not show the relevant side panel, state that the field was not visible at review time rather than importing text from a similar listing.

Build comparisons around shared fields and declared differences

A useful worksheet begins with package identity and format, then aligns serving language, net quantity, servings per container, ingredient row, other ingredients, preparation text, storage text, and source date. It should display original units and avoid collapsing format-specific fields into a false common score. Where formats do not share a meaningful field, use not applicable or not stated with a short reason instead of zero.

Reviewers should confirm that every image belongs to the same variant and market. Publish the comparison date and explain that label fields can change with formulation or packaging revisions. A revision log should name the field that changed, preserve the earlier capture, and avoid suggesting that an unexplained difference is necessarily a formulation change. The final description can say how the labels differ structurally, but it cannot establish which format is easier for a particular person, performs better, or is more appropriate. Those questions require context that a package transcription does not provide.

• Confirm the physical format from package-matched evidence.
• Transcribe the full serving phrase, including count or measure.
• Keep net quantity, servings per container, and ingredient amounts separate.
• Record both customary and metric measures when printed.
• Capture format-specific preparation, device, and storage text verbatim.
• Mark retailer-only fields with their source type.
• Use not applicable or not stated rather than a misleading zero.
• Avoid performance or suitability rankings based on format.