Wine Distributor Item Setup Checklist for Importer Operations Teams

Build one item record before filling out distributor forms

Distributor item setup turns a wine into a specific product that can be ordered, received, stored, priced, and sold. This checklist is for importer operations teams coordinating that handoff across compliance, finance, logistics, sales, and a distributor contact.

Start with one controlled item record. Distributor spreadsheets and portals should be outputs from that record, not separate sources of truth. When a distributor asks for a field under an unfamiliar name, map it to your record, confirm the meaning, and record what was submitted.

Three types of requirements belong in different lanes:

• Federal requirements: TTB label approval and mandatory wine label information, plus other federal import records where applicable.
• State and distributor requirements: Brand registration, price posting, item forms, case labels, portal fields, deadlines, and warehouse rules for the destination.
• Operational recommendations: Internal ownership, evidence, naming, revision control, and QA practices that make submissions repeatable.

The boundaries matter. TTB lists brand name, class or type, name and address, net contents, and alcohol content among the information required on wine labels in 27 CFR 4.32. A distributor can request many additional commercial and warehouse fields that are not federal label requirements. A state can add its own registration process. This guide helps organize the work, but it is not legal advice. Have the qualified compliance owner determine what applies to each wine and market.

Confirm the exact commercial item identity

Give every sellable configuration its own record. Do not start from a brand-level row when the distributor will buy a particular vintage, bottle volume, and case pack.

Capture:

• legal supplier or importer name
• producer and market-facing brand
• cuvée or product name
• vintage or controlled non-vintage status
• wine class or type
• country, region, and appellation
• grape variety or blend when the distributor requests it
• alcohol by volume
• bottle volume and package format
• importer SKU and producer code
• target state and distributor
• item owner, revision status, and intended launch date

Use label and compliance records for regulated identity statements. Use the current commercial record for the importer SKU, pack, and market assignment. If those sources disagree, stop the row rather than choosing the more familiar value.

Keep a visible distinction between the brand, the base bottle, and the shipping case. A distributor item number assigned after setup is another identifier, not a replacement for the importer SKU or GTIN. Record all of them with labels that explain their owner.

Assign and verify GTINs at the correct packaging level

A GTIN identifies a trade item. GS1 US explains that a GTIN-12 is commonly encoded in a UPC-A barcode for North American retail point of sale, while a GTIN-14 identifies trade item groupings such as a case and is not intended for point of sale in its GTIN overview. Do not describe the printed barcode, the encoded number, the importer SKU, and the distributor item number as if they were the same field.

For each item, record:

• consumer-unit GTIN or UPC
• case GTIN or shipping container code when required
• barcode symbology expected by the recipient
• company that assigned the number
• packaging level represented by each code
• human-readable digits copied from the package
• scan-test result from an actual production unit or approved final package

The brand owner should apply its GTIN assignment policy consistently. The GS1 GTIN Management Standard says a new product receives a new GTIN at the base unit and each higher packaging level. It also says a change in declared net content requires a new GTIN at the base and higher levels, while a change in case quantity requires a new GTIN for the higher packaging level. The same standard treats a wine vintage as a new product when the year is recognized as a different-quality product and is not handled as a flow-through commodity. This means a vintage change does not have one universal barcode answer. Confirm the brand owner’s policy and the distributor’s handling before reusing or replacing a code.

Do not generate a case code by intuition. In Pennsylvania, for example, the PLCB’s current case labeling requirements call for a vendor-assigned UPC on the retail unit, a 14-digit shipping container GTIN, and a PLCB item code on received cases. Treat that as a Pennsylvania-specific warehouse requirement, not a national template.

Assemble the COLA and label evidence

Open a compliance packet for the exact label configuration being submitted. Include the signed or electronic Certificate of Label Approval when required, the application record, label images, qualifications shown on the approval, and internal confirmation that the marketed package fits the approval and any allowable changes.

Federal wine rules generally require an approved TTB Form 5100.31 before wine is bottled or packed, or removed from the bottling or packing plant, subject to the exemption described in 27 CFR 4.50. The TTB wine labeling hub provides the agency’s mandatory-information checklist, application guidance, and allowable-changes resources. Compliance should review those sources rather than assuming an old approval covers a revised package.

The TTB Public COLA Registry provides approved, expired, surrendered, and revoked COLA information. Use the registry as a verification source, then retain the approval supplied by the responsible certificate holder in the controlled item packet. A registry result alone does not establish that the physical bottle, vintage presentation, importer statement, and distributor submission all match.

Record:

• TTB ID or COLA number
• approval status and certificate holder
• approved brand and fanciful name where applicable
• class or type and appellation presentation
• bottle volume and alcohol statement
• front, back, strip, and neck label files included in the approval
• approval qualifications or notes
• formula or pre-COLA evaluation reference when applicable
• state registration or approval reference
• compliance approver and approval date

For imported product, keep customs and FDA work connected but separate from distributor setup. FDA’s food-facility rules apply to facilities that manufacture, process, pack, or hold food for US consumption unless an exemption applies under 21 CFR 1.225 and 21 CFR 1.226. Prior notice for imported food requests product, manufacturer, shipper, importer, arrival, quantity, and packaging information under 21 CFR 1.281. Let the import and compliance owners decide how those rules apply. Do not paste confidential registration data into a distributor form unless the recipient and purpose are approved.

Measure the bottle, case, and pallet as shipped

Logistics data should come from a production sample, packing specification, warehouse measurement, or confirmed supplier document. Do not estimate case weight by multiplying a nominal bottle volume. Glass, closures, dividers, cartons, and case materials affect the shipped result.

Capture both bottle and case data:

• bottle height, width or diameter, depth where relevant, and gross weight
• units per case and unit of sale
• case length, width, height, and gross weight
• case GTIN and case-label position
• cases per layer, layers per pallet, and cases per pallet
• pallet dimensions, gross weight, and pallet type when requested
• lot or production-code format
• storage orientation and temperature instructions supplied by the producer
• warehouse, pickup point, freight terms, lead time, and minimum order rules

Write down the measurement convention and units. Identify which side is length, width, and height in the distributor’s template. Retain a photo of the measured case and its label when a future reviewer may need to reproduce the result.

Recipient specifications vary. The PLCB defines a quoted case pack as one physical shipping case and publishes separate packaging requirements for wine and spirits suppliers. Its case-label page adds placement and barcode rules. By comparison, the Oregon control system’s distilled spirits supplier manual asks for case pack quantity, case dimensions, case weight, UPC, and shipping container code on its quotation and specification form. The Oregon manual is for distilled spirits, so it is evidence of recipient-specific data design, not a wine rule to copy into another market.

Prepare pricing and commercial data by market

Build the commercial row from an approved market price record. Keep assumptions and calculated outputs separate from prices submitted to the distributor.

Prepare:

• distributor acquisition price or quoted case price
• price basis, currency, and effective period
• unit cost and case cost
• freight inclusion or exclusion
• allowances, bill-backs, depletion terms, or introductory programs approved for that market
• suggested retail price if requested and permitted
• on-premise and off-premise targets when the sales plan uses them
• tax treatment and deposit treatment as confirmed by finance
• payment terms and credit owner
• first available date, initial quantity, and ongoing availability

Never copy another state’s row without review. State systems can impose additional processes. New York requires brand-label handling for alcoholic beverages and explains that wine above 7 percent alcohol requires an appointment letter and federal label approvals rather than the same registration route used for lower-alcohol wine on the New York State Liquor Authority brand-label page. Pennsylvania requires a vendor to accept its contract terms before accessing the quotation form used for listing consideration on the PLCB supplier forms page. Ask the state and distributor contacts for their current instructions before setting the deadline.

For a fuller pricing workflow, use the wine distributor price list guide alongside this item checklist.

Attach sales and product assets to the same item

Operational setup and sales readiness should point to the same product identity. Assemble a clean recipient package rather than sending the distributor a folder of possible files.

Include what the recipient requests:

• current front bottle shot and back bottle shot
• front and back label images
• tech sheet
• sell sheet
• short and long product descriptions
• producer biography and brand overview
• tasting note, service guidance, and food pairing
• current vintage accolades with source evidence
• logo files and approved brand guidance
• sales contact and asset contact

Match the vintage, volume, label, and code across every file. The wine bottle shots workflow covers product-image control, while the wine tech sheet template provides an intake and rollover process. If the distributor has a portal specification for pixel dimensions, background, filename, or file type, export a recipient derivative from the approved master. Do not replace the master with that derivative.

Run a controlled submission workflow

Use one workflow for spreadsheets, emailed forms, and distributor portals:

1. Request the current specification. Obtain the distributor form, portal instructions, asset rules, state prerequisites, contact, and due date.
2. Create the market item record. Assign the owner, wine, vintage status, pack, state, distributor, and submission revision.
3. Collect evidence. Attach label approvals, state records, GTIN ownership, measurements, pricing approval, bottle images, and sales files.
4. Map recipient fields. Define each requested field and map it to the controlled source. Mark unknown rather than guessing.
5. Review by function. Compliance checks regulated identity, finance checks commercial data, logistics checks physical data, and sales checks market copy and launch details.
6. Submit one approved package. Save the exact spreadsheet, form, files, or portal export that left the company.
7. Resolve exceptions in the source record. Correct the controlled field first, regenerate affected outputs, and document what replaced the earlier submission.
8. Capture acceptance. Record the distributor item number, setup status, effective date, approver, and open conditions.
9. Test the live item. Confirm the distributor listing, pack, code, price, description, and assets against the approved submission.

Assign one accountable item owner. Contributors can own fields, but one person should manage readiness, submission, exceptions, and closure. A simple responsibility split is compliance for label and state evidence, finance for prices and terms, logistics for case and warehouse data, sales or portfolio for copy and launch assets, and operations for the complete record.

Treat vintage rollover as change control

Duplicate the prior item only as a starting point. Reopen every field that can change and classify it as confirmed unchanged, changed, awaiting evidence, or not applicable.

Review the new vintage, COLA coverage, state treatment, GTIN decision, importer SKU, distributor item treatment, bottle and case codes, pack, dimensions, weights, pricing, availability, bottle shot, labels, tech sheet, tasting note, and accolades. The GS1 standard’s conditional wine-vintage example means the GTIN decision should be documented, not assumed.

Keep the prior item active while saleable inventory and orders still require it. Link the successor record without overwriting the evidence for the older vintage. Search every outgoing filename and document for the prior vintage before approving the rollover.

When a change affects the sellable unit, ask what else follows. A new bottle volume can affect label approval, GTIN, case configuration, dimensions, weight, price, image, tech sheet, warehouse record, and distributor listing. Open one change set and close each affected output.

Complete final item setup QA

Run this task list against the approved source record and the exact submission package:

• Producer, brand, wine, vintage status, class or type, origin, ABV, and bottle volume match approved evidence.
• Importer legal name, address, license context, and market assignment have been reviewed by the responsible owner.
• COLA number, holder, status, qualifications, and label images describe the submitted package.
• State registration, appointment, price posting, or listing prerequisite is complete where applicable.
• Consumer GTIN or UPC scans and matches the human-readable digits.
• Case GTIN, case pack, and barcode treatment match the distributor’s current specification.
• Importer SKU, producer code, distributor item number, and state item number are stored as separate identifiers.
• Bottle and case dimensions use the requested axis order and unit.
• Bottle, case, and pallet weights identify gross or net basis clearly.
• Freight terms, warehouse, lead time, order minimum, and first available date are current.
• Price, currency, effective period, allowances, and payment terms have finance approval.
• Bottle shots, label files, tech sheet, sell sheet, descriptions, and accolades match the exact item.
• No prior vintage, old price, superseded code, placeholder, tracked change, or internal note remains.
• The saved submission package matches what was uploaded or emailed.
• Distributor acceptance, assigned item number, open exceptions, and live-item test are recorded.
• A second reviewer can trace each critical field to its source without asking the submitter.

For the broader document packet that often surrounds setup, see documents to have ready for your distributor.

Depletement is a pre-launch workspace being designed for alcohol importer operations teams to organize current product details, sales assets, distributor asset access, tech sheets, sell sheets, and vintage updates. Whether the team uses a workspace, ERP, or controlled spreadsheet, the operating standard stays the same: one current item record, named owners, preserved evidence, and a verified handoff.