Six skin sets, then a menu of parts to swap into them
Puca's vendor description does not present one demo with colour variants. It names six skin layouts, each carrying its own set of home pages: Puca Fashion with 14, Puca Fashion 03 with 4, Calarity Fashion with 9, Megabuy Supermarket with 3, Nicoshop Supermarket with 5, and Ohio Furniture with 24. That is 59 home pages in total if you count the listing, spread across fashion, supermarket and furniture directions.
Variation continues below the homepage. The vendor lists 11+ shop pages, 10+ product detail pages, 5+ product tab styles and 5 mini-cart positions as separate choices. Read together, they describe a storefront assembled from interchangeable arrangements rather than one fixed template you restyle.
What each arrangement changes for a shopper
The shop-page list is about how a product listing is framed. Left Sidebar Grid, Left Sidebar List, Right Sidebar Grid, Full Width Wide, Shop Page Divide, Shop Filter Bar, Multi Viewed Left and Right, Canvas Left and Right Sidebar, Full Width and Shop Instagram are the named options. A filter bar above the grid and a canvas layout without a sidebar are different browsing experiences, not cosmetic differences.
The product-detail list goes further into individual pages: product with a left or right sidebar, vertical left and vertical right, horizontal top and horizontal bottom, product with a menu bar, then full-width gallery, carousel, slide and stick variants. The four full-width options are variations on how product imagery occupies the screen, which is the part of a product page that decides most on a phone.
Tabs and the cart answer the same question from another angle. Five tab styles are listed \u2014 Tab Right, Tab Bottom, Tab Horizontal, Tab Vertical and a Product Accordion \u2014 and the collapsible accordion is the practical choice when page height matters. The mini cart can sit at the top, bottom, left or right, or open as a popup, and the vendor describes each as AJAX-driven, so a shopper can check the basket without leaving the page. The changelog backs that framing: 2.6.36 fixed accordion tabs not displaying content on the single product page, and 2.6.33 fixed an AJAX error and load-more problem on the shop archive.
Multi-store and catalogue tooling, as described
The vendor calls Puca a WooCommerce Multi-Store theme and backs that with HUSKY Products Filter for WooCommerce Professional 3.3.x readiness, a catalog mode, and product search that supports SKU lookup. Catalog mode matters for stores that present products without selling them online, and SKU search helps when customers arrive with a part number rather than a product name.
Marketplace tags on the listing also mention Dokan, WCFM, MultiVendorX and WC Vendors. Those tags describe declared compatibility, not a tested multi-vendor install, so treat them as a reason to check your chosen vendor plugin's own documentation rather than as confirmation that every marketplace feature works out of the box. The same caution applies to the item description's claim that bundled plugins are worth a set figure; that is a vendor statement about what the theme is sold alongside, not an inventory of any particular copy.
The changelog shows a template-override maintenance cycle
Puca's release notes are dominated by one recurring task: fixing WooCommerce template files the theme overrides that have gone out of date. Releases through 2025 and 2026 repeatedly repair cart, mini-cart, checkout, my-account, single-product image, thumbnail and review templates, each usually paired with a new WooCommerce version claim \u2014 11.2.x alongside 2.6.47, 11.1.x in 2.6.46, 11.0.x in 2.6.44, 10.8.x and 10.5.x earlier.
For a long-running shop this is the useful signal. A WooCommerce theme that ships its own copies of cart and checkout markup has to be updated when WooCommerce changes those templates, and the notes show Thembay doing that frequently. It also means older copies drift out of date quietly: a cart template that matched WooCommerce a year ago may not today. The root cause is visible in the file paths themselves, which sit under a theme-side woocommerce directory.
Mobile behaviour gets its own entries rather than only version bumps. Version 2.6.32 fixed a variable product error on mobile single product pages, and 2.6.19 fixed a mobile menu button click error.
Past security fixes are part of the record
Three security entries appear in the changelog: a critical local file inclusion fix in 2.6.34 (June 2025), an LFI fix in the Elementor widget Puca Posts Grid in 2.6.40 (November 2025), and an unauthenticated reflected XSS fix in the product tabs AJAX endpoints in 2.6.45 (August 2026).
Those entries are dated and specific. They show what has been patched over time; they do not tell you what any particular copy of the theme contains. If you inherit or acquire a Puca install, the release number it runs is worth establishing, because the fixes above are tied to specific releases rather than to the theme as a whole.
Editing surface and declared compatibility
Page building is described as running through Elementor or WPBakery Page Builder, with the Redux framework behind the theme options panel, custom CSS and JS fields in the settings, and Google font controls. The vendor's own feature list claims WordPress 7.1 readiness and PHP 8.3, and the marketplace attributes recorded on 4 November 2026 list Elementor, Elementor Pro, Contact Form 7, WPML and WooCommerce 7.x through 10.x under compatible with, with WordPress 6.5.x through 7.0.x as the software version. Gutenberg Optimized is marked No, which records that the theme was not built around block-editor patterns rather than that blocks cannot be used.
Where those two documents differ on version ranges, they are declarations made at different times, not test results. Package contents are listed as PHP files.
Where Puca's arrangement menus pay off
Puca earns its place when the store's structure is already decided and the work is assembling it: a fashion shop that wants a filter bar but no sidebar, a furniture catalogue that needs wide gallery product pages, a supermarket layout with a persistent mini cart. The skin sets give you a starting point close to your category, and the arrangement lists change the parts a shopper actually touches.
It is a weaker fit when the storefront is unlike any of the six named directions and you expect to design page structure from scratch, or when you want a block-based editing workflow. The options are rich within their arrangement menus, but they are still options the theme offers.
Questions & answers
Can I use Puca for a multi-vendor marketplace?
The vendor tags Dokan, WCFM, MultiVendorX and WC Vendors as compatible. Those are declarations on the listing rather than results of a tested marketplace build, so verify your chosen plugin's compatibility notes for the versions you plan to run.
Does Puca work with a catalog-style shop that does not sell online?
The feature list names a catalog mode among the theme's options. That mode is described by the vendor; how it behaves with your product types and any additional plugins is something to confirm on a staging copy.
What separates Puca's six skin layouts?
Each skin set ships its own home pages: Puca Fashion (14), Puca Fashion 03 (4), Calarity Fashion (9), Megabuy Supermarket (3), Nicoshop Supermarket (5) and Ohio Furniture (24). They correspond to fashion, supermarket and furniture directions, and the shop and product arrangements are chosen separately from the skin.
