The 360 spin viewer changes your photography before anything else
Most WooCommerce themes treat a product as a gallery plus a description. ThemeMove puts a different feature at the centre of LeArts. The marketplace description calls Product 360 a "super hot" feature and explains how it works: you build the spin from 8 to 24 frame images, and a visitor clicks the 360 icon, then drags horizontally to rotate the object.
For craft work that answers a real problem. A ceramic bowl, a woven basket or a carved chair has a profile and a surface that one straight-on photograph hides. Eight frames is enough for a chunky object; 24 smooths the turn.
The effort lands on your side of the build, not the visitor's. Someone has to shoot each product through a full rotation on a consistent axis and crop the frames evenly. With a small catalogue of distinctive pieces, that work buys something a gallery cannot. With hundreds of near-identical items, plan on using the viewer selectively instead of on every product.
Around it, the vendor lists Ajax advanced search that previews matching products with images and attributes as a visitor types, an off-canvas cart for revising an order without leaving the page, and Compare, Quick View and Wishlist controls on shop listings; the feature summary names YITH WooCommerce Smart Compare and Smart Wishlist against the last two.
What each of the seven product layouts lets you argue
The vendor's seven single product layouts are better read as decisions than as a count. Basic is the plain arrangement. Full-width gives the product the screen. Sticky Details keeps specification copy in view while the visitor scrolls, which suits pieces with dimensions, materials or care instructions worth re-reading. With Sidebar moves reference detail into a widget column. Extra Content opens a deeper introduction of attributes, the place for explaining how something is made. Variation Images swaps photography with the selected option, and Bought Together proposes additional items as a bundle.
Two of them need planning before you build. Variation Images only pays off if you photograph every variant, so a product sold in twelve glaze colours needs twelve sets of shots. Bought Together turns the product page into a merchandising decision about which pieces sit naturally beside each other.
The archive side mirrors this with seven layouts that collapse into a smaller choice. No sidebar, left sidebar and right sidebar are the standard three; four full-width variants add a no-extra-space mode or move the same sidebar choices onto a wider canvas. Since the marketplace lists 4+ columns, the full-width no-space option is the one that feels cramped first if you push the column count.
The bundle is broad, but hotspots cost extra
The vendor states that buying LeArts gives access to WPBakery Page Builder, Slider Revolution, Font Awesome Pro 5 and a Futura font without separate licences, and the feature summary attaches dollar values to the first two as savings. The package also lists a child theme, one-click demo import and 28+ shortcodes built for the WPBakery back-end editor. Those are vendor claims about the marketplace package; the file list of a given copy is the thing to check.
Shoppable Images sits on the other side of that line, and the description is unusually explicit. Tags that pop up with product information, prices and options appear in the demo, but the vendor's note says customers "must PURCHASE the plugin itself. It's NOT included in the theme package." If hotspot shopping is how you want to present a styled room scene or a gift set, budget for that plugin as a separate purchase.
The WPBakery Page Builder Clipboard is listed with a "Coming Soon" marker, so it is not something to build a workflow around. The shortcodes themselves are real and are inserted through the back-end editor's Add Elements panel, which shows the page-building habit the vendor assumes: rows of predefined elements rather than a blank canvas.
Twelve blog layouts for the half of the site that isn't the shop
Craft businesses tend to publish: process notes, workshop dates, maker interviews, care instructions. The vendor gives that side a large layout set: twelve-plus blog layouts covering single posts and archives, in standard, grid, list and masonry arrangements, each with a left sidebar, right sidebar or full-width variant.
That fullness matters because the archive choice changes how photographs read. A masonry archive without a sidebar handles mixed portrait and landscape process shots unevenly laid out; a standard list with a sidebar puts one large image beside a column of text and widgets. Two shops with identical products can look like different businesses because of this one setting.
The marketplace attributes also mark Gutenberg Optimized as Yes, which is a declaration about the block editor rather than a description of the theme's design workflow. Nothing in the description suggests pages are composed as blocks; the builder described throughout is WPBakery.
Compatibility claims inside LeArts disagree with each other
The marketplace attributes list WooCommerce 7.x through 10.x and WordPress 6.0.x through 7.0.x as compatible, alongside WPBakery, WPML, Contact Form 7 and Bootstrap 4.x. The description body, by contrast, still calls WooCommerce 3.5 "the latest version" and claims full compatibility with it. Both statements live in the same listing and were written years apart.
The reasonable reading is that the attribute list is the newer, more specific declaration and the body text is stale. Neither is a test result. Compatibility statements are vendor claims, and this article makes no claim of having run the theme against any stack.
The WPML entry deserves a similar reading: it says the theme is compatible, not that a translated product catalogue or menu structure has been verified. The browser list, which includes IE11 next to Chrome, Firefox, Safari, Edge and Opera, says more about the theme's ancestry than about how it behaves under current mobile traffic.
Where an edit lands: builder, presets, or the product layouts
A change on a LeArts site can happen in three places, and knowing which one saves time. Page content and row arrangement belong to WPBakery, where the shortcodes are assembled. Site-wide decisions sit above that: the vendor lists 7+ header presets and 7+ footer presets, an off-canvas menu and a 600+ Google Fonts library, so a rebrand splits between rearranging elements in the builder and changing the presets and typography that frame every page. Product presentation is a third layer, since the single product and archive layouts are theme-level choices rather than page content.
The twelve homepage demos named in the description show the vendor's intended range: Arts Propelled for handicrafts and artworks, Savvy Delight for furniture, Kitchen Cozy for kitchen and home decoration, Instagram Fever for an Instagram-led shop, Crafting House for handmade crafting, among others. They are starting points for composition, not templates that arrive filled with your products.
What the evidence supports is a narrow, real advantage. If your pieces reward close inspection and you will shoot frame sequences for the ones that do, LeArts gives you somewhere to put that inspection and a spread of layouts for handling variants, bundles and long attribute copy. If your shop runs on volume and standard product shots, the spin viewer stays idle and the layout variety is what you would actually be buying.
Questions & answers
How many images does a LeArts 360 product view need?
The vendor describes a spin built from 8 to 24 frame images. Fewer frames give a coarser rotation and a lighter photography workload; 24 frames produces a smoother turn.
Are shoppable image hotspots included with the theme?
No. The vendor's note says customers must purchase the Shoppable Images plugin separately and that it is not part of the theme package. The theme demonstrates the feature; the plugin is a separate cost.
Which WooCommerce version should I plan for with LeArts?
The marketplace attributes list WooCommerce 7.x through 10.x, while the older description body still refers to 3.5 as the latest release. Treat the attribute list as the vendor's current declaration and confirm compatibility against your own setup, since neither statement is a test result.



