Beer SKUs and master data: pack, size and brand hierarchies

What a SKU means in beer

A stock keeping unit (SKU) is the smallest item a company plans, stocks and sells separately. In beer it is usually a combination of liquid, pack type and pack size. A strong lager in a 650 ml bottle and the same lager in a 500 ml can are different SKUs, even though the beer inside is identical.

In many drinks companies the SKU also carries the selling unit, typically a case. A case of twelve 650 ml bottles and a case of twenty-four 330 ml cans are different selling units with different volumes, prices and pallet patterns.

A typical hierarchy, top to bottom

Most beer companies use some version of this structure:

• Category: beer, as opposed to spirits or wine in a multi-category company.
• Segment: for example mild lager, strong lager, wheat beer or premium import.
• Brand family: the master brand.
• Brand variant: the specific liquid, such as the strong version or the wheat version of the brand.
• Pack type: returnable glass bottle, non-returnable bottle, can or keg.
• Pack size: 330 ml, 500 ml, 650 ml or a keg volume.
• Selling unit: the case or keg configuration.

Our beer brand portfolio guide explains why brands are grouped the way they are.

Why India multiplies SKUs

State excise is the big multiplier. In many states a beer must carry a state-specific label, an approved price and sometimes a state marking or security sticker. So the same liquid in the same can may become a separate SKU for each state, because stock labelled for one state cannot legally be sold in another.

Returnable glass adds another twist. Returnable bottles circulate many times, so companies track bottle stock and crates as assets, often with their own codes. Promotional packs, festival multipacks and export versions add more.

The result is that a company with a modest portfolio of liquids can manage hundreds of active SKUs. Master data has to handle that without hiding the simple truth that many SKUs share one liquid.

Attributes that matter for reporting

Each SKU record should carry attributes that let teams aggregate correctly:

• Volume per selling unit in litres, so sales can roll up to hectolitres.
• Alcohol content, which feeds excise calculations and some reporting.
• Liquid code, linking every pack back to the beer recipe and the brewery's production records.
• State or market of sale, along with its excise label reference.
• Barcode such as a GTIN where used, plus status flags for active, phased out or seasonal.

Missing volume and missing liquid codes are common errors in drinks data. Without them, total volume and liquid-level forecasting both break.

Common master data problems

A few problems come up again and again in beer master data:

• Duplicate SKUs created for a short promotion and never retired.
• Inconsistent naming, so one system says "Strong 650" and another says "STR BTL 0.65".
• Wrong volume conversions, often a case of 24 x 330 ml entered as 24 x 500 ml.
• Changing hierarchies, when a brand moves segment and history is not restated.
• Planning and sales disagreeing, because one plans at liquid level and the other sells at state SKU level.

These issues show up later as forecast errors and arguments over whose numbers are right, a theme covered in shipments vs depletions.

Designing for planning and sales

Production plans liquids. The brewery cares how many hectolitres of each beer to brew. Packaging plans pack types and sizes. Sales and finance work at state SKU level. Good master data links all three so a planner can move from a state SKU forecast down to a liquid demand and back up again.

A sensible test: can you take last month's sales by SKU, convert to hectolitres and get a number that matches the brewery's packaged volume for the same period, allowing for stock changes? If not, the hierarchy has a hole.

Getting teams to agree

The technical design is the easier part. The hard part is agreement between marketing, supply, finance and IT on definitions, plus a single owner who approves new SKUs. Teams that understand how beer is made, packed and taxed find these conversations much shorter, because they can see why a new state label is a new SKU while a new carton print run may not be.

Common questions

Why does the same beer have many SKUs?

Different pack types and sizes create separate SKUs. In India, state excise labelling often makes the same pack a separate SKU for each state where it is sold.

What is a liquid code?

It is an identifier for the beer itself, separate from the pack. It links every SKU back to the recipe and production records, so liquid-level demand can be planned.

How do I convert beer sales to hectolitres?

Multiply the number of units by the litres per unit and divide by 100. Accurate volume data in each SKU record makes this reliable.