FTC/ASA Disclosure: Links in this post are affiliate links. At no additional cost to you, I will earn a commission if you purchase via my links. Thank you in advance for your support!
Flatsome has been one of the default answers to “what theme should I use for a WooCommerce shop?” for over a decade. On September 30, 2026, its maker UX-themes did something unusual for a bestseller: it opened a beta of a completely rebuilt product, Flatsome Site Builder, that ships with Flatsome MCP so AI agents can build pages alongside you. The theme most people know is now called Flatsome Classic, and it’s the one still sold on ThemeForest.
That split is why I’m covering Flatsome now. If you run or plan a WooCommerce store and you’re curious about AI-assisted site building, you’re really choosing between two products with one name. This review is based on the ThemeForest listing and changelog, UX-themes’ own Site Builder announcement, and recent independent reviews. It isn’t a hands-on build.
What you actually buy on ThemeForest
The ThemeForest item is Flatsome Classic, a multi-purpose WooCommerce theme with its own drag-and-drop page builder, UX Builder. At the time of writing, the listing showed:
- Price: $59 for a Regular License (ThemeForest item page, checked October 13, 2026).
- Sales: 270,489 (same page, same check).
- Current version: 3.20.11, released September 22, 2026, with a security fix for stored XSS in several theme behaviors.
- Included: future updates and 6 months of support from UX-themes. Extended support is sold separately by Envato.
At the time of writing, the listing also showed 8,153 reviews. I couldn’t confirm the average star rating from the page I could read, so I’m leaving that out rather than guessing.
What’s in the box: UX Builder, a child theme, demo content, Catalog Mode (hide cart and checkout for inquiry-only stores), WPML-ready translation files, and PSD assets. Product and slider images in the demos are not included.
The AI angle: Flatsome MCP lives in Site Builder, not Classic
This is the part that matters most if you came here from the AI side. In its announcement, UX-themes describes Flatsome MCP like this: it “exposes pages, blocks, global styles, forms, and media through the Model Context Protocol, so tools like Claude Code, Codex, and Cursor can read your site, build pages from real Flatsome blocks, and edit content safely with versioned writes.”
In plain terms: you could describe a landing page to an agent and have it assemble the page from the same blocks a human would use, instead of an AI spitting out raw HTML you then have to fix.
But Flatsome MCP is a Site Builder feature. It is not part of the Classic license sold on ThemeForest. UX-themes made that explicit when a ThemeForest buyer complained about paying extra for MCP. In its public reply on the item’s reviews page, the author wrote: “The licenses purchased here on ThemeForest are Flatsome Classic licenses. Nothing has changed with those licenses: there are no new recurring fees, no added restrictions, and you can continue using Flatsome Classic as before.” The same reply says Site Builder is “sold separately through flatsome.com” and that “the optional $45/year renewal applies only to continued updates and support for a Flatsome Site Builder license after its first year.”
So if your main reason for buying is “I want AI agents to build my store pages,” the ThemeForest purchase won’t get you that today.
Classic vs Site Builder, side by side
| Flatsome Classic (ThemeForest) | Flatsome Site Builder (flatsome.com) | |
|---|---|---|
| Status | Mature, current release 3.20.11 | Beta since September 30, 2026 |
| Builder | UX Builder, shortcode-based | Core WordPress blocks and theme.json |
| AI agents | No MCP | Flatsome MCP included |
| Payment | One-time license | Yearly renewal for updates and support after year one |
| Future of the product | Compatibility updates and critical fixes | Where new features go |
| Portability | Pages render only while Flatsome is active | Standard block content |
UX-themes says Classic “will always stay on ThemeForest, and it will keep getting updates for WordPress and WooCommerce compatibility, along with critical fixes.” Read that carefully: maintenance, not new features. The changelog backs up the maintenance part. Recent releases added WordPress 7.0 support and WooCommerce 10.8, 11 and 11.1 compatibility, and several were flagged as security releases.
Why Classic is still a reasonable buy for a store
Classic exists to sell things. Product grids, banners, category layouts, swatches, quick view, sticky add-to-cart, mini-cart options and free-shipping bars are built in rather than bolted on with extra plugins. WPJury summed it up this way: “Flatsome is worth buying if you want a polished WooCommerce storefront, a visual builder, and a large set of store-focused features without committing to a yearly theme subscription.”
The update record is the other quiet strength. Philip Barrett, who tested 3.20.10 on a wholesale store for LuxWP, put it well: “This is a maintenance release, not a dramatic rebuild. That is fine. On a WooCommerce site, boring updates are usually the ones I trust.”
The trade-offs nobody should skip
UX Builder lock-in
Classic stores your designed pages as Flatsome shortcodes. Switch themes later and your products, orders and customers stay in WooCommerce, but the pages you built need rebuilding. DataCram framed the choice neatly: 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.”
UX-themes says Site Builder will offer a migration plugin that converts UX Builder content to blocks. That’s promising, but it’s a plan, not a finished tool you can test today. Assume key pages will need rebuilding until it’s proven.
Speed depends on your setup
There’s an active r/Wordpress thread asking whether Flatsome is “really that slow,” and the honest answer is that it depends. LuxWP’s empty-page staging test measured more DOM elements, requests and page weight with the theme than on bare WordPress, and the reviewer called 3.20.10 “productive, flexible, and annoyingly wrapper-heavy.” He also notes the numbers are environment-specific. Hosting, caching, image sizes and WooCommerce plugins usually matter as much as the theme.
Site Builder is still beta
UX-themes’ own advice is clear: “This is a beta, so expect rough edges. Try it on a staging site.” Don’t move a store that has to take orders next week onto beta software.
Watch the official intro
UX-themes’ own getting-started video is short and shows the UX Builder workflow. It’s from the Flatsome 3.0 launch, so the interface has moved on since, but the core idea of dragging sections and product elements onto a live page is the same.
Who should buy Flatsome Classic
- You’re launching a conventional WooCommerce store and want to design shop pages visually without hiring a developer.
- You prefer a one-time license over a yearly theme bill.
- You’re fine with Flatsome being your long-term theme, or you’ll accept a rebuild if you ever leave.
- You want a store live soon and don’t need AI agents editing it.
Who should wait or skip
- Wait if AI-agent site building is the main attraction. Try the Site Builder beta on a staging copy instead, and make the call when it’s out of beta.
- Skip if you want native block editing and easy theme switching above everything else.
- Skip if you’re building a content site with no shop. You’d be paying for store features you won’t use.
- Skip if you want the leanest possible theme and don’t want to spend time on asset cleanup and cache testing.
JamoraquAI Take
I like that UX-themes didn’t just bolt an AI chatbox onto an old builder. Exposing real blocks and global styles to agents through MCP, with versioned writes, is the sensible way to let AI touch a live store. But that’s the future product, and it’s in beta.
What ThemeForest sells today is the proven one: a store-first theme with a long, steady update record and a one-time price. If you need a WooCommerce shop running now, Classic is still a solid pick, as long as you go in knowing your pages live in UX Builder and new features are heading to Site Builder. If you’re mainly here for AI-built pages, hold your money and test the beta on staging first.
FAQ
Does the ThemeForest version of Flatsome include Flatsome MCP?
No. According to UX-themes’ reply on ThemeForest, MCP belongs to Flatsome Site Builder, which is sold separately on flatsome.com. The ThemeForest license is Flatsome Classic.
Is Flatsome Classic being discontinued?
UX-themes says Classic will stay on ThemeForest and keep getting compatibility updates and critical fixes. New features are going to Site Builder.
Is there a subscription for Flatsome Classic?
No. The ThemeForest Regular License is a one-time purchase with future updates and 6 months of author support. The yearly renewal UX-themes mentions applies to Site Builder only.
Can I move my Classic pages to Site Builder later?
UX-themes says a migration plugin is coming that converts UX Builder content to blocks. Until it’s available and tested on a store like yours, plan for some rebuilding.
Is Flatsome slow?
Not inherently, but it isn’t minimal either. Independent tests show extra markup and requests compared with bare WordPress, so hosting, caching, images and plugin choices make a big difference.
Prices and figures are from the ThemeForest listing at the time of writing (October 13, 2026) and can change. Check the listing before you buy.
FTC/ASA Disclosure: Links in this post are affiliate links. At no additional cost to you, I will earn a commission if you purchase via my links.
