Wine Distributor Price List Template for Importer Operations

Build the price list for the team that will use it

This guide is for alcohol importer operations teams preparing a wine distributor price list for a defined market, distributor, and commercial audience. It covers document control, item rows, recommended columns, case and unit calculations, vintage and package distinctions, identifiers, discounts and charges, approval, controlled versions, spreadsheet QA, PDF QA, and superseded-file retention.

The goal is a price list that lets an authorized recipient identify the exact sellable item, understand the stated price basis, and know which version applies. It is an operational template, not legal advice, a live inventory report, or a substitute for required business records. Market rules and commercial terms need review by the people responsible for that jurisdiction and account.

Keep the price list separate from nearby documents

A price list repeats some fields found elsewhere, but its job is narrower. It communicates controlled commercial information for specific items and a specific context.

A portfolio overview introduces producers and organizes the range. An item master defines each sellable configuration with its full identity and logistics data. A sell sheet makes a focused sales case for one wine. An invoice records an actual transaction. A live inventory view reports changing stock or availability. The distributor price list states the authorized pricing offer or schedule for its named audience and effective context.

Use the item master as the source for identity, codes, volume, and pack. Use the approved commercial record as the source for prices, terms, and adjustments. Do not let a formatted PDF become the only record of either.

The broader guide to documents to have ready for a distributor places the price list alongside onboarding, item setup, logistics, compliance, sales, and brand materials. Keep those files connected, but do not merge them into one difficult-to-control workbook.

Start with a document-control header

Put the control block above the item table in both the spreadsheet and PDF. A recipient should be able to tell whether the document applies before reading a price.

Use this reusable header:

Field	Required entry
Supplier	Exact legal or approved trade name issuing the list
Document title	Wine distributor price list
Market	State, territory, or other defined commercial market
Audience	Named distributor, distributor group, internal team, or other authorized audience
Currency	Explicit currency for every monetary column
Price basis	Case, bottle, other unit, or clearly identified combination
Effective context	Start date, schedule period, or other approved applicability statement
Supersedes	Prior revision or file identifier, when applicable
Revision	Controlled version identifier
Status	Draft, approved, current, or superseded
Commercial owner	Person or function accountable for price approval
Operations owner	Person or function accountable for item accuracy and publication
Contact	Maintained route for questions, orders, or current availability
Confidentiality	Distribution restriction when required by company policy

Avoid vague labels such as current pricing, new list, or latest. A downloaded file can circulate after the commercial context changes. Market, audience, revision, and effective context make that copy identifiable.

Use one row per unique market sellable item

Each row should represent one exact configuration that can be priced and ordered in the stated market. Create separate rows when vintage, non-vintage status, bottle volume, package format, case pack, supplier code, distributor code, or applicable price differs.

Do not combine a 750 mL bottle and a 1.5 L bottle in one row. Do not put multiple vintages into a cell such as 2022/2023 when they have different item identities, availability, or prices. Do not use one row for both a standard case and a gift-box format. If two configurations need separate order references, they need separate price-list rows.

A stable internal market-item ID helps operations connect the row to its source. The visible product name should still be understandable to the distributor. An internal code alone should not force the recipient to search another system to learn which wine is being offered.

Use this recommended column template

Start with the minimum columns needed for the audience. Add fields because they prevent ambiguity or support the commercial process, not because the spreadsheet has room.

Column	What to enter	Control note
Producer	Approved producer name	Match the item master
Wine or cuvée	Exact product name	Preserve approved spelling and accents
Vintage	YYYY or non-vintage status	Never infer from an old filename
Appellation or region	Approved market wording	Include only at useful detail
Wine type	Still, sparkling, fortified, or other approved type	Keep controlled choices consistent
Bottle volume	Exact unit volume	Keep separate from pack
Format	Standard bottle, half bottle, magnum, can, gift box, or another precise format	Use the term your item records support
Case pack	Number and type of units in the priced case	Confirm against the current market item
Supplier item code	Importer or supplier order code	One code per exact configuration
Distributor item code	Market distributor reference, when assigned	Do not reuse across distributors without confirmation
Consumer GTIN	Unit identifier when used	Optional unless the operating process requires it
Case GTIN	Case identifier when used	Keep separate from the consumer unit identifier
Case price	Approved case amount in the named currency	State whether it is base or net
Unit price	Approved or calculated amount per bottle or unit	State the calculation and rounding rule
Price basis	Case, bottle, unit, or another basis	Do not leave the recipient to infer it
Availability status	Current, allocated, seasonal, future release, paused, or discontinued	Do not use as live inventory quantity
Notes	Only controlled commercial qualifications	Keep internal review notes elsewhere

Optional columns can include minimum order, mixed-case eligibility, deal code, freight basis, deposit, allowance reference, tax treatment note, or separate effective context. Add them only when their meaning is defined and their owner can keep them current.

Keep vintage, volume, format, and pack visible

Wine identity is not complete when the row shows only producer and cuvée. The recipient needs to know which vintage or non-vintage item, volume, format, and pack the price describes.

Use separate fields instead of embedding everything in the product name. Producer Cuvée 2023 750 mL 12-pack may be readable, but separate columns allow validation, sorting, export mapping, and comparison. The display name can combine those fields in the PDF while the spreadsheet retains the structure.

Treat a vintage rollover as a new item review, even when the supplier code remains unchanged. Confirm the current vintage practice with the distributor, then verify package, identifiers, price, availability state, and effective context. Do not replace the prior vintage string in the layout and assume the row is ready.

When two vintages remain available, list each intentionally. Their item codes, prices, or allocation terms may be identical, but the rows should still identify the exact wine being offered.

Handle supplier codes, distributor codes, and GTINs carefully

Supplier and distributor codes answer different operational questions. The supplier code connects the row to the importer’s record. The distributor code connects it to the distributor’s ordering or item system. Keep separate columns, and leave an unassigned distributor code blank or marked pending in the controlled working file rather than inventing one.

GTIN fields are optional unless the relevant workflow requires them. GS1 explains that a Global Trade Item Number identifies a trade item, that different packaging levels can use separate identifiers, and that the identifier does not contain the product’s price. A consumer bottle and a case can therefore have distinct GTIN fields in the item record.

Do not call a GTIN universally mandatory. Do not copy a consumer unit identifier into the case column simply to fill the cell. Validate each identifier against the approved item source and preserve leading zeroes in the spreadsheet by storing identifier fields as text.

Define case and unit price calculations

Choose a primary price basis and label it. If the approved price is per case, make case price the controlled input and calculate unit price from the verified case pack. If the approved price is per bottle, document whether the case amount is calculated or separately approved.

Use a written calculation rule:

Unit price = case price divided by sellable units per case

For an explicitly illustrative example, a fictional case price of $144.00 for a fictional 12-bottle case produces an illustrative unit value of $12.00. These figures demonstrate the formula only. They are not market prices, margins, or recommended benchmarks.

Rounding needs one documented policy. Decide the decimal precision for displayed unit prices, which value is authoritative, and whether downstream totals use the unrounded calculation or the displayed amount. Test the policy with packs that do not divide evenly.

For another explicitly illustrative calculation, a fictional $100.00 case divided by a fictional 6-unit pack yields $16.666... before rounding. If the display policy shows $16.67, do not multiply the displayed value back to $100.02 and silently replace the approved case price. Keep the approved case price authoritative when that is the defined basis.

Use formulas in the working spreadsheet, then protect or lock formula columns according to the team’s process. Do not hand-type both case and unit prices when one is supposed to derive from the other. Manual duplication creates a second value that can drift.

Separate base price from discounts and other adjustments

A single price column becomes ambiguous when the commercial offer also involves discounts, billbacks, depletion allowances, freight, taxes, or deposits. Decide whether the list shows base price, net price, or both, and label each amount.

Keep these concepts separate when they apply:

Base price: The approved starting amount for the stated basis.
Discount: A reduction tied to defined eligibility, quantity, period, or account condition.
Allowance: A separately approved commercial support amount with its own basis and owner.
Freight: Included, excluded, prepaid, collect, or otherwise stated using approved terms.
Taxes: Included, excluded, or handled separately according to the responsible market process.
Deposit or fee: A separate amount tied to the applicable package or market process.
Net price: A calculated result only when every included adjustment and formula is clear.

Do not hide several adjustments inside a notes cell. Use named columns or a controlled companion schedule when the terms need more structure. Identify whether an amount applies per case, bottle, unit, order, or other basis.

If an adjustment changes on a different schedule from base pricing, give it its own effective context. A permanent-looking PDF should not imply that a short commercial program remains active indefinitely.

Control currency, market, audience, and effective context

Never rely on a currency symbol alone when a list may cross borders or systems. Name the currency in the header and use consistent number formatting. Do not combine currencies in one price column.

Create separate controlled versions when market, distributor, audience, currency, price basis, terms, or effective context differs. A public sales asset should not carry confidential distributor pricing. An internal working sheet should not be forwarded as though every row and note were approved.

A practical filename is:

importer-wine-price-list-market-audience-effective-revision.pdf

Use an approved compact form for the effective context and revision. Avoid final, latest, new, or a filename that contains only a distributor nickname. Set the spreadsheet title, PDF title, footer, and filename to the same version identity.

Use an approval and change workflow

Keep item verification, commercial approval, and publication as distinct controls:

Pull current item identity from the approved item master.
Confirm market, audience, currency, price basis, and effective context.
Enter approved base prices and applicable adjustment records.
Calculate derived fields using documented formulas and rounding.
Validate codes, volume, format, pack, and identifiers against the exact item.
Have the commercial owner approve prices and terms.
Have operations approve item mapping, formulas, and version control.
Complete market or legal review where required.
Export the audience version and run spreadsheet and PDF QA.
Publish the approved file and mark its predecessor superseded.

For changes, record who requested them, the source, affected rows, old value, new value, reason, approver, and replacement version. A correction to pack may affect unit price even when case price does not change. A vintage change may affect item identity and supporting assets even when all prices remain the same.

Do not edit a published PDF directly. Update the controlled source, rerun calculations and approvals, then regenerate every affected export.

Keep regulatory examples limited and market-specific

Federal importer status does not settle every state or local requirement. TTB’s guidance on importing bottled alcohol beverages into the United States describes federal importer permit context and directs importers to consider additional state and local requirements.

A price list also does not replace required importer records. TTB’s importer compliance guidance addresses receipt and disposition records and advises checking requirements in each state where the business operates.

New York provides one specific example of a formal state process. The New York State Liquor Authority’s price-posting guidance describes wholesale and retail schedules and electronic filing. Use that source for New York work. Do not generalize its process to every state, and do not assume a federal permit or this operational template covers local review.

These are limited examples, not legal advice. Assign jurisdiction-specific questions to qualified counsel or the responsible compliance owner. The price list remains an internal commercial control document and does not replace applicable permit, filing, or recordkeeping obligations.

Run spreadsheet QA before making the PDF

Check the source workbook before formatting can hide problems:

Sort and filter by producer, item code, vintage, pack, and price to catch outliers and accidental duplicates. Compare row counts before and after export. Protect formulas only after review, so protection does not conceal a broken reference.

Review the PDF and retain superseded files

Open the rendered PDF outside the spreadsheet application. Check page width, repeated table headers, clipped columns, wrapped item names, decimal alignment, blank pages, footer identity, and searchability. Confirm that no hidden internal notes or formulas appear.

Use this final check:

Document-control header is visible and agrees with the filename.
Column headers repeat correctly on continuation pages.
Every amount has an unambiguous currency and basis.
Each item remains readable on one row.
Effective context, revision, owner, and contact are visible.
Links and contact details work.
The exported row count matches the approved source view.
The previous current file has been removed from normal distributor access.

Retain superseded price lists with their approvals and source snapshots according to the company’s record policy. Mark them superseded, restrict routine access, and link them to the replacement. Do not overwrite history or leave old and current versions together in an undifferentiated sales folder.

The guide to organizing distributor-facing wine assets provides a fuller current, superseded, and archived model. The pre-launch Depletement workspace for alcohol importer operations teams is intended to organize product details, sales assets, distributor asset access, sell sheets, tech sheets, and vintage updates. Whatever system holds the price-list workflow, keep commercial approval and jurisdiction-specific controls with the responsible team.