WoodMart WooCommerce Guide: Filters, Swatches, Layouts and the Plugins You Can Retire

A theme that sells the shelf, not just the shop window

WoodMart's argument is arithmetic. The vendor says the store features it builds in would cost '$813 every year' bought as separate plugins. We have not priced that list, and you should not take it as your saving, because few stores need every item. What is true is that the documentation now runs to whole sections on cart and checkout, conversion and upsells, and marketing and retention, each describing a job most WooCommerce stores hand to a plugin vendor.

All of it comes with the $69 Regular License as of October 2026, one store per license, with six months of support and a $21.38 extension for another year. There is no free version and no Pro add-on to buy later (the $3,999 Extended License is for end products users pay for, not extra features); the WoodMart pricing page has the detail and the WoodMart review judges the theme as a whole.

Wiring the Product filters element to the AJAX shop

Filters are where a fashion or furniture store wins or loses a shopper, and WoodMart's are built from one element called Product filters. It can filter by category, by attribute, by stock status (on sale, in stock, on backorder), by price, and by sort order. Attribute filters only work on global WooCommerce attributes, the ones made under Products, then Attributes. Attributes typed into a single product's custom attribute box will not appear, which is the first thing to check when a color filter shows nothing.

1. 1

   Build the form

   Create an HTML Block and add the Product filters element. In the block editor and WPBakery, add each filter inside its container; in Elementor, add them as items in the widget's filters section.

2. 2

   Pick the submit behavior

   In Elementor and WPBakery, Submit form on offers Button click or Dropdown select. Button click suits long filter lists on phones, where every tap otherwise reloads the grid.

3. 3

   Place it above the products

   Open Theme Settings, then Product archive, then Shop filters. Enable Shop filters, set Shop filters content type to HTML Block, and choose your block in Shop filters HTML Block.

4. 4

   Turn on AJAX shop

   The filters support WoodMart's AJAX filtering when AJAX shop is enabled, so results refresh without a full page load on shop and archive pages.

5. 5

   Test the edge cases

   Combine two filters with no matching products, clear them, and use the back button. Then repeat on a phone.

Every filter combination is also a URL. Left open to crawlers, a store with ten colors and eight sizes produces addresses by the hundred, each a near duplicate. Decide with your SEO plugin which filtered views deserve indexing, and keep the rest out.

Swatches, term by term and grid by grid

WoodMart's swatches live in two places, which confuses owners who look in only one. The look of each value is set on the attribute term: Products, then Attributes, then Configure terms, then edit a term and choose an image, a color or text in its Swatch settings. The look of all swatches together is set in Theme Settings, then Shop, then Variable products, where Swatch style, Disabled swatch style, Swatch shape (round, rounded or square) and Swatch size apply store-wide.

• Grid swatch attribute to display chooses which attribute shows under products in the shop grid, usually color. A single product can override it.
• Use images from product variations pulls each variation's main image into the swatch, falling back to the term swatch where no image is set. It saves uploading a color chip per term, and it means a missing variation image shows up in the grid.
• Linked variations groups separate products that share a global attribute, so a shopper switches between them with swatches on the product page. It is enabled in the same Variable products panel.
• A second swatch plugin is the mistake to avoid. The vendor's compatibility policy names plugins that alter or duplicate swatches as a conflict.

When variations stop appearing after an update or an import, the cause is usually WooCommerce data rather than the theme; WooCommerce variations not showing walks the checks in order.

Layouts Builder: product, archive, cart and checkout by condition

Under Dashboard, then Layouts, WoodMart keeps templates for the whole store: Single product, Products archive, Cart, Empty cart, Checkout, Thank you page and Product loop item, plus My account, Login/Register and Lost password. Each layout carries conditions. Include applies it to matching content and Exclude keeps it away, and product conditions can target all products, single products, categories, child categories, tags, brands, attributes or product types.

Two details save hours. First, layouts are built in your current builder, set under Theme Settings, then Other, then Current builder, and the vendor supports Gutenberg, Elementor and WPBakery. Second, Product loop item layouts, the cards in the shop grid, are always edited in Gutenberg, even when Elementor or WPBakery is the current builder. Owners who live in Elementor are often surprised by that the first time they redesign a product card.

If a shop page has lost its grid or sidebar, the general mechanism is explained in WooCommerce layout broken, and styles that refuse to change after an edit are covered in WoodMart CSS not updating.

The plugins to keep, and the ones WoodMart will fight

WoodMart's compatibility policy is unusually direct. It names three kinds of plugin it does not support: those that replace or modify the theme's AJAX filters, those that alter or duplicate product swatches, wishlist or compare, and page builders other than Gutenberg, Elementor and WPBakery. It also says the theme works with plugins compatible with WordPress's default annual themes and with Storefront, and it gives advanced support to more than 40 named plugins, including WooCommerce, Stripe, PayPal, WPML, Yoast SEO, WP Rocket, Dokan and Amelia.

Remove one plugin at a time on staging, and export its data first. Wishlists and waitlist sign-ups live in each plugin's own tables, and the theme will not import them. Emails are the quiet failure here: if order emails stop sending, cart recovery emails have usually stopped too. The store-side faults we see most are gathered in WoodMart WooCommerce issues.

Checkout speed on a theme that does this much

A page cache makes WoodMart's category pages quick for anonymous visitors. It cannot help the Cart, Checkout and My Account pages, which WooCommerce's own documentation tells you to exclude from caching because they hold one customer's data. On those pages every request runs WordPress, WooCommerce, the theme's feature set and every plugin, which is why the vendor's server recommendations matter: PHP 8.3 or newer, a 256M memory limit, max_execution_time of 180, max_input_vars of 10000 and 64M upload and post sizes.

Three store-specific costs deserve a check. AJAX filtering sends a request on each filter change, so a busy server shows up as a lagging grid. Filtered URLs split the page cache into many small copies that are rarely reused. And any live header cart count depends on WooCommerce's cart fragments refresh; open a content page in your browser's developer tools and see whether a get_refreshed_fragments request fires where nobody is shopping.

Inside Theme Settings, then Performance, use the Preload LCP Image switch, keep the main product photo out of lazy loading, host Google Fonts locally, and follow the vendor's rule of one lazy-loading system only. The full order of work is in the WoodMart speed guide. If the store throws 500 errors under load, compare your host's limits with the list above and see 500 internal server error; for a store already crawling, WoodMart slow website is the repair route, and our theme speed optimization service does the work for you.

When the feature shelf stops being enough

WoodMart is a strong choice for a catalog of ordinary products where shoppers filter, compare and pick a color. It stops fitting when the store's rules are unusual: wholesale and retail prices for the same item, quote requests, configurators, memberships sold alongside products, or inventory synced from an ERP. Each of those means a plugin that has to coexist with a theme that already owns filters, swatches and the cart, and the vendor's own policy tells you where coexistence ends.

WoodMart replaces five vendors with one. It cannot replace the plugin model itself.

At that point the question is the stack, not the theme. WoodMart vs Next.js compares the theme with a custom build, WooCommerce vs Next.js for ecommerce explains why uncached checkouts behave as they do, and WooCommerce to Next.js covers products, customers and redirects. The theme-specific route, including what replaces the Layouts Builder, is WoodMart to Next.js. Our e-commerce development builds on Athena CMS, where e-commerce is built in and Demeter drafts seasonal offers for approval.

Staying on WoodMart? Keep the theme, WoodMart Core, your builder and WooCommerce updating together on staging; WoodMart update problems shows what to check when one of them breaks the shop. Every fix is in the WoodMart repair hub, outside-the-theme faults go to WooCommerce website repair, and the closest rival is in Flatsome with WooCommerce. More store themes are reviewed under WordPress themes.