Storefront vs Next.js: What a WooCommerce Store Should Do Now

The theme that came in the WooCommerce box

Storefront was the safe pick for a decade. WooCommerce's own developers released it in 2014 to sit on top of their plugin, and it still does that job with very little fuss. The cart in the header updates itself. Product grids, the single product page and the checkout look the way WooCommerce intended, because the people who wrote WooCommerce styled them. It costs nothing, licenses nothing and runs on as many stores as you like. As of our October 2026 check, wordpress.org counts more than 90,000 active installs.

The code deserves credit too. Storefront grew from Underscores, a plain starter theme, and it exposes action hooks throughout its templates. A developer can rearrange header pieces or add a trust badge under the price from a child theme without touching the parent. Recent releases fixed real things: sale prices now meet AAA contrast, coupon errors are styled properly, and 4.6.2 stopped certain product pages timing out on WordPress 6.9. The full Storefront review covers the rest of the record.

Critical fixes only: what Storefront's own status file says

WooCommerce has been candid about this. A file in the Storefront GitHub repository, STOREFRONT_STATUS.md, still describes the theme as in active development, then narrows the phrase until little is left: critical bugs, bugs with broad impact, compatibility fixes and release-process work. Most enhancement requests and feature pull requests get closed. At our check the repository held about 93 open issues and 15 open pull requests. It is not archived. It is not growing either.

The headers tell the same story in smaller print. The README says Storefront was tested up to WordPress 6.5 and WooCommerce 8.8; style.css says 6.7. Current releases are WordPress 7.1.3 and WooCommerce 11.1.2. A stale header does not switch anything off. It means nobody has formally signed off on the combination you run, so your live store becomes the test bench unless you keep a staging copy.

WooCommerce's buying advice already leans the same way. Its February 2025 article on choosing a theme files Storefront under classic themes and says block themes allow much more customization without code. A feature request in the Storefront repository asks for exactly that: Site Editor control over the shop templates. Under the limits the status file sets, that kind of work is not on the table.

What actually sits under a Storefront shop

Nobody runs Storefront alone. The theme is a frame for WooCommerce, and WooCommerce is a frame for extensions: a payment gateway, shipping rates, tax, perhaps subscriptions, product add-ons and a reviews tool. Then the general WordPress crew moves in: search metadata, contact forms, page caching and backups, each from its own vendor. Storefront offers few design controls without code, a point the review summary on WooCommerce's own Marketplace page makes, so most stores also grow a child theme with a lengthening stylesheet and a functions.php file full of hook changes.

Look at what the theme itself sends to every visitor. Storefront enqueues its main style.css, an icons.css file, gutenberg-blocks.css, a navigation script and a homepage script, plus WooCommerce's cart-fragments script so the header cart stays current. Its Source Sans Pro font comes from fonts.googleapis.com rather than your own server, which means extra connections to Google before text can render in that font. None of this is outrageous. All of it is decided for you, and the Storefront speed guide shows which parts you can trim.

• The child theme holds every visual change, which is good practice and also the only place your design lives.
• template-homepage.php shapes the homepage when that template is assigned, so layout changes there often mean code edits rather than clicks.
• Extensions add their own templates to product, cart and account pages, each styled against a theme that no longer gets design updates. Our page on Storefront with WooCommerce shows how the pieces connect.

Twenty-two questions a store owner should ask, answered three ways

The left column is Storefront as shops actually run it: WooCommerce, a handful of extensions and a child theme. The middle is a custom Next.js store build. The right adds Athena CMS, the editing system and agent staff we put behind every site we deliver.

Pay attention to two rows. Ecommerce is Storefront's strongest line: if WooCommerce does everything your shop needs, the theme WooCommerce built is hard to beat on fit. Updates is its weakest, because the rest of the stack keeps moving while the theme stands still. For the broader store argument, see WooCommerce vs Next.js for ecommerce.

The van that still starts: who should keep driving Storefront

Plenty of shops should keep Storefront. The theme is not broken; it is finished, the way a reliable old delivery van is finished. Here is how we sort the two camps when a store owner asks which one they are in.

If you land in the left column, keep the theme current, keep a copy of your child theme somewhere safe, and watch Purple as it leaves beta. If the right column reads like your Monday morning, keep going.

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

Small frictions where an old theme meets a new stack

• Menus that misbehave on phones. Storefront has a separate Handheld Menu location and a JavaScript toggle; an unassigned location or a script conflict can leave visitors with nothing to tap. The Storefront mobile menu guide walks through the checks.
• Long dropdowns that grow a second scrollbar. Menus with many sub-items can produce double scroll lines and extra space. It is a reported GitHub issue, number 2222, with a CSS workaround offered rather than a release fix.
• Child theme CSS that refuses to show. Edits compete with caching plugins and the parent's load order. See Storefront CSS not updating.
• Shop pages knocked out of shape. WooCommerce templates, extension templates and Storefront's styles all touch the same pages. Start with Storefront WooCommerce layout broken or the missing header fix.
• Timeouts after a core update. WordPress 6.9 exposed a slow adjacent-product query that produced 504 errors on some product pages until 4.6.2 shipped. The next core change may find the next slow query.

When faults arrive faster than fixes, our WooCommerce repair service and theme repair team can steady the shop while you weigh the bigger decision. A checkout that will not complete is its own emergency, covered in WooCommerce checkout not working.

Your exits from Storefront, cheapest first

Storefront owners have more freedom than owners of most themes, because their store data lives in WooCommerce, not in the theme. Products, orders, customers and coupons stay put whichever road you take. The theme only owns the look, a few Customizer settings and whatever your child theme adds.

Leaving Storefront costs less than leaving a builder theme. There is no shortcode soup to decode and no proprietary layout format to translate. The real work sits in the extensions: each one that adds fields, emails or checkout steps has to become a built feature or a connected service. The Storefront to Next.js migration guide lists what moves cleanly, and moving WooCommerce to Next.js covers products, orders and redirects. Every product URL is kept or redirected to its new home.

A shopkeeper's view of Athena CMS

The usual objection to Next.js for a shop is practical: who adds the new spring line on a Saturday? With Athena CMS, the owner does. Products, pages and offers sit in plain fields, previewed exactly as they will publish, and every earlier version is kept, so a bad price edit can be rolled back to the version before it. The store is built in, and memberships can bill through Stripe subscriptions.

Then there are the agents. Picasso keeps product images described and sized. Demeter drafts seasonal offers. Echo works on reviews. Argus patrols for dead links, failing forms and pages that drag, so a dead product link gets caught before a customer finds it. Most agents draft for approval, so nothing reaches shoppers without your say. Set it beside a plugin stack in Athena vs WordPress, or read how Athena works.

Which kind of shop are you?

Torn between two cards? A free site audit looks at the store as it runs today and says plainly whether to stay, switch themes or rebuild, and WordPress financing spreads the cost of a rebuild. Rival shop themes face the same 22 rows in our comparison library, among them Flatsome and WoodMart.