Neve WooCommerce Layout Broken: Work Out Who Is Drawing the Store

Shelves out of line: how a Neve store comes apart

Store layouts rarely fail everywhere at once. One template breaks, or one device, and the pattern is the best clue you have. Check the shop page, a category, a single product, the cart and the checkout, on a desktop and a phone, logged out, and note which of these you see.

• Shop columns ignore the number you set, or products stack one per row on a wide screen.
• On phones, the filter icon above the products does nothing, or the shop sidebar lands beneath the grid.
• Cart or checkout looks nothing like the Checkout Style chosen in the Customizer.
• Quick view, wishlist, comparison or variation swatches vanished after an update or a renewal date passed.
• Product pages built in Elementor lost Neve's breadcrumbs, spacing and sidebar.
• The product gallery sits in an odd spot, or the Exclusive Products carousel stays a still row.

What free Neve does to a store page, and when it steps aside

With WooCommerce active, Neve's store module wraps shop content in its own containers, moves the breadcrumbs and sorting control into its own shop header, and replaces WooCommerce's sidebar with a widget area called Shop Sidebar. It also changes WooCommerce's default Products per row from 4 to 3. Sidebar placement lives under Customize > Global > Content / Sidebar; switch on Enable Advanced Options there and Shop / Archive and Single Product get layouts of their own. When the Shop Sidebar holds widgets and sits left or right, Neve adds a filter toggle for small screens.

Two files carry the store's look and behavior. woocommerce.min.css, about 39 KB, loads on every page while WooCommerce is active, articles included, except pages using Elementor's checkout widget. shop.js, about 33 KB, loads asynchronously only on WooCommerce pages such as the shop, categories and products, not on the cart or checkout. It wires up the phone filter toggle and the Exclusive Products carousel once the browser's load event fires. When WooCommerce's setup tool creates the cart, checkout and My Account pages, Neve marks them full width.

Booster, Sparks and settings that only apply sometimes

The WooCommerce Booster comes with Neve Pro's Business and Agency plans, $149 and $259 for the first year and $299 and $519 at renewal as of October 2026. It is switched on under Neve > Dashboard > Settings > Manage Modules. Themeisle's documentation states that it requires the Sparks plugin, which supplies quick view, wishlist, the comparison table, variation swatches, Advanced Reviews, the product tabs manager, custom thank-you pages and announcement bars. Without Sparks active and current, those features have nothing to run on. The Booster's own settings sit in three Customizer sections:

• Customize > WooCommerce > Product Catalog: Products per row (up to 6), products per page, Grid or List cards, image hover effects, element order and sale tag styling.
• Customize > WooCommerce > Single Product: Gallery Layout with images to the left or bottom, tabs, Sticky Add to Cart, upsells and recently viewed products, next to the free theme's Exclusive Products option.
• Customize > WooCommerce > Cart Page and Checkout: Checkout Style with Standard, Vertical or Stepped layouts, for shortcode-based pages only.

That last qualifier causes more confusion than anything else on a Neve store. Themeisle's documentation says a cart or checkout built from WooCommerce blocks is edited on the page itself, and the Customizer settings do not apply to it. WooCommerce has created block-based cart and checkout pages on new installs since version 8.3, so an owner can choose Stepped, publish, and watch nothing happen. The general mechanics are in WooCommerce layout broken.

Seven causes on a Neve store, most likely first

Version history matters as well. Neve's changelog lists a fix for a single product gallery layout issue (4.2.2), for a Related Products slider that stayed a plain grid on products without gallery images (4.2.10), and for mobile off-canvas carts that would not open after adding a product (4.2.12). If one of those matches, update Neve on staging before changing anything else. A license that will not reactivate after a lapse has its own checklist in our Neve Pro license guide.

Rebuilding the Neve store layout on staging

1. 1

   Clone the shop before touching it

   Work on a staging copy with caching off for cart and checkout. A live store taking orders is the wrong place to discover which plugin owns the checkout.

2. 2

   Record every version

   Write down Neve, Neve Pro, Sparks, WooCommerce and any builder version. Mismatched releases explain a surprising share of store faults.

3. 3

   Name the owner of each page

   For the shop, a product, the cart and the checkout, decide whether Neve, an Elementor Pro template or WooCommerce blocks draws it. Edit each page once to see.

4. 4

   Fix settings where the owner reads them

   Block checkout is styled in the block editor. Shortcode checkout follows the Customizer. Elementor templates follow their own widget settings, so a Neve option will not move them.

5. 5

   Restore the Booster's foundations

   Activate and update Sparks, confirm the Neve Pro license, and check the module under Manage Modules. Then reopen Product Catalog and Single Product and save once.

6. 6

   Exempt the store scripts

   Exclude shop.js and Neve's frontend.js from JavaScript delay and combine, purge, and test the filter icon and Exclusive Products carousel on a real phone.

7. 7

   Clear old overrides and test a purchase

   Update outdated templates in the child theme's woocommerce folder, purge every cache, then place a test order from product page to confirmation before pushing live.

Keeping a Neve shop in shape after updates

• Update Neve, Neve Pro and Sparks together on staging, then WooCommerce, and look at four templates after each.
• Pick one owner per page type and write it down. A product page half in Neve and half in Elementor breaks in both directions.
• Keep child theme template overrides to the bare minimum; each is a file someone must update by hand.
• Put the Neve Pro renewal date in the calendar, since store features are tied to the license.
• Never cache cart, checkout or account pages, and confirm your optimizer agrees.

When the layout is fine but orders fail, the fault is elsewhere: see WooCommerce checkout not working and variations not showing. Neve-specific neighbors include a mobile menu that ignores taps, styles that will not update and an update that broke the layout. The Neve speed guide explains how to keep store CSS off pages that never show a product.

When the store has more owners than the owner

A product page on a typical Neve store is drawn by WooCommerce's templates, restyled by Neve, extended by Neve Pro and Sparks, sometimes replaced by an Elementor template, and rewritten again by an optimizer. Each vendor updates on its own day. For a small catalog that arrangement works, and our Neve review says so plainly: the Business plan's Booster covers what many small shops need. Our Neve pricing breakdown totals what that stack costs per year.

Five vendors can draw one product page, and each of them thinks it is in charge.

Stores that need custom pricing, fast product pages on phones or a checkout that never surprises anyone can outgrow the arrangement. A Next.js build puts the shop in one tested codebase, and Athena CMS includes built-in e-commerce with plain fields for products. WooCommerce vs Next.js, Neve vs Next.js, moving WooCommerce to Next.js and the Neve to Next.js guide lay out the trade. If you are staying, our WooCommerce repair and WordPress theme repair teams fix the store as it is, and the Neve repair hub and troubleshooting section cover the rest.