Molla treats the product page as editable content
Plenty of WooCommerce themes list a gallery, a badge and a zoom. Molla's changelog shows the author building those as per-product fields instead. Version 1.3 records four additions in the same release: "360 degree gallery", "Product video thumbnail", "Product custom label", and a single product gallery rebuilt as a carousel for all product types.
That grouping is the useful signal. A 360-degree sequence is usually a set of frames you shoot and attach to one product; a video thumbnail means a product can lead with a play overlay rather than a still image; a custom label is text you write per product rather than a fixed sale flag. The vendor also added a new label type to its WooCommerce product options and a quantity option in the same release, both of which read as settings for the same editing screen.
The vendor documents the label fix in detail: earlier, a custom product label on the product edit page did not carry across other languages (version 1.3.2). If you sell in more than one language, that history is worth knowing before you assume the label behaves identically everywhere.
Running a catalogue without selling from it
WooCommerce Catalog Mode is listed as a feature, and it is the item that changes what the site is for. It strips the purchase path so visitors can browse a product range without prices and cart buttons — the arrangement a wholesale enquiry site, a lookbook, or a pre-launch store needs.
The vendor does not describe how the mode is switched or what it hides; confirm that against the documentation before you build around it. Related shop-side options appear in the changelog rather than the feature list: version 1.3.2 fixed a "Disable out of stock products" option that was not working for the products widget, and stopped a hurry-up label appearing on products that were already out of stock. Both are small things until a customer sees them.
Narrowing a long catalogue in place
The feature list names wishlist, Ajax search, filtering and sorting, grid or list view, shop pages, and Ajax filtering specifically on shop and product archive pages. Put together, a visitor can narrow a category by attribute and see the grid change without a page load, then switch between tile and row display.
The filter work has its own trail in the changelog. Version 1.3.2 fixed the translation of "Filters" and "Price Range" on the shop page and compatibility with YITH WooCommerce Ajax Product Filter 4.2.1; the description separately claims compatibility with the WooCommerce Product Filter plugin and with YITH's Ajax Search.
One archive detail is easy to miss: version 1.5.22 fixed product catalogue loop images rendering at full size — a fault where thumbnails ignored their configured dimensions and overflowed the grid. If you inherit a build made before that release, check how your archive tiles sit against the columns.
Headers: what the vendor actually specifies
The description claims 20+ different headers and an "exclusive header builder", plus a mega menu with a three-level drop-down and a switch to turn the sticky header on or off. It does not say whether the builder is a drag-and-drop canvas or a set of predefined variants chosen in the customiser.
That gap is worth resolving early, because header work is the recurring task on a live shop: adding a seasonal promotion bar, inserting a new category into the mega menu, or moving a contact line into the top strip. If you need to restructure the header rather than swap a preset, find out how the builder works before committing to it.
The sticky switch is the concrete item. It lets you decide whether a category bar or navigation trail follows the visitor down a long product page, which on a large catalogue is a navigation decision rather than a decorative one.
Two 2025 fixes that concern the Ajax hooks file
Two changelog entries are security fixes rather than features, and both target the same theme file under the Ajax hooks directory. Version 1.5.17 records a Local File Inclusion fix at line 469 of molla\\inc\\functions\\hooks\\ajax\\functions.php; version 1.5.19 records an XSS fix at line 666 of the same file.
The straightforward reading is that these problems existed above the Ajax layer and were patched in those releases. If you are evaluating an older copy of Molla, the version number is the thing to check against this log. That is a statement about what the vendor recorded, not an audit of any particular set of files.
What the marketplace listing declares
Observed on 4 November 2026, the listing marks Molla compatible with Contact Form 7, Elementor, Elementor Pro, WPML and WooCommerce 6.x through 10.x, with WordPress versions from 5.8.x to 7.0.x, and files listed as PHP and CSS. The theme is marked Gutenberg optimized, widget ready and responsive.
Those are declarations attached to the product; they are not results of testing against your PHP build, caching layer or plugin mix. The vendor's summary text and changelog also name later WooCommerce releases than the attributes do, which is common when attribute fields lag behind releases. Treat the changelog as the vendor's more recent statement of what was checked, and the attributes as the broader range.
Questions & answers
Do I need Elementor to build a Molla store?
No dependency is stated. Elementor and Elementor Pro appear in the marketplace compatibility list, the vendor names Elementor and Visual Composer among the builders it works with, and the theme is marked Gutenberg optimized. The changelog also records a recommended Alpus Elementor FlexBox addon for Elementor's container feature — recommended, not required.
Which release introduced the 360-degree gallery and video thumbnail?
Version 1.3, alongside the custom product label and the single product gallery rebuild as a carousel. Version 1.3.2 later fixed the custom label not applying across other languages.
