Wine Case and Pallet Spec Sheet Template for Importer Operations

Build the spec sheet around the shipped configuration

This guide is for alcohol importer operations teams coordinating packaging data between wineries, brand owners, freight partners, warehouses, and distributors. It covers bottle and unit identity, inner packs, shipping cases, dimensions, gross and net weight distinctions, pallet patterns, calculated totals, GTINs, measurement basis, tolerances, evidence, ownership, versions, approvals, mixed cases, change control, and distributor handoff.

One spec sheet should describe one exact shipped configuration. A wine name alone is not enough. Vintage treatment, bottle volume, package format, units per inner pack, units per case, case construction, case code, and pallet pattern can each change what a warehouse receives.

Treat the sheet as a controlled logistics record, not a sales document. Supplier declarations, physical measurements, calculated values, recipient requirements, and internal recommendations belong in separate fields. When those values disagree, show the exception and assign an owner rather than selecting the convenient number.

Distinguish five kinds of data

Every important field should state what kind of value it contains. This prevents a supplier’s nominal specification from being presented as a warehouse measurement or a calculated pallet total from being presented as a scale reading.

Data class	Meaning	Example source	Control rule
Supplier fact	Value declared by the winery, packer, bottle supplier, or case supplier	Approved packaging specification	Preserve the source and its revision
Measured fact	Observation from a named sample and method	Warehouse scale, tape, caliper, or receiving inspection	Record sample, unit, method, operator, and measurement context
Calculation	Formula output from controlled inputs	Cases per pallet or estimated loaded weight	Show the formula and input fields
Requirement	Limit or format imposed by a distributor, warehouse, carrier, or authority	Distributor setup guide or warehouse manual	Name the recipient, scope, and source
Internal recommendation	Team rule for creating and reviewing records	Required owner, second-person check, or photo evidence	Label it as company process, not an external mandate

Add a value class field when one column can hold different types of values. Better still, use separate columns such as supplier case gross weight, measured case gross weight, and approved handoff case gross weight. Keep the conflict visible until the responsible owner decides which value applies.

Define the record and effective context

Create one record for each market item and package configuration. Use a stable record ID that does not change when a description is corrected.

Start with this header:

Field	Required entry
Spec sheet ID	Stable internal identifier
Supplier	Winery, producer, packer, or other source entity
Importer	Legal or operating entity managing the handoff
Producer and brand	Approved product identity
Wine or cuvée	Exact wine name
Vintage status	Exact vintage or controlled non-vintage status
Market item ID	Importer record for the sellable configuration
Distributor and market	Named recipient and jurisdiction when the sheet is recipient-specific
Package configuration	Bottle, inner pack, case, and pallet configuration represented
Revision	Controlled spec-sheet revision
Status	Draft, in review, approved, current, superseded, or archived
Effective date	Date this configuration becomes applicable
Supersedes	Prior record or revision when one exists
Operations owner	Person accountable for completion and handoff
Approvers	Supplier, logistics, compliance, and distributor owners as applicable
Evidence packet	Durable location for specifications, measurements, labels, and photos

Do not use the file’s modified date as its effective date. Record approval and effective dates as separate decisions. An approved future configuration should not silently replace the package still moving through the warehouse.

Map the complete packaging hierarchy

Describe only the levels that exist:

1. Consumer unit: One sellable bottle, can, box, or other retail unit.
2. Inner pack: A physical carton, tray, gift pack, or bundle inside a shipping case when applicable.
3. Shipping case: The case handled as a logistics unit.
4. Pallet load: Cases arranged in a defined pattern on a named pallet type.

Record each parent-child relationship. If inner packs exist, verify that units per inner pack multiplied by inner packs per case equals total consumer units per case. Avoid an unqualified pack field. Use labels such as consumer units per inner pack and inner packs per shipping case.

Use this reusable spec sheet schema

The following schema can be one workbook table, a structured form, or related records. Keep the field definitions with the template.

Bottle or consumer-unit fields

Field	What to record	Source and QA
Market item ID	Stable importer item reference	Item master
Producer, wine, vintage status	Exact product identity	Approved product record
Package format	Bottle, can, box, or precise alternative	Final package specification
Declared net contents	Labeled quantity and unit	Approved label or package
Unit gross weight	Filled sellable unit including packaging	Supplier fact or measured fact, labeled clearly
Unit height	Maximum vertical extent in stated orientation	Measurement record
Unit width or diameter	Defined horizontal basis	Measurement record
Unit depth	Required for non-round packages	Measurement record
Consumer GTIN or UPC	Identifier for the consumer trade item when used	Assignment evidence and package check
Closure and special features	Closure, capsule, handle, protrusion, or gift package affecting fit	Final sample or approved drawing
Measurement basis	Orientation, tool, sample, unit, and rounding	Method record

Record declared net contents separately from measured gross bottle weight. Do not convert liquid volume directly into shipped weight inside the sheet. If a weight is calculated, identify the assumptions and keep it separate from a scale reading.

Inner-pack fields

When a physical inner pack exists, record its ID, description, unit count, GTIN when assigned, dimensions, gross weight, material, case orientation, barcode location, and evidence. A gift box may be part of the consumer unit rather than a separate level, so confirm the orderable and scannable hierarchy with the item owner and recipient.

Shipping-case fields

Field	What to record	Control note
Case description	Exact wine, vintage status, volume, and count	Must match item identity
Consumer units per case	Total sellable units in one physical case	Verify against inner-pack math when applicable
Inner packs per case	Count when inner packs exist	Use not applicable otherwise
Case GTIN or shipping code	Identifier for the case trade item when used	Keep separate from the consumer identifier
Case length	Outside extent on the defined length axis	State closed and loaded measurement basis
Case width	Outside extent on the defined width axis	Use the same axis convention throughout
Case height	Outside vertical extent in shipping orientation	Include closure as defined by the method
Case gross weight	Product and all case packaging as shipped	Supplier or measured value labeled by class
Case net weight	Precisely defined content basis	Do not confuse with declared liquid volume
Case packaging tare	Empty case, dividers, liners, and other included packaging	Measured or supplier-declared basis
Case material and closure	Board, tray, wrap, tape, glue, or other relevant construction	Supplier specification
Case label location	Named case faces and placement	Recipient requirement or approved internal rule
Handling constraints	Orientation, stack, fragility, or other approved instruction	Supplier and warehouse review

Define gross, net, and tare in the workbook instructions. If the team uses case net weight to mean the combined gross weight of filled bottles before the outer carton, say so. If it means product content only, say that instead. Never assume two organizations use the field identically.

Pallet fields

Field	What to record	Value class
Pallet type	Recipient-approved type or supplier description	Requirement or supplier fact
Pallet length and width	Actual or nominal footprint with basis	Requirement or measured fact
Empty pallet weight	Tare from source or measurement	Supplier or measured fact
Cases per layer	Count in the approved pattern	Supplier fact or approved plan
Layers per pallet	Number of loaded layers	Supplier fact or approved plan
Cases per pallet	Controlled total	Calculation and physical verification
Pattern or diagram	Case orientation and count by layer	Approved attachment
Loaded length and width	Maximum outside load extent	Measured fact or controlled calculation
Loaded height	Pallet plus complete secured load	Measured fact or controlled calculation
Product and case weight	Case gross weight multiplied by case count	Calculation
Estimated pallet gross weight	Product and case weight plus pallet and approved packaging tare	Calculation
Measured pallet gross weight	Scale result for a representative completed load	Measured fact
Securing materials	Wrap, straps, corner boards, top cap, slip sheets, or other materials	Supplier fact or requirement
Overhang or underhang	Observed or permitted relationship to pallet edge	Measured fact and recipient requirement
Stackability	Approved handling condition	Supplier and recipient decision

Do not publish one pallet footprint as universal. Record the pallet type, dimensions, entry orientation, height limit, weight limit, and securing method requested by the distributor, warehouse, consolidator, or carrier for the actual lane.

Keep GTINs tied to packaging levels

A GTIN identifies a trade item. GS1 US explains that a GTIN-12 is commonly used in a UPC-A barcode at North American retail point of sale, while a GTIN-14 can identify trade-item groupings such as cases and is not intended for point of sale in its GTIN overview. Record each identifier beside the level it identifies.

Use separate fields for:

• consumer-unit GTIN or UPC
• inner-pack GTIN when assigned
• case GTIN or shipping container code
• pallet trade-item GTIN when the pallet is a predefined trade item
• SSCC or other logistics-unit identifier when required by the recipient
• importer SKU
• distributor item code
• state or warehouse code

Do not create a case GTIN by copying the consumer identifier. Do not label a serial logistics identifier as the product’s GTIN. Record the assigning organization, packaging level, human-readable digits, barcode symbology requested by the recipient, and scan-verification status.

The GS1 GTIN Management Standard says that a change in the number of trade items in a case or the number of cases in a predefined pallet configuration requires a new GTIN at the affected higher packaging level. Use the brand owner’s assignment process and confirm the distributor’s item treatment before publishing revised codes.

Recipient rules can add market-specific fields. The Pennsylvania Liquor Control Board’s case-labeling requirements distinguish the PLCB item number, retail-unit UPC, and a 14-digit shipping container code or GTIN, and set their own case-label content and placement rules. Treat that as a Pennsylvania requirement, not a national default.

Define the measurement method before collecting values

For each package level, state the sample and production status, loaded condition, orientation, axis definitions, included protrusions or securing materials, instrument, unit, sample count, rounding, operator, and evidence. Measure outside extents on a closed package in normal shipping configuration. For a pallet, state whether the basis includes the pallet, complete stack, wrap, straps, and top protection.

Keep source and converted units in separate fields. Use a controlled formula, retain the original value, and identify the value approved for handoff. Preserve supplier drawings and physical measurements by value class when they differ.

Handle gross weight, net weight, and calculations explicitly

Every weight needs a noun and basis. Separate declared unit net contents, filled-unit gross weight, inner-pack gross weight, case gross and defined net weights, case tare, pallet tare, securing-material tare, calculated pallet gross weight, and measured pallet gross weight.

Use a visible planning formula:

Calculated pallet gross weight = case gross weight multiplied by cases per pallet, plus pallet tare, plus included securing-material tare

Label the result calculated. Keep a requested measured load value separate and flag differences for review using an approved internal threshold or recipient limit.

Record pallet pattern and totals so they can be reproduced

Attach a top-view pattern or diagram. Record case orientation, cases per layer, layers, total cases, total consumer units, loaded extents, overhang, interlayers, protection, securing materials, and label visibility.

Use controlled calculations:

Cases per pallet = cases per layer multiplied by layers per pallet

Consumer units per pallet = consumer units per case multiplied by cases per pallet

For alternating patterns, record each layer and sum the counts. Verify calculated totals against a completed load or supplier palletization record. Keep recipient height, weight, overhang, and case-count limits in separate requirement fields.

Set tolerances and exceptions without inventing a standard

Keep nominal targets, measured values, observed ranges, supplier tolerances, recipient limits, internal review thresholds, and approved handoff values separate. Do not invent one percentage tolerance for all package levels. Obtain production tolerances from the supplier, receiving limits from the recipient, and internal thresholds from the logistics owner.

For an exception, record the field, result, source, affected configuration, owner, decision, and replacement evidence. Do not change the nominal value to absorb an outlier.

Address wood packaging only when the route uses it

Include wood-packaging review only when the international route uses relevant wood packaging or dunnage. The International Plant Protection Convention’s ISPM 15 publication says the standard covers raw-wood packaging in international trade, includes dunnage, and excludes processed wood that is free from pests, such as plywood.

Have import and logistics owners assess the pallet, bracing, origin, and route. Where relevant, record construction, treatment or mark evidence required by the responsible process, supplier, inspection, dunnage, and exceptions. Keep evidence with the pallet or shipment record.

Treat mixed cases as defined configurations

Define whether mixed case means a fixed supplier assortment, fixed importer assortment, warehouse pick-and-pack case, or permission to place several full-case SKUs on one order. Record components, quantities, packer, case code, dimensions, weight basis, label, price basis, and recipient acceptance for the exact model.

GS1 defines a predefined assortment as a fixed composition of two or more trade items sold together as one physical trade item. The GS1 GTIN Management Standard says changing, adding, or replacing a component in that predefined assortment requires a new GTIN, while the component trade items retain their own identifiers. Apply that rule only to the fixed assortment it describes.

For a variable pick-and-pack case, do not publish one weight or dimension as if every combination is identical. Ask the warehouse and distributor how they identify, label, price, and constrain the mixed case. Use a maximum, range, per-order calculation, or separate record only when that treatment is approved and clearly defined.

Use recipient requirements rather than pallet folklore

Ask each distributor or warehouse for its current specification before approving a load. Obtain requirements for pallet type, footprint, access direction, loaded height, gross weight, overhang, stackability, wrap, labels, appointment process, and exception approval.

Pennsylvania offers one example of recipient-specific rules. The PLCB says its quoted case pack must be one physical shipping case and cannot be assembled by strapping or taping multiple cases together on its packaging requirements page. Its separate case-label page includes its own label size, placement, item-code, UPC, and shipping-container-code requirements. Use those sources for the applicable Pennsylvania handoff, not as universal distributor specifications.

If a recipient instruction conflicts with a supplier’s normal pallet, open an exception before shipment. Record who approved the alternate pattern, which market items and purchase orders it covers, and whether the supplier master specification also changes.

Run a controlled creation and approval workflow

Use this sequence for a new item or revised package:

1. Request recipient requirements. Obtain current distributor, warehouse, consolidator, and carrier instructions for the intended lane.
2. Define the exact configuration. Confirm wine, vintage status, volume, inner pack, case pack, ship point, pallet type, and market.
3. Open the spec record. Assign its ID, revision, owners, effective context, status, and evidence packet.
4. Collect supplier facts. Obtain final bottle, case, label, GTIN, pallet, and tolerance specifications.
5. Plan measurements. Define samples, orientation, loaded condition, axes, instruments, units, rounding, and photo evidence.
6. Measure representative packages. Record bottle, inner-pack, closed-case, and loaded-pallet observations by value class.
7. Calculate totals. Derive hierarchy counts and planning weights from approved inputs, with formulas visible.
8. Resolve discrepancies. Compare supplier, measured, calculated, and recipient values without overwriting any source.
9. Verify identifiers. Confirm packaging level, assignment owner, barcode, digits, and recipient treatment.
10. Review special conditions. Address mixed cases, wood packaging, stackability, labels, and handling only where applicable.
11. Approve by function. Supplier, logistics, item-data, compliance, warehouse, and operations owners review their fields.
12. Publish the handoff version. Export only approved values, definitions, pattern diagrams, and recipient notes.
13. Capture recipient response. Record acceptance, assigned codes, corrections, and approved exceptions.
14. Test the first shipment. Compare the purchase order, physical case, pallet, warehouse receipt, and approved sheet.
15. Close or revise. Correct the controlled source, regenerate the sheet, and supersede the prior version when needed.

Keep one accountable operations owner even when several specialists approve fields. That owner should manage unresolved values, handoff scope, recipient feedback, and closure.

Treat vintage and package changes as change sets

A new vintage requires documented review even when physical packaging appears unchanged. Reopen identity, GTIN decisions, bottle and gift package, inner-pack count, case count and construction, dimensions, weights, labels, pallet pattern, mixed-case components, recipient requirements, evidence, effective date, approvals, and submissions.

The GS1 standard treats wine vintage as a new product when the year is recognized as a different-quality product and is not handled as a flow-through commodity in the GTIN Management Standard. Confirm the brand owner’s policy and distributor handling rather than applying one answer to every vintage.

For a case-quantity change, reopen unit pricing, warehouse setup, case GTIN, dimensions, weight, pallet pattern, and distributor item treatment. Keep old and new configurations active at the same time when inventory or orders require both. Link the successor without erasing the former package history.

Prepare the distributor handoff

Create a recipient version from the controlled record. Include only the fields needed for setup, receiving, ordering, and approved exception handling.

Include the document revision, exact item, hierarchy counts, identifiers, measurements, weight definitions, pallet type and pattern, calculated totals, loaded extents, measurement basis, receiving tolerances, label and handling rules, contacts, exceptions, and requested photos.

Save the exact spreadsheet, PDF, portal values, or form submitted. Record the recipient, date, revision, rows or items included, and response. Do not edit a sent PDF directly. Update the controlled source, repeat affected approvals, and regenerate the handoff.

The Depletement pre-launch workspace being designed for importer operations is intended to organize current product details, bottle and brand assets, tech sheets, sell sheets, distributor asset access, and vintage updates. Whether the team uses a workspace, database, or spreadsheet, case and pallet values should remain tied to exact items, evidence, owners, versions, and recipient decisions.

Complete final case and pallet spec QA

Run this checklist against the controlled record, physical package, calculations, and recipient handoff.

Identity and hierarchy

• Supplier, importer, producer, wine, vintage status, volume, market item, distributor, and market are correct.
• Spec sheet ID, revision, status, approval date, effective date, superseded record, and owners are visible.
• Consumer unit, inner pack, shipping case, and pallet levels are present only where they exist.
• Units per inner pack, inner packs per case, and total units per case agree.
• One row and one sheet describe one exact shipped configuration.
• Mixed cases identify whether they are fixed assortments, warehouse-built cases, or ordering terms.

Identifiers and labels

• Importer SKU, distributor code, consumer GTIN, inner-pack GTIN, case GTIN, pallet identifier, and logistics-unit identifier are separate.
• Every identifier names its packaging level, assignment owner, symbology where required, and verification status.
• Case quantity and predefined-pallet changes received the required GTIN review.
• Fixed-assortment components and assortment identifiers are documented separately.
• Case-label content, size, placement, and visibility match the named recipient requirement.
• Human-readable digits and scanned barcode data match the approved record.

Dimensions, weights, and tolerances

• Bottle, inner-pack, case, pallet, and loaded-pallet dimensions use defined axes and units.
• Measurement basis states sample, orientation, loaded condition, method, instrument, rounding, operator, and evidence.
• Supplier facts, measured facts, calculations, recipient requirements, and internal recommendations remain distinguishable.
• Unit gross, case gross, case net, packaging tare, pallet tare, calculated pallet gross, and measured pallet gross are defined.
• No liquid-volume value is presented as a measured shipping weight.
• Cases per pallet and consumer units per pallet recalculate correctly from approved inputs.
• Alternating or irregular layer patterns use an explicit layer sum rather than an incorrect simple formula.
• Nominal values, observed ranges, supplier tolerances, recipient limits, and internal review thresholds are separate.
• Every out-of-tolerance result has an owner, decision, and replacement evidence.

Pallet and route readiness

• Pallet type, footprint, tare, access orientation, layer pattern, and diagram describe the actual load.
• Loaded length, width, height, gross weight, overhang, securing materials, and stackability have approved bases.
• Recipient height, weight, footprint, overhang, label, and handling limits have been checked.
• Wood packaging and dunnage review is included only where relevant to the international route.
• Treatment or mark evidence is connected to the responsible pallet or shipment record where required.
• Case and pallet photos match the configuration represented by the sheet.

Approval and handoff

• Supplier, logistics, item-data, compliance, warehouse, and operations approvals are complete where assigned.
• Source specifications, measurement records, calculations, photos, recipient instructions, and exceptions are accessible.
• The exported handoff contains only approved fields and the correct revision.
• Spreadsheet, PDF, portal, and submitted values agree.
• The exact sent package and recipient response are retained.
• First-shipment purchase order, physical case, pallet, and warehouse receipt were compared with the sheet.
• Corrections were made in the controlled source and regenerated rather than patched only in the recipient copy.
• Superseded configurations remain traceable and do not compete with the current default record.
• A second reviewer can reproduce every calculation and trace every critical value to evidence.

A dependable wine case and pallet spec sheet does not force every supplier into one pallet convention. It gives each exact configuration a clear hierarchy, defined measurements, honest calculations, named requirements, evidence, approval, and a reproducible distributor handoff.