Wine merchants, spirits importers and food and beverage wholesalers share an operational reality that catalog automation tools rarely take seriously. Their price list changes faster than the products it describes, carries pricing rules that no generic SKU schema can hold, and ships into markets where the same wine sells under different tax regimes, in different pack sizes and against different commercial agreements.
This guide explains how beverage price list automation works in practice: data model, template rules, market versions and scheduled output.
What Is Beverage Price List Automation?
Beverage price list automation is the practice of generating a wholesale beverage price list from structured data into a designed InDesign price list template, so each market, channel or category version is produced automatically rather than rebuilt by hand.
The result: one source of data, one template, multiple PDF and InDesign outputs.
The three building blocks
A reliable automation workflow needs three things:
- A structured product data model: fields for vintage, pack composition, market availability, price tier
- A conditional InDesign template: one design with rules that decide what appears in each version
- Clear market and category rules: applied in the data layer, not inside the layout
Beverage Product Data Model: What Fields Are Needed?
For a beverage catalogue, the data source should include:
- Product code
- Producer, region, appellation
- Vintage (as a separate field, not as text in the name)
- Bottling year (separate from vintage, printed on the price list and used to sort older bottlings, which usually carry a higher price)
- Category
- Bottle size
- Pack composition (single bottle, case, wooden case, magnum, keg for beer)
- Availability by market
- Trade and consumer prices (typically two price columns: one for resellers, one for end customers)
- Per-product price adjustments (where a specific reference carries a market-specific markup)
- Tier and allocation notes
- Legal or regulatory attributes
Vintage and pack composition deserve dedicated fields: the template uses them to group products, display variants and remove unavailable items automatically. Same principle behind every catalog automation project.
Pricing Rules And Product-Specific Adjustments In Beverage Price List Automation
In most beverage operations, prices arrive in Pagination already calculated by the PIM or ERP, usually as two parallel columns: a trade price for resellers and a consumer price for end customers. The template reads the right column for each variant and renders it.
Some references need exceptions. A premium Champagne, for example, may carry a market-specific surcharge in the Austrian and export price lists but not in the German one, because the source system does not handle that one-off rule. Pagination applies that uplift at generation time, on the specific SKU, in the specific variant, without changing the source data.
When this kind of commercial logic sits inside the InDesign file, every adjustment becomes a layout edit. When it lives in the rules layer, the same template handles every variant correctly.
How Pack-Format Management Improves Catalog Accuracy
Beverage products often exist in multiple formats: single bottle, six-bottle case, wooden case, magnum. When pack composition is a dedicated data field, the template can:
- Group related variants under one block
- Decide whether to show unit price or pack price
- Apply pack-specific labels
- Keep presentation consistent across editions
If pack info is stored only as text inside the product description, automation becomes fragile.
Legal Text and Terms and Conditions in Automated Price Lists
Terms & Conditions, allergen statements and regulatory notes change on a different schedule from product data. Treat them as a separate content block, inserted into the template at generation time.
The legal team owns the text; the marketing team owns the layout; nobody copy-pastes from Word into page 184 of an InDesign file.
Scheduled Generation For Beverage Price List: From Event To Process
Mature workflows do not treat document production as a manual event. They run on a schedule: typically overnight. The source data is exported, Pagination generates the InDesign and PDF files, the team finds the latest versions ready in the morning.
Teams integrating with PIM, ERP or e-commerce can drive generation through custom integrations.
What A Reliable Beverage Price List Workflow Looks Like
| Concern |
How Pagination handles it |
| Source data |
ERP, PIM or curated Excel master, exported on schedule |
| Country variants |
Conditional sections in a single InDesign template, driven by per market fields |
| Pricing model |
Two price columns from the source (e.g. trade and consumer), rendered selectively per variant |
| Per-product adjustments |
Market-specific surcharges or one-off uplifts applied to specific SKUs at generation time |
| Pack composition |
First class data field, controlled vocabulary; template chooses unit vs pack price |
| Bottling year |
Separate data field; used for display on the price list and for sorting (older bottlings typically appear first because they carry a higher price) |
| Vintage rotation |
Current vintage flag in the source; phasing-out vintages drop off the next release |
| Tier pricing |
Alphanumeric input accepted in price columns (“≥”, “on allocation”, “on request”) |
| Allocation lists |
Allocation flag in the data, conditional inclusion in named customer variants |
| Multi language |
Translated fields in the source, language flag at generation time |
| Legal section |
Externalised content block, owned by the legal or commercial team |
| Generation cadence |
Scheduled overnight job, or on demand via integration |
| Output formats |
Print ready PDF, packaged InDesign, editable Excel with formulas |
| Archive |
Every generated variant stored, indexed by date, market and variant |
The Kate & Kon case study shows this architecture in production since 2018.
FAQ
Can the price list apply a markup to specific references in some markets only?
Yes. When a single SKU needs a market-specific adjustment that the PIM or ERP does not handle (for example a premium Champagne that carries a surcharge in the Austrian and export price lists but not in the German one), Pagination applies the uplift at generation time on the specific reference in the specific variant. The source data stays untouched.
Can the price list show both a trade price and a consumer price for the same wine?
Yes. Two price columns (typically trade and consumer, or B2B and B2C) live as separate fields in the source data and are rendered side by side, or selectively, depending on the variant. The same SKU can also carry per-market columns or per-channel pricing (HoReCa, retail, export) when the commercial agreement requires it.
How do you handle vintage rotation when the previous vintage is still on stock?
A main vintage flag in the source controls visibility. The template shows only the main vintage in the next price list run, while the phasing-out vintage drops off the next release automatically. The SKU stays in the master because stock is still moving.
How are pack formats like single bottle, six pack and wooden case managed in price list automation?
Pack composition is a dedicated data field with a controlled vocabulary (single, six pack, wooden case, magnum, jeroboam). The template reads it to group variants of the same producer code, choose between unit and pack pricing and apply pack specific labels.
How is the bottling year handled in the price list, and can wines be sorted by year?
Bottling year is a dedicated data field, distinct from vintage, and it gets printed alongside the producer and the wine name. Sorting by bottling year is one of the standard rules: older bottlings usually appear first within a producer or a category, because in many segments the older the bottling, the higher the price. The rule lives in the data layer, applied at generation time, so the order is consistent across every release.
Review Your Beverage Price List Automation Potential
If your beverage price list still depends on manual InDesign updates at every cycle, the first useful step is a review of your current PDF and your underlying data. Pagination can identify which sections can be automated, which rules need to be defined and how the first automated version would be generated for your specific market mix.
