Wine SKU Master Spreadsheet Template for Importer Operations

Build the SKU master for importer operations

This guide is for wine importer operations teams that need one controlled spreadsheet for product identity, compliance references, packaging, logistics, market setup, pricing references, ownership, and status. It is designed for a portfolio with several producers, vintages, bottle formats, case packs, states, or distributors.

The template can feed distributor item forms, price lists, portfolio exports, sales documents, warehouse records, 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 wine facts, market-specific facts, supporting evidence, and published exports connected without forcing them into one oversized cell. The objective is not to collect every possible fact. It is to make each important value identifiable, owned, traceable, and safe to reuse.

Define what the master controls

A SKU master should answer five questions without requiring an inbox search:

1. What exact wine and package does this record describe?
2. Which identifiers belong to the bottle, case, importer, distributor, and state system?
3. Which evidence supports the regulated and operational fields?
4. Where is the item active, pending, blocked, superseded, or discontinued?
5. Who approved the value, and which output uses it?

Keep nearby documents separate:

Record or document	Primary job	Relationship to the SKU master
Wine SKU master	Define controlled product and market-item data	Source for structured identity, packaging, logistics, status, and references
Distributor item form	Request setup in one distributor system	Recipient-specific export and response record
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
Tech sheet	Explain one wine in production and sensory detail	Reads approved wine and vintage facts
Sell sheet	Support a focused sales conversation	Reads approved identity, positioning, and commercial facts
Compliance packet	Preserve approvals and review evidence	Supplies references and files linked from the master

Do not make the spreadsheet the only home for a COLA, label image, contract, or supplier specification. Store the controlled file in its approved location and place a durable reference in the row. Conversely, do not leave the spreadsheet with a filename that nobody can trace to the supporting record.

Set the row grain before choosing columns

The row grain is the rule that determines what one row represents. Write it at the top of the workbook instructions tab.

A useful grain for distributor operations is:

One row = one importer SKU + one vintage status + one bottle or package format + one case pack + one market + one distributor

That grain intentionally creates separate rows for differences that can affect ordering or setup. Examples include:

• the same wine in 750 mL and 1.5 L bottles
• two vintages available at the same time
• a standard bottle and a gift-box presentation
• 6-bottle and 12-bottle cases
• the same importer item handled by two distributors
• one item active in one state but awaiting approval in another

A broader product table can hold facts shared across markets. A market-item table can then hold the distributor, state, price reference, availability state, and recipient codes. If the team keeps everything on one tab, repeat shared facts deliberately and add checks that expose disagreement. Do not merge cells to make related rows appear grouped. Merged cells interfere with sorting, filtering, validation, and export mapping.

Choose stable internal keys

Create an internal key that does not depend on a description, vintage label, or distributor number. A simple pattern might be WINE-0042 for the wine identity and MI-0187 for a market item. The exact syntax is an internal decision. Stability matters more than embedding every attribute in the code.

Do not silently recycle an inactive SKU for a new wine. Keep the former record, change its status, and link a successor when appropriate. A human-readable description can change after a spelling correction. The stable key should continue to connect approvals, exports, and history.

Use a workbook structure that separates concerns

A small portfolio may begin with four tabs. Add a tab only when it has a distinct 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 filters and exports
Lists	One allowed value	Validation options for status, units, wine type, 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 Producers, Wines, Vintages, Packages, Market_Items, Assets, and Exports. Do that only when the relationships can be maintained reliably. A collection of loosely connected tabs is not safer than one table.

Keep formulas out of free-text notes. Put calculated fields in named columns and explain the formula in Instructions. Freeze the header row, use filters, and keep a unique column name for every field. Avoid blank separator rows inside the controlled table because they can be mistaken for the end of an export range.

Start with a minimum viable SKU template

The following columns form a practical first version. They identify the 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 ordering or operational code	Store as text
Producer	Approved producer name	Select from controlled producer records
Brand	Approved brand name when distinct	Do not substitute producer automatically
Wine or cuvée	Exact product name	Preserve spelling and accents
Vintage status	Four-digit vintage or controlled non-vintage value	Do not infer from an old file
Wine type	Controlled category used by the team	Keep separate from sales copy
Country	Approved country value	Use a controlled list
Region or appellation	Approved market presentation	Link evidence where review is required
ABV	Approved alcohol statement	Record source and review status
Bottle volume	Numeric value	Pair with a separate unit column
Volume unit	mL, L, or another approved unit	Use validation
Package format	Bottle, can, box, gift pack, or precise alternative	Do not hide format in the name
Units per case	Sellable 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
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
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	Concise reason for the latest material change	Link to detailed log entry

This minimum is a starting point, not a universal requirement. A distributor may ask for dimensions, weights, pallet configuration, warehouse, freight basis, tax treatment, or descriptions. Add those fields with definitions and owners rather than placing them in Notes.

Keep identifiers distinct

SKU, UPC, GTIN, case code, distributor item number, and state item number are not interchangeable labels. The GS1 US GTIN overview explains that a GTIN identifies a trade item and distinguishes structures used for consumer units and higher packaging levels. State who assigned each identifier and which packaging level it represents.

Use separate columns for:

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

Format identifier columns as text before pasting values. This protects leading zeroes and prevents scientific notation. Validation can flag unexpected lengths, but it should not manufacture missing digits or declare a code valid solely because its length looks right.

Record packaging level and assignment evidence

For each GTIN, include packaging level, assigning organization, verification method, and evidence location. Scan a production unit or approved final package when the operating process requires scan confirmation. Record the result rather than typing looks correct into notes.

The GS1 GTIN Management Standard says a new product receives a new GTIN at the base-unit level and each higher packaging level. It also calls for a new GTIN when declared net content changes, and its wine example makes vintage treatment conditional on whether the vintage is recognized as a different-quality product rather than handled as a flow-through commodity. Document the brand owner’s GTIN policy and the recipient’s handling instead of applying one blanket vintage rule.

Recipient rules can add another identifier layer. The Pennsylvania Liquor Control Board’s case labeling requirements distinguish the PLCB item code, a vendor-assigned 14-digit shipping container code or GTIN, and the UPC on the retail selling unit. That is a Pennsylvania-specific example. It should not be copied into every market row as a national rule.

Structure product identity and compliance references

Product identity fields need a named source. TTB’s wine labeling guidance organizes federal label topics including brand name, class and type, alcohol content, name and address, and net contents. Use the applicable approved label and compliance review as sources for regulated identity. Do not use a sales deck as the deciding record when label evidence disagrees.

Add these fields when they apply to the operating process:

Field group	Recommended columns	Source or owner
Legal identity	Importer legal name, trade name, producer, brand	Compliance-approved company and product records
Wine identity	Cuvée, vintage status, class or type, variety or blend	Approved label, producer evidence, and compliance review
Origin	Country, region, appellation, vineyard when used	Approved label and verified producer source
Package statement	ABV, net contents, container type	Approved label and final package specification
COLA reference	TTB ID, holder, status, approval file, qualifications	Compliance packet
State reference	Market, registration or approval number, status, evidence	Responsible state compliance owner
Review control	Compliance owner, decision, reviewed context, exception	Internal approval record

The TTB Public COLA Registry provides information on approved, expired, surrendered, and revoked COLAs. A registry result can support verification, but the operations row should still point to the exact approval packet and review used for the marketed package.

Do not paste sensitive permit credentials or confidential registration data into a broadly shared workbook. Store the approved reference needed for operations and restrict underlying records according to company policy.

Capture packaging and logistics as measured data

Bottle volume is not a substitute for shipped weight or case dimensions. Use an approved supplier specification, production sample, warehouse measurement, or other controlled source. Record the measurement units and whether a weight is net or gross.

Bottle and package fields

• package format
• bottle or package volume and unit
• bottle height, width or diameter, and depth where applicable
• empty or gross bottle weight, clearly labeled
• closure type when operationally useful
• consumer GTIN and barcode verification status
• package material or special handling when needed

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. Packaging materials contribute to shipped weight, and the resulting estimate is not a measurement. If dimensions or weights remain unconfirmed, use an exception state that blocks the relevant export.

A useful validation rule checks that cases per pallet = cases per layer × layers per pallet when all three values are present. Treat a mismatch as a review prompt, not as permission for the spreadsheet to overwrite a supplier-confirmed pallet count.

Separate market and commercial fields

A product can be physically identical across markets while its distributor assignment, status, recipient code, price reference, freight basis, or launch timing differs. Put market-specific fields on the market-item row or in a related market table.

Recommended market columns include:

• market and territory
• distributor and division
• distributor item code
• state item or registration reference
• setup status and submission date
• accepted date and accepting contact
• first available context
• allocation or seasonal 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

Do not turn the SKU master into a casually edited price list. Keep approved case price, unit price, discounts, allowances, and effective context in the controlled commercial record. The master can link that record and expose selected approved fields when operations needs them.

TTB’s guidance for importing bottled alcohol beverages into the United States describes federal importer permit and COLA context while also directing importers to state requirements. This is why a federal product row should not be treated as proof that every market-specific step is complete.

Build source, ownership, and status into the template

A field without a source becomes difficult to review after the person who entered it leaves the project. A field without an owner can remain pending through several distributor deadlines. Control both in the spreadsheet.

For critical fields, capture:

Control	Meaning	Example entry
Source type	Kind of evidence used	Approved label, producer specification, 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	Conflicting supplier specifications
Next action	Specific step needed	Measure production case
Successor	Replacement record when changed	New vintage or package record ID

Avoid one workbook-wide verified flag. Identity can be approved while case dimensions remain pending. Use field-group status columns such as identity_status, compliance_status, logistics_status, commercial_status, and assets_status when those groups have different reviewers.

Define item lifecycle separately from evidence status. Current should mean the item is intended for normal use in the defined context. It does not mean every optional field is populated. Blocked should identify an item that cannot proceed to a named output. Superseded should point to a replacement rather than disappearing from history.

Add validation without hiding uncertainty

Spreadsheet validation should prevent avoidable entry mistakes and surface incomplete work. It should not turn an assumption into an approved value.

Use controlled lists for:

• item and evidence status
• vintage treatment
• market and distributor
• wine type
• 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 rows marked current
• numeric volume, pack, dimensions, and weight values
• nonpositive case pack
• consumer and case identifiers duplicated unexpectedly
• distributor code present without a distributor
• current status with blocked compliance or logistics status
• superseded status without a successor
• formula errors and broken source links

Conditional formatting can make exceptions visible, but color should not be the only signal. Add a text status or error column so filtered views, 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 producer item, package variation, and new market assignment:

1. Define the sellable configuration. Confirm the wine, vintage treatment, volume, format, case pack, market, and intended distributor.
2. Assign stable internal keys. Create the wine, package, and market-item references required by the workbook model.
3. Collect source records. Obtain approved label evidence, producer specifications, codes, final package details, logistics measurements, market requirements, and commercial references.
4. Enter facts by owner. Have compliance, logistics, finance, portfolio, and operations enter or approve the fields they control.
5. Resolve conflicts. Stop the affected output when label, producer, package, warehouse, or commercial sources disagree. Record the issue and deciding owner.
6. Verify identifiers. Confirm assignment, packaging level, text formatting, and scan result where required.
7. Run workbook validation. Check row grain, required fields, duplicates, formulas, statuses, and source access.
8. Approve the market item. Record each functional decision and move the item to the state defined by the operating policy.
9. Generate recipient outputs. Map only approved fields into distributor forms, price lists, catalogs, and asset records.
10. Capture the response. Add assigned distributor or state codes, acceptance status, exceptions, and the exact submitted version.
11. Test downstream use. Compare the live distributor or warehouse item against the approved source row.
12. Close or retain exceptions. Resolve the source first, regenerate affected outputs, and preserve what the corrected 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 role is to keep the item moving, expose gaps, and preserve the connection between source and output.

Treat vintage and package changes as change sets

Do not overwrite the prior vintage to create the next one. Duplicate only as a controlled starting point, assign the proper keys, and reopen every field that may have changed.

Review:

• vintage and label presentation
• COLA coverage and qualifications
• state treatment
• GTIN decision at each packaging level
• importer and producer codes
• bottle volume and package format
• case pack, dimensions, weights, and pallet pattern
• distributor item treatment
• commercial record and availability
• bottle images, tech sheet, sell sheet, descriptions, and accolades
• 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 survived the previous review.

Keep both vintage records current when both remain intentionally available. Identify each one precisely in outputs. When the former vintage is no longer active, mark it superseded or discontinued according to the policy, retain its evidence, and connect it to the successor.

Apply the same method to a volume, closure, bottle, label, or case-pack change. A change to declared net content requires a new GTIN under the GS1 GTIN Management Standard, but the operational impact can extend beyond the identifier. Reopen label review, case configuration, measurements, pricing references, images, distributor setup, and every export that describes the package.

Publish views instead of sharing the working master

The working master may contain internal notes, blocked records, source paths, confidential references, and irrelevant columns. Create named export views with explicit filters and fields.

Useful views include:

• distributor item setup
• approved current item list
• compliance exception queue
• logistics measurement queue
• vintage rollover review
• price-list source view
• portfolio item 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 save the exact file that was sent.

Never patch a recipient file without correcting the SKU master. Update the source, repeat the necessary approval, and regenerate each affected output.

Late in the workflow, the pre-launch Depletement workspace being designed for importer operations can be considered alongside a controlled spreadsheet for organizing product details, sales assets, distributor access, and vintage updates. The tool choice does not change the control standard: exact row grain, named owners, preserved evidence, intentional status, and reproducible exports.

Complete final wine SKU master QA

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

• Workbook scope, row grain, revision, status, and owner are visible.
• Every market item has a unique stable key.
• Producer, brand, wine, vintage status, class or type, origin, ABV, and volume describe the same product.
• Bottle volume, package format, case pack, case dimensions, and weight describe the shipped configuration.
• Importer SKU, producer code, consumer GTIN, case GTIN, distributor code, state code, and legacy code have separate columns.
• Identifier columns are formatted as text and preserve leading zeroes.
• Each GTIN records its packaging level, assignment source, and verification state.
• COLA and state references point to the evidence reviewed for the exact market item.
• Market, distributor, warehouse, availability, and setup status are current for the row.
• Pricing fields point to an approved commercial record with currency, basis, and effective context.
• Critical field groups have named owners, sources, and verification states.
• Unknown values are marked awaiting confirmation or exception rather than guessed.
• Duplicate, required-field, formula, status, and source-link checks pass.
• No blank separator rows, merged data cells, hidden errors, or broken formulas affect the controlled range.
• Current, blocked, superseded, and discontinued states follow the written policy.
• Every superseded item points to a successor when one exists.
• Vintage and package changes preserve the prior record and reopen affected fields.
• Export filters exclude internal notes, blocked rows, confidential references, and unintended markets.
• Export row count and item keys match the approved source view.
• The exact distributor submission or published export is retained with its revision and response.
• A second reviewer can trace a critical value from export to SKU row to supporting evidence.

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