Catalogue mode, and deciding what a product page shows
The vendor's shop feature list contains two controls that, taken together, give a winery unusual latitude over how wine is presented. The first is catalogue mode, which the description says turns the buying feature off so the theme works as a catalogue. The second is a show/hide list covering product title, price, add to cart, category, description, product meta, tabs, upsells, cross sells and related products.
A cellar door and a wholesale operation rarely want the same page. Catalogue mode settles the wholesale case in one switch: bottles stay listed and describable, but nothing is purchasable. The per-element list works at a finer grain, and without switching selling off. You could leave checkout running for wines you release publicly while hiding the price and add-to-cart button on an allocation-only bottle so the page reads as a profile rather than an offer.
The important caveat is that the vendor presents these as theme settings, not as documentation of every page template. How the two interact on a specific product template — whether hiding add-to-cart on one product is a global switch or can be set per product — is not spelled out in the supplied description, so it belongs on your staging list.
Two page builders, one of them newer than the feature list
Villenoir's documented editing surface is Visual Composer, now sold as WPBakery Page Builder. The feature list names it, and the marketplace compatibility field lists WPBakery Page Builder alongside Elementor and Elementor Pro.
Elementor is a recent arrival. The vendor's changelog records "Massive Update: Elementor support" in version 6.0.1, dated 24 May 2026. Read that line carefully before you plan around it: it announces support for the second builder, and it does not state that every demo, shortcode module or product-grid element was rebuilt for Elementor. The description still describes product elements in Visual Composer terms.
If your team already works in Elementor, this matters more than any styling option. Elementor support arriving in a maintenance release, on a theme with a long WPBakery history, suggests a choice between two editing paths rather than a migration. Confirm which one the demo content you intend to import actually uses before you commit.
Product grids you can target by SKU, category or price
The vendor describes a set of Visual Composer product elements — a products filter with category filtering and masonry or carousel layout, featured, on-sale, best-selling, top-rated and recent products, product categories, and a products element that shows items by SKU or ID.
The SKU and ID route is the one to note for a winery. A mixed catalogue can have flagship bottles, quiet library releases and gift sets that deserve their own block on the homepage without forcing them into a shared category. Naming them by SKU or ID gives you that block directly.
Around these sit 15 WooCommerce widgets, including price filter, layered navigation, recently viewed products, top rated products, recent reviews, best sellers and a login widget. Some of that is standard WooCommerce furniture restyled, but together it means the shop and the editorial pages share one toolset rather than needing extra plugins for filtering and product promotion.
Where the wine-club offer would live
The vendor states support for integration with a premium Wine Club Membership plugin, describing it as a route to special offers, wines that other visitors cannot buy, and access to exclusive wine posts.
Support is the operative word. The description does not say the plugin ships with the theme, so treat it as a separate purchase and a compatibility claim rather than something included. The value, if you take that route, is conceptual as much as technical: membership tiers that gate both bottles and content let a winery treat its mailing list as a publishing audience, not just a discount list.
Whether that plugin's gating rules apply to product visibility settings — the same settings discussed above — is not documented in the supplied material. It is worth checking before you design a member-only allocation page around it.
Shop styles, and a count that does not match
The description advertises "4 different shop styles." The changelog for version 5.2 records two more added, "6 in total." Both statements sit in vendor material; the changelog is the later record, but neither is a specification of what is in the current build. The safer reading is that several shop layouts exist and that the exact count should come from the theme options you see after installing.
A separate change added a dark style, switched on from Theme Options >> General >> Theme style. It is a site-wide style choice rather than a per-page one.
Page-level control is described as a set of page options: full width or left or right sidebar, the ability to enable or disable the page header, an aligned page description, and a page slideshow set through Slider Revolution. A 2023 release added tablet and mobile design-editor control, which means the responsive layout can differ from the desktop arrangement rather than merely shrinking it.
One practical note carried in the vendor's own text: images shown in the preview are not included in the download folder. The marketplace files list records PHP Files only, so plan on supplying your own product and vineyard photography.
Declared versions, and what the flags mean
As observed on the marketplace on 4 November 2026, the compatibility fields declare WordPress 6.8.x through 7.0.x and WooCommerce 9.x.x and 10.x.x, plus WPML, The Events Calendar and Events Calendar Pro, and Contact Form 7. These are declarations recorded at a point in time, not the results of running the theme against your PHP version, your plugins or your host.
Gutenberg Optimized is recorded as No. That describes whether block-editor layouts receive styling priority; it does not mean the block editor is unusable on the site. Combined with the theme's WPBakery and Elementor surfaces, it does tell you that block-built pages are not the design path here.
The changelog also offers a maintenance signal worth heeding: ACF, WPBakery and Slider Revolution are updated in the theme's releases, and shop styles, PHP 8.2 and 8.3 compatibility and WooCommerce template overrides appear as fixes across 2024 and 2025. The vendor advises backing up content and theme options before upgrading, and provides export and import under Appearance for those settings.
Questions & answers
Can Villenoir run a shop where some wines are purchasable and others are not?
Catalogue mode is described as a single switch that turns buying off across the theme, not a per-product setting. The finer control the vendor documents is the show/hide list for product elements, which lets you remove price and add-to-cart from product pages while leaving the shop active. Whether both can be applied selectively per product is not stated in the supplied description; verify that on a staging install.
Does the theme include the Wine Club Membership plugin?
No inclusion is claimed. The vendor says the theme offers support for integration with that premium plugin. You would licence and install it separately.
Is Villenoir built on Elementor or WPBakery?
Both are listed. WPBakery Page Builder (formerly Visual Composer) is the long-standing builder named in the theme's feature list and product elements. Elementor support is recorded in the vendor changelog for version 6.0.1. Which builder the bundled demo content uses is not documented in the supplied material.
