Wine Product Launch Checklist for Wineries

Build one controlled launch record before releasing the wine

This guide is for winery operations, compliance, production, sales, and marketing teams preparing a wine for a new market or sales channel. It covers launch scope, product facts, labels and approvals, packaging, identifiers, commercial decisions, inventory, logistics, sales assets, distributor handoff, vintage transitions, launch-day checks, and final QA.

A launch is not complete because the wine is bottled, the label is approved, or a sell sheet has been emailed. The product must be represented consistently across the package, item record, warehouse setup, price record, distributor submission, and sales materials. Each team should approve the part it controls, and one launch owner should track the whole release.

Use this checklist as an operations control, not as legal advice. A winery selling domestically, exporting through an importer, using a custom-crush arrangement, or launching direct to consumers can have different obligations and counterparties. Have qualified owners confirm the exact requirements for the business, product, jurisdiction, and route to market.

Define exactly what is launching

Start with the sellable configuration, not a broad instruction such as launch the new red wine. One wine may have multiple vintages, bottle sizes, packs, labels, markets, warehouses, prices, and partner item codes.

Create a separate launch record whenever one of those controlled elements differs.

Launch control	Required entry
Launch ID	Stable internal reference
Producer and brand	Approved company and market-facing identity
Wine and release	Exact wine, cuvee, vintage, or non-vintage status
Package	Bottle volume, closure, label set, case pack, and case configuration
Market	Country, state, territory, channel, or other defined scope
Route to market	Winery direct, importer, distributor, agent, retailer, or approved combination
Intended recipients	Named partners, sales teams, accounts, or consumers
Launch owner	Person accountable for the full record
Functional owners	Product, compliance, production, finance, logistics, sales, and brand owners
Target launch context	Approved release window, event, or readiness gate
Status	Planned, collecting, blocked, in review, approved, released, corrected, or closed
Source packet	Controlled location for facts and evidence
Revision	Current launch-package identifier
Open exceptions	Unresolved issue, owner, effect, and next decision

Keep the product, release, market item, and launch event distinct. The product can continue across vintages. The release describes one vintage or non-vintage expression. The market item describes a sellable package in a defined route. The launch record coordinates when and how that item becomes ready.

Assign responsibility before collecting files

Do not ask one person to approve facts or obligations owned by another party. A winery can control production records, package specifications, source assets, and its own business records. An importer, distributor, warehouse, certifier, regulator, or market partner may control other decisions.

Use a responsibility matrix:

Workstream	Accountable owner	Contributors	Evidence of completion
Product identity	Winery product owner	Production, brand, compliance	Approved source record
Formula or process review	Qualified compliance owner	Winemaking and laboratory contacts	Decision and approval reference when applicable
Label review	Qualified compliance owner	Brand, production, importer when applicable	Approved label set and review record
Packaging	Production or operations	Bottler, printer, closure and carton suppliers	Final specification and production check
Item identifiers	Identifier owner	Operations, packaging, trade partners	Assignment record and package verification
Commercial approval	Finance or commercial owner	Sales, importer, distributor	Approved audience-specific price record
Inventory release	Production and quality owners	Warehouse and operations	Released lot and availability record
Logistics	Logistics owner	Warehouse, carrier, importer, distributor	Approved shipping and receiving setup
Sales assets	Brand owner	Product, compliance, sales	Approved recipient asset set
Partner acceptance	Launch owner	Importer, distributor, retailer, platform	Submission and acceptance evidence

Use responsible, approver, consulted, and informed consistently if the team maintains a RACI chart. The launch owner coordinates the decisions but does not replace the accountable specialist.

Confirm business and market readiness

Before committing inventory or publishing a release date, verify that the planned activity fits the entities, premises, permits, licenses, agreements, and route to market that the responsible owners have approved.

TTB’s federal application process for the wine industry directs prospective industry members to determine whether their business plan requires federal qualification and explains that different wine operations can follow different application paths. Use the current agency guidance and qualified advice for the actual activity. Do not treat a permit held by one entity or premises as automatic coverage for another arrangement.

Record the business-readiness decision without copying credentials or sensitive filings into a broadly shared launch tracker:

Control	Entry
Operating entity	Exact legal entity for the activity
Premises and production arrangement	Approved winery, bonded premises, custom-crush, bottler, or other arrangement
Seller and invoicing entity	Party selling and invoicing through the route
Market partners	Importer, distributor, agent, warehouse, retailer, or platform as applicable
Agreement status	Executed, pending, exception, or not applicable
Territory and channel	Scope granted or approved
Responsible compliance owner	Person confirming federal, state, local, and market steps
Restricted evidence location	Controlled reference to permits, licenses, agreements, and filings
Blocking decision	Exact unresolved issue and owner

Do not announce availability before the seller, route, inventory owner, and fulfillment path are clear.

Approve the wine identity and technical record

Open one source record for the exact release. Do not build labels, item forms, and sales copy from separate email threads.

Identity and composition fields

Field	Required treatment
Producer	Use the approved legal or market-facing name for the destination
Brand and wine name	Preserve approved spelling, punctuation, and hierarchy
Vintage status	Record the exact vintage or non-vintage treatment
Class or type	Use the compliance-approved description
Country, region, and appellation	Use the approved market presentation
Variety or blend	Show only supported wording and percentages
Vineyard or estate claim	Include only with current evidence and approval
ABV	Link to the current package and production source
Net contents	Match the bottle and label under review
Lot or bottling reference	Connect the release to production and quality records

Production and claim fields

Capture harvest, fermentation, aging, finishing, analysis, farming, certification, tasting, service, and aging statements only when the team has a current source for the release. Name the source, owner, scope, and approval state for each claim.

Use these statuses:

confirmed for this release
confirmed unchanged
changed
awaiting evidence
not approved for publication
not applicable

A blank cannot distinguish unknown from unchanged. Do not let a copied predecessor value become approved merely because no one challenged it.

Resolve formula and process questions before label submission

Do not assume that a previous wine’s formula decision applies to a product with different ingredients or production treatment. TTB states that certain wines require evaluation of ingredients and production processes before they can be made or imported and before label submission when label approval is required. The agency provides a wine and cider decision tool on its formula approval guidance.

Have the qualified owner record:

Formula control	Entry
Product and process scope	Exact release, ingredients, and treatment reviewed
Decision source	Current agency tool, specialist review, or other approved source
Formula required	Yes, no, pending, or not applicable
Laboratory analysis required	Decision and source when applicable
Submission or approval reference	Controlled identifier and evidence location
Conditions	Qualifications that must remain true
Label dependency	Whether label work is blocked by the result
Owner and review status	Accountable person and current state

Keep trial versions and abandoned formulations separate from the launch release. If production changes after review, reopen the formula decision instead of editing only the technical sheet.

Lock the label and package as one release

A label approval record and a physical packaging run answer different questions. Review the final front, back, neck, closure, carton, and case presentation as one package.

TTB’s wine labeling guidance identifies label topics that include brand name, class or type, alcohol content, name and address, net contents, health warning, sulfite declaration, and appellation of origin when applicable. The compliance owner should determine which statements and conditions apply to the exact wine and market.

Use a package review table:

Package element	Approved source	Production proof	Final sample	Status
Front label	[File and revision]	[Proof reference]	[Sample reference]	[Status]
Back label	[File and revision]	[Proof reference]	[Sample reference]	[Status]
Neck or auxiliary label	[File and revision]	[Proof reference]	[Sample reference]	[Status]
Bottle and closure	[Specification]	[Supplier proof]	[Sample reference]	[Status]
Carton	[Artwork and specification]	[Proof reference]	[Sample reference]	[Status]
Case label and barcode	[Controlled data]	[Proof reference]	[Scan result]	[Status]

Compare the approval evidence with the final production artwork and a physical or production-representative sample. Check text, legibility, color-dependent distinctions, dimensions, placement, scannability, and release identity. Record deviations and obtain a decision before inventory release.

The TTB Public COLA Registry provides information on approved, expired, surrendered, and revoked COLAs. A registry result can support verification, but the launch record should still connect the exact approval, represented labels, qualifications, and final package review.

Build exact item identifiers

Keep identifiers separate by issuer and packaging level. GS1 US explains that a GTIN identifies a trade item and that a GTIN-14 can identify a grouping such as a case in its GTIN overview.

Create distinct fields for:

winery or producer item code
consumer GTIN or UPC
case GTIN
internal inventory SKU
importer SKU
distributor item code
state or listing code
warehouse code when different

Use this identifier control:

Identifier	Issuer	Packaging level	Assigned value	Verified against	Status
Consumer GTIN or UPC	[Owner]	Bottle or retail unit	[Value]	Final package and assignment	[Status]
Case GTIN	[Owner]	Case	[Value]	Final case and assignment	[Status]
Winery SKU	Winery	Defined internal item	[Value]	Item master	[Status]
Importer SKU	Importer	Defined market item	[Value or pending]	Importer confirmation	[Status]
Distributor code	Distributor	Recipient item	[Value or pending]	Distributor confirmation	[Status]

Store codes as text and preserve the displayed digits. Do not invent a recipient code or copy the bottle identifier into the case field to eliminate a blank. Scan the production barcode using the team’s approved test process before releasing the packaged inventory.

Confirm bottle, case, and pallet specifications

The launch package must describe what the warehouse and partner will receive, not an estimate based on an earlier bottling.

Capture:

Specification	Required entry
Bottle	Volume, bottle type, closure, unit dimensions, and unit weight when used
Case	Pack, orientation, dividers, dimensions, gross weight, and case barcode treatment
Pallet	Pallet type, cases per layer, layers, total cases, total height, and handling limits when used
Lot marking	Format, location, and example from production
Storage	Approved handling and storage instructions
Ship configuration	Full pallet, mixed pallet, floor-loaded, parcel, or other approved method
Source	Measured production sample or current approved specification
Owner	Operations, production, or logistics approver

Measure the completed production case or use a current approved production specification. Do not calculate gross case weight from liquid volume alone. If the bottle, closure, carton, dividers, or pack changes, reopen the affected dimensions, weight, barcode, pallet, freight, and price-basis records.

Approve pricing and commercial terms separately

Keep the internal financial model, partner price record, suggested market positioning, and consumer-facing communication as separate controlled outputs.

For each route and market, record:

Commercial control	Required entry
Seller and buyer	Exact entities
Product and package	Release, bottle volume, and case pack
Currency	Named currency
Price basis	Bottle, case, pallet, or other defined basis
Base price	Approved audience-specific amount
Freight treatment	Included, separate, pickup, delivered, or other approved term
Discounts or programs	Separate approved fields with conditions
Taxes or deposits	Treatment confirmed for the market when applicable
Order minimum	Approved unit and amount
Payment terms	Agreement or approved commercial reference
Effective context	Approved start condition or release window
Approver	Commercial owner
Superseded record	Prior price reference when applicable

Do not publish a planning scenario as an approved price. Check that the case pack used in the price calculation matches the launch item and partner setup. Route jurisdiction-specific posting, filing, or notice questions to the market owner.

Release inventory with a documented gate

Marketing readiness does not make the wine shippable. Define the production and quality evidence required before inventory status changes.

A practical inventory release record includes:

production and bottling reference
lot identification
quantity by approved unit
quality decision and owner
packaging inspection result
barcode test result
warehouse receipt or transfer status
hold, quarantine, release, and exception states
sample quantity and ownership
sellable availability source
first approved ship context

Keep produced, bottled, in transit, received, quality released, and available to order as separate states if they describe different gates in the team’s process. Sales language should use the state approved by inventory and fulfillment owners.

Prepare the logistics handoff

Confirm the route from released inventory to the intended customer or partner. Ask each warehouse, importer, distributor, carrier, or fulfillment provider for its current requirements rather than relying on an old launch.

Use this logistics template:

Control	Entry
Inventory owner	Entity controlling the stock
Ship-from location	Exact facility and approved account
Order route	Purchase order, portal, email, EDI, or other approved process
Order unit	Bottle, case, pallet, or other defined unit
Item codes	Winery, importer, distributor, and warehouse values
Appointment process	Contact, system, lead time, and required references
Shipping documents	Current recipient list and owner
Case and pallet treatment	Approved configuration and labels
Claims route	Shortage, damage, refusal, and discrepancy contacts
First-shipment owner	Person monitoring the initial movement
Acceptance evidence	Warehouse or partner confirmation

Run a desk simulation before the first shipment. Compare a sample purchase order, pick record, case label, packing record, price basis, ship point, and receiving item. Record every mismatch as an exception instead of expecting the receiving team to resolve it later.

Assemble one approved launch asset set

Build assets from the approved release record after factual conflicts are closed. Each file should identify the wine and release it represents.

Prepare only the materials needed for the audience:

front bottle image
back bottle or label image when useful
current tech sheet
sell sheet
short and long product descriptions
winery and winemaker biographies
logo and approved brand elements
vineyard, cellar, and lifestyle images with recorded usage rights
approved tasting and service guidance
verified certification and claim support
verified accolades tied to the correct wine and vintage
trade presentation and training material
current sales and operations contacts

Use a control table for every published asset:

Asset	Product scope	Audience	Owner	Approval	Rights or usage scope	Current revision
[File or collection]	[Release and market]	[Recipient]	[Owner]	[Status]	[Scope]	[Revision]

Keep drafts, source analyses, internal margin files, expired rights, and superseded materials outside the recipient collection. Use filenames that remain clear after download. Avoid final, new, and latest as the only version signal.

Create a partner-ready launch package

An importer or distributor should not have to reconcile multiple files to determine the product identity, package, price basis, and next action.

Use this partner submission header:

Field	Required entry
Submission ID	Stable reference
Partner and division	Exact recipient scope
Market and channel	Approved launch scope
Product and release	Exact wine and vintage status
Package	Bottle volume, pack, and identifiers
Purpose	Vendor setup, item setup, listing, pricing, sales release, or combined handoff
Requested action	Specific task for the recipient
Response requested	Approval, assigned code, exception, or confirmation
Attachments and links	Exact approved revision of each item
Sender	One coordinating contact
Submission status	Draft, sent, accepted, corrected, blocked, or closed
Evidence	Copy of exact submission and recipient response

Request the partner’s current templates and field definitions. Map each submitted value back to the controlled source. Save the exact workbook, email, portal values, and attachments that left the winery.

Sent is not the same as accepted. Record partner approval, assigned identifiers, requested corrections, open conditions, and downstream completion separately.

Plan sales training, samples, and launch communications

Sales readiness should follow product approval, not run ahead of it. Give each audience enough information to present the wine accurately and route operational questions correctly.

The launch brief should state:

exact wine and vintage status
launch market and intended accounts
approved positioning and product story
production facts that matter to the audience
tasting and service guidance
bottle volume, pack, and order reference
availability wording
approved price reference for the audience
sample request and tracking route
approved assets and training materials
contact for product, order, and issue questions
claims or wording that should not be used

Separate a target from a confirmed order, a release plan from available inventory, and a suggested account from an approved customer. Do not place projections in product-fact fields.

For samples, record inventory owner, quantity, purpose, recipient, market, shipment or handoff, approval, and disposition according to the team’s applicable process. Keep sample inventory distinguishable from sellable stock.

Use a launch readiness dashboard with hard gates

A single completion percentage can hide a critical blocker. Track workstreams and gates separately.

Gate	Ready when	Blocked by	Approver
Product facts	Identity, technical data, and claims are sourced and approved	Unresolved source conflict	Product owner
Compliance	Applicable business, formula, label, and market decisions are complete	Pending decision or approval	Compliance owner
Package	Final components and production sample match approved records	Artwork or specification deviation	Production owner
Item data	SKUs, GTINs, pack, and partner mappings are verified	Pending assignment or mismatch	Item-data owner
Commercial	Audience price and terms are approved	Pack, cost, or agreement conflict	Commercial owner
Inventory	Lot and packaging are released	Quality or warehouse hold	Quality and inventory owners
Logistics	Order, ship, receive, and claims routes are tested	Partner or warehouse exception	Logistics owner
Assets	Current recipient files are approved and accessible	Stale facts, rights, or links	Brand owner
Partner	Required submissions are accepted	Open recipient request	Launch owner
Go-live	Every required gate is ready or has an approved exception	Any unaccepted critical blocker	Launch approver

An exception should name the affected item, risk, temporary treatment, approving person, owner, and closure condition. Do not convert a blocker to ready by moving the explanation into notes.

Run the wine product launch workflow

Use one controlled sequence:

Open the launch record. Define the wine, release, package, market, route, owner, target context, and required gates.
Map responsibilities. Assign each decision to the winery, importer, distributor, warehouse, or other accountable party.
Confirm business readiness. Verify entities, premises, permissions, agreements, territories, and channels for the planned activity.
Approve the release facts. Resolve identity, composition, production, analysis, and claim evidence.
Complete formula and label decisions. Record applicability, submissions, approvals, conditions, and represented files.
Lock the package. Compare final artwork, bottle, closure, carton, case label, and production sample.
Assign and verify item data. Separate identifiers by issuer and packaging level, then test the final barcodes.
Approve physical specifications. Confirm bottle, case, pallet, lot, storage, and handling data.
Approve commercial records. Lock the audience, item, currency, basis, pack, terms, and effective context.
Release inventory. Record quality, packaging, warehouse, quantity, and availability decisions.
Test logistics. Simulate ordering, picking, shipping, receiving, and exception handling.
Publish the asset set. Release approved images, sheets, descriptions, training, and contacts to the intended audience.
Submit to partners. Preserve exact forms, portal values, files, links, and recipient responses.
Train the launch team. Use approved language, availability, ordering references, sample routes, and escalation contacts.
Hold the readiness review. Close every gate or document an accepted exception and closure condition.
Release communications. Publish only the approved message and current links.
Monitor first activity. Check orders, shipments, receiving, live listings, price presentation, and asset access.
Close or correct. Retain evidence of completion or issue a controlled replacement.

A Depletement pre-launch workspace for importer operations is being designed to organize product and catalog information, bottle and brand assets, technical sheets, sell sheets, distributor asset access, and vintage updates. Whether a winery works through an importer workspace, a shared drive, or controlled spreadsheets, it should preserve source evidence, ownership, approvals, recipient access, and the exact launch release.

Manage vintage rollover as another launch

A new vintage is a successor release, not an edit to the previous record. Preserve the predecessor, create the successor, and reopen every field that could have changed.

Use this rollover table:

Control	Prior release	Successor release	Decision
Vintage and product identity	[Prior]	[Successor]	Confirm approved presentation
Blend and vineyard sources	[Prior]	[Successor evidence]	Changed or confirmed unchanged
Production and analysis	[Prior]	[Successor evidence]	Reapprove release facts
Formula and label treatment	[Prior decision]	[Successor decision]	Compliance owner confirms
Bottle and case	[Prior]	[Successor]	Reopen package controls
GTINs and SKUs	[Prior]	[Approved treatment]	Identifier owners decide
Partner item codes	[Prior]	[Assigned, reused, or pending]	Partner confirms
Price and terms	[Prior]	[Successor]	Commercial owner approves
Inventory status	[Prior]	[Successor]	Define overlap and availability
Images and documents	[Prior files]	[Successor files]	Replace as a coordinated set
Claims and accolades	[Prior evidence]	[Successor evidence]	Do not carry forward without review

Keep both releases visible when both are intentionally active. Define whether orders can specify a vintage, whether the partner uses one continuing item or separate items, and which assets belong to each release. Do not promise a specific vintage unless inventory and fulfillment controls support that promise.

Search the complete successor package for the prior vintage string. Check visible copy, filenames, links, bottle images, document titles, image descriptions, and PDF metadata.

Correct launch errors at the source

If an item code, pack, price, label image, product fact, or claim is wrong after publication, do not patch only the recipient-facing file.

Follow this correction sequence:

Stop use or shipment of the affected material or item where the responsible owner requires it.
Define the incorrect value, correct value, product scope, market scope, and affected recipients.
Correct the controlled source record.
Identify every generated file, partner submission, system, listing, and communication that repeated the error.
Repeat the required specialist approvals.
Regenerate the complete replacement package with a new revision.
Mark the former revision superseded while preserving its history.
Send a clear correction stating the affected item, prior value, corrected value, and requested action.
Capture recipient acknowledgment and downstream correction.
Verify the live item, order route, warehouse record, and current assets.

A second reviewer should be able to trace the correction from discovery through source approval to every completed replacement.

Complete final wine product launch QA

Run this checklist against the controlled launch record, physical package, released inventory, exact partner submissions, current assets, and live route to market.

Scope and ownership

Producer, brand, wine, release, vintage status, package, market, channel, and route to market are explicit.
Product, release, market item, and launch event remain separate and linked.
Legal entity, winery, seller, importer, distributor, warehouse, and other partners are identified by role.
Every workstream has an accountable owner, approval state, evidence, blocker, and closure condition.
Target launch context and actual readiness are recorded separately.
Planned, submitted, approved, released, accepted, and closed are not treated as one status.

Product, formula, and label controls

Producer, brand, wine, vintage, class or type, origin, appellation, variety or blend, ABV, and net contents match approved sources.
Production, analysis, farming, certification, tasting, service, and accolade claims have current release evidence.
Unknown, unchanged, pending, not approved, and not applicable fields are distinguished.
Formula or process applicability was reviewed for the exact product and production method.
Label decisions identify the represented files, approval reference, conditions, owner, and market scope.
Final front, back, auxiliary, closure, carton, and case presentation matches approved records.
A production-representative package was inspected and deviations were resolved.
Federal, state, local, partner, and internal requirements remain separate.

Item, package, and commercial controls

Winery SKU, consumer GTIN, case GTIN, importer SKU, distributor code, state code, and warehouse code remain separate.
Every identifier records its issuer, packaging level, assignment source, and verification status.
Production barcodes were tested using the approved process.
Bottle volume, closure, case pack, dimensions, gross weight, pallet data, lot marking, and handling instructions match the released configuration.
Published price records identify seller, buyer, item, currency, basis, pack, terms, effective context, and approver.
Internal cost, margin, projection, and unapproved price scenarios are excluded from recipient materials.
A package or pack change reopened affected identifier, logistics, freight, and commercial decisions.

Inventory and logistics

Production, bottling, lot, quality, packaging, barcode, and warehouse evidence support release.
Produced, in transit, received, quality released, and available to order are distinguished where applicable.
Inventory quantity and sample quantity have named sources and owners.
Ship-from location, order route, unit, item mapping, appointment process, documents, and claims contacts are current.
A desk simulation compared the purchase order, pick record, case label, price basis, shipment, and receiving setup.
The first order and shipment have a monitoring owner and escalation route.
Sales availability language matches the approved inventory and fulfillment state.