WoodMart vs Next.js: A Feature-Packed Store Theme Against a Custom Build

What 119,473 buyers got for $69

WoodMart is a WooCommerce theme from xtemos, sold on ThemeForest, where it shows 119,473 sales; the vendor's own site says it is used by 120,000+ online stores. The current version is 8.6.4, and the listing was updated on October 6, 2026, the very day we checked. If you bookmarked the old documentation, note that it has moved: xtemos.com and woodmart.xtemos.com now redirect to woodmarttheme.com.

It is a classic theme, not a block theme, with its own Theme Settings panel, a Header Builder, a Layouts Builder and a mega menu builder. You choose the page builder underneath it: Elementor, WPBakery or the block editor. And it carries a store's worth of features that most WooCommerce sites buy one plugin at a time:

• Shopping tools: AJAX product filters, variation swatches, quick view, AJAX live search and size guides.
• Retention tools: wishlist, compare, back-in-stock alerts and abandoned cart recovery.
• Order-value tools: frequently bought together and free gifts.
• Templates for the money pages: the Layouts Builder designs single product, product archive, cart and checkout pages.
• A head start: the vendor lists 100+ prebuilt websites and 400+ templates.

That is genuine value, and for a lot of stores it is the right purchase. The WoodMart WooCommerce guide goes through each feature's settings. This page asks the other question: what does all of that weigh once a real catalog sits on top of it?

WoodMart against a Next.js store, all 22 rows

The left column is a working WoodMart store: theme, WoodMart Core, a page builder, WooCommerce and its payment and shipping extensions. The middle column is a custom Next.js storefront. The right adds Athena CMS, which includes e-commerce and is part of every site we build.

The commerce rows get a fuller treatment in WooCommerce vs Next.js for e-commerce, which applies to any WooCommerce theme. WoodMart's twist is that more of the store lives inside the theme, which helps on day one and complicates the day you leave.

The real WoodMart stack, from setup wizard to checkout

The setup wizard asks one question that shapes everything after it: which builder? Prebuilt demo content is prepared separately for Elementor, WPBakery and Gutenberg, so the choice has to be made before import and is awkward to reverse. From there, a working store usually stacks up like this:

• WoodMart, the theme, with Theme Settings, Header Builder, Layouts Builder and mega menus.
• WoodMart Core, the required companion plugin, installed during setup.
• A page builder: Elementor (often with Elementor Pro), WPBakery Page Builder, which ThemeForest lists as included, or the block editor.
• WooCommerce, plus gateways such as Stripe or PayPal and whatever shipping and tax extensions the business needs.
• The theme's built-in image optimizer for WebP, lazy loading and LCP preloading, often joined by a separate optimization plugin that wants the same job.
• WPML, Dokan or WCFM where the store is multilingual or multivendor; the vendor claims enhanced integration with 40+ plugins.
• The usual WordPress layer: SEO, forms, security, backups and cookie consent.

None of these is a bad choice. The friction is in the overlaps, and WoodMart's own documentation is candid about it: its third-party compatibility policy warns about plugins that replace or modify the theme's AJAX filters or duplicate its swatches and wishlist. A theme that does everything has opinions about everything.

A theme that does everything has to agree with everything else you install.

License math: $69 once, and everything around it

As of October 2026, a Regular License costs $69 on ThemeForest. It covers one end product that is free to its end users, which for most merchants means one store. It includes six months of support; extending support by 12 months costs $21.38. The vendor promises free lifetime updates. The Extended License, for an end product that end users pay for, is $3,999, the steepest of any theme we cover. Refunds follow Envato's rules: no change-of-mind refunds, but money back if the item is broken or not as described and cannot be fixed, has an unpatched security hole, the promised support is not delivered, or it was never downloaded within 30 days.

The $69 is honest. It is also the smallest number on the bill. What it does not cover:

• A hosting plan strong enough for the vendor's recommended PHP limits.
• Elementor Pro, if you pick Elementor and want its theme-building tools.
• WooCommerce extensions for subscriptions, bookings or B2B pricing that the theme does not include.
• Support after the first six months, unless you renew it.
• A second store, which needs a second license.

The full breakdown, plan by plan, is on the WoodMart pricing page. If a rebuild is on the table but the cash is not, e-commerce financing spreads the cost.

Where WoodMart stores tend to break

A theme this capable fails in its own particular ways. The vendor documents most of them, which is to its credit.

Front-end symptoms have their own guides: a header that will not show, a mobile menu that will not open, CSS changes that do not appear and fonts that fail to load. Everything WoodMart-specific is gathered in the WoodMart repair hub, and if the store is down right now, our theme repair service takes the call.

The third option

Athena CMS, with AI agents on staff.

Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.

• PPicassoImages
• AApolloSite analysis
• AAresCompetitor watch
• PPrometheusContent holes
• AAtlasPage depth and structure
• DDelphiAI search visibility

ZDAOAand 12 more agents. Two come with Athena; the rest are monthly add-ons.

Meet the agentsTake the Athena tour

PPicassoWeekly · ImagesAApolloWeekly · Site analysis

Store speed once the catalog and the traffic grow

The vendor makes three speed claims worth quoting carefully. It says WoodMart loads only the CSS and JavaScript each page needs, which cuts page size two to three times. It says stores reach 90+ PageSpeed scores without a separate optimization plugin. Its homepage shows a PageSpeed report for a WoodMart store with Core Web Vitals passed and a performance score of 100. We have not tested those claims, and a vendor's showcase store is not your store with 4,000 products and a chat widget.

Selective loading genuinely helps. What it cannot change is where the work happens. A page cache can hand the same product page to every anonymous visitor, but the cart, checkout and account pages are personal and have to be built fresh. Filtered category pages multiply into thousands of URL combinations, and each one is assembled by PHP and the database the first time it is asked for. So the heavy lifting lands on the server exactly when a shopper is deciding whether to buy.

A Next.js storefront moves that work earlier. Product and category pages are prerendered and refreshed with incremental regeneration when price or stock changes. Filtering runs against a prepared index or in the browser. Checkout is a dedicated path that hands payment to the processor. The WoodMart speed guide shows how far tuning can take the theme, and our theme speed optimization service does that tuning when staying is the right call.

Which stores should keep WoodMart, and which have outgrown it

WoodMart is the right tool for more stores than its critics admit. It is also the wrong tool for a specific kind of store that tends to find out late.

If you are still weighing store themes, WoodMart vs Flatsome sets the two big ThemeForest options side by side, and Flatsome vs Next.js runs the same test you are reading now.

Leaving WoodMart, and where Athena picks up

Leaving WoodMart is harder than leaving a lightweight theme, and it is better to know that up front. The good news first: products, variations, orders and customers live in WooCommerce's own tables and export cleanly. The harder part is everything the theme drew. Layouts are stored in the format of whichever builder you chose, Elementor data, WPBakery shortcodes or blocks, and WoodMart's own elements, Layouts Builder templates and header settings do not travel. They are rebuilt as components. Filter and attribute URLs need a redirect plan so search engines do not lose the category pages that earn traffic.

The sequence is set out in moving WoodMart to Next.js and, for the store data itself, WooCommerce to Next.js. We keep your URLs and redirect every old one.

On the other side, Athena CMS gives the store team plain fields for products, pages and offers, with a preview and every version kept. The agents take on merchandising chores: Demeter prepares seasonal offers, Zeus builds event banners from live feeds, Echo handles reviews, Ares keeps watch on competitors and Argus reports failing forms and slow pages. Features WoodMart bundled, such as filters or a wishlist, are built into the storefront as code where the business needs them, not switched on because they came in the box.

Verdict by store type

• Boutique fashion or home goods, a few hundred SKUs: keep WoodMart, choose one builder, one optimizer and a good host, and tune it.
• Furniture and large catalogs with deep filtering: start planning a move; filter pages are where PHP pays the heaviest bill.
• B2B and wholesale: Next.js. Account pricing and quote flows fight WooCommerce settings.
• Multivendor marketplaces on Dokan or WCFM: WoodMart supports them, so stay until scale forces a custom marketplace, which is a serious project.
• Subscription boxes and member pricing: Next.js with Athena's membership areas and Stripe billing.
• Stores living on paid ads: Next.js. Speed on landing product pages pays for the build fastest.

Want a second opinion on your store? A free site audit lists what each plugin does and where the time goes. If a rebuild makes sense, our e-commerce development team and Next.js development service quote it fixed. Other themes get the same treatment in the WordPress vs Next.js comparison center.