Spirits SKU Master Spreadsheet Template for Importer Operations

Build the SKU master for importer operations

This guide is for distilled spirits importer operations teams that need one controlled spreadsheet for product identity, formula and label references, packaging, logistics, market setup, commercial data, assets, ownership, and status. It is designed for portfolios with multiple brands, expressions, proofs, bottle sizes, case packs, states, or distributors.

The template can feed distributor item forms, control-state submissions, price lists, catalogs, warehouse records, sell sheets, and launch reviews. It is not an inventory ledger, compliance determination, accounting system, or substitute for required records. Qualified owners should decide which federal, state, local, and distributor requirements apply.

Use one row for one precisely defined sellable configuration in one market context. Keep shared liquid facts, package facts, market-specific facts, supporting evidence, and published outputs connected without squeezing all of them into an unstructured notes cell. The goal is simple: each important value should be identifiable, owned, traceable, and safe to reuse.

Define what the master controls

A useful spirits SKU master should answer six questions without an inbox search:

What exact liquid and consumer package does this record describe?
Which bottle, case, and market configuration is being sold?
Which identifiers belong to the importer, brand owner, packaging levels, distributor, and state system?
Which evidence supports the compliance and operational fields?
Where is the item active, pending, blocked, superseded, or discontinued?
Who approved the value, and which outputs use it?

Keep neighboring documents separate:

Record or document	Primary job	Relationship to the SKU master
Spirits SKU master	Define controlled product and market-item data	Source for structured identity, packaging, logistics, status, and references
Formula packet	Preserve formula review and supporting material when applicable	Supplies the approved reference and qualifications
COLA packet	Preserve label approval and internal review evidence	Supplies label identity and approval references
Distributor item form	Request setup in one distributor system	Recipient-specific export and response record
Control-state submission	Request code, listing, or quotation handling	Market-specific output with its own status and response
Price list	Communicate approved commercial terms	Reads item identity and approved pricing references
Inventory ledger	Track quantities and movements	Uses stable item IDs but changes on a different schedule
Technical sheet	Explain production and product details	Reads approved liquid and package facts
Sell sheet	Support a focused sales conversation	Reads approved identity, positioning, and commercial facts

Do not make the spreadsheet the only home for a formula, COLA, final label file, supplier specification, or contract. Store each controlled file in its approved location and place a durable reference in the row. The reverse matters too. A row that points only to final-label-v4.pdf is not traceable if nobody can locate or identify that file later.

Set the row grain before choosing columns

The row grain determines what one row represents. Put the rule on the workbook’s Instructions tab before anyone begins entry.

A practical grain for importer operations is:

One row = one importer SKU + one liquid identity + one bottle or package format + one case pack + one market + one distributor

That rule creates separate rows for differences that can change ordering, approval, or setup. Examples include:

the same spirit at 750 mL and 1 L
the same expression at two approved proof levels
a standard bottle and a gift-box presentation
6-bottle and 12-bottle cases
a bottle and a sellable multipack
the same item handled by two distributors
one item active in one state but awaiting listing in another

A product table can hold facts shared across markets. A package table can define the bottle and case. A market-item table can hold the state, distributor, price reference, availability, recipient codes, and submission status. If the team keeps everything on one tab, repeat shared facts deliberately and add checks that reveal disagreement.

Do not merge cells to make related records look grouped. Merged data cells interfere with sorting, filtering, validation, and exports.

Choose stable internal keys

Create internal keys that do not depend on a product description, proof statement, distributor number, or state code. A simple pattern might use SPIRIT-0042 for the liquid identity, PKG-0097 for the package, and MI-0187 for the market item. The exact syntax is an internal choice. Stability matters more than encoding every attribute in the key.

Do not recycle an inactive SKU for a new expression. Keep the old record, update its lifecycle status, and link a successor when one exists. Descriptions can change after a spelling correction or packaging revision. The stable key should continue to connect approvals, submissions, assets, and history.

Use a workbook structure that separates concerns

A small portfolio can start with four tabs. Add a tab only when it has a distinct row grain, owner, or update pattern.

Tab	One row represents	Required purpose
`Instructions`	One workbook	Scope, row grain, controlled values, owners, formulas, revision, and publication rules
`SKU_Master`	One exact market sellable item	Approved working data used for review, filters, and exports
`Lists`	One allowed value	Validation options for status, units, category, market, and ownership fields
`Change_Log`	One approved or rejected change	Old value, new value, source, reason, requester, reviewer, and effective context

Larger teams can split the source into Brands, Liquids, Packages, Cases, Market_Items, Assets, and Exports. Use that structure only when the relationships can be maintained reliably. Several tabs with copied names and no stable keys create more ambiguity, not less.

Keep calculated fields in named columns and explain each formula in Instructions. Freeze the header row, turn on filters, and use a unique name for every column. Avoid blank separator rows inside controlled ranges because an export tool or operator may read the first blank row as the end of the table.

Start with a minimum viable spirits SKU template

The following columns form a practical first version. They identify the exact item, control its state, and give reviewers a route to the evidence.

Column	Entry	Control rule
Market item ID	Stable internal key	Required and unique
Importer SKU	Importer’s operational or ordering code	Store as text
Brand	Approved brand name	Use the compliance-approved spelling
Expression	Fanciful name or exact product expression	Do not substitute a sales nickname
Class or type	Approved distilled spirits designation	Link to the reviewed label record
Country of origin	Approved country statement for an import	Do not infer from the brand story
Producer or distiller	Approved responsible party value	Keep distinct from importer and brand owner
ABV	Approved alcohol by volume	Store numeric value and display rule separately
Proof	Approved proof statement when used	Validate against the reviewed product record
Age statement	Exact approved statement when applicable	Preserve wording and source
Bottle volume	Numeric value	Pair with a separate unit column
Volume unit	mL, L, or another approved unit	Use validation
Package format	Bottle, can, pouch, gift pack, or precise alternative	Do not hide format in the description
Units per case	Consumer units in the shipping case	Numeric and greater than zero
Consumer GTIN	Base-unit identifier when used	Store as text and preserve leading zeroes
Case GTIN	Higher-level packaging identifier when used	Keep separate from consumer GTIN
COLA reference	TTB ID or internal approval reference	Point to the exact reviewed packet
Formula reference	Formula ID or controlled not-applicable state	Do not guess applicability
Market	Defined state or territory	Required for a market-item row
Distributor	Named distributor or controlled pending value	Never invent an assignment
Distributor item code	Recipient-assigned code when available	Blank or pending until assigned
State or control code	Market authority code when applicable	Keep separate from distributor code
Item status	Draft, in review, current, blocked, superseded, or discontinued	Controlled list
Evidence status	Unverified, partial, verified, or exception	Controlled list
Item owner	Accountable person or function	Required
Last reviewed	Team-defined review date	Update through the review workflow
Source packet	Durable location for supporting records	Test access before publication
Change note	Reason for the latest material change	Link to the detailed log entry

This is a starting point, not a universal requirement. A distributor or state may ask for dimensions, weights, pallet configuration, proof gallons, warehouse information, freight basis, tax treatment, descriptions, or image files. Add a defined field and owner when the information is required. Do not bury recurring data in Notes.

Keep identifiers distinct

SKU, UPC, GTIN, case code, Control State Code, distributor item number, and state item number are not interchangeable terms. Create separate columns for each identifier the workflow uses:

importer SKU
producer or supplier code
consumer-unit GTIN or UPC
inner-pack GTIN when applicable
case GTIN or shipping container code
distributor item code
state or control-system item code
warehouse item code when distinct
legacy code retained for cross-reference

Format identifier columns as text before pasting values. This preserves leading zeroes and prevents scientific notation. Validation can flag unexpected lengths, but it should not add digits, strip digits, or declare a code valid solely because the character count looks right.

Record packaging level and assignment evidence

For each GTIN, capture the packaging level, assigning organization, product relationship, verification method, and evidence location. Scan a production unit or approved final package when the operating process calls for scan confirmation. Record the result.

The GS1 GTIN Management Standard treats a new product as requiring a new GTIN at the base-unit level and at each higher packaging level. It also identifies declared net-content changes as changes that require a new GTIN. Use the standard and the brand owner’s assignment policy to document the decision. Do not copy the bottle code into the case field merely because a recipient requires a value.

Recipient systems can add another code layer. The NABCA Control Systems page describes a six-digit Control State Code for beverage alcohol brands and sizes, with a three-digit class prefix and a two-digit size suffix used in the coding structure. Store those parts according to the current recipient instructions. Do not label that code as a consumer GTIN.

Pennsylvania provides a concrete warehouse example. The PLCB’s labeling requirements distinguish its item code, the vendor-assigned shipping-container identifier, and the UPC on the retail selling unit. That is a Pennsylvania-specific requirement. It should not become a national default in the workbook.

Structure liquid identity and federal references

The product record needs an approved source for every regulated identity field. TTB’s distilled spirits labeling hub identifies mandatory label topics including brand name, class or type, alcohol content, health warning, name and address, net contents, and country of origin for imports. Use the reviewed label and compliance record as sources for those values. A distributor form or sales deck is an output, not the deciding source.

Add these field groups when they apply:

Field group	Recommended columns	Source or owner
Legal identity	Importer legal name, trade name, brand owner, producer, bottler	Compliance-approved company and product records
Product identity	Brand, expression, class or type, production designation	Approved label, formula record when applicable, and compliance review
Alcohol statement	ABV, proof, tolerance or presentation note used internally	Approved label and product specification
Claims	Age, origin, finish, flavor, treatment, or other reviewed statement	Approved label and substantiation packet
Package statement	Net contents, container type, consumer package	Approved label and final package specification
Formula reference	Formula ID, applicant, status, qualifications, evidence location	Compliance packet
COLA reference	TTB ID, holder, status, approval file, qualifications	Compliance packet
State reference	Market, registration or listing number, status, evidence	Responsible state compliance owner
Review control	Compliance owner, decision, reviewed context, exception	Internal approval record

TTB’s mandatory distilled spirits label information says brand name, alcohol content, and class, type, or other designation must appear in the same field of vision. It lists other information that may appear on any label, including name and address, net contents, certain ingredient disclosures, age statement, and state of distillation where applicable. This is a useful reason to keep the label packet connected to the structured record rather than relying on manually transcribed product copy.

Track formula applicability without pretending every spirit is the same

Not every distilled spirits item follows the same formula path. TTB states in its formula approval guidance that certain alcohol beverages require evaluation of ingredients and production process before they are made or imported and before a label application is submitted when required. The agency provides a product-specific tool for determining applicability.

Use controlled values such as Required, Not required, In review, and Exception. Include the compliance owner and source for the decision. When a formula is required, capture the formula number, applicant, status, product relationship, qualifications, and packet location. Keep confidential recipes and restricted supporting material outside a broadly shared workbook.

Connect COLA evidence to the exact package

For imported bottled alcohol, TTB’s importing bottled alcohol guidance says the importer must obtain a TTB-issued COLA for each unique product or label after receiving its importer permit and must possess the COLA at importation. The same page notes that pre-COLA approval may be needed depending on the product and directs importers to state and local requirements in addition to federal requirements.

A COLA reference should connect to the marketed package, not merely to the brand. Capture the TTB ID, holder, approval status, brand, expression, class or type, ABV, net contents, label images, qualifications, and compliance review. If the physical bottle or market label differs from the packet, block the affected output until the owner resolves the difference.

Capture packaging and logistics as measured data

Bottle volume does not establish the shipped bottle weight, case dimensions, or pallet configuration. Use a final supplier specification, production sample, warehouse measurement, approved packaging drawing, or another controlled source. Record the units and identify whether each weight is net or gross.

Bottle and consumer-package fields

package format
bottle or package volume and unit
bottle height, width or diameter, and depth where applicable
filled bottle gross weight
closure type when operationally useful
gift box, sleeve, tube, or other presentation component
consumer GTIN and barcode verification status
label version and package-image reference
special handling requirement supplied by the producer

Case and pallet fields

units per case
unit of sale
case length, width, and height with a defined axis order
case gross weight
case GTIN and label position
cases per layer
layers per pallet
cases per pallet
pallet dimensions, type, and gross weight when requested
lot or production-code format
warehouse and pickup point
storage or handling instruction supplied by the producer

Do not calculate case weight by multiplying liquid volume. Glass, closures, cartons, dividers, and other materials contribute to shipped weight. If a dimension or weight remains unconfirmed, use an exception state that blocks the output which needs it.

A useful formula checks whether cases per pallet = cases per layer × layers per pallet when all three fields are present. A mismatch should create a review task. It should not silently overwrite a supplier-confirmed pallet count.

Separate market, distributor, and control-state data

The same physical item can have different distributor assignments, recipient codes, listing statuses, prices, warehouses, and launch dates across markets. Put those values on the market-item row or in a related market table.

Recommended market columns include:

market and territory
regulatory or control authority
distributor and division
distributor item code
state registration, listing, or control-code reference
setup or listing status
submission date and revision
accepted date and accepting contact
first available context
allocation, seasonal, or limited status
warehouse or ship point
order minimum and lead-time source
currency and price basis
approved price-record reference
freight, allowance, deposit, and tax-treatment references
sales owner and operations owner

Control jurisdictions deserve their own workflow rather than a single checkbox. NABCA’s control-system overview explains that control jurisdictions use government agencies at the wholesale level for distilled spirits, and some also exercise control over off-premises retail sales. The page also provides links for Control State Code applications and product registration. Treat that as a routing signal. Obtain the current instructions for the named jurisdiction instead of assuming one control-state process covers every market.

Do not turn the SKU master into a casually edited price list. Keep case price, unit price, allowances, freight treatment, and effective context in the controlled commercial record. The master can link to that record and expose approved fields needed for operations.

Build source, ownership, and status into the template

A value without a source becomes hard to defend after the original operator leaves. A field without an owner can remain pending through several launch reviews. Store both controls with the record.

For critical field groups, capture:

Control	Meaning	Example entry
Source type	Kind of evidence used	Approved label, formula decision, measured case, distributor confirmation
Source location	Durable file or record reference	Controlled path or record ID
Field owner	Function accountable for the value	Compliance, operations, logistics, finance, portfolio
Verification state	Readiness of the value	Unverified, in review, verified, exception
Reviewed context	Team-defined review marker	Approval record or reviewed date
Exception reason	Why the value cannot be approved	Bottle image conflicts with approved label
Next action	Specific step needed	Measure production case
Successor	Replacement record when changed	New package or expression record ID

Avoid one workbook-wide verified flag. Label identity can be approved while case dimensions remain pending. Use group statuses such as identity_status, formula_status, label_status, logistics_status, commercial_status, and assets_status when those areas have different owners.

Keep lifecycle state separate from evidence state. Current should mean the item is intended for normal use in the defined market context. It does not mean every optional field is complete. Blocked should identify an item that cannot proceed to a named output. Superseded should preserve history and point to the replacement when one exists.

Add validation that exposes uncertainty

Spreadsheet validation should prevent routine entry mistakes and surface incomplete work. It should not convert an assumption into an approved fact.

Use controlled lists for:

item and evidence status
formula applicability and status
label-review status
market and distributor
class or type values used internally
package format
measurement and currency units
owner function
source type
yes, no, not applicable, and awaiting confirmation states

Use formula checks for:

duplicate market-item keys
duplicate combinations at the defined row grain
missing required fields on current rows
numeric volume, proof, pack, dimension, and weight fields
nonpositive case pack
consumer and case identifiers duplicated unexpectedly
distributor code present without a distributor
control code present without a market or authority
current status with blocked formula, label, or logistics status
superseded status without a successor when one exists
ABV and proof values that require review
formula errors and broken source links

Conditional formatting can make exceptions easier to see, but color cannot be the only signal. Add a text status or error column so filtered exports and colleagues who cannot distinguish the colors receive the same information.

Run a controlled SKU creation workflow

Use the same sequence for a new expression, package variation, case-pack change, or market assignment:

Define the sellable configuration. Confirm the liquid, proof, bottle volume, presentation, case pack, market, and intended distributor.
Assign stable internal keys. Create the liquid, package, case, and market-item references required by the workbook model.
Collect source records. Obtain the formula decision, approved label evidence, producer specification, identifiers, final packaging data, logistics measurements, market instructions, and commercial references.
Enter facts by owner. Have compliance, logistics, finance, portfolio, and operations enter or approve the fields they control.
Resolve conflicts. Stop the affected output when label, formula, producer, package, warehouse, or commercial sources disagree. Record the issue and deciding owner.
Verify identifiers. Confirm assignment, packaging level, text formatting, and scan result where required.
Run workbook validation. Check row grain, required fields, duplicates, formulas, statuses, and source access.
Approve the market item. Record each functional decision and move the item to the state defined by operating policy.
Generate recipient outputs. Map approved fields into distributor forms, state submissions, price lists, catalogs, and asset records.
Capture the response. Add assigned codes, acceptance status, exceptions, and the exact submitted revision.
Test downstream use. Compare the live distributor, warehouse, or state item with the approved source row.
Close or retain exceptions. Correct the source first, regenerate affected outputs, and preserve what the new version replaced.

One operations owner should manage the complete row even when several functions own individual fields. That person does not make every approval decision. The owner keeps the item moving, exposes gaps, and preserves the connection between sources and outputs.

Treat proof, package, and presentation changes as change sets

Do not overwrite the existing record to represent a materially changed product or package. Duplicate only as a controlled starting point, assign the proper keys, and reopen every affected field.

Review:

formula applicability and approved formula relationship
brand, expression, class or type
ABV and proof
age, origin, finish, flavor, and other claims
COLA coverage and qualifications
state registration or listing treatment
consumer and case GTIN decisions
importer, supplier, distributor, and control-state codes
bottle volume and package format
gift packaging or consumer multipack
case pack, dimensions, weights, labels, and pallet pattern
commercial record and availability
bottle images, tech sheet, sell sheet, descriptions, and awards
market status and launch timing

Classify copied values as confirmed unchanged, changed, awaiting evidence, or not applicable. A copied value is not verified merely because it passed the previous review.

A declared net-content change requires a new GTIN under the GS1 GTIN Management Standard. The operational effect can be broader. Reopen label review, package specifications, case configuration, measurements, price references, images, distributor setup, state handling, and every export that names the old package.

Keep the former record available while inventory, orders, returns, and distributor history still refer to it. Link the successor rather than renaming the old row or deleting its evidence.

The working master may contain blocked records, internal notes, restricted source paths, and columns that a recipient should never see. Create named export views with explicit fields and filters.

Useful views include:

distributor item setup
approved current item list
formula and label exception queue
logistics measurement queue
control-state listing queue
price-list source view
portfolio catalog view
asset readiness view
discontinued and superseded history

Give every export a market, audience, status, revision, owner, and generated context. Record the export definition in the workbook so another operator can reproduce it. Compare source and export row counts, inspect hidden rows and columns, and retain the exact file or portal values submitted.

Never patch a recipient file without correcting the source. Update the SKU master, repeat the required review, and regenerate every affected output.

Late in the workflow, the pre-launch Depletement workspace for alcohol importer operations teams can be considered alongside a controlled spreadsheet for organizing product and catalog information, bottle and brand assets, technical sheets, sell sheets, distributor asset access, and product updates. The tool choice does not change the control standard: exact row grain, named owners, preserved evidence, intentional status, and reproducible exports.

Complete final spirits SKU master QA

Run this checklist against the controlled workbook and at least one real export:

A useful spirits SKU master is not the spreadsheet with the most columns. It is the controlled record that lets an importer identify the exact liquid and package, explain where each important value came from, change the item without erasing history, and reproduce the approved output another team needs.