Theme review: Flatsome
Flatsome Theme Review (2026): Classic, the Site Builder Beta and Which One a Store Should Buy
Flatsome has sold 270,401 copies to store owners, and for a small WooCommerce shop it still earns the sale. This month it also became two products under one name: a one-time Classic license and a yearly, block-based Site Builder in beta. We review both, so you pay for the right one.
October 9, 2026 · 11 min read
The short answer
Flatsome Classic is a strong, cheap choice for a small to mid-sized WooCommerce store whose owner wants to design shop pages in UX Builder, at $59 once as of October 2026. The new Site Builder is promising but in beta. Skip both if your store needs custom pricing, heavy integrations or a speed-first rebuild.
On this page
- Two Flatsomes, one maker in Norway
- Scorecard: Classic against the beta, row by row
- Designing the shop in UX Builder
- Checkout, catalog, header: the store owner's tour
- Fifty-nine dollars once, or a bill every year
- Speed and search: read the labels on the scores
- Where Flatsome stores get stuck, and where to start
- Which stores should buy Flatsome, and which should not
Two Flatsomes, one maker in Norway
Flatsome is made by UX Themes AS, a company registered in Ås, Norway, that has sold the theme on ThemeForest since roughly 2013; the listing says it was created 13 years ago. The maker has not changed hands. What changed is the product line. On September 30, 2026, UX-Themes opened a beta of Flatsome Site Builder, and the original theme took a new surname: Flatsome Classic.
Flatsome Classic
The theme most stores run today. Version 3.20.11, released September 22, 2026. Its own front-end drag-and-drop UX Builder, reusable UX Blocks and Theme Options in the Customizer. Sold on ThemeForest as a one-time license. The vendor says Classic stays on sale and keeps receiving compatibility releases for new WordPress and WooCommerce versions, plus critical fixes.
Flatsome Site Builder (beta)
A block-based builder plugin built on core WordPress blocks and theme.json, paired with a new Flatsome Block Theme. Sold only on flatsome.com with yearly per-site pricing. Plans bundle a blocks library, forms, dynamic pricing, an SEO module and Flatsome MCP, which lets an owner drive the site with an AI agent such as Claude or ChatGPT.
The announcement is frank about the beta: expect rough edges, and try it on a staging site. That is good advice, and it shapes every verdict on this page. If you are buying today for a store that has to take orders next week, you are buying Classic. If you are planning a rebuild for next year, Site Builder belongs on the shortlist.
Scorecard: Classic against the beta, row by row
| Flatsome Classic | Site Builder beta | |
|---|---|---|
| Speed approach | Smart Lazy Loading on images and backgrounds; the rest depends on host, cache and plugins | Vendor promises faster first paint and less layout shift; not yet measured by us |
| Ease of setup | Quick: UX Builder is learned in a day, Theme Options are spread across panels | Familiar to anyone who knows WordPress blocks; beta gaps likely |
| Design flexibility | High inside Flatsome, but layouts only render while Flatsome is active | High, on standard blocks that outlive the product |
| WooCommerce | The reason to buy: shop, product, cart and checkout design plus Catalog Mode | WooCommerce blocks, mini-carts, quick view, free-shipping bars, dynamic pricing |
| Builder fit | UX Builder is the builder; the vendor pages do not mention Elementor | Native blocks; nothing extra to bolt on |
| SEO | Leans on Yoast, Rank Math or SEOPress, all covered in the docs | Includes its own SEO module |
| License value | Excellent: $59 once for one store | Cheap per site, but billed every year |
| Support and ownership | Six months of support; maintenance promised, new features go elsewhere | Where the vendor's new work goes; 30-day refund |
| Long-term risk | Moderate: a maintained product whose future is somebody else | Moderate: beta software with an unsettled migration story |
The pattern is plain once it sits in two columns. Classic is the safer purchase and the riskier asset: cheap, proven and supported for compatibility, but holding your pages in a format nothing else reads. Site Builder is the riskier purchase and the safer asset: young and subscription-priced, with content stored as ordinary blocks that any future WordPress theme can open.
Designing the shop in UX Builder
Setup on Classic starts with Theme Options in the Customizer: header, footer, colors, typography and shop layout. Page design happens in UX Builder, a front-end editor where you drag sections, rows, banners and product grids onto the live page and see the result at once. Repeated pieces become UX Blocks, saved once and placed wherever they are needed, including inside menus. A child theme comes in the download, which is where any custom code belongs.
Store owners like UX Builder for one reason above all: it was built for selling. Product grids, banners and category layouts are first-class elements rather than add-ons from a third-party pack. The cost of that convenience is stored in the database. UX Builder saves pages as Flatsome shortcodes, and those render only while Flatsome is the active theme. Switching themes later means rebuilding those pages, whatever you switch to.
Page builders and plugins Flatsome expects
- Gutenberg: the ThemeForest listing marks Classic as Gutenberg optimized, and Site Builder is built entirely on blocks.
- Elementor: neither the listing nor flatsome.com mentions it. Plan a Flatsome store around UX Builder, not a second builder layered on top.
- SEO plugins: the docs cover Yoast, Rank Math and SEOPress.
- Translation: WPML and Polylang have their own integration articles, which matters for stores selling across languages.
- Menus: UberMenu is documented, though Flatsome's own UX Block mega menus cover most stores.
If UX Builder will not open, or Theme Options have vanished from the Customizer, UX-Themes treats it as common enough to keep a dedicated help article. Our own checklist is at UX Builder not loading.
Checkout, catalog, header: the store owner's tour
Flatsome is a shop theme before it is anything else. The ThemeForest listing claims compatibility with WooCommerce 5.x through 10.x. Catalog Mode hides the cart and checkout for businesses that take inquiries instead of payments. The vendor describes designing product, shop, cart and checkout pages, with mini-carts, quick view and free-shipping bars, features many stores otherwise buy as separate plugins. Settings by name, and the conflicts they cause, are covered in Flatsome with WooCommerce.
There is a maintenance cost built into that polish. Flatsome ships its own versions of WooCommerce template files to draw the store its way. When WooCommerce revises a template, the status screen warns that the theme carries outdated copies until a matching Flatsome release arrives, and any overrides added in a child theme have to be brought up to date by hand. It is routine, and it is also the reason a store owner should never be more than a release or two behind.
Headers and the mobile menu
The header is built in Theme Options > Header, with a separate Header Mobile panel, and the elements inside the mobile sidebar menu are switched on and off there too. A different menu can be assigned to phones. Since version 3.13.0, mega menus are UX Blocks attached to menu items, which gives a store full design control over a department menu without another plugin. When a header disappears or the hamburger stops responding, start with Flatsome header not showing and Flatsome mobile menu not working.
Fifty-nine dollars once, or a bill every year
As of October 2026, a Classic Regular License on ThemeForest costs $59 for one end product, with six months of support from UX-Themes and lifetime updates. An Extended License, for an end product your customers pay for, costs $2,950. UX-Themes also enforces one purchase code per registered site, so a second store means a second license and a domain move means unregistering the old site at account.uxthemes.com first. Refunds follow Envato rules, which exclude a change of mind.
Site Builder is sold directly with a 30-day money-back guarantee. Early-access prices run at half off until October 14, 2026: $44.50 for one site (listed at $89), $149.50 for five ($299) and $249.50 for ten ($499). The pricing page lists renewals at $45 per site per year. For a single store that is small money. For an agency with forty client stores on Classic, the move from one payment to a yearly per-site fee changes the math, and the Flatsome pricing page works through both cases.
Speed and search: read the labels on the scores
UX-Themes calls Flatsome the fastest multi-purpose theme on ThemeForest. Its homepage shows a mobile PageSpeed score of 98 and a GTmetrix A, and labels them, to its credit, as not a measured audit. The verifiable feature is Smart Lazy Loading, which the vendor says delays images and backgrounds until they are needed and which its performance demo says is switched on under Advanced settings. For Site Builder, the vendor says mobile and desktop page speed is up by a wide margin, with better Core Web Vitals out of the box. Both are claims until they are measured on your own product pages.
On a live store the theme is rarely the slowest part. WooCommerce scripts, payment widgets, review apps, tracking pixels and oversized product photos usually are. The vendor's first troubleshooting step for odd behavior is to reset or disable every cache and minify plugin, which tells you how often optimization layers fight the theme. Our Flatsome speed guide covers the settings that matter, Flatsome slow website is the repair checklist, and Core Web Vitals by theme shows how to judge the result.
On search, Classic stays out of the way and lets your SEO plugin handle titles, product schema and sitemaps. That is the right division of labor, with one caution: WooCommerce and the SEO plugin can both print product markup, so check a product page in a structured data tester after setup. Site Builder adds its own SEO module, which we have not tested. Category pages tend to be a store's strongest search assets, so give them real copy, not just a product grid.
Where Flatsome stores get stuck, and where to start
| First thing to check | Our guide | |
|---|---|---|
| Outdated WooCommerce template warning | Whether a Flatsome release supports your WooCommerce version, then any child theme overrides | Flatsome checkout issues |
| 'Purchase code already registered on another site' | Which domain the code is registered to at account.uxthemes.com | Update and registration problems |
| Styles stuck or layout scrambled after optimizing | Cache and minify plugins; the vendor says to switch them all off first | Flatsome CSS not updating |
| Wrong or missing typefaces | Caching and optimization plugins, before anyone touches Theme Options | Flatsome fonts not loading |
| Blank UX Builder or missing Theme Options | The vendor keeps a dedicated help article for this one; start there | UX Builder not loading |
Every one of these has a known fix, and most take an hour when the store is on staging and the person fixing it knows Flatsome. The full set sits in the Flatsome repair hub. Our Flatsome developers maintain Classic stores, test the Site Builder beta on copies, and handle the template overrides nobody else wants to open.
A theme can dress the store. WooCommerce and its plugins still run it.
Which stores should buy Flatsome, and which should not
Buy Classic
A new or growing store with a catalog in the hundreds, an owner who wants to arrange product pages without a developer, and a budget that likes $59 once. Keep the plugin list short and stay current on releases.
Pilot Site Builder
A store planning a redesign in the next year that wants to stay on WordPress and get its pages onto standard blocks. Test on staging now, decide at version 1.0.
Skip Flatsome
A store that wants Elementor as its builder, a brochure site with no shop, or an agency that dislikes per-site yearly fees for the long run.
Skip WordPress
A store where wholesale pricing, quotes, subscriptions, ERP sync or paid traffic decide revenue, and where every plugin is another thing to reconcile.
Against other store themes, WoodMart vs Flatsome is the closest fight, and the WoodMart review covers the rival in full. For a lighter general-purpose base, compare Flatsome vs Astra and Flatsome vs Blocksy; for the free WooCommerce default, read the Storefront review. The rest of the matchups live under theme comparisons, and the full roster is in our WordPress theme reviews.
Leaving Flatsome is a two-part job: WooCommerce data moves cleanly, UX Builder pages get rebuilt. Flatsome vs Next.js weighs the three roads, and Flatsome to Next.js covers products, orders and every /product/ URL. Our Next.js stores run on Athena CMS, with built-in e-commerce, plain fields and every version kept. A free site audit tells you which road is cheaper for your store.
Questions people ask before they call
For a small to mid-sized WooCommerce store, yes. Flatsome Classic costs $59 once as of October 2026, designs shop, product, cart and checkout pages in UX Builder, and the vendor says it will keep getting compatibility releases and critical fixes. Buy it knowing that new features now go to the block-based Site Builder, and that UX Builder pages only render inside Flatsome.
Classic is the original theme with its own UX Builder, sold once on ThemeForest. Site Builder, in beta since September 30, 2026, is a block-based builder plugin with a new Flatsome Block Theme, sold yearly per site on flatsome.com. Classic stores pages as Flatsome shortcodes; Site Builder stores them as standard WordPress blocks.
Not with confidence yet. The pricing page lists a Classic migrator among Site Builder features, while the beta announcement says a migration plugin is planned. Until it ships and is proven on stores like yours, assume your key pages will be rebuilt. Products, orders and customers live in WooCommerce and are not affected by the switch.
Flatsome's own pages and its ThemeForest listing do not mention Elementor, so we would not plan a store around that pairing. Flatsome ships its own builder, UX Builder, and its new Site Builder runs on native WordPress blocks. If Elementor is a requirement, a theme built for it is the better starting point.
It is neutral in a good way. Classic leaves titles, sitemaps and product schema to Yoast, Rank Math or SEOPress, all covered in its docs, and Site Builder adds its own SEO module. Speed matters more than the theme here, so read the Flatsome speed guide and check product pages for duplicate structured data.
Keep reading
- Flatsome store guideFlatsome WooCommerce Setup: Catalog Mode, Custom Product Pages and the Store Settings That MatterFlatsome WooCommerce settings by name: Catalog Mode, quick view, custom product layouts, outdated template warnings, cart speed, and the Site Builder beta.
- Two Flatsomes, two billsFlatsome Price in 2026: $59 Once for Classic, or a Yearly Site Builder PlanFlatsome Classic is $59 once. Site Builder runs $44.50 to $249.50 until October 14, 2026, then $89 to $499 a year. Renewals, refunds and a store's real bill.
- ThemeForest heavyweightsWoodMart vs Flatsome: The Two ThemeForest Store Giants, WeighedWoodMart vs Flatsome for WooCommerce: built-in store features, server demands, builder choice, ThemeForest prices as of October 2026, and which fits.
- Flatsome developmentFlatsome Developer for WooCommerce Stores Facing the Classic or Site Builder ChoiceA Flatsome developer for WooCommerce stores on Classic and UX Builder, with a careful plan for the new Flatsome Site Builder beta. Fixed quote after an audit.
- Flatsome on phonesFlatsome Mobile Menu Not Working: Why the Sidebar Stays ShutFlatsome mobile menu not working? Check script optimizers, the Nav Icon, Menu Elements and the Main Menu - Mobile location, in that order, then fix it.
- Flatsome performanceFlatsome Speed Optimization: Product Grids, Lazy Loading and the Uncacheable CheckoutFlatsome speed optimization for store owners: Smart Lazy Loading, local fonts, UX Builder sections, cart and checkout that no cache can hold, in order.
- Everything in WordPress ThemesSee the section
Get a straight answer on your Flatsome store
Tell us about your store. We check the Flatsome version, registration, template overrides, plugins and speed, then tell you whether to stay on Classic, test Site Builder or move, with a fixed quote if work is needed.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.