Lot, Batch, Date, and Storage Fields on Supplement Packages

Survey the complete container before transcribing

Lot codes, batch references, printed dates, and storage statements can appear on the label, cap, neck, bottle base, carton flap, sachet seam, or an ink-jetted area that is absent from catalog photography. Review all available package surfaces and record which surfaces were actually visible. A missing field in an online image set should be described as not visible in the reviewed evidence, not as absent from every retail package.

Match the evidence to the exact name, variant, size, format, market, and packaging configuration. An outer carton may carry a code that does not appear in the same way on an inner bottle, while a multipack may include several levels of identification. Store the package hierarchy and image source. Avoid combining a code from one listing with label text from another merely because the front panels look similar.

Preserve codes as strings rather than guessed dates

A lot or batch identifier can contain letters, punctuation, leading zeros, and manufacturing-specific segments. Store it as a verbatim string and retain a close image crop plus the wider location view. Do not strip spaces, change capitalization, or coerce the value into a number. Optical character recognition may confuse zero with the letter O or one with the letter I, so require manual review and an uncertainty flag for ambiguous characters.

Do not decode a manufacturing date, facility, production line, or sequence from the code unless the responsible company publishes a package-specific decoding method. Informal code lists can be outdated or apply only to another brand or period. A record may identify a field as lot-like based on nearby wording, but it should keep that classification separate from the literal text. Unknown segments remain unknown until supported by a direct source.

Keep the date and its qualifier together

A printed calendar value may be introduced by words or abbreviations such as best by, use by, expiry, expiration, manufactured, packed, or another market-specific phrase. Capture the qualifier exactly because it defines what the package states. A bare date copied into a database can be misleading when the original phrase and placement are lost. Record the apparent format, separator, language, and whether day and month ordering is unambiguous.

Never guess an ambiguous date order from the reviewer’s locale. Store the verbatim value, package market, and a machine-readable date only when the format can be established from the package or an authoritative source. If a seller writes a date in listing text while the package image is unreadable, keep the seller statement in a separate source field. Do not use a later listing to overwrite an earlier package capture without recording the revision.

Transcribe storage wording without creating new directions

Storage statements may mention temperature, moisture, light, closure, refrigeration, or other handling conditions. Quote the complete wording and identify its panel. Do not paraphrase several fragments into a new instruction or add a numerical range that the package does not print. When a statement refers to conditions before or after opening, preserve that distinction and any cross-reference to another panel.

A comparison can show that two packages use different storage text, but it should not decide which condition applies to an unidentified container or a package from another market. Manufacturer web pages can provide supporting information, yet the page date and product match still matter. If web text conflicts with a current label, present both sources and ask the responsible company for clarification rather than choosing the more specific statement.

Use the fields for traceability, not a condition verdict

Lot, batch, and date data can help distinguish package evidence and align an official notice with its stated scope. A comparison record should show the literal identifier, date wording, package surface, source type, capture date, reviewer status, and any uncertainty. When referencing an official alert or recall, reproduce the authority’s named identifiers and link directly to the notice. Do not broaden its scope to codes or variants the notice does not name.

These fields do not allow MIHEN to inspect the contents, confirm handling history, or determine the condition of a particular package. The guide therefore stops at documentation and directs package-specific questions to the responsible company or relevant authority. Preserve historical captures, because they can explain why two legitimate images differ. Note whether a code was transcribed from a physical observation, a manufacturer image, or a seller image, since variable print may differ between individual units. A transparent unknown or source conflict is more useful than a confident interpretation unsupported by the printed evidence.

• Review all visible package surfaces, including carton and container components.
• Match the code and date evidence to the exact variant, size, and market.
• Store lot and batch identifiers as verbatim strings.
• Flag characters that remain unclear after manual image review.
• Capture every date together with its printed qualifier and format.
• Keep seller-supplied dates separate from package evidence.
• Transcribe storage statements without adding new instructions.
• Link official notices only to identifiers within their stated scope.