Spirits Distributor Product Setup Checklist for Importer Operations Teams

Build the product record before you open the distributor form

This guide is for alcohol importer operations teams preparing a distilled spirits product for distributor setup. It covers item identity, federal and state records, bottle and case data, pricing, logistics, sales assets, submission control, and updates after launch.

Start with one controlled record for the exact product the distributor will buy. A distributor spreadsheet, state portal, and emailed setup form should be outputs from that record. They should not become three competing sources of truth.

Keep three requirement layers separate:

• Federal compliance: Importer permit context, formula or laboratory review when required, Certificate of Label Approval, and federal label requirements.
• State and distributor requirements: Brand registration, appointments, listing review, price quotation, warehouse fields, codes, forms, and deadlines.
• Internal controls: Ownership, source evidence, revision status, approval, and the exact submission retained by the importer.

The distinction prevents a common error. A field requested by one control state is not automatically a federal requirement or a standard used by every distributor. Maine, for example, requires a proposed spirits item to be submitted through NABCA’s price quotation reporting system and asks for a listing fee, COLA copy, and electronic sell sheet. That is a Maine listing process, documented on the state’s Becoming a Spirits Supplier page. It is not a national item setup template.

This checklist organizes the handoff. It does not decide whether a permit, formula, registration, or label treatment applies. Give those decisions to the qualified compliance owner for the product and market.

Define the exact sellable spirits item

A brand name is not enough to identify an item. The distributor orders a specific liquid in a specific consumer package and case configuration.

Capture these fields before mapping a form:

Field group	Controlled fields	Primary source
Supplier identity	Importer legal name, trade name, supplier number, primary contact	Approved company and distributor records
Product identity	Brand, fanciful name, class or type, product description	Approved label and compliance record
Liquid	Alcohol by volume, proof, age statement when used, flavor or finish description	Approved label, formula record, producer specification
Origin	Country of origin, producer, bottler, distiller, and applicable place claims	Approved label and substantiation record
Consumer package	Net contents, container type, closure, gift package, units in a multipack	Final package specification
Shipping item	Units per case, case configuration, case code, dimensions, gross weight	Final case specification or measured production case
Commercial assignment	Importer SKU, target market, distributor, division, unit of sale	Approved internal and distributor records
Control	Owner, status, revision, evidence location, launch date	Item workflow

TTB explains that proof is twice the alcohol by volume, so a product labeled 40 percent alcohol by volume is 80 proof, in its Distilled Spirits FAQs. Store ABV and proof as separate approved fields. A formula in a spreadsheet can flag a mismatch, but it should not overwrite the values reviewed for the package.

Do not hide meaningful differences inside a long description. A 750 mL bottle and a 1 L bottle are different trade items. A single bottle and a gift box may require separate product and asset records. A six-bottle case and a twelve-bottle case need distinct shipping data even when the consumer bottle is unchanged.

Set the record grain in writing. A practical rule is:

One row = one liquid identity + one consumer package + one case configuration + one market + one distributor

If the team uses related tables rather than one spreadsheet, keep stable keys for the liquid, package, case, and market item. The relationship matters more than the software.

Clear formula, label, and import dependencies

Distributor setup should not be the first place the team notices that the federal evidence is incomplete. Review the compliance chain before presenting the item as launch-ready.

Confirm whether formula review applies

Not every distilled spirits product requires a formula. TTB says that certain alcohol beverages must have their ingredients and production process evaluated before they are made or imported and before a label application is submitted. Its formula approval guidance is the proper starting point for determining whether the product belongs in that group.

For products that require formula approval, retain:

• formula number and status
• applicant and responsible company
• product name used in the formula record
• approved ingredients and production description reference
• required supporting documents
• laboratory sample or analysis reference when applicable
• qualifications or limitations
• compliance reviewer and review date

Do not send confidential recipe documents to a distributor merely because the setup form asks whether a formula exists. Provide the approved reference or evidence appropriate for the recipient, and keep restricted details in the compliance packet.

Match the COLA to the marketed package

TTB’s distilled spirits labeling guidance states that distilled spirits must be properly labeled before sale in the United States and directs industry members to mandatory label information and COLA resources. For imported bottled alcohol, TTB says an importer must obtain a COLA for each unique product or label after receiving its importer’s permit on the agency’s importing bottled alcohol beverages page.

Build a label packet for the exact item. Record:

• TTB ID or COLA number
• certificate holder
• status
• brand and fanciful name
• class or type
• alcohol by volume and proof
• net contents
• age statement when applicable
• country of origin and importer statement
• label images covered by the approval
• qualifications and allowable-change decision
• formula or pre-COLA reference when applicable
• responsible compliance approver

The TTB Public COLA Registry provides public access to COLA information. Use it to verify a certificate, but keep the controlled approval and internal decision connected to the item. A registry result does not prove that the bottle photograph, case configuration, importer statement, and sales sheet all describe the same current product.

Imported spirits can also carry age or origin claims that need supporting records. TTB advises that the COLA holder is responsible for substantiating those claims in its country of origin certification guidance. Link the substantiation packet to the item without exposing restricted supplier records in routine distributor access.

Verify the container size

Net contents should come from the final approved package, not a sales presentation. TTB explains that net contents for distilled spirits covered by a prescribed standard of fill must follow 27 CFR 5.203 on its distilled spirits net contents page.

Record the numeric volume and unit in separate fields. Then make sure the label, SKU description, consumer GTIN assignment, bottle image, case pack, price record, and distributor submission all use that same package.

Complete state registration and market prerequisites

Federal approval does not complete a state launch. Open a market readiness record for every state and assign the owner who knows the current state process.

Track:

• state regulator and official instruction source
• applicant or brand holder
• license or shipping authority relevant to the submission
• wholesaler appointment or source-of-supply evidence
• brand or label registration number
• filing date, fee, status, and renewal context
• state product classification
• price filing or quotation requirement
• distributor and territory
• effective or approval date
• unresolved condition and next action

Nebraska shows why a market-specific record matters. The Nebraska Liquor Control Commission says brands must be approved before shipment into the state, a wholesaler must be selected during registration when applicable, and separate bottle sizes are not currently registered in its brand registration FAQs. The Commission’s brand label registration page lists an initial fee of $20 per brand and an annual renewal period from April 1 through June 30 with a $10 renewal fee. Those details belong in a Nebraska workflow with a source date. Do not turn them into defaults for another state.

Maine uses a different process. Its official supplier page says new spirits products go to the Bureau of Alcoholic Beverages and Lottery Operations for listing consideration, require a Maine broker or licensed representative, and must be listed with NABCA. Each proposed item needs a PQRS quote with its TTB ID, plus the state’s specified submission materials. Read the current Maine spirits supplier requirements before setting a launch date.

Use states as evidence that requirements vary, not as templates for one another. Confirm the current process with the regulator and distributor contact for every intended market.

Assign GTINs to the correct packaging level

Keep the product identifier, barcode, importer SKU, state code, and distributor item number in separate fields. They have different owners and purposes.

GS1 US explains that a GTIN identifies the product, while a UPC is the barcode that carries a GTIN for scanning. It also says each product variation, including size or package count, needs its own GTIN and that higher packaging levels such as cases and inner packs require identification. See the GS1 US GTIN guidance for the source definitions.

For each code, record:

Field	What to capture
Identifier	Full digits stored as text
Identifier type	Consumer GTIN, case GTIN, distributor code, state code, or internal SKU
Packaging level	Bottle, multipack, case, or other defined level
Assigning party	Brand owner, GS1 licensee, distributor, state, or importer
Product relationship	Exact liquid, volume, package, and count represented
Barcode symbology	Symbology printed for the recipient’s use
Evidence	Assignment record or approved package
Verification	Scan result and reviewer
Status	Planned, assigned, in use, replaced, or retired

Never create a case code by adding digits to a bottle code unless the authorized numbering method and packaging relationship support that assignment. Do not copy a consumer GTIN into a case field just to satisfy a required cell.

Scan the actual production bottle and final case label when possible. Compare the encoded value with the human-readable digits and the controlled record. A valid scan of the wrong product is still a setup failure.

Measure the bottle, case, and pallet that will ship

Logistics values should come from a production unit, final supplier specification, warehouse measurement, or approved packaging drawing. Nominal liquid volume does not determine gross bottle or case weight.

Capture:

Consumer package

• bottle height, width or diameter, and depth where relevant
• bottle gross weight
• net contents and unit
• closure and special package details
• consumer GTIN and barcode location
• units in a consumer multipack

Shipping case

• units per case
• unit of sale
• case length, width, and height
• dimension axis order and unit
• case gross weight and weight unit
• case GTIN
• barcode and label placement
• lot or production code format
• dividers, inserts, or special handling

Pallet and fulfillment

• cases per layer
• layers per pallet
• cases per pallet
• pallet dimensions and type
• pallet gross weight when requested
• warehouse or ship point
• freight basis
• lead time and order minimum
• pickup or delivery constraints
• storage and handling instructions supplied by the producer

The recipient’s form determines which values it needs. Montgomery County Alcohol Beverage Services publishes a new item setup form for suppliers. Treat that form as an instruction for that recipient, then map its fields to the controlled product record. Do not broaden one county system’s terminology into an industry-wide requirement.

Retain measurement evidence when a later operator may need to reproduce the result. A dated photograph of the case on a scale or beside a measuring reference can be useful, provided the image clearly identifies the case and does not expose unrelated warehouse information.

Prepare market-specific pricing and availability

A distributor cannot activate an item from an unlabeled cost figure. Every submitted price needs a basis, currency, market, unit, and effective context.

Prepare these fields as applicable:

• quoted case price
• units per case
• derived unit price
• currency
• freight included or excluded
• ship point or delivery basis
• effective date or pricing period
• suggested retail price when requested and permitted
• allowances, bill-backs, or approved launch programs
• tax and deposit treatment confirmed by finance
• payment terms
• initial available quantity
• first available date
• ongoing, seasonal, limited, or allocated status
• commercial approver and approval record

Keep calculations visible. If unit price is calculated from case price, mark it as calculated and define the rounding rule. Do not type over it after a distributor asks for a different display precision.

Control-state quotation systems can incorporate additional listing and price fields. Maine, for example, requires a quote sheet in NABCA PQRS for each proposed item according to its spirits listing instructions. Save the exact quote submitted and the state’s response. A row in the internal price master is not evidence that the recipient received or accepted it.

Never reuse another state’s price row without review. The bottle may be identical while freight, tax treatment, listing method, distributor assignment, allowances, and effective timing differ.

Attach current sales and product assets

Item setup is operational, but many recipients need enough product material to review, list, and sell the item. Build one narrow package for the named recipient.

Include only requested and approved files:

• front and back bottle images
• front and back label images
• case image when required
• sell sheet
• technical or product sheet
• short and long product descriptions
• brand and producer overview
• production method approved for external use
• tasting note and service guidance
• awards or reviews with source evidence
• logo files and approved brand guidance
• sales contact and asset contact

Every asset should match the item’s brand, expression, proof, ABV, volume, package, market label, and revision. Check visible label details rather than trusting the filename.

Keep source masters separate from recipient derivatives. If a distributor asks for a specific filename, image size, background, or file type, create a derivative tied to the approved master. Do not overwrite the master with the first portal-ready export.

A sell sheet can be required as part of the listing package. Maine explicitly requests an electronic sell sheet for each SKU in its supplier submission requirements. That does not mean every distributor wants the same layout or content. Record the recipient’s current specification.

Map and submit the product through one controlled workflow

Use the same sequence whether the recipient accepts a spreadsheet, PDF, portal entry, or email package.

1. Request the current instructions. Obtain the form, portal fields, asset specification, state prerequisites, contact, and due date.
2. Open the exact market item. Confirm liquid, package, case, state, distributor, owner, and revision.
3. Collect source evidence. Link formula and COLA records, state approval, identifiers, measurements, price approval, and assets.
4. Map recipient fields. Define what every requested field means and map it to a controlled source. Mark unclear fields for confirmation.
5. Review by responsibility. Compliance reviews regulated identity. Logistics reviews the physical configuration. Finance reviews pricing. Sales or portfolio reviews external copy and launch assets.
6. Freeze the submission revision. Save the completed form, export, asset package, and portal values that will leave the company.
7. Submit through the approved route. Record the sender, recipient, date, and confirmation.
8. Log questions and rejections. Correct the controlled source first, regenerate affected outputs, and preserve the replacement relationship.
9. Capture acceptance. Store the distributor item number, accepted date, conditions, and any remaining tasks.
10. Test the live item. Compare the distributor’s item description, pack, codes, price, and assets with the approved submission.

Assign one accountable operations owner. Several functions may approve fields, but one person should reconcile readiness, exceptions, submission, and acceptance.

Keep a field map

Distributor language is not consistent. One form may use supplier item number, another vendor SKU, and another product code. Do not decide those fields are equivalent from the labels alone.

Use a small mapping table:

Recipient field	Recipient definition	Controlled source	Owner	Submitted value	Status
Field label from form	Instruction or confirmed meaning	Record and field name	Responsible function	Exact exported value	Ready, question, blocked, accepted

This record prevents a correction from being trapped inside one emailed spreadsheet. When the source changes, the team can identify every affected submission.

Handle product changes as controlled replacements

Do not edit a live item in place when the change creates a different trade item or requires new approval. Create a change set and let compliance, operations, and the recipient decide whether the existing listing can continue.

Reopen the affected fields when any of these change:

• formula, ingredients, flavor, coloring, or production method
• class or type
• proof or alcohol by volume
• age statement, origin claim, or other label claim
• brand, fanciful name, or label design
• net contents or container format
• closure, gift box, or consumer multipack
• consumer or case GTIN
• case pack, dimensions, weight, or pallet pattern
• importer, source of supply, or wholesaler appointment
• state registration or listing status
• price, freight basis, or availability
• bottle image, sell sheet, technical sheet, or description

The qualified owner should determine whether a revised formula, COLA, or state filing is required. TTB notes that proof variations permitted by TTB do not require a new Nebraska brand registration unless a new COLA is issued in the Nebraska spirit registration FAQ. That is a useful Nebraska example, not a blanket rule for every state or every product change.

Keep the former record available while inventory, orders, returns, and distributor history still refer to it. Link the successor. Do not rename the prior record to old and overwrite its evidence.

Complete final spirits item setup QA

Run this checklist against the controlled item record, source evidence, exact submission package, and distributor response.

Product and compliance

• Importer, supplier, brand, fanciful name, and product description identify the same item.
• Class or type, ABV, proof, age statement, origin, and net contents match approved evidence.
• Formula requirement was assessed, and the approved reference is linked when applicable.
• COLA number, holder, status, qualifications, and label images match the marketed package.
• Age, origin, and other label claims point to the substantiation retained by the responsible owner.
• State registration, appointment, listing, and price prerequisites are complete for the target market.
• No restricted compliance record is exposed in the distributor package without an approved reason.

Codes and package

• Importer SKU, producer code, consumer GTIN, case GTIN, state code, and distributor item number remain separate.
• Identifier fields are stored as text and preserve leading zeroes.
• Every GTIN identifies the intended packaging level and exact variation.
• Production bottle and case barcodes scan to the recorded digits.
• Bottle volume, package format, closure, and gift presentation match the item.
• Units per case and unit of sale match the physical shipping configuration.
• Bottle and case dimensions use the recipient’s axis order and unit.
• Gross and net weights are labeled clearly.
• Pallet pattern, warehouse, lead time, freight basis, and minimum order are current when requested.

Commercial and assets

• Price has a market, currency, unit, freight basis, effective context, and finance approval.
• Calculated unit and case values follow the documented rounding rule.
• Availability, initial quantity, and first available date are current.
• Bottle images show the correct label, proof, volume, closure, and market package.
• Sell sheet, technical sheet, descriptions, claims, and awards match the exact item.
• Recipient derivatives point to approved source assets.
• No draft, prior package, obsolete price, placeholder, internal note, or tracked change remains.

Submission and acceptance

• Every recipient field has a definition or confirmed interpretation.
• Unknown values are marked and resolved rather than guessed.
• The saved submission revision matches the files and values actually sent.
• Portal confirmation or email delivery evidence is retained.
• Rejections and questions have an owner, reason, next action, and replacement record.
• Distributor acceptance and assigned item number are recorded.
• The live distributor item was checked against the approved source.
• A second reviewer can trace each critical submitted value to its evidence.

A reliable setup packet is not the form with the most populated cells. It is the package that lets a distributor identify, receive, price, and sell the intended item while the importer can explain where every critical value came from.

Depletement’s pre-launch workspace for alcohol importer operations teams is being designed to organize product and catalog information, bottle and brand assets, technical sheets, sell sheets, distributor asset access, and vintage updates. That product connection is practical here: item setup depends on keeping the current product record and its approved files together before the handoff. Whether the team uses Depletement, an ERP, or a controlled spreadsheet, preserve the same standard: one exact item, named owners, traceable evidence, and a verified recipient submission.