Biagiotti

Wishlist and quick view, with two plugin families to choose from

The vendor lists full compatibility with QODE Wishlist for WooCommerce and QODE Quick View for WooCommerce, and also names YITH WooCommerce Wishlist and YITH WooCommerce Quick View as compatible. That gives you a choice of supplier for the two features a cosmetics shop leans on most: saving a product for later and previewing it in a pop-up from a category listing.

Compatibility is a declaration, not a bundled plugin. Neither family is listed among the components included with the theme, so budget for installing and maintaining whichever one you pick, and pick one — a single wishlist surface is what you are actually testing.

The changelog suggests the theme's own work has concentrated on the QODE pair. QODE Wishlist support was added in 3.1, with styling adjustments for Product Carousel in 3.1.1 and for the Product List shortcode in 3.2; QODE Quick View compatibility arrived in 3.2. The YITH line appears in older fixes, such as the 2.8 note about improving YITH Wishlist and QuickView for the then-current WooCommerce. If YITH is your preference, that is the area where the vendor's recent public record is thinnest.

The shop-page shortcodes the vendor actually names

The vendor's feature list does not stop at "WooCommerce compatible". It enumerates the commerce shortcodes: Product List, Product List Simple, Product List – Carousel, Product Exhibition, Product Info and Product Category List, plus a Dropdown Shop Cart widget and multiple shop layouts.

What that list tells you is which display pieces the theme declares it can place on a page. How each one renders, what options it exposes and whether it suits your catalogue are things to check in the theme's documentation and demo rather than assume from the names. The names alone do not say whether Product List and Product List Simple differ in data shown or only in styling.

One smaller item from the changelog shows the shop chrome being maintained: version 3.6 stopped the dropdown cart widget from loading on the cart page, where a mini-cart is redundant.

Bundle versus compatibility: the two plugin routes

WPBakery Page Builder and Slider Revolution are stated as included with the theme, with the vendor attaching its own valuations to each. Elementor sits on the other side of that line: the vendor calls the theme Elementor compatible and names Qi Addons for Elementor as a compatible plugin, alongside Qi Blocks for Gutenberg and the block editor recorded as optimised in the marketplace attributes.

So the installed route is WPBakery with Slider Revolution, and the Elementor route depends on plugins you install and update yourself. Both are visible in the changelog. The 3.6 release moves WPBakery to 8.7.2 and Slider Revolution to 6.7.53, and an earlier fix addressed WPML Translation Management failing to translate Elementor widgets and WPBakery shortcodes — a reminder that on a multilingual build both builders need checking, not just the one your team prefers.

A practical consequence: if your existing content, templates or team habits live in Elementor, nothing in the package forces you back to WPBakery, but the bundled slider and shortcode set belong to the WPBakery side of the theme's own history.

Headers, and why a vertical option changes the top of the page

The vendor lists five header types — Standard, Minimal, Divided, Centered and Vertical — along with multiple header behaviours, separate logos for regular, sticky and mobile headers, and dark and light logo variants.

Vertical is the one worth thinking about first. It moves navigation to the side of the viewport, which changes how much width and height a hero image or a product banner gets at the top of the page. For a beauty brand where a single campaign photograph carries the homepage, that is a layout decision with real consequences rather than a cosmetic toggle. Separate sticky and mobile logos mean the mark can change size and proportion as the visitor scrolls or switches device, without you editing the image in CSS.

The vendor also describes User Dashboard, User Login and Registration, a Mega Menu, 800+ Google Fonts, a boxed layout option, an optional passepartout border around the site, and a child theme. Those user pages are presentation around WooCommerce's own account system — order history, addresses and payment details stay with WooCommerce.

Demo images are not yours to publish

The vendor states clearly that it does not own copyright in the demo photographs and that they are used for presentation only; you need your own stock licence or photography before publishing product shots. For a cosmetics store, where the imagery is most of the merchandising, that is a real line in the budget rather than a footnote.

Keep that in mind when reading the six homepages and the larger inner-page collection, which the vendor describes as installed through a one-click demo import. The demos show proportion, spacing and typographic scale; the pictures in them do not travel with your licence.

Marketplace attributes observed on 3 November 2026 declare WordPress 6.5.x through 7.0.x, WooCommerce 9.x and 10.x, and compatibility with Elementor, WPBakery, WPML and Contact Form 7. The marketplace's latest recorded release is 3.6, dated 17 April 2026. These are declarations, not the result of installing the theme here. One related detail from the changelog: version 3.5 removed the Biagiotti Instagram and Twitter feed plugins because of API changes, although social widgets still appear in the older feature list.

Questions & answers