WooCommerce at a crossroads
Flatsome vs Next.js: A Store Owner's Fork in the Road
On September 30, 2026, the company behind Flatsome announced its next product was "not an update. It is a new beginning." If you run a store on Flatsome, that sentence just handed you a decision. There are now three roads, and only one of them was on the map a month ago.
October 7, 2026 · 11 min read
The short answer
Flatsome is still a sensible, low-cost theme for a WooCommerce store with a modest catalog and an owner who likes UX Builder. Next.js is the better choice when store speed drives revenue, the catalog or checkout needs custom logic, or you would rather not rebuild on Flatsome's new block-based Site Builder while it is in beta.
On this page
- Why 270,401 store owners said yes to Flatsome
- Classic, Site Builder, or neither: the three roads since September 30
- Flatsome against Next.js, one row per store worry
- Child theme, overrides and the commerce plugins Flatsome cannot replace
- The four tickets Flatsome stores file most
- Licenses: one-time Classic, yearly Site Builder
- Which road fits your store
- The UX Builder exit tax, and what Athena does with the store
- Boutique, catalog, wholesale: where each store lands
Why 270,401 store owners said yes to Flatsome
Flatsome is a shop theme first and a theme second. It has sold 270,401 copies on ThemeForest, mostly to people who wanted a WooCommerce store that looked finished without hiring anyone. For $59, one time, you got a theme with its own front-end drag-and-drop editor, UX Builder, plus reusable UX Blocks, a header builder and lifetime updates.
The store features are the point. The vendor describes designing product, shop, cart and checkout pages, adding mini-carts, quick view and free-shipping bars. Catalog Mode hides the cart and checkout for shops that take inquiries instead of orders. Mega menus are UX Blocks assigned to menu items. The ThemeForest listing claims compatibility from WooCommerce 5.x through 10.x. For a small merchant, that bundle covered features other stores buy one plugin at a time.
It also won loyalty through restraint on price. No yearly fee, no tiers, no upsell wall. The Flatsome review covers the theme in full, including where it beats WoodMart and where it does not.
Classic, Site Builder, or neither: the three roads since September 30
Here is what changed. UX-Themes put a new product into beta: Flatsome Site Builder, a block-based builder plugin built on core WordPress blocks and theme.json, paired with a new Flatsome Block Theme. It is sold directly through flatsome.com, not ThemeForest, and it is billed yearly per site. The vendor says it is aiming for version 1.0 within about a month and that Classic customers get in first.
Road one: stay on Classic
Flatsome Classic 3.20.11 shipped on September 22, 2026. The vendor says Classic will keep getting WordPress and WooCommerce compatibility updates and critical fixes, and that moving to Site Builder is optional. Safe for now, though the promise covers compatibility and critical fixes, not new features.
Road two: rebuild on Site Builder
A beta product with real ambitions: a blocks library, forms, an SEO module, dynamic pricing and Flatsome MCP, which lets you drive the builder with your own AI agent. The pricing page lists a Classic migrator; the beta announcement calls the migration plugin planned. Those two pages disagree.
Road three: leave WordPress
Move the store to a custom Next.js build with your products, customers and URLs carried over. The most work up front, the least dependence on any one theme vendor's roadmap afterward.
Roads one and two both keep you on WordPress and WooCommerce. Road two also means rebuilding your pages, because UX Builder layouts do not turn into blocks by themselves. If you are going to redesign anyway, it is worth pricing road three before you commit.
Flatsome against Next.js, one row per store worry
The Flatsome column describes Classic as most stores run it: theme, child theme, UX Builder, WooCommerce and the plugins a real shop accumulates. Where Site Builder changes the answer, the cell says so. The same rows, filled in for every popular theme, live in the WordPress vs Next.js comparison center.
| Flatsome + plugins | Next.js build | Next.js + Athena CMS | |
|---|---|---|---|
| Performance | Lazy-loads images and backgrounds; WooCommerce scripts and UX Builder markup still load | Product and category pages prerendered, cart logic sent only where needed | Same storefront speed; editing adds nothing for shoppers |
| Core Web Vitals | Workable on Classic; vendor says Site Builder beta improves first paint and layout shift | Image sizes and slots reserved in code, so product grids do not jump | Same, and Argus flags a slow product page |
| Hosting requirements | PHP host with a database sized for WooCommerce orders and sessions | Static and serverless hosting plus a commerce back end | Same, with Athena holding products and orders |
| Security | Checkout, wp-admin and every Woo extension are entry points to patch | No WordPress login or plugin endpoints exposed | Same, with Aegis checking daily for intrusions |
| Plugin dependency | Theme covers store design; payments, shipping, SEO, cache stay plugins | Payment and shipping APIs called directly from code | Built-in store; no extension marketplace |
| Maintenance | Woo updates can flag Flatsome's template overrides as outdated | Dependencies upgraded and tested in a build | Same, with agents watching forms and checkout pages |
| Updates | Classic promised compatibility updates and critical fixes; the new work is Site Builder | Shipped on your schedule after preview | Content and products change without a code deploy |
| SEO | Docs cover Yoast, Rank Math and SEOPress; Site Builder adds an SEO module | Product metadata and canonical URLs set per route | Same, with Iris writing product titles and social cards |
| Schema | Product schema from WooCommerce and the SEO plugin, sometimes duplicated | Product, offer and review markup generated once, correctly | Same, fed by the product fields |
| Page speed | flatsome.com shows PageSpeed 98, labeled by the vendor 'Not a measured audit' | Fast by construction; measure it yourself in PageSpeed Insights | Same |
| Mobile performance | Separate Header Mobile settings; phones load the same theme and Woo scripts | Phone-sized product images via next/image | Same, with Picasso keeping every image sized and described |
| Custom development | Child theme and Woo template overrides, which need upkeep after updates | Custom bundles, quotes or B2B pricing written as features | Same, with fields designed around your catalog |
| CMS usability | UX Builder for pages, Theme Options in the Customizer, Woo screens for products | Needs a CMS or developer for changes | Products, pages and offers edited in one place with preview |
| Ecommerce | WooCommerce with Catalog Mode, quick view, mini-cart and shipping bars | Commerce service or custom checkout | Built-in store plus Stripe subscription billing |
| Scalability | Big catalogs and sales events lean on server power and object caching | Product pages served from a CDN; checkout scales separately | Same |
| Hosting cost | Store hosting tiers rise with orders and traffic | Usage-based; static pages are cheap to serve | Similar to a plain Next.js store |
| Development cost | $59 Classic license, or Site Builder from $44.50 for the first year | Highest up front: custom commerce work | Custom work, fixed quote after a free audit |
| Long-term maintenance | Classic includes six months of support; Site Builder renews yearly per site | Low and scheduled | Low, with routine checks run by agents |
| Content editing | UX Builder drag and drop; layouts stay tied to Flatsome | Through whatever CMS is attached | Plain fields and every version kept |
| Integrations | Docs cover WPML, Polylang and UberMenu; others via Woo extensions | Direct connections to ERP, inventory or shipping APIs | Same, plus agents acting on store data |
| API support | WooCommerce REST API for products; UX Builder layouts render only inside Flatsome | API routes built into the app | Same |
| Headless CMS capability | UX Builder pages cannot feed a headless front end cleanly | Works with any headless commerce or CMS | Athena is the headless store and CMS |
That PageSpeed row is not a joke at Flatsome's expense. The vendor labels its own score as not a measured audit, which is more candor than most theme sites manage. Measure your own store the same way you would any other, using the steps in the Flatsome speed guide.
Child theme, overrides and the commerce plugins Flatsome cannot replace
Flatsome removes plugins from the design side of a store. It cannot remove them from the commerce side. A typical live shop on Classic carries a child theme (included), WooCommerce, a payment gateway, a shipping or tax plugin, an SEO plugin, a caching layer, often a translation plugin like WPML, and sometimes UberMenu. Each one updates on its own day.
The overrides are the hidden cost. Flatsome ships its own copies of WooCommerce template files so the shop looks like Flatsome. When WooCommerce changes a template, the store shows a warning that the theme contains outdated copies, and the fix is to wait for a Flatsome release that matches. Any overrides you added in a child theme must be fixed by hand. The Flatsome WooCommerce guide shows where those files live.
Flatsome took the plugins out of the shop window. The stockroom is still full of them.
The four tickets Flatsome stores file most
- 1.Outdated WooCommerce template warnings after a Woo update, covered above. If checkout itself breaks, start with Flatsome WooCommerce checkout issues.
- 2."The purchase code is already registered on another site." Each install needs its own registration, so moving to a new domain or staging site means unregistering the old one at account.uxthemes.com. We untangle these under Flatsome update and registration problems.
- 3.Cache and minify plugins breaking layouts. The vendor's first troubleshooting step is to reset or disable all caching and minifying, which tells you how often it happens. Stale styles show up as Flatsome CSS not updating.
- 4.Missing Theme Options or a blank UX Builder. UX-Themes keeps a dedicated article for this one. Our checks are in UX Builder not loading.
Header and mobile menu quirks round out the list; see Flatsome mobile menu not working. Everything else is gathered in the Flatsome repair hub.
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.
- PicassoImages
- ApolloSite analysis
- AresCompetitor watch
- PrometheusContent holes
- AtlasPage depth and structure
- DelphiAI search visibility
and 12 more agents. Two come with Athena; the rest are monthly add-ons.
Licenses: one-time Classic, yearly Site Builder
Flatsome's pricing is now two systems. As of October 2026, Classic on ThemeForest costs $59 for a Regular License covering one end product, with six months of support and lifetime updates, or $2,950 for an Extended License when end users pay for the product. Refunds follow Envato's rules, which do not cover a change of mind.
Site Builder is sold directly with a 30-day money-back guarantee. The early-access prices are half off until October 14, 2026: $44.50 for one site (listed $89), $149.50 for five (listed $299) and $249.50 for ten (listed $499). The pricing page lists renewals at $45 per site per year. For a single store that is not much money. It is, however, a change in kind: a theme you used to own outright becomes one you rent. The Flatsome pricing page tracks both models.
Which road fits your store
When Flatsome is the better choice
- A boutique store with a few hundred products that already looks right on Classic
- An owner who likes arranging product pages in UX Builder without a developer
- A launch budget that fits a $59 license and a mid-tier host
- A simple WooCommerce setup: standard checkout, standard shipping, a handful of extensions
- A small team that edits banners, sales and collections daily and wants that control in-house
When Next.js is the better choice
- Paid traffic lands on product pages and every extra second lowers conversion
- Thousands of SKUs, or category and filter pages you want generated and indexed
- Wholesale pricing, quotes, configurators or subscriptions that strain WooCommerce extensions
- Inventory, ERP or marketplace feeds that must sync without a stack of connector plugins
- Holiday traffic spikes that currently mean upgrading the host every November
For the long version of the commerce argument, read WooCommerce vs Next.js ecommerce. Still deciding between themes instead? Compare Flatsome and Astra or Flatsome and Blocksy.
The UX Builder exit tax, and what Athena does with the store
Leaving Flatsome is a story of two kinds of data. Products, variations, customers and orders live in WooCommerce, and they move cleanly into a new store. Pages built in UX Builder are another matter: the layouts are proprietary and only render while Flatsome is active, so homepages, landing pages and UX Blocks are redesigned rather than exported. The Flatsome to Next.js guide and our WooCommerce migration notes cover the order of work. We keep your URLs or redirect every old one, product pages included.
On the other side sits Athena CMS, which includes e-commerce out of the box. Products, pages and offers are plain fields with a preview. Demeter drafts seasonal offers, Echo handles reviews, Picasso keeps product photos described and sized, and Argus watches for failing forms and slow pages. Agents draft; you approve.
Boutique, catalog, wholesale: where each store lands
- New store under a few hundred products: Flatsome Classic at $59 is still good value. Keep the plugin list short.
- Established Classic store, happy with it: stay. Watch Site Builder through its 1.0 release before rebuilding anything.
- Classic store due for a redesign anyway: price Site Builder and a Next.js rebuild side by side. Both mean redoing your pages.
- Store where speed, custom pricing or integrations decide revenue: Next.js with Athena.
- Agency running many client stores: note that Site Builder bills per site per year, then do the math.
Need a hand either way? Our Flatsome developers maintain Classic stores, and the WordPress to Next.js section lays out the alternative. Financing for ecommerce builds exists if a rebuild is the right call.
Questions people ask before they call
Not according to the vendor. UX-Themes says Classic will keep receiving WordPress and WooCommerce compatibility updates and critical fixes, and that moving to the new Site Builder is optional. Version 3.20.11 was released on September 22, 2026. The new block-based product, Site Builder, entered beta on September 30, 2026.
Not reliably yet. Flatsome's pricing page lists a Classic migrator among Site Builder features, while the beta announcement describes a migration plugin as planned. Until that ships and is proven, expect to rebuild key pages by hand. Products and orders in WooCommerce are unaffected either way.
Flatsome offers what it calls Smart Lazy Loading, and the vendor calls it the fastest multi-purpose theme on ThemeForest, but that is the vendor's claim. A WooCommerce page still loads theme, store and plugin scripts on each request. A Next.js store prerenders product pages and sends only what each page uses. Measure your own pages with the Flatsome slow website checklist.
UX-Themes allows one site registration per purchase code. If you moved domains or cloned the site to staging, unregister the old domain at account.uxthemes.com, then register the new one. A Regular License covers one end product, so a second store needs a second license.
It depends on catalog size, how many UX Builder pages need redesigning, and integrations like shipping, tax or inventory. Product data moves cleanly; layouts are rebuilt. We give a fixed quote after a free audit. The cost drivers are explained in WordPress to Next.js cost.
Keep reading
- Theme vs frameworkAstra vs Next.js: A Light Theme, a Heavy Stack and a Custom BuildAstra vs Next.js, row by row: the 2026 AI bundles, the 3-site Pro cap, Elementor and Spectra, real failure modes, and when Astra is still the smart buy.
- New owner, old questionKadence vs Next.js: A Block-First Theme Under New Owners, Against Custom CodeKadence vs Next.js after the Liquid Web shake-up: Kadence Blocks, the new $99 to $499 plans, known issues, and which businesses should stay or move.
- WordPress at its leanestGeneratePress vs Next.js: The Fairest Fight WordPress Can OfferGeneratePress vs Next.js, argued fairly: a sub-10kb theme, a $59 license for 500 sites, the coming template engine, and where a custom build still wins.
- A Customizer theme, weighedBlocksy vs Next.js: A Great Free Theme Against a Site With No Plugins at AllBlocksy vs Next.js compared on 22 rows: the free header builder, Companion and Pro, lifetime licenses, the 2.1.5x regressions and when to stay put.
- The Elementor stack, weighedHello Elementor vs Next.js: The Empty Theme and the Builder That Fills ItHello Elementor vs Next.js on 22 rows: the 6KB vs 30KB claims, Theme Builder dependency, Elementor's real weight, and when the builder is the right call.
- The developer's builderBricks Builder vs Next.js: The Best Case for Staying on WordPress, TestedBricks Builder vs Next.js on 22 rows: clean output, no jQuery, the $599 lifetime plan, 2.4 AI editing and its regressions, and where Next.js still wins.
- Everything in WordPress vs Next.jsSee the section
Pick your Flatsome road with real numbers
Tell us about your store. We will look at the catalog, the plugins and the pages, then tell you whether to stay on Classic, try Site Builder, or move to Next.js.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.