Wine Distributor New Vintage Announcement Template for Importer Teams

Announce a controlled transition, not only a new year

This guide is for alcohol importer operations teams preparing a new-vintage announcement for distributor sales, purchasing, item-data, warehouse, marketing, and compliance contacts. It covers predecessor and successor records, item identity, GTIN and distributor-code decisions, overlapping inventory, availability, pricing, assets, approvals, recipient actions, corrections, and downstream tracking.

A useful announcement tells the recipient exactly what is changing, what remains active, when the successor can be ordered, and which action is required. It should not force a distributor to compare two technical sheets or infer whether a code, price, case pack, or bottle image changed.

Treat the announcement as an output from an approved vintage change record. It does not replace the distributor’s item-setup form, state process, price submission, purchase order, or internal inventory system. Keep legal and market decisions with the qualified owners for the jurisdiction and relationship.

Define the predecessor and successor before drafting

Create a successor release without overwriting the prior vintage. Link both records to the continuing wine identity and preserve the prior record’s approvals, assets, and distributor history.

Use a transition table internally:

Control	Prior vintage	Successor vintage	Decision
Release ID	Stable prior release reference	New release reference	Separate records required
Producer and wine	Approved prior identity	Approved successor identity	Confirm spelling and hierarchy
Vintage status	Exact prior year or non-vintage status	Exact successor year or non-vintage status	Never use old and new as identifiers
Market item	Prior market configuration	Successor market configuration	Confirm whether the commercial item relationship continues
Importer SKU	Prior code	Approved successor treatment	Issuer decision required
Consumer GTIN	Prior identifier	Approved successor treatment	Brand-owner decision required
Case GTIN	Prior case identifier	Approved successor treatment	Review package and case configuration
Distributor code	Prior recipient code	Assigned, reused, pending, or not applicable	Distributor decision required
Availability	Prior inventory context	First approved successor availability	Market and warehouse confirmation
Transition state	Active, sell-through, paused, or closed	Preparing, approved, available, or active	Defined by market and recipient
Replacement assets	Prior bottle image and sheets	Approved successor set	Publish and retire intentionally

Do not send the announcement while the successor row is still a copy of the predecessor with unreviewed fields. Mark inherited data as confirmed unchanged, changed, awaiting evidence, not applicable, or retired.

Identify the audience and requested action

One email can reach several distributor functions, but each recipient needs a clear task. Name the audience in the announcement record and route sensitive or specialized attachments only to the people who need them.

Common recipient actions include:

• purchasing updates the expected vintage and availability context
• item data changes a vintage field or opens a successor item
• warehouse operations confirms code, pack, and receiving treatment
• pricing confirms whether the current schedule continues or a replacement follows
• sales receives the approved transition note, tech sheet, sell sheet, and bottle image
• marketing replaces vintage-specific product assets
• compliance or state operations completes a separate market process where required

Do not write Please update your system without naming the field, item, effective context, and owner. If the distributor has separate divisions or states, create recipient-specific versions rather than implying one transition applies everywhere.

Use this reusable announcement control header

Keep an internal control block above the message draft:

Field	Required entry
Announcement ID	Stable internal reference
Producer and wine	Exact approved identity
Prior vintage	Predecessor release
Successor vintage	New release
Market and distributor	Exact scope of the announcement
Distributor division	Branch, channel, state, or other recipient context
Purpose	Notice, item update, new-item request, sales release, or combined handoff
Requested action	Specific recipient task
Response requested	Confirmation, assigned code, approval, or exception
Planned send context	Approved date or release gate
Effective context	When the stated transition applies
Operations owner	Person accountable for the complete handoff
Approvers	Product, compliance, commercial, logistics, sales, and brand owners as applicable
Revision and status	Draft, in review, approved, sent, corrected, accepted, superseded, or closed
Evidence packet	Controlled source for item data and attachments
Downstream tracker	Systems, documents, and recipients requiring confirmation

The planned send date, effective date, first available date, and predecessor sell-through context answer different questions. Keep separate fields even when they initially match.

Build the message from a structured template

Use a concise email or portal note for the announcement itself. Attach structured records when the recipient needs more detail.

Subject line

Use a subject that remains meaningful in a distributor inbox:

New vintage action required: [Producer] [Wine], [Successor vintage], [Market]

For an informational notice, replace action required with availability notice. Include the distributor item code when that is the recipient’s primary reference.

Opening paragraph

State the transition and scope:

We are preparing the [Successor vintage] [Producer] [Wine] for [Market or division]. This release succeeds the [Prior vintage]. Please use the transition details below for [specific requested action].

Do not call the successor current until the market owner has approved that status. Use preparing, available to order, first shipping, or another controlled phrase that matches the actual state.

Item and transition table

Put the operational comparison in the message or a clean attachment:

Field	Prior vintage	Successor vintage	Recipient action
Producer	[Approved name]	[Approved name]	Confirm display value
Wine	[Approved name]	[Approved name]	Confirm display value
Vintage	[Prior vintage]	[Successor vintage]	Update or create item as instructed
Importer SKU	[Prior SKU]	[Successor SKU or unchanged]	Use approved supplier reference
Distributor item code	[Prior code]	[Assigned, unchanged, or pending]	Confirm treatment
Consumer GTIN	[Prior GTIN]	[Successor GTIN or unchanged]	Load only after verification
Case GTIN	[Prior case GTIN]	[Successor case GTIN or unchanged]	Confirm receiving record
Bottle volume	[Prior volume]	[Successor volume]	Flag any package change
Case pack	[Prior pack]	[Successor pack]	Update ordering and pricing basis if changed
Price basis	[Prior basis]	[Successor basis]	Refer to approved price record
Availability	[Prior context]	[Successor context]	Confirm order timing
Transition	[Sell-through or closed]	[First order or ship context]	Keep both visible if overlap continues

Use unchanged only after the owner of that field confirms it. Use pending distributor confirmation for recipient-owned codes. Do not leave a blank that could mean unchanged, unknown, or not applicable.

Changed product facts

Add a short section for approved release differences that help sales and item teams:

• blend or variety presentation
• appellation or vineyard source
• ABV or technical analysis
• farming, harvest, fermentation, or aging details
• tasting and service language
• certification or claim status
• awards or reviews tied to the successor
• package, closure, label, or case change

Include only fields supported for the successor. A vintage announcement does not need to repeat the full tech sheet.

Attachments and links

List each approved successor asset by purpose:

• tech sheet
• sell sheet
• front bottle image
• back bottle or label image when requested
• approved item-setup file
• case and pallet specification when changed or requested
• controlled price list or price notice for the market
• portfolio or training material when ready

Keep draft labels, working spreadsheets, source analysis, internal margin files, and superseded assets outside normal distributor access.

Response request

End with a testable request:

Please confirm by [response context] whether the [Successor vintage] will use distributor item code [code or pending] and whether any additional item, warehouse, pricing, or asset fields are required.

Name the importer contact who will consolidate the response. Do not ask the distributor to reply separately to several contributors.

Decide GTIN treatment instead of assuming it

A vintage change does not produce one universal GTIN answer. Record the brand owner, identifier type, packaging level, prior value, proposed treatment, deciding evidence, recipient handling, and approver.

The GS1 GTIN Management Standard treats a wine vintage as a new product when the vintage year is recognized as a different-quality product rather than handled as a flow-through commodity. The same standard says a change in declared net content requires a new GTIN and that a case-quantity change requires a new identifier at the affected higher packaging level. Apply the relevant rule to the actual product and package change.

Keep these identifiers separate:

• importer SKU
• supplier or producer code
• consumer GTIN or UPC
• case GTIN or shipping container code
• distributor item code
• state or warehouse item code

GS1 US explains that a GTIN identifies a trade item and distinguishes consumer and case-level structures in its GTIN overview. A distributor item number belongs to the recipient’s system and should not be presented as the GTIN.

Ask the distributor whether it will update the vintage on the existing item, create a successor item, retain a code through sell-through, or follow another documented process. Record that response for the named market. Do not extrapolate one distributor’s decision to another.

Review label and approval evidence narrowly

The successor announcement should use approved product identity for the destination market. TTB’s wine labeling guidance identifies federal wine-label topics including brand name, class or type, alcohol content, country of origin for imports, name and address, and net contents.

Do not assume every vintage needs a new COLA. TTB’s allowable revisions guidance includes adding a vintage date among its examples of revisions that may be made to an approved label without obtaining a new COLA, subject to the conditions in that guidance. Have the qualified compliance owner confirm whether the successor package fits the applicable approval and allowable-revision conditions.

The TTB Public COLA Registry provides information on approved, expired, surrendered, and revoked COLAs. Use the registry as supporting evidence, then retain the exact approval and internal package review linked to the successor item.

Keep federal label review separate from state registration, appointment, price posting, distributor setup, and warehouse acceptance. A completed federal review does not decide those other workstreams.

Explain overlapping vintages without creating ambiguity

The predecessor can remain orderable or present in distributor inventory after the successor becomes available. Announce overlap explicitly instead of sending one global current vintage value.

Record transition state by market item and distributor:

State	Meaning	Announcement treatment
Predecessor active	Prior vintage remains the normal item	Do not direct replacement yet
Sell-through overlap	Both vintages may be available	Show both identities, codes, assets, and order guidance
Successor first available	New vintage can enter orders or receiving	State exact approved context
Successor active	New vintage is the normal item for the defined market	Update default assets and item display
Predecessor closed	Prior vintage is no longer offered through the stated route	Retain internal history and remove routine access

Do not promise that an order will contain a specific vintage unless inventory and fulfillment owners support that commitment. If the distributor treats vintage as a flow-through field, describe the approved notice and receiving process. If it creates separate items, provide both codes and prevent orders from using an unassigned successor code.

During overlap, keep separate bottle images, tech sheets, sell sheets, accolades, tasting notes, and item records. A general product link should not silently switch its visible vintage before the intended transition.

Confirm availability and logistics before sending

An announcement can create orders. Verify the successor can move through the approved route before stating availability.

Confirm:

• production and release status
• quantity or allocation source used by the team
• importer warehouse or ship point
• first approved order or ship context
• lead-time source
• bottle volume and case pack
• case dimensions and gross weight when changed
• case GTIN and label treatment
• pallet pattern when changed or requested
• sample availability and route
• operations contact for purchase orders and receiving exceptions

Keep available, in transit, received, released, and available to order as separate operational states if the team uses them. Choose the one supported by the warehouse and commercial process.

If the case pack changes, reopen case price calculations, case GTIN treatment, warehouse setup, and pallet data. Link the approved wine case and pallet spec sheet when the distributor needs the revised physical configuration.

Keep pricing decisions in their governed process

A new vintage may keep the current price, receive a new price, or remain pending commercial approval. State the result without turning the announcement into an uncontrolled price list.

Record:

• market and distributor
• currency
• case or unit basis
• case pack used in calculations
• approved base price
• adjustments or programs when applicable
• freight and deposit treatment when applicable
• effective context
• commercial approver
• superseded price reference

Use pricing unchanged under current approved schedule only after the commercial owner confirms the schedule still applies to the successor. If pricing is pending, separate the product announcement from the price release unless the distributor requires one combined submission.

Do not paste internal cost, margin, or planning scenarios into the distributor notice. Link or attach only the approved audience version. The wine distributor price list workflow provides the fuller commercial control process.

Replace assets as a coordinated change set

Prepare the successor asset set before the sales announcement reaches a broad audience. Every asset should identify the exact vintage and market item it depicts or describes.

Review:

• front and back bottle images
• front and back label files
• tech sheet
• sell sheet
• short and long product descriptions
• tasting and service guidance
• producer and portfolio pages
• certification evidence and wording
• successor-specific accolades and quotations
• presentation and training material
• filenames, document titles, metadata, links, and image descriptions

Do not copy the predecessor’s score, quotation, analysis, tasting note, or bottle image into the successor package without approved successor evidence or an explicit decision that reuse is accurate.

Give distributor users one current set for each active vintage. When the predecessor closes, remove its files from the successor’s default collection while preserving them internally. The wine bottle-image requirements guide covers image identity and recipient derivatives.

Approve the exact announcement package

Use separate approvals for fields that have different owners:

Approval	Reviewer responsibility
Product	Producer, wine, vintage, origin, technical facts, and successor relationship
Compliance	Label, market presentation, regulated identity, and applicable review evidence
Item data	SKU, GTIN, volume, pack, distributor code, and system mapping
Logistics	Warehouse, availability, case, pallet, and receiving details
Commercial	Price, basis, currency, programs, freight, and effective context
Brand and sales	Copy, bottle images, sheets, claims, and training materials
Operations	Recipient scope, revision, attachments, links, requested action, and tracking plan

Approve the exact email body, comparison table, attachments, links, recipient list, and send context. An approved tech sheet does not approve a draft price table or an outdated bottle image attached beside it.

Use one operations owner to consolidate decisions. Contributors should not send partial updates directly to distributor contacts unless the communication plan assigns that task.

Track every downstream update

Create a row for each system, document, and recipient that may repeat the vintage:

Downstream target	Owner	Required change	Status	Evidence
Importer item master	Operations	Add successor and predecessor relationship	[Status]	Record link
Distributor item system	Distributor contact	Update or create item	[Status]	Confirmation or export
Warehouse system	Logistics	Map code, pack, and receiving data	[Status]	Live-item check
Price list	Commercial	Continue or replace approved row	[Status]	Published revision
Tech sheet and sell sheet	Portfolio	Publish successor documents	[Status]	Approved files
Bottle-image collection	Brand	Publish successor views	[Status]	Recipient download
Portfolio and training	Sales	Update active-vintage presentation	[Status]	Published revision
State process	Compliance	Complete applicable market task	[Status]	Filing or approval evidence
Announcement recipients	Operations	Confirm requested action	[Status]	Reply or portal result

Sent is not the same as accepted. Record the recipient’s confirmation, assigned code, requested correction, or open condition. Test the live item after the distributor completes its work.

Search downstream files for the predecessor vintage string. Inspect visible copy, filenames, PDFs, bottle images, metadata, direct links, and presentation notes. Keep intentional predecessor references during overlap and remove only the stale ones.

Correct mistakes through a replacement notice

If the sent announcement contains an error, do not edit only an attachment or send an unlabeled follow-up.

Use this sequence:

1. Stop use of the affected announcement or file where possible.
2. Confirm the correct source value and affected scope.
3. Update the controlled successor record.
4. Identify every recipient and downstream output that received the error.
5. Repeat the required field approvals.
6. Issue a replacement notice with a new revision and clear subject.
7. State the incorrect value, corrected value, affected item, and requested action.
8. Replace the affected attachments and links.
9. Mark the earlier notice superseded internally.
10. Capture recipient acknowledgment and downstream correction.

Do not describe a correction as a new vintage update if its purpose is to fix the prior notice. The recipient should be able to distinguish correction, replacement, and later transition messages.

Run the complete announcement workflow

Use one controlled sequence:

1. Open the successor release. Link the prior vintage and define markets, items, owners, and target transition.
2. Reopen successor fields. Review product, label, technical, item, package, commercial, availability, and asset data.
3. Decide identifier treatment. Record GTIN and SKU decisions by issuer and packaging level without assuming a change.
4. Ask the distributor about its process. Confirm whether it updates an item, creates a new one, or requires another workflow.
5. Define overlap. Record predecessor and successor status by market and distributor.
6. Approve availability and pricing context. Use warehouse and commercial sources rather than estimates.
7. Prepare successor assets. Publish the approved bottle images, tech sheet, sell sheet, descriptions, and supporting files.
8. Draft the recipient version. Include the comparison table, changed facts, requested action, attachments, contact, and response context.
9. Review by function. Product, compliance, item data, logistics, commercial, brand, sales, and operations owners approve their parts.
10. Send one controlled revision. Preserve the exact message, files, links, recipients, and send record.
11. Track responses. Record acceptance, assigned codes, corrections, open conditions, and due owners.
12. Verify downstream systems. Compare the live distributor item, warehouse record, price, and assets with the approved successor.
13. Manage sell-through. Keep predecessor records and assets visible only where overlap requires them.
14. Close or correct. Complete the tracker or issue a controlled replacement notice.

A Depletement pre-launch workspace being designed for importer operations is intended to organize current product details, bottle and brand assets, tech sheets, sell sheets, distributor asset access, and vintage updates. Whatever system holds the announcement workflow, preserve the prior release, successor evidence, approved package, recipient response, and downstream completion record.

Complete final new-vintage announcement QA

Run this checklist against the controlled successor, exact announcement package, recipient list, and downstream tracker.

Scope and identity

• Producer, wine, prior vintage, successor vintage, market, distributor, and division are explicit.
• The successor has its own release record linked to the predecessor.
• Prior history, approvals, assets, and distributor records remain intact.
• Every inherited field is confirmed unchanged, changed, awaiting evidence, not applicable, or retired.
• Vintage, origin, class or type, ABV, bottle volume, package, and market language match approved evidence.
• The announcement states whether it is a notice, item update, new-item request, sales release, or correction.

Identifiers, availability, and price

• Importer SKU, producer code, consumer GTIN, case GTIN, distributor code, and state code remain separate.
• GTIN treatment records the issuer, packaging level, rule considered, evidence, and approver.
• The announcement does not claim every vintage requires a new GTIN or item number.
• Distributor-owned code treatment has been confirmed or marked pending.
• Bottle volume, case pack, case data, and warehouse mapping describe the successor package.
• Availability language matches the approved production, transit, warehouse, and order state.
• Prior and successor ordering instructions remain clear during overlap.
• Currency, price basis, case pack, effective context, and commercial approval are complete.
• Unapproved costs, margins, estimates, and internal scenarios are excluded.

Labels, assets, and claims

• Compliance reviewed the successor package against the applicable label approval and allowable-revision process.
• State and distributor requirements remain separate from the federal label review.
• Front image, back image, tech sheet, sell sheet, descriptions, and labels show the same successor.
• Blend, vineyard, production, analysis, tasting, certification, and accolade fields have successor evidence.
• No predecessor score, quotation, bottle image, or technical value was copied without review.
• Filenames, document titles, metadata, links, and image descriptions identify the intended vintage.
• Distributor access contains only approved current files for each active vintage.

Message and downstream completion

• Subject line names the product, successor vintage, market, and action or notice type.
• Comparison table clearly shows prior value, successor value, and recipient action.
• Unchanged, pending, not applicable, and unknown states are not represented by blanks.
• Requested action, response context, and accountable importer contact are visible.
• Email body, attachments, links, recipient list, revision, and send context received approval.
• The exact sent package is retained.
• Distributor item data, warehouse, pricing, assets, portfolio, training, and market tasks have tracker rows.
• Recipient acceptance, assigned code, exception, or correction is recorded separately from sent status.
• The live distributor item matches the approved vintage, code, pack, price basis, and assets.
• Intentional overlap references remain visible and stale predecessor references are removed.
• Any correction supersedes the faulty notice and identifies the exact changed value.
• A second reviewer can trace the announcement to successor evidence, approvals, recipient response, and every downstream completion record.

A dependable new-vintage announcement makes the transition operationally clear. It preserves the predecessor, identifies the successor, avoids assumptions about codes, states the availability and commercial context, delivers approved assets, and follows the change until each recipient system reflects the intended vintage.