Blocksy WooCommerce: Shop Extra, the Free Store Options and the 2.1.50 Product Page Break

Three packages, one storefront

A Blocksy store is not one download. The theme draws the pages. The free Blocksy Companion plugin, with 300,000+ active installs, carries many of the features people credit to the theme. Blocksy Pro extends Companion with the paid extensions, including Shop Extra. As of October 2026 the theme is at 2.1.58, released October 2, and Companion is at 2.1.58, released a day earlier. The matching numbers are not a coincidence, and they are the first rule of running a shop on Blocksy: update the pieces together, on a copy, before the live store sees them.

The upside of this design is real. Store features you never switch on do not run, and the free layer is generous enough that many small shops never buy Pro at all. For the full verdict on the theme, including its header builder and support record, read the Blocksy review.

The free shop, setting by setting

Once WooCommerce is active, Blocksy adds its own WooCommerce sections to the Customizer. The vendor's documentation names the controls below. Where the docs mark something as Pro, it is noted.

• WooCommerce General: styling for info, success and error messages; the star rating look; a Custom Quantity Input with two designs; product badges with a shape choice, sale badge placement and a custom sale value such as a percentage, plus out-of-stock labels.
• Account and checkout: the My Account page can show the customer's avatar, name and quick links. On checkout you can move the coupon form to the top and show product thumbnails in the order summary.
• Product Archives: a Page Title in Type 1 or Type 2, Columns and Rows, and a Card Design in three types: classic, an inbox style with grouped content, and a minimal card whose buttons appear on hover. Since Blocksy 2, every element inside a card can be reordered, hidden or styled.
• Single Product: a Product Title area in Type 1 or Type 2 that can show the title, excerpt, breadcrumbs and meta. The free gallery is the classic large image with thumbnails; three more gallery types are Pro.
• Header Cart element: six icons, a count badge, an optional cart total and a fly-out mini cart. Pro adds an off-canvas cart drawer with panel width, reveal side and Open Cart Automatically, which needs WooCommerce's AJAX add to cart switched on.

That is enough for a well-dressed catalog. What the free tier leaves out is the behavior shoppers notice: quick view, filters that slide in, swatches, wishlists. Those live in Shop Extra.

Shop Extra, module by module, and the plans that include it

Shop Extra, once called WooCommerce Extra, is a set of modules. You enable the extension under Blocksy > Extensions, then toggle each module on its own; settings appear in the Customizer only for modules that are on. Here is what the docs list, with the caveats worth knowing before you flip anything.

The Cart Reserved Timer deserves a second look. Because it reduces available stock the moment a limited item goes into a cart, a slow-browsing shopper can make a product look sold out to everyone else until the timer expires. For flash sales that is the point. For a small store with one of each item, it can cost a sale.

As of October 2026, Shop Extra is not in Personal ($69 a year or $199 lifetime, one site). It starts at Business ($99 a year or $299 lifetime, up to 10 sites) and is in Agency ($149 a year or $499 lifetime, unlimited sites). Staging and development domains do not count toward activations, and if an annual license lapses the store keeps working without updates or support. There is a 14-day refund window. Every tier is laid out in Blocksy pricing.

2.1.50: the update that moved the product gallery

In the 2.1.50 release, some store owners found their single product pages rearranged: the gallery overlapping the product details, or the details pushed below the images. The wordpress.org thread records that rolling back fixed it, and support asked for a live URL to investigate. A separate thread from the same release shows a fatal error on sites without WooCommerce at all, caused by a database migration calling an undefined function, blocksy_get_woo_single_layout_defaults(). Both point at the same part of the code: the new single product layout handling.

Product pages are where a layout bug costs money directly, because the gallery and the add to cart button are the page. A broken grid is ugly; a product page with the buy button pushed off screen on phones is a quiet revenue leak. Here is the order we would work in.

1. 1

   Confirm the version

   Appearance > Themes shows the theme version; Plugins shows Companion and Pro. Note all three before changing anything.

2. 2

   Reproduce on staging

   Copy the store, then check a simple product, a variable product, a product with many gallery images and one with a video, on desktop and a real phone.

3. 3

   Isolate the gallery

   Blocksy documents a filter, blocksy:woocommerce:product-view:use-default, that switches back to WooCommerce's built-in gallery. If the layout recovers with it on staging, the fault is in the gallery handling.

4. 4

   Roll back or update as a set

   Return theme and Companion to the last good pair, or move both to the newest release, so they never run at mismatched versions.

5. 5

   Report with a URL

   Support asked for a live URL in the 2.1.50 thread. A staging link with the problem showing gets a faster answer than a screenshot.

The step-by-step version for this exact symptom is Blocksy WooCommerce layout broken. If the whole site went sideways, start at Blocksy update broke my site.

What Blocksy leaves on your plugin list

Shop Extra replaces a surprising number of store plugins: filters, swatches, wishlists, compare, size guides and brands. That still leaves the parts of a store that are not about display.

• Payments: a gateway plugin for each provider you accept.
• Tax, shipping and subscriptions: WooCommerce settings for the simple cases; extensions for live rates, multistate tax and recurring billing. When renewals stall, see subscriptions not renewing.
• SEO, backups and security: none ships with Blocksy. Given how often agencies say Blocksy appears in weekly vulnerability lists, a security plugin and prompt updates are not optional.
• Local Google Fonts: a Pro extension on Blocksy, so free-tier stores that care about font privacy or speed need a plugin or a manual setup.
• Transactional email: an SMTP plugin, or receipts may never arrive. The order emails fix covers diagnosis.

The trap to avoid is duplication. If you turn on the Wish List module, remove the old wishlist plugin; if you use Variation Swatches, do not keep a second swatch plugin around. Two scripts fighting over the same variation form is how variations stop showing.

Where a Blocksy shop spends its milliseconds

Blocksy's defaults are kind to speed. Customizer > General Options > Performance sets Dynamic CSS Output to File, the recommended mode, so the theme's generated styles load as a cacheable stylesheet. No script in the 2.1.58 theme package declares a jQuery dependency. Unused Shop Extra modules stay off, which is the right way to sell features.

The costs arrive with the store itself. In the 2.1.58 source, Blocksy enqueues WooCommerce's cart fragments script whenever the header contains a Cart element, so the mini cart refresh runs an AJAX request on every page with that header. And no theme can rescue the cart, checkout and account pages from being rebuilt per visitor: they are personal, so WooCommerce keeps them out of page caches, and every visit there pays for the theme, Companion, Pro, WooCommerce and every other plugin.

The practical test takes ten minutes. Load a product page with the network panel open, filter for get_refreshed_fragments, then run a test checkout on a throttled phone profile and note where it stalls. The full tune-up order is on Blocksy speed, and our WordPress performance consulting team does this on live stores.

Other Blocksy worries store owners raise

• Custom header forms broke in 2.1.58. After that update, input elements were stripped from the Header Builder's HTML element on the front end, which broke one store's custom search form. If your header search vanished, that is the first suspect.
• Security list anxiety. Agencies note Blocksy appears in weekly vulnerability lists; staff reply that issues are resolved before they are published. Either way, the answer is the same: update promptly.
• Starter sites that will not import. Blocksy keeps a troubleshooting doc for stuck imports, and support says it cannot diagnose sites that are not publicly reachable.
• Styles that do not change. With CSS output set to File, a stale stylesheet in a cache can hide your edits. See Blocksy CSS not updating.
• Category menus missing on phones. For a store, the mobile menu is navigation to the catalog. Blocksy mobile menu not working has the checks.

When the cause is not obvious, the cross-theme WooCommerce layout broken checklist and a plugin conflict test narrow it fast. For a checkout that will not complete, go straight to checkout not working. Or hand it to us: WooCommerce website repair and theme repair cover Blocksy stores.

When the next version of the store is not a theme

Blocksy plus Shop Extra is one of the better-value ways to run a small or mid-sized WooCommerce catalog, and we say so to clients. The limits show when the store needs things no module covers: quotes, custom pricing, configurators, member-only catalogs, or a checkout that has to be fast on a phone in every season. At that point you are no longer choosing modules; you are choosing an architecture.

A Next.js store builds those features into one tested codebase, prerenders product pages and keeps checkout on a short server path. Every site we build includes Athena CMS with e-commerce built in. Compare the two honestly in Blocksy vs Next.js, then read WooCommerce to Next.js and Blocksy to Next.js for the move, or start with our ecommerce development page. More theme guides are in the WordPress themes section.