Multipack Listings for Drinks Upload Teams

Say a drinks brand sends over a supplier file with 60 SKUs: a craft lager in single cans, 6-can packs and 24-can slabs, alongside several mixed variety packs. Getting multipack listings for drinks upload teams right starts with one decision: which pack sizes become variants and which become separate products on Shopify.

In most cases, a single can and a 24-can slab of the same beer are separate products, not size variants. Here is how that decision works, and what the team needs in the file to build it correctly.

Key takeaways

• Different pack sizes of the same drink are usually separate products in Shopify, not variants, because they have different GTINs, different prices and different shipping weights.
• Pack type (single, 6-pack, 24-pack) can be a Shopify variant option only when the variants share the same label design and differ by quantity alone, with the same GTIN family and no meaningful size or format difference.
• Volume belongs in two fields: millilitres per unit and millilitres per pack, so customers comparing products can read the numbers they expect.
• ABV, tasting notes and food pairing suggestions belong in product metafields, not in the product options or the main description body.
• Upload teams need the brand to confirm whether mixed variety packs are separate products or bundle-style listings before data entry starts.

When a pack becomes its own product

The core rule is that Shopify variants share a product page because they represent the same item in different configurations. A shopper choosing between a large and a small of the same shirt is making one decision: size. The product is the same.

A single can and a 24-can slab of lager are rarely the same decision. They ship differently, have different GTINs from the manufacturer, and often have different label artwork or batch codes. Putting them as variants on one product means sharing one product page image gallery, one description and one product type, which creates problems in search results and in collection filtering.

The exception is when a brand deliberately positions packs as options: for example, a craft soda offered in 330mL and 500mL versions with the same label and no GTIN difference. In that case, volume as a Shopify option works. Shopify products support up to three options per product, so a product could have volume alongside a flavor option.

The practical test: if the packs have different GTINs, different shipping dimensions or different image assets from the supplier, treat them as separate products.

How the supplier file usually arrives

Drinks brands send supplier files in a few common formats. The most useful for upload teams is a spreadsheet with one row per SKU, columns for the product name, format (single, 6-pack, 24-pack), volume in mL, GTIN, ABV, case quantity and RRP.

The less useful format is a price list that groups packs under a product name without individual GTINs, or a file that records volume as a text string ("330mL × 24") rather than split numeric columns.

When the file is set up well, the upload team can map each row directly to a Shopify product. When it is not, the team needs to split text strings, derive GTINs from partial data or request missing fields before data entry can begin. Including a brief that lists exactly which columns the team needs reduces that back-and-forth.

Part of a Shopify product data entry brief for a drinks catalog would specify:

• One row per SKU (not one row per product with pack sizes in separate columns)
• GTIN for each pack size as its own value
• Volume in mL as a numeric field (not "330 mL" as text)
• ABV as a decimal (e.g. 4.9, not "4.9%")
• Tasting notes and food pairings as separate columns if used

Worked example: single, 6-pack and 24-pack from one brand

For example, say a lager brand has three pack formats that need to become three separate Shopify products. Here is how the key fields map.

Field	Single can (330mL)	6-can pack (1980mL)	24-can slab (7920mL)
Title	Brand Lager 330mL Can	Brand Lager 6-Pack (330mL × 6)	Brand Lager Slab 24 × 330mL
GTIN	9312345000001	9312345000018	9312345000025
Volume per unit (mL)	330	330	330
Total volume (mL)	330	1980	7920
Pack count	1	6	24
ABV	4.9	4.9	4.9
Product type	Lager	Lager	Lager
Shipping weight	0.38 kg	2.1 kg	8.4 kg

Notice that "Volume per unit" stays at 330mL across all three products. That field lets a customer compare a price-per-mL across pack sizes if the store displays it. "Total volume" is the pack's total content, which is what matters for shipping weight calculations and for customers buying the slab as a party purchase rather than a weekly shop.

Keeping both fields separate in the supplier file, rather than combining them into a text string like "330mL × 6", makes it possible to filter collections by serve size and by pack quantity independently.

Volume, ABV and tasting note fields in Shopify

Shopify does not have a built-in ABV field or a tasting notes field. These go in product metafields, which the store's theme can display on the product page.

For drinks catalogs, the team typically creates or populates these metafields:

• custom.abv (decimal number): 4.9
• custom.tasting_notes (single-line text): "Crisp, light-bodied, slightly bitter finish"
• custom.food_pairing (single-line text): "Pizza, chips, grilled chicken"
• custom.serve_temperature (single-line text): "2 to 4 degrees C"
• custom.country_of_origin (single-line text): "Australia"

The metafield namespace and key names need to match what the store's theme expects. The brand or the developer needs to provide these before the upload team can populate them. If they are not provided, the team leaves a note in the task and skips those fields.

ABV should not go in the product description body or the product title. It is searchable as a metafield filter and does not clutter the title with regulatory-style text.

Mixed variety packs

Mixed variety packs present a separate problem. A "Summer Sampler" case might contain six different beers: two IPAs, two lagers and two ciders, each from the same brand.

Shopify does not have a native bundle product type. A mixed variety pack is typically listed as a single product with no variants. The contents go in the product description under a "What's in the box" or "Pack contents" heading, with the quantity and name of each beer.

The tricky part is inventory. If the brand tracks stock by individual SKU, a mixed pack reduces stock across six separate products when it sells. Apps handle this better than Shopify's native inventory, and that is a question for the brand's developer, not the upload team. What the team needs to know is whether the brand wants the pack listed as a product with its own SKU and GTIN (usually yes), and whether it has its own image (often yes for a gift-style box).

For our food and beverage product upload work, the brief typically asks the brand to confirm: does the variety pack have its own GTIN, its own image, and is it tracked as its own inventory item or as a deduction from components?

Multipack drinks listings: what to tell your upload team

Upload teams handle multipack drinks data more reliably when the brief is specific. Beyond the standard fields that apply to all Shopify jobs (covered in what to send your upload team before a job), drinks catalogs need:

1. Pack structure decision: separate products per pack size (most common), or variants on one product (only if same GTIN family and no meaningful attribute difference).
2. Volume format: numeric mL per unit and total mL, not text strings.
3. GTIN per pack: one GTIN for each pack format (single, 6-pack, slab).
4. ABV format: decimal number only, no % symbol.
5. Metafield keys: the namespace and key for ABV, tasting notes and any other custom fields the theme expects.
6. Variety packs: whether they have their own GTIN and image, and whether inventory is tracked at the pack level or deducted from components.
7. Product type taxonomy: how the brand categorizes its products (Lager, IPA, Cider, Spirits) so collection conditions and product filters work correctly.

A Shopify product data entry checklist covers the core fields that apply across all product types. For drinks, adding the volume, ABV and pack structure fields to that checklist before the job starts prevents the most common delays.

Frequently asked questions