A Wine Catalogue's Vintage Year Is Not Its Bottling Date
A wine catalogue should not fill its vintage field from the bottling date, purchase date or latest stock receipt. For a winery or importer commissioning a catalogue integration, the useful requirement is a supported harvest-year statement for the particular wine being offered, with a separate decision about the market and label it covers.
This is a software-planning guide, not permission to label or sell a particular wine. The regulatory example below is United States federal wine-labeling text in the 2025 CFR edition. Have a competent wine-labeling specialist confirm current applicability and any additional requirements before implementing rules or publishing claims. Translating the catalogue into German or Arabic does not change that jurisdiction.
Give each date its real meaning
A fictional importer receives a newly bottled wine made from earlier harvests. A database with one field called “year” invites an avoidable mistake: the stock import can replace a harvest statement with the delivery year, and a website can display it as a vintage.
Specify distinct fields for the relevant operational dates and the proposed vintage statement. The public vintage must come from reviewed product information, not a convenient fallback when that information is missing. If the supplier gives no supported vintage, the application should preserve that uncertainty rather than manufacture one.
The cited section defines vintage wine by the year of harvest of the grapes, subject to its stated wine classes and conditions. A later bottling event does not answer that question. Nor should a blank vintage automatically be rendered as a claim that a wine is a particular type of non-vintage product; agree the public wording with the responsible reviewer.
The percentage depends on the statement's context
The 2025 text of 27 CFR 4.27 requires an appellation of origin and distinguishes two vintage-percentage cases. For an American or imported wine labeled with a viticultural-area appellation, or its foreign equivalent, it states at least 95 percent from grapes harvested in the labeled calendar year. For an appellation other than a viticultural area or its foreign equivalent, it states at least 85 percent.
These are not interchangeable catalogue defaults. A single global rule called “vintage percentage” loses the distinction. The section also includes other conditions, including a winery-volume limitation, producer-record provisions for American wine and additional conditions for imported wine. Passing a percentage test is not complete approval.
In the project brief, ask which market, wine and proposed appellation the specialist has reviewed, what evidence supports the vintage statement and who may release it. Do not infer an appellation from a supplier address or treat a website's language as the destination-market rule.
Preserve the offered wine when a blend changes
A product name may remain the same while the wine available for sale changes. The application needs to distinguish the commercial product family from the particular offered wine and its approved statement. Lot tracking can help identify the goods, but a lot number alone does not substantiate a vintage.
Ask how producer documentation and reviewed composition information will be associated with the offered wine. If a new blend or replacement supply changes the supporting facts, make the required reassessment visible. An old approval should not silently follow the unchanged product title into a new offer.
Keep the exact approved public wording as well as the underlying year. This allows staff to compare what was reviewed with the label information and catalogue output actually in use. The proposed record structure is an implementation recommendation, not a statutory database format prescribed by the cited section.
Imported wine needs more than a copied year
The imported-wine paragraph requires more than conformity with the general paragraph. It addresses the country-of-origin laws regulating vintage dates, conformity with those laws and entitlement to use that date there. It also requires the relevant importer or domestic bottler to be able to demonstrate entitlement on request.
Consequently, a supplier spreadsheet containing a year is not the same thing as a completed review of those conditions. Define how staff obtain the relevant evidence, record missing information and hand questions to the responsible specialist. Do not ask the developer to decide foreign-law compliance from a filename or a country dropdown.
Demonstrate the whole catalogue handoff
Use synthetic records to show an earlier harvest with a later bottling date, missing vintage evidence, a changed blend and two specialist-reviewed examples with different appellation contexts. Check that importing stock does not overwrite the harvest statement and that unresolved records do not acquire a guessed year.
Then inspect the actual catalogue export and customer page. A correct internal form is not evidence that a downstream connector used the right field. Include a correction test that preserves the earlier offered version rather than rewriting its history.
Bring an anonymised blank data example to a catalogue or workflow-app discussion. The deliverable is a traceable path from producer evidence and specialist review to the exact public wine description, not an automatic legal certificate.
Source: 27 CFR 4.27, 2025 edition, published by GovInfo. The regulatory example is explicitly edition-bound; current professional review remains necessary.