Evidence policy
- A name-derived value requires explicit, context-constrained wording.
- A taxonomy-derived value requires an unambiguous DABS class. Grouped classes such as “Syrah, Petite Sirah” do not assign either varietal without name evidence.
alcohol_by_volume_percentis either explicitly labeled or exactlyproof / 2;alcohol_by_volume_basistells you which.- Country codes are emitted only when one country is explicit in the DABS class name. They describe the source taxonomy, not independently verified production or bottling origin.
- An empty array or
nullmeans “not established.” It does not mean the characteristic is absent.
name is a consumer display title. When Nektir has resolved the brand, the title omits that brand; it also omits structured volume and pack-count suffixes. Use brand and package_size to compose the presentation your application needs. Package metadata separates container_count, unit_milliliters, and total_milliliters; check interpretation before using calculated dimensions. The legacy milliliters value remains for v1 compatibility but can have ambiguous multipack semantics. If the brand is unresolved, its source text remains in name rather than being guessed away.
The raw DABS label and taxonomy remain available on product detail under source_fields. Editorial overrides can correct public names, name components, and supported intelligence values without altering source evidence. A non-null review states whether an owner confirmed the deterministic output or published a correction. alcohol_by_volume_basis: editorial_review distinguishes reviewed ABV from a source label or proof-derived value.
Reviewed corrections are auditable and immediately republished. They never alter price, status, inventory, raw DABS fields, or the three source/retrieval/publication clocks.
Filter products
Use comma-separated values withwine_varietals, beverage_styles, origin_country_codes, or production_designations. Values within one parameter use OR semantics; different filter parameters combine with AND semantics.
data.product_intelligence.filters in /v1/meta; do not hard-code them into a browsing interface.