Skip to content
CMS Max Documentation

Liquor Max

A plugin to manage and display beverage information for your products.

Overview

Liquor Max is a product management add-on designed specifically for liquor retailers. It extends your product catalog with fields and attributes tailored to wine, spirits, cider, and sake — giving your customers the detailed product information they expect when shopping for beverages.

Getting Started

  1. Go to Settings > Plugins in the admin panel
  2. Find Liquor Max and click to open the settings page
  3. Click Save and Install

Liquor Max plugin settings page

Bottle Size Shipping Dimensions

Products default to inheriting bottle-size dimensions when they have no custom measurements. This choice can remain on before beverage data or a bottle size exists. Assigning a bottle size later, including through Central or POS enrichment, makes its shipping values apply automatically when a complete profile is available. Products explicitly set to custom keep that choice. If a selected size has incomplete or missing shipping values, inheritance remains checked and saved product measurements serve as fallback; partial bottle-size values are not applied individually.

In Settings > Plugins > Liquor Max > Shipping Dimensions, each row shows the Central bottle-size name. Every Central bottle size displays its current shipping weight (pounds) and dimensions (inches). Every row starts with Sync to Central checked. Uncheck it for an individual size to enter and save a store-specific override. Check it again to return that size to current Central defaults. Saving other settings does not enable overrides.

On a product's Dimensions tab, Use bottle size default settings. uses the assigned bottle size's store override, falling back to Central defaults. Inherited measurements are displayed in greyed-out, read-only fields, including after their saved product values have been cleared. The Dimensions tab labels them Inherited from bottle size. If no complete profile is available, it explains this and allows custom measurements. Uncheck the box to enter custom dimensions. Changes to the matrix apply to inheriting products without editing each product, including products with Central sync disabled. Variation-specific dimensions still take precedence when shipping a variation.

Individual product exclusion turns inheritance off and saves the current bottle-size measurements as custom values before removing liquor data. POS category exclusions and moves schedule the same conversion in background batches on the nexus queue; each batch rechecks current exclusions. Restoring an archived POS product also schedules a check. Including the product again does not automatically enable inheritance. Opening an excluded product's editor also repairs any retained inheritance setting; its Dimensions fields stay editable while the Liquor Max tab and inheritance checkbox are hidden.

New products created through the editor have inheritance checked. After deployment, an administrator can run a separate classification command. Existing products without a saved inheritance choice are set to inherit when all four saved measurements match a complete Central bottle-size profile, or are entirely empty (null/zero), even before beverage data is available. Explicit inherited or custom choices are preserved. Products already excluded from Liquor Max are classified as custom. Other existing products with partial or differing measurements, or saved measurements without a matching size, keep inheritance unchecked for review. Inheriting products use current bottle-size values. Their saved measurements can be cleared separately after deployment; custom product measurements stay on the product. New products created by integrations, including POS imports, inherit when measurements are absent or entirely empty/zero. Explicit measurements use custom dimensions unless inheritance is explicitly requested. Central sync preserves the inherited or custom choice and does not replace custom product dimensions. While Liquor Max is active, products with an effective inherited bottle-size profile show read-only dimensions in the bulk grid; non-liquor, excluded and unmapped products remain editable. Dimension changes through Apply to selection are blocked if any selected product inherits. To opt out explicitly, select the products, choose Bulk Edit Selected → Use bottle size default settings. → Off, and apply. Each inheriting product keeps its current effective measurements as custom values, including tenant bottle-size overrides. Already-custom products keep their measurements. The affected grid fields become editable immediately; for selections processed in the background, wait for the completion notification and refresh the table. You can also turn inheritance off on an individual product edit page. To enable inheritance instead, choose On; every selected product must be included in Liquor Max and have a complete bottle-size profile. This makes its dimensions read-only and retains saved custom measurements as fallback data. Other bulk fields remain editable. Queued dimension changes recheck effective inheritance and current plugin activation before applying each chunk. Large On selections validate profile eligibility in the background. Mapped CSV dimension edits select custom dimensions and keep the other current measurements, including an explicitly cleared field. Unmapped CSV headers and later variant rows do not turn a new parent product into a custom one. POS mappings with measurements select custom dimensions; an entirely empty/zero measurement update preserves inheritance. Bulk-added variants on inheriting products continue using the parent bottle-size profile.

An administrator can deliberately reassign existing inheritance choices with beverage:classify-dimension-inheritance --reclassify (preview) and --reclassify --apply (save). Empty measurements become inherited, including products awaiting enrichment. Measurements matching either Central or the current store bottle-size profile also become inherited; differing or partial custom measurements remain saved as custom. Products already inheriting keep their existing inheritance and effective measurements. This one-time operation resets previous opt-outs with empty or matching measurements. Counts show only inheritance flags that would change; saving skips flags already at their target value. Omit --tenant to process all Liquor Max tenants, or repeat --tenant=ID to restrict the run. Normal classification and synchronization preserve subsequent user choices. POS exclusions remain in effect for products being classified.

When no size mapping is available, any remaining saved product measurements are used. Missing measurements use the usual store shipping defaults. The cleanup command reports products that would rely on those defaults separately, so an administrator can review them before applying it.

Rebates on Product Pages

With Liquor Max active and Enable Rebates turned on, a green bubble with a ticket icon appears near the price for each active offer linked to a product, in both standard product-page layouts. The bubble shows the offer's amount (for example Rebate: Save $3), or Rebate available when the offer has no amount. Clicking it opens the same rebate details modal used on the rebates page, including the offer, dates, description, code, image when available, and eligible products. Close it using the close button, Escape, or the backdrop.

Future and expired offers are hidden automatically. An empty start or end date leaves that side of the offer period unrestricted. Rebates must be claimed separately under their terms: they do not reduce the product price or checkout total, and the rebate details modal tells shoppers this.

AI Search Settings

The Edit AI Settings button on the Central AI Enrichment Audits and Image Audits pages, also available in the beverage-products actions menu, selects the models used for beverage data and image searches. Both searches look across the web. Data searches seek the exact product; image searches can also return possible matches and proposed product corrections for Central review. Product details and image candidates still undergo source verification before use. Product corrections require explicit selection and approval.

Supported Beverage Categories

Liquor Max supports four beverage types, each with fields matched to the information relevant to that category:

  • Wine — includes vintage year, professional ratings, varietal, country, region, and subregion
  • Spirits — covers whiskey, vodka, rum, gin, tequila, and other distilled beverages
  • Cider — supports hard ciders and fruit-based beverages
  • Sake — for Japanese rice wine products

Liquor Max keeps a top-level category for each beverage type. While the plugin is installed, you can edit a type category's content and visibility, but its URL and parent category are fixed, and Archive is unavailable. Generated root beverage categories remain protected after uninstalling Liquor Max.

Archiving Beverage Categories

Generated beverage category slugs and parent categories cannot be changed; rename the display title instead. A first-level beverage category cannot be archived while any active or archived product uses it or its children; reassign those products first. The blocked archive dialog links to the filtered Products table with both active and archived products visible. When archiving a category with children, choose Archive child categories; moving beverage children during archive is not supported. A beverage subcategory can be archived while products use it: those products keep their parent beverage category and lose only the subcategory value. Categories with the same name under a different beverage type are unaffected.

Product Fields

Fields Available for All Beverage Types

Every beverage product can include:

  • Bottle size — required for all products
  • Brand — the producer or label name
  • Dietary and sustainability attributes — mark products as organic, vegan-friendly, or gluten-free
  • Ownership diversity badges — highlight Black-Owned/Operated or LGBTQ+ Owned/Operated businesses
  • Kosher certification — indicate certified Kosher products
  • Store Pick designation — flag products as a curated staff recommendation

Additional Fields for Wine

Wine products support the most detailed metadata, making them well-suited for premium and collectible inventory:

  • Vintage year — select a year from 1900 through next year, or NV for non-vintage. If an active POS connection maps Vintage, an empty Wine vintage is prefilled from the stored POS value before saving. A note beneath Vintage identifies the POS source while the prefilled value remains selected. A selected year or NV is preserved on that save. When Wine data is first added or another beverage type changes to Wine, a vintage left blank or cleared after prefill is filled from a valid mapped POS value. Clearing an existing Wine vintage without changing its type survives that save; the blank remains until another POS field changes, the Vintage mapping changes, or a forced full apply runs. An eligible apply fills the missing vintage, even under Don’t change. Later POS updates follow the connector’s Vintage update rule.
  • Professional rating — enter scores on a 70–100 scale
  • Rating source — record where the rating came from, such as Wine Spectator
  • Varietal, country, region, and subregion — full geographic and grape variety classification

Adding a Beverage Product

When creating or editing a product:

  1. Select the beverage category (required for all beverage products)
  2. Choose the bottle size (required for all beverage products)
  3. Fill in any optional fields relevant to the product type. Record Alcohol by Volume for wines you list on Vivino, because Vivino asks for alcohol strength
  4. For wine, use the rating fields to add professional scores and their sources

Country, Region, and Subregion dropdowns offer an initial list before you type. Choose a country to enable its regions, then a region to enable its subregions. Changing a parent clears the dependent selections. Type to search beyond the initial list.

All other standard product settings — pricing, images, inventory — are managed through the main product form alongside these beverage-specific fields.

Product edit form showing beverage-specific fields

Reviewing Bulk AI Category Guesses

Central AI Enrichment Audits retains category guesses from new bulk lookups. Pending guesses display Category review instead of a success badge. Use Category guess awaiting review to find them, then open View Details. The guess is labelled AI guess, please double check. Use this category explicitly saves it and starts the normal tenant sync; closing the window changes nothing. A guess cannot overwrite an existing category or be used twice. The action checks the product and category again before saving. Guesses that no longer apply remain visible as history with No longer applicable, without a review badge or use button. Accepting one also removes the product’s other guesses from pending review. Older audits without a saved guess show none.

Fetching Beverage Data with AI

When the OpenAI plugin is active and a product has a GTIN, Fetch AI Data in the product's Liquor Max section looks the product up for you. Clicking it starts a new web search for the GTIN right away, using the beverage enrichment model selected in Central, then checks the source pages before using anything. The search can take a few minutes. The popup stays open and shows how long it has been searching and its current step (waiting to start, searching the web, fetching source pages, validating fields, or preparing results); a short step can pass between updates. When a verified result is ready, the fields fill in and the popup closes, unless it shows a category guess (below). If the search has not started after 5 minutes because other AI lookups are using the service, the popup says AI lookups are busy, and clicking Fetch AI Data again tries again. If a search stops before it finishes, the popup says so and nothing is changed; clicking Fetch AI Data again starts a new search. If you close the popup, the search keeps going: reopening Fetch AI Data shows its progress, or uses its result for up to 5 minutes after it finishes.

  • A listing for a pack of the same drink can supply verified shared details when its barcode matches. Pack listings do not supply the product title or bottle size. Mixed or variety packs identified in the product name or product metadata cannot establish a match. Pack promotions elsewhere on the page can still allow verified shared details, while withholding the title and bottle size.
  • When a source lists several bottle sizes without identifying which one belongs to the barcode, its shared details can still be used, but its title and bottle size are withheld.
  • Beverage fields the source pages verify replace the current values in the form. A bottle size already set on the product is kept. Save the product to keep the changes.
  • Country names are checked independently of the beverage catalog. A state such as California cannot be used as a country, even if an old catalog entry lists it there. Verified valid origins can create missing location records; unsupported countries and their dependent locations stay unapplied for review.
  • When verified data changes a category, country or region without supplying its dependent value, the old subcategory, region or subregion is cleared. Changing beverage type clears incompatible categories, subcategories and brands. Suggestions already matching the current value are hidden.
  • A category is filled in only when a source page states one of the approved categories. Otherwise, if the category is still empty, the popup can stay open on the AI's closest approved category for the beverage type: "AI guess: …, please double check". Click Use this category to fill it in (it can be clicked about a second after the guess appears, once the page has finished loading), or Close to leave it empty. Check the guess before you save. If the category is no longer approved when you click, the guess is not used and the category stays empty.
  • If an exact-barcode product page verifies an approved category, its beverage type can also be filled when the search omits it. For example, a verified Mezcal category belongs to Spirits. This requires an unambiguous approved category; an AI category guess cannot supply the beverage type.
  • If the search finds the product but no source page verifies it, both store and Central editors keep an unverified proposal open with the source checks. Nothing is selected or changed automatically. Check the sources, select the classification, brand or origin suggestions you want, then click Apply selected suggestions. Only selected fields replace their current form values; save the product separately to keep them. Suggestions remain unverified. Bottle size and product name are not offered. Close matches show the AI wording alongside an existing value; each field offers one choice, starting at Keep current. To add a new category or subcategory, select its Create new option and tick Confirm creation, which appears only after choosing a new value. Changing a choice clears confirmation. Ticking permission alone creates nothing, and high confidence never grants permission. Catalog creation happens immediately on Apply; product changes still need Save. Store-created values are available to that store and sent to Central for global approval. An approved or store-created subcategory name cannot be created again under another category. Select matching parent fields with dependent fields (for example, country with region); conflicting existing fields must be reviewed in the form first. Close discards the selection.
  • If nothing matches the GTIN, or the search runs out of time, an error explains why and nothing is changed.

For bulk enrichment, unverified proposals are available in Central under AI Enrichment Audits → View Details. The same classification, brand and origin suggestions, close matches, parent checks and creation permission apply there as in the product editors. Product name and bottle size cannot be accepted from an unverified proposal. Apply selected suggestions saves the selected values immediately and records them in the audit; no separate product Save is needed. Unselected values are kept and the suggestions remain unverified. Verified bulk updates are kept while any unmatched catalog values are listed in a separate review entry; even a high-confidence review needs explicit permission to create taxonomy.

On both store and Central product edit pages, failed searches stay open with the error and available source checks. The error notification fades normally while the popup keeps the details available. Use the source links to review the evidence, Try Again to run a fresh search, or Close to dismiss it. Retrying preserves your unsaved form values. A page containing the barcode can still fail verification if its product name, bottle size, packaging or beverage type cannot be established.

Beverage Details on Product Pages

Product pages show a details box, such as Wine Details, listing the beverage fields that have a value: country, region, subregion, category, varietal, brand, vintage, rating, bottle size and alcohol. Country through vintage link to the matching product list. The rating appears under the vintage with its source, for example 90 pts - Wine Spectator, or as just the points when no source is set. Fields without a value are left out.

Storefront Location Filters

When a product list shows beverage filters, shoppers can choose a country, region, or subregion. Region choices include their country, and subregion choices include both region and country. Each choice filters products to that exact location, even when another location uses the same name.

Vivino Feed

With store inventory enabled, the feed uses the configured Delivery and shipping store for bottle counts. Stock at other locations is excluded.

Vivino can list your wines and link shoppers back to your store. To do that it needs an XML feed of what you currently have in stock, which Liquor Max can publish for you.

Go to Plugins → Liquor Max and open Vivino Feed. The How Vivino product names are built table pairs each part of the feed name with the field to edit on the wine, in the order Vivino receives it. You can consult it before enabling the feed.

To publish the feed:

  1. Turn on Enable Vivino Feed. The feed is published at your store's own address, shown as the Feed URL — for example https://yourstore.com/vivinofeed.xml. While the setting is off, that address returns "not found", so nothing is exposed until you are ready.
  2. Under Bottle Sizes Sent to Vivino, check each bottle size you want on Vivino. These are the sizes Vivino accepts (375 ml, 500 ml, 750 ml, 1 L and 1.5 L), and all of them start checked. Keep at least one checked while the feed is on.
  3. Optionally set a Price Markup (%). The markup is added to each wine's current single-bottle price, including an active sale or a quantity tier that begins at one bottle. Leave it at 0 for the unmarked price.
  4. Save your changes, then give the Feed URL to your Vivino representative.

Once the feed is saved as enabled, the section shows Current Eligible Products: the number of wines the feed sends right now.

Choosing which wines go to Vivino

While the feed is enabled, each product's Marketplaces tab shows a Vivino checkbox. It is checked by default, so every wine that meets the rules below is sent. Uncheck it and save to leave that wine out of the feed. A duplicated product keeps the original's choice.

The checkbox is greyed out and unchecked, with the reason beside it, when a product can never be in the feed:

  • Unsupported bottle size — the wine's bottle size is not one Vivino accepts
  • No bottle size set — choose a Bottle Size on the product's Liquor Max tab
  • Only wines can be listed on Vivino — the product is not a wine, or has no liquor data
  • 375 ml bottles are turned off in the Liquor Max Vivino Feed settings (or another size) — your store does not send this size; check it under Bottle Sizes Sent to Vivino

Fix the product (for example, choose a supported bottle size) or turn its size back on, and the checkbox becomes available again with its saved choice.

Turning a bottle size off and on

Unchecking a size under Bottle Sizes Sent to Vivino and saving leaves every wine in that size out of the feed. Each wine keeps its own Vivino choice while its size is off; the checkbox is just greyed out.

When you check a size that is off, a popup asks whether to update the products, just like turning on a fulfillment method in Store Settings. It shows how many wines are in that size and how many have Vivino checked now:

  • Yes, Apply to All Products checks Vivino on every existing wine in that size.
  • No, Skip unchecks Vivino on every existing wine in that size. Check Vivino on a wine's Marketplaces tab to send it.

Either choice replaces each wine's own Vivino choice, archived wines included, and updates the products straight away. Save your changes to start sending the size. Wines added later are checked by default. The popup does not appear when you have no wines in that size, or when you uncheck and recheck a size before saving.

The checkbox is your choice to include the wine. The wine is sent only while it also meets the rules below, such as being In Stock and priced. Use the count or the filter to see what the feed sends.

To see the wines the feed sends, go to Ecommerce > Products and choose Marketplace > Vivino in the filters. The list matches the Current Eligible Products count. When a Google Merchant Center account is linked, the same filter's Google Shopping option lists the products CMS Max sends to Google.

What gets included

Only wines that are ready to sell appear in the feed:

  • The product is a wine with a positive price and inventory count
  • Vivino is checked on its Marketplaces tab (the default)
  • The product is publicly visible — drafts, password-protected and members-only wines stay out of the feed
  • It has a positive shopper price and does not use an alternative-buy action
  • It is a simple product without active options, variations, or dimension-based pricing
  • Its availability is set to In Stock; pre-orders and backorders stay out even when their recorded stock count is positive because Vivino cannot carry those statuses
  • Its bottle size is one Vivino accepts (375ml, 500ml, 750ml, 1L, or 1.5L) and is checked under Bottle Sizes Sent to Vivino
  • It is bottled wine in a supported presentation; products recorded as cans, boxes, kegs, pouches, boxed wine, special editions, mixed cases, multi-bottle cases or packs, or gift packaging stay out
  • It is a wine product rather than a wine accessory

Here, a simple product means its price and stock are recorded directly on the wine product, with no active option or variation choices underneath it and no dimension-based pricing. Liquor Max wines are expected to use this shape. Vivino provides one price and one inventory count per feed entry, so products with active child choices are left out rather than combining them in a way that could advertise the wrong price or stock. Disabled old choices do not prevent the otherwise-simple wine from appearing.

The selected Bottle Size is enough for this check, including older products whose separate numeric volume was never stored. A non-bottle size such as a keg or pack is still excluded even if it has the same volume as an accepted bottle. Wines in other bottle sizes (such as 187ml splits or large formats above 1.5L) are left out rather than being sent and rejected. Each entry carries the available producer, wine name, most-specific recorded appellation, vintage, colour, varietal, alcohol strength, country and image, plus its bottle size, current quantity-one price with any configured Vivino markup, stock count and a link back to the product page. Wines without a vintage are sent as NV (non-vintage).

Alcohol strength comes from the product's Alcohol by Volume field. A wine without it is still sent, with no alcohol details. Vivino's feed guidelines ask for alcohol strength, and Vivino can skip a wine that does not have it, so record Alcohol by Volume on the wines you want listed. Enter 0 for a non-alcoholic wine so it is marked as non-alcoholic.

The bottle size and unsupported punctuation are removed from the composed product name because Vivino reads only its defined name parts — so products titled "Grand Reserve 750ml" or "Grand Reserve Magnum" are sent as "Grand Reserve" with the size in its separate field. Red wines do not have a red colour appended to the composed name, which is Vivino's convention. When a real label already contains its colour, such as "Apothic Red", "Conundrum White", or "Ménage à Trois Rosé", the full label is kept and the colour is not appended a second time.

Each entry represents one bottle. Its current quantity-one price is sent with the markup applied on top. A tier beginning at one bottle changes that price; tiers beginning above one bottle are not advertised. Tracked products send the available bottle count from the simple product in Global inventory mode, or from the configured Delivery and shipping store in Store inventory mode, while a wine that does not track inventory is sent at the highest count Vivino accepts. Products with active options, variations, dimension-based pricing, or alternative-buy actions are left out rather than advertising a price or stock value that does not represent a fixed single-bottle offer.

The feed is generated fresh each time Vivino requests it, so stock levels and prices are always current — there is nothing to re-upload after changing a product.

Restrict beverages by state

You can prevent specific beverage types from being shipped to individual US states.

  1. Go to eCommerce > Store Settings > Shipping
  2. In the Shipping Zones table, click Edit on a zone (or Add Shipping Zone), then in the Countries section make sure United States is selected
  3. In the US States section, select the states you want to restrict
  4. For a selected state, click the settings link that appears next to its name (it shows the current zip/beverage summary) to open its settings, then switch to the Beverage Restrictions tab
  5. Uncheck any beverage types that should not ship to that state
  6. Save the zone

All beverage types are allowed by default. Excluded beverages are blocked at checkout for addresses in that state, and the shopper is asked to remove them from the cart. A state ban always wins and applies store-wide: if the beverage type is blocked for that state on any of your shipping zones, it is blocked for every product shipping to that state — even a product limited to a different zone that would otherwise allow it.

For safety, a product marked as liquor but with no beverage category set is blocked from any state that has restrictions configured (its type can't be verified). Set the product's beverage category to have it evaluated against the specific per-type rules instead.

Comparing POS Records for Central Duplicates

In the central admin, open Liquor Max > Products > Duplicate Products. The POS Records row shows imported records linked to matching products on Liquor Max sites. Each record identifies the site and product, and shows the mapped fields with their source names and imported values.

Expand Show all fields to compare the remaining source fields before choosing which duplicate to keep. Records for deleted products or archived POS items are excluded. No linked POS records means no active imported record is linked to a matching site product.