A catalogue theme built around a vertical menu
The vendor's summary leads with a design idea rather than a feature list: Marketo is meant to use as much of the available space as it can to show a lot of products in different ways, and the vertical menu is how it does that. Navigation runs down the side of the page instead of across the top.
A side rail changes how a category-heavy shop reads. The menu stays visible while someone scans products, and category entries can open large panels without pushing page content down. It also costs horizontal room on desktop, so the product grid beside it has to be designed for a narrower column. That trade-off is the first thing to judge in the published demo.
The menu is clearly maintained as its own component. The changelog records seven new menu styles added in 1.2.0, a fix to a broken vertical menu text issue in 1.9.8, a fix to mega menu badge encoding for Hebrew in 4.6, and a vertical mega menu fix in 5.3.0.
What the Dokan layer covers, and what it leaves to the plugin
The vendor lists Dokan multivendor support and describes Marketo as compatible with Dokan as a multivendor solution, with commissions and products ranging from digital and physical to variable. Dokan is a separate plugin; a compatibility declaration is not a bundled marketplace. The marketplace file list for Marketo names PHP, CSS and JS files.
The changelog shows which vendor-facing screens have needed work over time. Version 2.1 fixed a Dokan map issue, 2.7 fixed a broken Dokan vendor biography layout, and 1.5.1 fixed a general multivendor plugin issue. Older entries also record Dokan compatibility fixes in 1.5 and 1.9. Those entries point at the places where compatibility friction has shown up: vendor store pages, the store map, and the biography block on a vendor profile.
So the theme contributes storefront and vendor-page presentation. Seller accounts, product submission, commission rules and payouts come from Dokan's own configuration, and the listing does not say how the two divide every screen. If each seller gets a storefront, set up a test vendor account with a filled biography and a store location before committing.
Header and footer sit outside Elementor
Marketo declares Elementor as its page builder, and the same feature list also names the Kirki Customizer and the Unyson framework, which the marketplace framework attribute confirms. Settings are therefore spread across more than one surface, and the listing does not map which option lives where.
The header is the clearest example. Version 2.3 added header and footer builder support along with sticky behaviour for the header builder, and the release notes say existing customers could reuse the builder through JSON files included in the Marketo package folder. So page content is edited in Elementor, while the header and footer layout comes from the theme's own builder, and global options such as typography are the kind of thing the Kirki Customizer typically holds. Version 4.5 added a global fonts loader option to the customizer, which fits that split.
A short discovery pass after setup saves rework: locate the header builder, the customizer panel and any Unyson panels, and note which typography and colour settings live outside Elementor. Otherwise you can style something in Elementor and then find it inheriting a different value from the theme layer. Newer releases still touch Unyson directly: 5.3.0 updated Unyson custom code alongside WooCommerce template versions and Slider Revolution.
Eleven homepages and fifteen headers as starting arrangements
The vendor advertises 11+ homepage designs and 15+ header styles. Treat both as different arrangements of the same building blocks rather than finished sites. The homepage count is useful because you can start from the layout closest to your category structure, then replace copy, images and products.
The header count answers the question the vertical menu raises: if a side rail does not suit your catalogue, other header arrangements exist. The listing does not say which header styles pair with which homepage demo, so matching them is demo work.
Shop behaviour has its own history worth reading before you plan customisations. Version 4.6 added AJAX load more for shop products, and later releases adjusted cart, mini-cart and product-listing behaviour. Version 5.3.1 updated WooCommerce template versions, and 5.3.0 did the same. If you override shop templates in a child theme, re-check those overrides after a theme update, since template version bumps are where overrides drift out of date.
Declared compatibility, and the vendor's browser list
Marketplace attributes observed on 3 November 2026 list Elementor and Elementor Pro, WooCommerce 7.x, 8.x and 9.x, and Bootstrap 4.x, with WordPress versions from 6.0.x through 7.0.x and Gutenberg Optimized marked Yes. The vendor's feature list separately says the theme is fully responsive with retina-ready assets, Google Fonts, Font Awesome and 200+ line icons, and declares cross-browser compatibility with Edge, IE11+, Firefox, Safari, Opera and Chrome.
These are listing declarations, not the result of installing the theme on a current site, and browser and WordPress figures in a listing are not a test record. The changelog does show a maintenance pattern around deprecations: 4.6.3 fixed an Elementor register_control deprecation, and 5.3.1 fixed PHP deprecated issues while updating WooCommerce template versions.
The most recent entry recorded for the theme, 5.3.2, is a fix to a license activation issue, so activation is part of the product's own code. Where you obtain the theme affects which of these fixes you get.
FAQ: Marketo and Dokan
The practical questions reviewers tend to reach concern the marketplace layer rather than the design. Dokan supplies vendor accounts, product submission and commission mechanics; Marketo supplies the storefront and the vendor-facing layouts the changelog keeps fixing. Budget configuration time for the plugin, and read its own documentation for seller onboarding.
On the vertical menu: it is an identity choice, not a lock-in. With 15+ header styles declared, other arrangements are available, but the homepage demos were built around a dense product display, so a horizontal header can leave gaps in a layout intended for a side rail. Judge that against your own category depth rather than the sample catalogue.
Questions & answers
Does Dokan come bundled with Marketo?
The vendor lists Dokan multivendor support and describes the theme as compatible with Dokan. That is a compatibility declaration, and the marketplace file list names PHP, CSS and JS files only. Dokan is a separate plugin with its own configuration and pricing.
Can I replace the vertical menu with a horizontal header?
The vendor declares 15+ header styles, so other arrangements are available, and version 2.3 added a header and footer builder. The listing does not specify which header styles pair with which homepage demo, so check the published demo before committing to a horizontal layout.
Where do header and footer changes happen?
Separately from Elementor. Version 2.3 added header and footer builder support with sticky header support, so the header is built in the theme's own builder while page content is edited in Elementor.
