Wine Product Catalog Template for Distributors

Build a distributor catalog from controlled product records

This guide is for alcohol importer operations teams, portfolio managers, and supplier coordinators building a wine product catalog for distributor sales, purchasing, item-data, and marketing users. It covers catalog scope, product and market records, identifiers, compliance references, logistics, pricing, assets, access, publication, vintage rollover, a reusable template, and final QA.

A distributor catalog should help its intended reader find the correct active wine, understand what it is, locate the approved sales materials, and identify the right operations contact. It should not become the only place where the importer stores evidence or approves product facts.

Build the catalog as a recipient view of controlled source records. Keep internal evidence, restricted commercial files, drafts, and prior revisions connected to those records but outside the distributor’s normal access. This is an operations template, not legal advice. The responsible compliance owner should decide which federal, state, and market requirements apply.

Define the catalog before collecting fields

Do not begin by copying every row from an item master into a brochure. Define the catalog’s audience, market, product scope, and purpose first.

Use this control block:

Control	Required entry
Catalog ID	Stable internal reference
Catalog purpose	Item setup, sales reference, asset access, portfolio presentation, or another named use
Distributor	Exact recipient organization
Division and market	State, territory, channel, branch, or other defined scope
Included portfolio	Brands, producers, categories, and active items covered
Excluded material	Drafts, restricted records, discontinued items, or other defined exclusions
Operations owner	Person responsible for completeness and publication
Field approvers	Product, compliance, commercial, logistics, and brand owners as applicable
Source location	Controlled product records and evidence
Publication format	Portal, spreadsheet, PDF, shared collection, or approved combination
Revision	Controlled release identifier
Status	Draft, in review, approved, published, superseded, or archived
Effective context	Event or approved period for which the release is intended
Reopen triggers	Changes that require review and republication

One importer may need more than one catalog. A public portfolio catalog, a distributor item-setup workbook, and a sales asset collection serve different purposes. Reuse approved source values, but publish only the fields each audience needs.

Separate the product, release, and market item

A single row is often asked to represent three different records. Keep them distinct even if the final distributor view combines selected fields.

Record	What it represents	Typical fields
Product	The continuing wine identity	Producer, brand, cuvee, category, country, region, appellation
Release	A vintage or non-vintage expression	Vintage status, blend, production details, analysis, tasting copy, bottle image
Market item	A sellable configuration for one route to market	Importer SKU, volume, pack, GTINs, distributor code, price reference, warehouse, status

This separation prevents a vintage update from overwriting product history and prevents a market-specific price or distributor code from appearing as a universal product fact.

Create a separate market-item row when volume, case pack, identifier, warehouse treatment, commercial basis, market status, or recipient code differs. Link all market items back to the correct release.

Use one reusable catalog item template

Complete this record before formatting a spreadsheet, PDF, or portal page. Use Not provided, Pending review, or Not applicable instead of leaving an ambiguous blank.

Catalog identity and control

Field	Entry
Product record ID	[Stable product reference]
Release ID	[Stable vintage or non-vintage release reference]
Market-item ID	[Stable sellable-configuration reference]
Catalog display name	[Approved producer and wine name]
Status	[Preparing, active, sell-through, paused, discontinued, or other controlled state]
Market and distributor	[Exact scope]
Record owner	[Named role or person]
Approved revision	[Revision identifier]
Last reviewed	[Internal review record]
Source packet	[Internal location]

Product and release facts

Field	Entry	Deciding source
Producer	[Approved display name]	Product identity record
Brand and cuvee	[Approved display name]	Product identity record
Vintage status	[Vintage or non-vintage wording]	Release evidence
Wine class or type	[Approved wording]	Label and compliance record
Country, region, and appellation	[Approved presentation]	Label and producer evidence
Variety or blend	[Verified wording and percentages when approved]	Producer technical evidence
ABV	[Approved value]	Current package and compliance record
Net contents	[Bottle volume]	Current package record
Production summary	[Concise verified text]	Producer technical evidence
Tasting and service copy	[Approved trade copy]	Release review
Certification or claim	[Approved wording or not shown]	Current scoped evidence

TTB’s wine labeling guidance lists federal wine-label topics that include brand name, class or type, alcohol content, name and address, net contents, and appellation of origin when applicable. Use the qualified compliance owner’s approved wording for the actual package and market. Do not treat a catalog field as a substitute for label review.

Identifiers and ordering

Field	Entry	Control rule
Producer code	[Value or not assigned]	Preserve the issuer’s value
Importer SKU	[Value]	Use the controlled item master
Consumer GTIN or UPC	[Value or not assigned]	Identify the packaging level
Case GTIN	[Value or not assigned]	Keep separate from the bottle code
Distributor item code	[Assigned value, pending, or not applicable]	Distributor-owned field
State or listing code	[Value and jurisdiction]	Market-specific field
Bottle volume	[Value and unit]	Match the exact market item
Case pack	[Units per case]	Match ordering and pricing basis
Order contact or route	[Approved recipient guidance]	Confirm with operations

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. Do not copy a consumer code into a case field to fill a gap. Store identifiers as text so leading digits and formatting are not altered by spreadsheet software.

Logistics and commercial references

Field	Entry	Deciding source
Ship-from location	[Approved warehouse or route]	Logistics record
Case dimensions	[Length, width, height, and unit]	Current measured or approved specification
Gross case weight	[Value and unit]	Current measured or approved specification
Pallet pattern	[Cases per layer, layers, total when used]	Warehouse specification
Lead-time guidance	[Approved context]	Current operations source
Availability status	[Controlled state]	Inventory or release owner
Price-list reference	[Approved document or record]	Commercial source
Currency and basis	[Currency, bottle or case basis]	Commercial source
Effective context	[Approved market context]	Commercial source

The catalog should point to the current controlled price record rather than expose internal cost, margin, or planning scenarios. If price appears in the distributor view, show the item, currency, unit or case basis, pack, and applicable context together.

Assets and contacts

Field	Entry	Publication check
Front bottle image	[Approved file]	Correct release and package
Back bottle or label image	[Approved file when needed]	Correct release and package
Tech sheet	[Approved current file]	Facts match this record
Sell sheet	[Approved current file]	Claims and contacts match
Producer or brand assets	[Approved collection]	Usage scope recorded
Training material	[Approved file or collection]	Intended audience recorded
Sales contact	[Role, inbox, phone, or approved route]	Current and recipient-facing
Operations contact	[Role or approved route]	Current escalation owner

Use filenames that remain meaningful after download. Include the producer, wine, vintage status when relevant, market or language when relevant, and revision. Avoid filenames built around final, new, or latest.

Create a field ownership matrix

Every catalog field needs one deciding source and one accountable owner. Several teams can contribute, but several conflicting sources should not compete at publication time.

Field group	Accountable owner	Typical source	Publication gate
Product identity	Portfolio or product owner	Controlled identity record	Name and hierarchy approved
Label-facing facts	Compliance owner	Current package and approval evidence	Market wording approved
Production facts	Producer liaison or product owner	Current technical evidence	Release-specific facts confirmed
Item identifiers	Item-data owner	Assignment and item-master records	Packaging level verified
Logistics	Logistics owner	Warehouse and package specification	Configuration confirmed
Pricing	Commercial owner	Approved price record	Audience version approved
Claims and accolades	Brand and compliance owners	Current claim evidence	Scope and wording approved
Assets	Brand owner	Approved asset library	Rights and release identity checked
Catalog release	Operations owner	Approved records and files	Complete package accepted

If sources conflict, stop publication for the affected field. Record the conflict, owner, required evidence, and due context. Correct the source record first, then regenerate every affected catalog output.

Keep compliance evidence connected but restricted

A distributor may ask for a COLA reference, label image, or market-registration evidence. Provide only the approved recipient-facing record and keep the internal review packet under appropriate access.

The TTB Public COLA Registry provides information on approved, expired, surrendered, and revoked COLAs. Treat a registry result as a verification input. It does not establish that a catalog image, physical bottle, market status, or current sales claim matches the represented approval.

For every compliance reference included in the catalog, record:

Control	Required entry
Requirement class	Federal, jurisdiction-specific, distributor-required, or internal
Product and package scope	Exact release and configuration covered
Market scope	Jurisdiction or distributor relationship
Evidence reference	Controlled filing, approval, certificate, or decision
Status	Pending, approved, exception, expired, superseded, or not applicable
Owner	Qualified person responsible for the decision
Recipient version	Exact field or file approved for sharing

Do not present distributor acceptance as regulatory approval. Do not present a federal label record as proof that every state, price, appointment, warehouse, or distributor step is complete.

Design the catalog for retrieval, not decoration

A distributor user should be able to filter or scan the catalog by producer, brand, wine, vintage status, category, origin, package, item code, and availability state. Place those fields before long product copy.

Use a repeatable display order:

Product name and active status.
Producer, brand, wine, and vintage identity.
Country, region, appellation, category, and variety or blend.
Bottle volume, case pack, importer SKU, and distributor code.
Short verified product and tasting copy.
Approved tech sheet, sell sheet, and bottle-image links.
Availability, ordering route, and contact.

Keep paragraphs short. Use tables for exact item data and prose for context. If a PDF becomes too dense to scan, publish a compact index with links to product sheets rather than shrinking every field onto one page.

Control distributor access by purpose

Do not give every recipient access to the working source library. Publish a deliberate recipient collection.

Collection	Intended access	Exclude
Distributor catalog	Approved distributor users	Draft and internal-only items
Sales assets	Sales and marketing users	Source evidence and expired rights
Item setup	Operations and item-data contacts	Internal planning notes
Commercial files	Authorized commercial contacts	Cost, margin, and unrelated markets
Compliance packet	Named compliance or setup contacts	Credentials and unrelated records
Internal archive	Authorized importer users	Not available through recipient links

Test access as a recipient. Confirm that an approved user can open and download the intended files without requesting internal permissions, and that the same link does not expose neighboring drafts or restricted records.

Run the catalog workflow from intake to publication

Use one sequence with visible approval gates:

Define the audience. Record distributor, division, market, purpose, format, scope, and exclusions.
Open the release. Assign the catalog ID, owner, revision, approvers, and effective context.
Select exact market items. Include only the products, releases, packages, and statuses intended for this catalog.
Map every field. Connect each published value to a deciding source and accountable owner.
Resolve identity conflicts. Reconcile names, vintage status, origin, ABV, volume, pack, and identifiers before writing copy.
Verify recipient codes. Keep importer, producer, consumer, case, distributor, and state identifiers separate.
Confirm market evidence. Record the applicable compliance and distributor decisions without exposing restricted material.
Confirm logistics and commercial context. Check the package, warehouse, availability source, currency, and price basis.
Assemble approved assets. Match bottle images, tech sheets, sell sheets, claims, and training files to each release.
Build the recipient view. Apply the approved display order and remove fields outside the audience’s purpose.
Review by function. Each owner approves the values and files under that function’s control.
Test links and access. Use a recipient account or equivalent permission test.
Publish one revision. Preserve the exact spreadsheet, PDF, portal export, or collection that recipients received.
Capture acceptance. Record distributor feedback, assigned codes, exceptions, and requested corrections.
Verify downstream use. Compare a live item and downloaded assets with the approved source record.

Published should not mean accepted. Keep publication status, recipient acceptance, and downstream completion as separate fields.

Handle vintage rollover as a catalog change set

Create a successor release and preserve the prior vintage. Do not replace the vintage value inside the old record.

Review this transition table for every affected market item:

Control	Prior release	Successor release	Required decision
Vintage status	[Prior value]	[Successor value]	Confirm release identity
Blend and production	[Prior values]	[Verified successor values]	Confirm changed or unchanged
ABV and analysis	[Prior values]	[Verified successor values]	Use current evidence
Consumer GTIN	[Prior code]	[Approved treatment]	Identifier owner decides
Case GTIN	[Prior code]	[Approved treatment]	Review package level
Distributor item code	[Prior code]	[Assigned, reused, or pending]	Distributor confirms
Volume and pack	[Prior configuration]	[Successor configuration]	Reopen logistics and price basis if changed
Availability	[Prior state]	[Successor state]	Define overlap and order guidance
Bottle image	[Prior file]	[Successor file]	Verify visible release identity
Tech and sell sheets	[Prior files]	[Successor files]	Regenerate from approved facts
Claims and accolades	[Prior evidence]	[Successor evidence]	Do not carry forward without review

A vintage date can be an allowable change to an approved label under the conditions in TTB’s allowable label revisions guidance. That does not mean every successor package is automatically covered. The compliance owner should review the actual change and applicable conditions.

During sell-through, keep both releases visible when both can be ordered. State the market, distributor, code, asset set, and availability for each. Remove the predecessor from routine recipient access only after the responsible owners confirm the transition.

Correct a published catalog without hiding the error

Do not patch only the visible PDF or distributor portal row. A local patch leaves the source ready to recreate the same error.

Use this correction process:

Record the incorrect value, correct value, affected items, recipients, and outputs.
Stop use of the affected revision where possible.
Confirm the correction with the accountable field owner.
Update the controlled source record.
Repeat affected compliance, commercial, logistics, or brand approvals.
Regenerate the complete recipient output.
Publish a replacement with a new revision.
Mark the earlier release superseded without deleting its history.
Notify affected recipients with the exact correction and requested action.
Verify the distributor’s live record and downloaded assets.

Keep the correction record linked to both revisions. A reviewer should be able to see what changed, why it changed, who approved it, and where the replacement was confirmed.

Choose a system that preserves the controls

A spreadsheet and controlled shared drive can support this process if ownership, source links, status, permissions, and revision history are maintained consistently. The system matters less than whether the team can identify the approved source, exact recipient release, and current market item.

Depletement’s pre-launch workspace for alcohol importer operations is being designed to organize product and catalog details, bottle and brand assets, technical sheets, sell sheets, distributor asset access, and vintage updates. Until a pre-launch product becomes part of an approved workflow, keep using the controls your team can verify today.

Complete final wine product catalog QA

Run this checklist against the controlled records, exact recipient release, access settings, and live distributor use.

Scope and control

Catalog purpose, distributor, division, market, portfolio scope, and exclusions are explicit.
Product, release, and market-item records remain separate and linked.
Every included item has an owner, status, source packet, revision, and approval state.
Product identity, compliance, commercial, logistics, brand, and operations owners approved their fields.
Unknown, pending, unchanged, not applicable, and discontinued states are not represented by blanks.
Published, accepted, and downstream-complete statuses are tracked separately.

Product identity and evidence

Producer, brand, cuvee, vintage status, class or type, country, region, and appellation match approved sources.
Variety, blend, production, farming, certification, tasting, and service statements have current evidence.
ABV and net contents match the exact package and approved market presentation.
Claims and accolades identify the correct wine and release and have retained evidence.
Catalog copy does not replace label, regulatory, or market review.
Federal, jurisdiction-specific, distributor-required, and internal controls are distinguished.

Identifiers, logistics, and commercial data

Producer code, importer SKU, consumer GTIN, case GTIN, distributor code, and state code remain separate.
Each GTIN identifies its packaging level and has been checked against its assignment source.
Bottle volume and case pack match the item, price basis, and warehouse record.
Case dimensions, gross weight, pallet data, ship point, and lead-time guidance are current where published.
Availability language reflects the approved operational state.
Published pricing identifies the item, currency, unit or case basis, pack, market context, and approval.
Internal costs, margins, projections, and unapproved price scenarios are excluded.

Assets and access

Bottle images, label images, tech sheets, sell sheets, descriptions, and training files show the same release.
Every published asset has an owner, approved revision, intended audience, and current rights status.
Filenames remain meaningful after download.
Links open the intended current files and do not redirect users to superseded versions.
Distributor users can reach approved materials without gaining access to drafts or restricted records.
A recipient-level access test was completed for the published collection.

Vintage and publication controls

Every successor release preserves and links to its predecessor.
Carried fields were confirmed rather than assumed from the prior vintage.
GTIN, distributor code, pack, price, availability, and asset treatment were decided separately.
Both vintages remain clear when sell-through overlaps.
Prior-vintage strings were checked in copy, filenames, links, image descriptions, and document metadata.
The exact published workbook, PDF, portal values, links, and access revision are retained.
Recipient corrections update the source first and produce a controlled replacement.
A distributor user can identify the current item, code, pack, asset set, and contact without internal guidance.
A second reviewer can trace each published value to its source, approval, recipient release, and downstream confirmation.