Are WooCommerce shortcodes deprecated? No, and here’s what’s actually happening in 2026

Summary

You read a blog post claiming WooCommerce shortcodes are dead. So you rip [woocommerce_my_account] off your account page and brace for a block that never arrives.

Meanwhile your working [products] grid runs fine, though you worry it will vanish in the next update. Neither reaction holds up. As of WooCommerce 11.0, released August 4, 2026, all 11 core shortcodes still work exactly as documented.

Introduction

The confusion has a real source. WooCommerce soft-deprecated a set of older product-grid blocks back in WooCommerce 9.5, replacing them with the newer Product Collection block. Somewhere between that change and today, blog posts and plugin changelogs started treating shortcodes and blocks as the same thing.

This guide separates the two clearly, then covers what the official docs and most competitor articles skip. You’ll get the complete attribute list for every core shortcode and an honest shortcode-versus-block call. You’ll also see how shortcodes behave in block themes and full site editing, plus fixes for eight documented failure modes.

Are WooCommerce shortcodes deprecated in 2026?

No, all 11 core WooCommerce shortcodes are fully supported in WooCommerce 11.0, released August 4, 2026. That release’s notes list zero shortcode-specific changes.

What actually changed is a set of older product-grid blocks, not the shortcodes themselves. WooCommerce soft-deprecated those blocks back in version 9.5, in favor of the newer Product Collection block.

One shortcode deserves a special note. [woocommerce_my_account] has no block-based alternative at all, per WooCommerce’s own documentation, so there’s no decision to make there yet.

What’s actually being deprecated (it isn’t the shortcodes)

The Product Collection block now replaces older grid blocks like Products by Category, Best Selling Products, and Products by Tag. WooCommerce announced the change in a Product Collection block announcement, framing it as a soft deprecation rather than a removal. Store owners who never touched those specific blocks have nothing to change.

Why the confusion started

Competitor articles and even WooCommerce’s own troubleshooting page use loose language that blurs shortcodes and blocks together. Some guides still write as if the classic editor, Gutenberg, and block themes are three separate worlds. The official shortcodes page sits under “Classic themes” and nudges readers toward blocks, without saying shortcodes still work fine elsewhere.

That framing is technically accurate but easy to misread. If you’re not planning a WooCommerce migration guide anytime soon, nothing here forces your hand.

What are the complete WooCommerce shortcodes and their attributes?

WooCommerce ships 11 core shortcodes, each with a documented attribute set, and every one still works exactly as built. Nothing on this list changed in WooCommerce 11.0.

Product display shortcodes

The workhorse is [products], which accepts limit, columns, orderby, order, category, tag, attribute, terms, visibility, ids, skus, and class. Category and tag values pull straight from your store’s product taxonomy, so slugs have to match exactly. Three special flags, on_sale="true", best_selling="true", and top_rated="true", can’t combine with the content attributes above.

[products limit="4" columns="4" orderby="popularity" category="apparel"]

[product_page] pulls a single product by id or sku. [product_category] and [product_categories] handle category grids. Both use category (required on the singular version), limit or per_page, columns, orderby, order, hide_empty, and parent.

[product_category category="hoodies" columns="3" orderby="date" order="DESC"]

[add_to_cart] and [add_to_cart_url] output a standalone buy button using id or sku, plus show_price, style, class, and quantity. [shop_messages] takes no attributes. It needs “Enable AJAX add to cart buttons on archives” turned off under WooCommerce > Settings > Products > General to display correctly.

How you configure these attributes also affects what’s crawlable on your shop pages. Virtina’s WooCommerce SEO guide covers that side of things if product visibility is a priority.

Cart, checkout and account shortcodes

[woocommerce_cart], [woocommerce_checkout], [woocommerce_my_account], and [woocommerce_order_tracking] take no attributes at all. Each renders a full page based on your settings under WooCommerce > Settings > Advanced > Page setup.

[woocommerce_my_account] is the one to flag plainly. It has no block-based alternative, so there’s nothing to switch to even if you wanted to. Readers building self-service features should see Virtina’s B2B customer portal guide for what’s possible beyond the default layout.

One bonus shortcode sits outside the official 11: [related_products] takes limit, columns, and orderby, and it doesn’t paginate. It’s documented on the same official page but isn’t part of the core list.

If you eventually need programmatic control beyond what these attributes offer, Virtina’s WooCommerce REST API guide picks up from here.

Every example above uses straight double quotes, not curly ones. Pasting from Word or Google Docs converts them automatically, and a curly quote breaks the shortcode with no visible error. More on that fix in the troubleshooting section below.

Should you use a WooCommerce shortcode or a block?

Use the block version by default for a new store. Fall back to the shortcode only when a payment gateway or extension hasn’t declared block compatibility.

When the block checkout is the right call

Blocks give you direct visual control inside the site editor: add trust badges, reorder fields, adjust copy, without a developer. Since WooCommerce 8.3, the Cart block and Checkout block became the default for new installs. Existing stores can switch anytime.

The switch is reversible. Select the block, click Transform in the toolbar, and choose “Classic Shortcode” to fall back instantly if something breaks.

That level of no-code control is exactly what Virtina’s WooCommerce customization guide covers in more depth.

When the shortcode is still the correct technical answer

Extension and payment gateway compatibility is the real deciding factor here, not nostalgia for the old checkout. The block checkout runs on React instead of the classic PHP hook system.

A gateway that hasn’t declared block support can silently drop off the block checkout. It may still work fine on the shortcode version.

WooCommerce developer Mike Jolley has said there are “no plans to phase out the classic cart and checkout in core.” That’s meant to protect stores that depend on older extensions or custom checkout code.

Official documentation also states plainly that in some cases the shortcode version has better extension compatibility. That’s WooCommerce acknowledging the shortcode path is sometimes the more reliable choice, not just a legacy fallback.

If page speed is the real concern behind this question, neither option is a documented performance advantage on its own. Virtina’s WooCommerce performance guide covers the levers that actually move the needle.

Do WooCommerce shortcodes work on block themes and full site editing?

Yes, WooCommerce shortcodes render normally on block themes and inside full site editing templates, with two narrow developer-facing exceptions. Neither exception is a shortcode bug specific to FSE.

The two things to actually watch for

First, the function wc_current_theme_is_fse_theme() was deprecated as of WooCommerce 9.9, in favor of WordPress core’s wp_is_block_theme(). It still works for now, but custom shortcode wrapper code checking theme type this way should switch before removal.

Second, a shortcode pasted into a block that doesn’t parse shortcodes will render as literal bracketed text. That includes some custom blocks and page-builder text fields. It’s the same root cause documented on classic themes, not something unique to block themes or full site editing.

Shortcodes render fine inside a Shortcode block or a Paragraph block in the block editor. They also work inside a template part in most current setups.

[woocommerce_order_tracking] is worth a specific mention here. It reads order data through WooCommerce’s own CRUD methods, the correct pattern for High-Performance Order Storage (HPOS). That means it isn’t directly affected by an HPOS migration.

Some third-party order-tracking plugins report issues even after declaring HPOS compatibility, according to one technical write-up on the topic. If you’re evaluating that migration separately, Virtina’s HPOS migration guide walks through readiness and rollout.

Why is your WooCommerce shortcode not working?

Most WooCommerce shortcode failures trace back to one of eight documented causes, and each one has a specific fix. Virtina’s WooCommerce bug fix guide covers store-wide issues if the problem turns out to be bigger than one shortcode.

Rendering and syntax failures

• 1. Shortcode renders as literal text on the page. Symptom: the bracketed text shows up exactly as typed instead of running. Cause: it’s wrapped in <pre> or <code> tags, or sits in a text field that doesn’t parse shortcodes. Fix: strip the wrapper tags in the Text/HTML view, or use a dedicated Shortcode widget instead.
• 2. Curly quotes break the shortcode silently. Symptom: a shortcode with attributes fails silently, while the same shortcode with no attributes still works. Cause: pasting from Word or Google Docs converts straight quotes into curly ones, which the shortcode parser rejects. Fix: retype the quotes directly in the WordPress editor, or use code view to force straight quotes.
• 3. [products skus="..."] returns nothing for a variable product. Symptom: the SKU clearly exists on the product edit screen, but the shortcode returns nothing. Cause: that SKU belongs to a product variation, and the shortcode only matches parent-level SKUs. Fix: pull the SKU from the parent product’s Inventory tab, not the individual variation.

Display and query bugs

• 4. [products] or [product_category] shows fewer products than expected. Symptom: a category with dozens of products displays only a handful, or none. Cause: one report documents a counting bug where the out-of-stock filter excludes items before the limit is applied. Fix: raise the limit to cover the full category, or disable “Hide out of stock items from the catalog” in WooCommerce > Settings > Products > Inventory.
• 5. [products ids="..."] fails with a very large ID list. Symptom: passing thousands of IDs returned “No products were found matching your selection” instead of a subset. Cause: logged as a confirmed bug on GitHub issue #31709, and the issue has since been closed. Fix: if you still see this on a current WooCommerce release, break large ID lists into batches, or query by category instead.

Cart, checkout, caching and widget failures

• 6. Cart or checkout renders blank or shows a stale cart. Symptom: the cart or checkout page loads blank, or shows another visitor’s contents. Cause: these pages are per-visitor and dynamic, so aggressive caching, including WooCommerce’s own transient cache, can serve stale results if exclusions aren’t set. Fix: exclude cart, checkout, and my-account URLs from every caching layer, then purge and retest. See Virtina’s Checkout troubleshooting guide for a deeper walkthrough.
• 7. Elementor 3.33.5 breaks cart or checkout JavaScript. Symptom: raw JavaScript appears as visible text, and quantity fields stop responding. Cause: a confirmed regression in Elementor version 3.33.5, reproduced on WooCommerce 10.4.2 and WordPress 6.9. Fix: downgrade Elementor to 3.33.4 or earlier until a patched release ships.
• 8. Shortcodes in a widget or template part don’t execute. Symptom: a shortcode pasted into a Text widget outputs as plain text instead of running. Cause: WordPress’s widget_text filter doesn’t run do_shortcode() on widget content by default. Fix: add a filter to run do_shortcode on widget_text, or use a block-based Shortcode widget instead.

People also ask

But doesn’t WooCommerce’s own site say to use blocks instead?

The official docs do steer new users toward blocks, but that’s a recommendation, not a deprecation notice. All 11 core shortcodes remain fully supported in WooCommerce 11.0, and nothing in the roadmap points to their removal.

Will shortcodes eventually be removed?

No announced removal date exists for any of the 11 core shortcodes. WooCommerce has stated it has no plans to phase out the classic cart and checkout from core. The other shortcodes carry no removal notice at all.

Is [products] safe to keep using on a high-traffic store?

Yes, [products] is a supported, documented shortcode with no performance warning attached in current WooCommerce documentation. Set a sensible limit and avoid unbounded queries, the same caching and query discipline you’d apply to any dynamic page.

Conclusion

Shortcodes are safe to keep using wherever they’re the right technical fit for your store. The real work isn’t migrating away from them out of fear. It’s verifying that your extensions and payment gateways have actually declared block compatibility before you switch anything.

If a shortcode is misbehaving, the fix is almost always one of the eight causes covered above. It’s rarely a sign the feature is dying.

Check the syntax, check the cache exclusions, check the plugin versions. You’ll usually find the answer in minutes, not a migration project.