Wine Distributor Onboarding Checklist for Suppliers and Importer Teams

Prepare one controlled onboarding package

This guide is for winery suppliers, brand owners, US wine importers, and importer operations teams preparing to onboard with a distributor. It covers company and contact setup, agreements, item data, federal and market evidence, pricing, logistics, sales materials, access, submission, acceptance, and launch checks.

The accountable party depends on the task. An overseas winery can supply product facts, appointments, production records, labels, packaging specifications, and assets. The US importer normally controls its own permits, federal import work, importer records, market registrations, distributor agreement, commercial approvals, and submission. A distributor can add vendor, item, warehouse, portal, and sales requirements. Do not tell a winery to certify completion of an importer obligation it does not control.

Build one controlled onboarding record for the legal supplier, distributor, market, and intended portfolio. Link each answer to its source, name the owner, and save the exact package submitted. This checklist supports project control. It does not determine whether a legal requirement applies or replace advice from the responsible compliance professional.

Separate four kinds of requirements

A distributor checklist can mix laws, recipient requests, and internal process choices on one page. Classify every line before assigning it.

Requirement class	Who defines it	Examples	How to handle it
Federal rule	Federal statute, regulation, or agency	Importer permit, label approval, importer records, FDA import process	Assign to the US importer or other legally responsible party and retain primary evidence
Jurisdiction-specific rule	State or local authority	Brand registration, appointment, price posting, state item or listing process	Confirm for the exact product, market, route to market, and license structure
Distributor requirement	Named distributor	Vendor application, insurance evidence, item template, warehouse specification, portal profile, training format	Request the current instructions and record who approved the response
Internal recommendation	Importer or supplier operating policy	Ownership, source links, version status, review gates, access controls, archive process	Document the rule and apply it consistently

A federal approval does not complete every state or distributor step, and a distributor request is not automatically a federal requirement. Track requirement class, authority or requester, responsible party, and evidence for every line.

Define the onboarding record before collecting files

Create one record for each distributor relationship and market scope. If one distributor has separate divisions, warehouses, states, or vendor entities, confirm whether they require separate records.

Start with this control block:

Field	Required entry
Onboarding ID	Stable internal reference
Legal supplier	Entity contracting with and invoicing the distributor
Brand owner or winery	Entity supplying the portfolio and source materials
US importer	Responsible importing entity when applicable
Distributor	Exact legal or approved operating name
Division or market	State, territory, channel, branch, or other defined scope
Agreement owner	Person responsible for commercial and legal coordination
Operations owner	Person responsible for tracker, files, submission, and closure
Distributor contact	Maintained contact for vendor and item setup
Target launch context	Approved planning date or release window
Status	Draft, collecting, in review, submitted, accepted, blocked, or closed
Revision	Controlled package identifier
Source location	Internal location for evidence and submitted copies
Open exceptions	Count or link to unresolved items

Keep the legal entity, brand owner, and importer as separate fields even when one company fills all three roles. The distributor needs to know which entity signs, invoices, ships, owns the product data, and answers compliance questions.

Complete company and vendor setup

Ask the distributor for its current vendor application, required tax documentation, insurance requirements, payment method, remittance instructions, credit process, contacts, and secure transfer route. Do not build the package from a form used for a different division or prior onboarding.

Company identity and contacts

Prepare controlled values for:

• legal name and approved trade name
• business and remittance addresses
• federal and state permit or license references requested for the relationship
• tax classification and taxpayer form handled by the authorized owner
• accounts receivable and payment contacts
• purchase-order and customer-service contacts
• compliance, logistics, sales, marketing, and executive contacts
• escalation route for shortages, damages, deductions, and item errors
• certificate of insurance when the agreement or distributor requires it
• banking or electronic payment record transmitted through the approved restricted channel

For a US entity asked for Form W-9, use the current form and instructions linked from the IRS Form W-9 page. Keep tax and bank files outside the normal product-asset collection. Record that the authorized person sent them through the approved route without copying sensitive values into a broadly shared tracker.

Agreement and appointment controls

Summarize the executed agreement in operational fields for entities, territory, channels, brands, effective context, ordering, payment, freight, reporting, support, contacts, amendments, and approved-copy location. Keep the contract authoritative.

Have qualified owners review the agreement and any producer appointment. Operations should record the decision as tasks, access, and market-item scope. Do not interpret ambiguous language inside a spreadsheet note.

Confirm importer responsibilities before assigning supplier tasks

TTB states that a person engaging in the business of importing wine into the United States must apply for a Federal Basic Importer’s Permit, and that the importer must obtain a TTB-issued COLA for each unique product or label covered by the federal requirement on its bottled alcohol import guidance. Assign those actions to the US importer or its authorized compliance owner, not automatically to the foreign winery.

The supplier can support the importer with:

• producer and bottler identity
• authorization or appointment documents
• final labels and product information
• country and origin evidence
• bottle, closure, carton, case, and lot-code specifications
• certifications and their scope
• product and brand assets
• a contact who can resolve factual conflicts

The importer should decide what evidence is sufficient, what must be submitted, and which version may be used. If a consultant or customs broker performs a task, keep the importer owner visible. CBP advises that even when a customs broker is used, the importer of record remains responsible for entry-document correctness and applicable duties, taxes, and fees in its tips for new importers.

Do not send import credentials, customs data, or private regulatory account details to a distributor unless the request, purpose, authorization, and transfer method have been confirmed. Distributor onboarding should reference importer readiness without duplicating every restricted import record.

Build one exact item record for every sellable configuration

Distributor onboarding usually moves from vendor approval to item setup. Prepare structured item data before filling a portal. Use one row for each combination that the distributor must order or receive separately.

Use separate rows when vintage status, volume, format, pack, identifier, market assignment, or approved commercial treatment differs.

The item record should include:

Field group	Recommended fields	Deciding source
Product identity	Producer, brand, wine or cuvée, vintage status, class or type	Approved product and label records
Origin and composition	Country, region, appellation, variety or blend when used	Approved label and verified producer evidence
Package	ABV, net contents, bottle format, closure, units per case	Approved label and final package specification
Identifiers	Importer SKU, producer code, consumer GTIN or UPC, case GTIN	Identifier assignment and verified package
Logistics	Case dimensions, case weight, pallet pattern, warehouse, lead time	Measured shipment or approved logistics specification
Market	State, distributor, division, registration or listing reference, status	Market compliance and distributor records
Commercial	Price-record reference, currency, price basis, freight and allowance references	Approved commercial record
Control	Owner, evidence status, revision, exception, successor item	Internal onboarding record

Do not extract operational values from a sell sheet when a controlled item source exists. A sales document may omit pack, shorten a name, or remain in circulation after a vintage change.

Keep GTINs and recipient identifiers separate

GS1 US explains that a GTIN identifies a trade item and that a GTIN-14 can identify a grouping such as a case, while the consumer item may use a different GTIN structure in its GTIN overview. Record the packaging level, assignment source, and verification state for every identifier.

Use distinct columns for:

• producer code
• importer SKU
• consumer GTIN or UPC
• case GTIN or shipping container code
• distributor item code
• state item or listing code
• warehouse code when it differs

Do not fill a case field with the consumer code to remove a blank. Do not invent a distributor code before the distributor assigns it. Store codes as text, preserve their displayed digits, and confirm them against the final package or controlled assignment record.

Recipient requirements can be more specific than the general item master. The Pennsylvania Liquor Control Board distinguishes a PLCB item code, the UPC on the retail selling unit, and a vendor-assigned 14-digit shipping container code or GTIN in its supplier case-labeling requirements. Treat that as a Pennsylvania process, not a rule for every distributor.

Assemble federal evidence without turning it into a distributor rule

The compliance owner should maintain the complete federal packet. Share the part requested for onboarding and retain the internal review that connects it to the exact item.

Label identity and COLA evidence

TTB’s wine labeling guidance identifies federal wine-label topics including brand name, class or type, alcohol content, name and address, net contents, and country of origin for imports. Use the approved label and compliance decision for the applicable fields rather than copying wording from an old deck.

Record the TTB ID or COLA reference, certificate holder, status, product identity, class or type, origin presentation, alcohol and net-content statements, represented label files, qualifications, owner, and evidence location.

The TTB Public COLA Registry provides information on approved, expired, surrendered, and revoked COLAs. Use it as a verification source, then preserve the exact certificate and package review used by the importer. A registry search does not prove that a bottle image, distributor description, or current physical package matches the approved record.

Import and FDA references

Keep import execution separate from distributor vendor setup. TTB’s bottled-alcohol guidance says alcohol importers must comply with applicable FDA registration and prior-notice requirements and links to FDA resources on the same federal import guidance. The compliance owner should determine which facility, shipment, and party details apply.

FDA states that imported food must meet US food requirements and that importers must follow import procedures including food-facility registration and prior notice on its food import overview. FDA’s Prior Notice of Imported Foods page is the direct agency source for that process. These are import controls, not default distributor-upload fields.

Importer records

TTB says federal importers must keep daily records of physical receipt and disposition of wine and identifies the governing record fields in its importer compliance guidance. The onboarding tracker can link the responsible record system and owner, but it should not replace that required record or expose it to normal distributor users.

Verify state and local steps for the exact market

Do not copy a state task from another market. Ask the responsible compliance owner to confirm brand registration, appointment, price posting, label filing, tax, franchise, local, and product-listing steps for the actual license structure and route to market.

New York illustrates why alcohol level matters. The New York State Liquor Authority says wine containing 7 percent alcohol or less requires brand-label registration. For wine over 7 percent alcohol, the Authority says brand-label registration is not required and instead calls for submission of an appointment letter and federal label approvals on its brand-label registration page. Its separate price-posting guidance describes New York wholesale and retail schedules. Record each as a distinct New York task only after the market owner confirms it applies to the item and parties.

For each jurisdictional task, capture:

Control	Entry
Jurisdiction	Exact state or locality
Requirement	Plain-language task name
Authority	Official agency and source link
Responsible party	Importer, wholesaler, supplier, or other confirmed party
Product scope	Brand, wine, vintage, package, or market item covered
Submission evidence	Filing, approval, appointment, posting, or confirmation record
Status	Not started, in review, submitted, approved, exception, or not applicable
Owner	Qualified person responsible for the decision
Distributor dependency	Item or launch step blocked by the result

Do not mark a state task complete because a distributor accepted a spreadsheet. Keep regulatory evidence and recipient acceptance as separate decisions.

Prepare pricing and commercial terms for the named audience

Create a controlled price record for the distributor, market, currency, and applicable period or context. Keep pricing approval separate from item identity approval.

Prepare the approved distributor price, case or unit basis, currency, case pack, freight, payment terms, order minimum, adjustments, approved positioning, effective context, superseded reference, and commercial approver.

Label every amount and basis. Do not put several commercial adjustments in one notes cell. Do not present a planning estimate as an approved distributor price. If the distributor provides its own template, map each field back to the controlled price record and preserve the submitted version.

State pricing procedures may require a separate workstream. Keep the distributor price list, state filing, internal margin model, and sales positioning connected but distinct.

Confirm warehouse and order readiness

Obtain warehouse instructions directly from the distributor or appointed logistics contact. Confirm whether the setup covers pickup, delivered freight, a third-party warehouse, a consolidator, or another approved arrangement.

Prepare the ship-from entity, purchase-order route, item identity, bottle volume, pack, case measurements, case-label treatment, pallet pattern, lot-code format, lead-time source, order minimum, appointment process, claims contacts, and availability source.

Measure the production case or use a current approved specification. Do not estimate gross case weight from nominal liquid volume. Keep stable package facts separate from changing inventory and lead-time reports.

Run a receiving simulation before the first purchase order. Compare the order unit, case pack, distributor item code, case label, ship point, and approved price basis. Record unresolved differences instead of relying on the warehouse to correct them at receipt.

Deliver a distributor-ready sales and asset set

Onboarding is incomplete when the item can be ordered but the sales team cannot identify or present it. Prepare one approved collection for the exact market items.

A practical set includes bottle images, a current tech sheet and sell sheet, producer and wine descriptions, a portfolio overview, approved tasting guidance, verified accolades, logos and usage guidance, rights-cleared brand imagery, training material, and current contacts.

Match producer, wine, vintage, volume, package, and codes across every file. Keep drafts, source evidence, expired rights, internal pricing models, and superseded assets outside the distributor’s default collection.

Use a short launch brief to state audience, account priorities, sample route, training plan, approved support, launch context, and contacts. Label targets and projections as plans. Do not place them in product-fact fields.

Control access and the submitted record

Separate access by sensitivity and task:

Collection	Intended access
Company onboarding	Restricted vendor, tax, insurance, and payment participants
Item setup	Operations, compliance, logistics, and distributor setup contacts
Commercial	Authorized commercial and finance participants
Sales and brand assets	Approved distributor sales and marketing users
Internal evidence	Importer and supplier reviewers only
Archive	Authorized operations users, excluded from routine distribution

Name one current file or collection for each purpose. Use a revision and status rather than filenames such as final or latest. When a file is replaced, remove the former version from normal recipient access and retain it internally with the submission history.

Save the exact workbook, PDF, form, email attachment, or portal export that left the company. If the distributor uses a portal, capture the submitted values and confirmation. A current internal record alone does not show what the recipient received.

Run the onboarding workflow from request to live item

Use one sequence with explicit gates:

1. Request current instructions. Obtain vendor, item, logistics, commercial, portal, and asset specifications from the named distributor division.
2. Open the controlled record. Define legal entities, market, portfolio scope, owners, target context, revision, and requirement classes.
3. Map responsibilities. Assign federal and import work to the responsible US importer, supplier evidence to the winery or brand owner, jurisdictional decisions to the market compliance owner, and recipient fields to the appropriate contributor.
4. Complete restricted vendor setup. Submit company, tax, insurance, credit, and payment records through the approved channel.
5. Approve relationship scope. Record the executed agreement, territory, brands, contacts, and operational tasks.
6. Build exact market items. Verify identity, vintage, package, identifiers, logistics, status, and source records.
7. Close compliance prerequisites. Record federal evidence and complete each confirmed state or local dependency.
8. Approve commercial terms. Lock the price basis, currency, adjustments, freight, and applicable context.
9. Prepare sales readiness. Publish the approved bottle images, product sheets, descriptions, training material, and contacts.
10. Review by function. Compliance, finance, logistics, sales, marketing, and operations approve the fields and files they own.
11. Submit one package. Send the controlled revision and retain the exact submission and confirmations.
12. Resolve recipient exceptions. Correct the source first, repeat affected approvals, and resubmit only the controlled replacement.
13. Capture acceptance. Record vendor approval, item codes, warehouse approval, open conditions, and distributor contacts.
14. Test the live workflow. Verify ordering, pack, price basis, receiving data, portal access, assets, and escalation routes.
15. Close onboarding. Mark accepted exceptions, owners, next triggers, and the location of the final record.

Do not use one overall percentage as the only status. Vendor approval can be complete while item setup, state work, warehouse validation, or asset access remains blocked.

Reopen onboarding when material facts change

Onboarding is not a permanent state. Reopen the affected sections after a new vintage, package or case change, new GTIN, price update, warehouse move, territory amendment, distributor division change, ownership change, contact change, registration change, or corrected product claim.

For a vintage rollover, preserve the prior item and review:

• label and COLA coverage
• state treatment
• importer and distributor codes
• GTIN decision at each packaging level
• bottle and case configuration
• dimensions, weights, and pallet data
• price and availability
• bottle images and label files
• tech sheet, sell sheet, descriptions, and accolades
• distributor portal and training material

Classify copied values as confirmed unchanged, changed, awaiting evidence, or not applicable. Keep both vintages visible when both are intentionally active. Retire the predecessor from current access only when the responsible owners confirm the transition.

A pre-launch workspace being designed for importer operations can help organize current product details, bottle and brand assets, tech sheets, sell sheets, distributor asset access, and vintage updates. Whether the team uses a workspace, shared drive, or controlled spreadsheet, preserve responsibility boundaries, evidence, approved status, recipient access, and submission history.

Complete final distributor onboarding QA

Run this checklist against the controlled onboarding record, the exact submission, and the live distributor setup:

Scope and ownership

• Legal supplier, brand owner or winery, US importer, distributor, division, territory, and market are identified separately.
• The agreement, operations, compliance, finance, logistics, sales, marketing, and distributor contacts are current.
• Every line is classified as federal, jurisdiction-specific, distributor-required, or internally recommended.
• Each task names the responsible party, source, evidence, status, and blocker.
• Supplier support tasks do not misstate obligations controlled by the US importer.
• The target launch context, package revision, and source location are visible.

Company and agreement

• Vendor application uses the exact contracting entity and current distributor form.
• Tax, insurance, credit, banking, and remittance records were reviewed by authorized owners.
• Sensitive records were transferred through the approved restricted route.
• Contracting entities, territory, channels, brands, effective context, terms, and amendment references match the executed agreement.
• Purchase-order, payment, compliance, logistics, sales, asset, and escalation contacts have been tested.

Product and compliance

• Every sellable vintage, volume, package, case pack, and market configuration has a separate controlled item.
• Producer, brand, wine, vintage status, class or type, origin, ABV, and net contents agree across approved sources.
• Importer SKU, producer code, consumer GTIN, case GTIN, distributor code, and state code remain separate.
• Identifier assignment, packaging level, displayed digits, and verification status are recorded.
• COLA reference, holder, status, qualifications, label files, and package review describe the submitted item.
• Federal import, FDA, customs, and importer-record responsibilities remain with their confirmed owners.
• State and local requirements were checked for the exact product, parties, and route to market.
• Regulatory approval and distributor acceptance are recorded as separate decisions.
• No unresolved identity or compliance conflict is hidden by a completed overall status.

Commercial and logistics

• Distributor price identifies item, case pack, currency, basis, applicable context, and approver.
• Discounts, allowances, freight, taxes, deposits, and other adjustments are labeled separately when used.
• Planning estimates are excluded from approved recipient pricing.
• Ship point, purchase-order route, order unit, lead time, minimum, and warehouse contacts are current.
• Case dimensions, gross weight, pallet data, lot code, barcode, and label treatment match the actual shipment or approved specification.
• Initial order and receiving checks use the same pack, code, price basis, and ship point as the approved setup.

Sales assets and access

• Bottle images, label files, tech sheets, sell sheets, descriptions, portfolio, and training materials describe the same item.
• Accolades, certifications, production statements, and product claims have approved evidence.
• Usage rights, audience, market, revision, owner, and currentness are recorded for shared assets.
• Distributor users can reach the approved collection and cannot reach restricted internal records.
• Tax files, banking details, contracts, importer records, drafts, and superseded assets are excluded from normal sales access.
• Downloaded filenames remain meaningful outside the portal or shared drive.

Submission and launch

• The exact files and portal values submitted to the distributor are retained with the revision.
• Vendor, item, warehouse, commercial, and asset approvals are recorded separately.
• Assigned distributor item codes and accepted exceptions are written back to the controlled source.
• Corrections were made in source records and regenerated, not patched only in recipient files.
• A live order test confirms item identity, pack, price basis, warehouse data, and escalation route.
• A distributor user can find the current bottle image, product sheet, code, and contact without internal guidance.
• Superseded files are removed from routine recipient access and linked to their replacements internally.
• Vintage, package, price, warehouse, territory, distributor, ownership, and contact changes have defined reopening triggers.
• A second reviewer can trace a live distributor item back through the submission to its approved product, compliance, commercial, and logistics sources.