Shopify's 2,048 Variants Stop at 250 in Liquid: A Furniture Guide

When a platform raises a limit, it rarely raises it everywhere at once. The admin, the APIs, the theme language and every app in between each have their own ceiling, and the lowest one is the one your customers hit. Before you build to a new limit, find out which layer still enforces the old one.

Shopify's variant limit is a clean example. In October 2025, Shopify raised the per-product limit from 100 variants to 2,048, but Liquid themes still see only the first 250. Kurt Elster and Paul Reda of Ethercycle covered the catch in episode #592 of the Unofficial Shopify Podcast (November 4, 2025). For furniture retailers, where one sofa can come in dozens of fabrics, several sizes and multiple leg finishes, it's the difference between a product that works and one that quietly breaks past option 250.

What Kurt and Paul said in episode #592

• 2,048 is the new admin limit. Paul confirmed products can now have 2,048 variants, up from 100.

• Up to 250 should just work. In his view, a store with 250 or fewer variants per product should behave the way it always did, because the Liquid ceiling moved from 100 to 250.

• Past 250, it depends on the theme. Liquid "only has access to the first 250." Paul tested four themes. Some handled more variants fine. On others, the swatches and selectors still appeared, but variant 251 and everything after it showed as unavailable, even though those variants existed.

• Themes need another way to load the rest. He said themes have to use the Storefront API to get variants beyond 250, so an older theme, or a newer one that only uses standard Liquid, won't handle them.

• Variant metafields don't come along for free. When a shopper changes variants, his themes receive a standard payload of variant data, and variant metafields aren't in it. His workaround was a snippet that writes his own JSON into the template for things like per-variant ship times, and he noted that approach won't work above 250 variants.

Kurt summed it up: 250 covers most of his use cases, and going past it turns a Liquid problem into a JavaScript-and-API one.

What Shopify's documentation says

The episode matches Shopify's own docs, with one useful addition.

• The limit change. Shopify's changelog entry from October 15, 2025 confirms the 2,048 limit for all merchants and warns that apps not using the current GraphQL product APIs "may have a downgraded or broken experience" on products with more than 100 variants.

• The Liquid ceiling. Shopify's theme guide, Support high-variant products, says product.variants returns a maximum of 250 variants and tells theme developers to audit any code that assumes every variant is present. It points out that a loop over product.variants that builds a hidden variant select only iterates through the first 250, while simple checks such as product.variants.first still work.

• Shopify's recommended fix. The same guide introduces the product_option_value Liquid object and an option_values URL parameter, so a theme can load only the variants relevant to the shopper's current selection instead of all of them. That's a Liquid-native path in addition to the Storefront API approach Paul described.

• Three options per product. Shopify's help center says each product can have up to three options. For more than three options or more than 2,048 variants, it points to apps or line item properties.

Why furniture hits 250 sooner than you'd think

Here's a hypothetical upholstered sectional: 3 configurations, 30 fabrics and 3 leg finishes. That's 270 variants, already past the Liquid ceiling, and it uses all three of the options Shopify allows. Add a second cushion type and you're out of options entirely, so something has to be combined or moved into separate products.

That's why I treat the option model as a business decision, not a theme detail. On a furniture replatforming project in 2025, before any theme work started, we compiled the variant options used across each STORIS product category from the old platform's attribute export and the STORIS export. Later that year, the same project ran into a question every furniture catalog faces: should ERP fabric and size values be stitched into the product title automatically? We recommended against it. Descriptors that vary by variant, like size, belong in options. A descriptor shared by every variant, like a single fabric, can go in the title. And naming stays the merchandiser's job, with the STORIS fields shown alongside as reference. How options are modeled affects the theme, the ERP sync, filtering and how products appear in search.

Where variant data breaks in practice

Paul's metafield point matches what we've seen. Variant-level data is second-class in more places than the theme:

• Variant-change scripts can overwrite what Liquid rendered. On a furniture retailer's theme, the variant-change JavaScript replaced a custom showroom availability message with a generic "Sold out" label. Our fix read the label from the server-rendered product form in the section response instead of a hardcoded string. We wrote it up in keeping custom unavailable messages through variant changes. Reading variant-specific content from section-rendered markup, rather than from a JSON blob of every variant, is also the pattern that fits Shopify's high-variant guidance. Test it on your own theme before relying on it.

• Liquid loops over variants share the same ceiling. In September 2026, a retailer asked us to show products with a "stocking item" variant metafield first in search results. Shopify search can't sort on a variant metafield on the server, so a Liquid approach has to loop through each product's variants on the current results page, and that loop only sees the first 250 per product. The options we laid out were to roll the flag up to a product-level metafield or to sort in a custom search service.

• Variant metafield edits can miss your sync. In January 2026, our testing on a client's middleware found that editing only a variant metafield did not fire the product update webhook the sync depended on, while changing a standard field did. If your ERP integration relies on that webhook, variant metafield changes may never arrive. That's one reason we include variant handling in every Shopify and STORIS integration review.

A configuration checklist for furniture catalogs

1. Count the worst case. Multiply options for your most configurable products before import, not after.

2. Search the theme. Look for every product.variants loop, filter or JSON dump, and check each against Shopify's high-variant guide.

3. Test variant 251. On a staging theme, select a variant past 250, confirm it shows as available, add it to the cart and check out.

4. Move variant-specific display data. Render it in section markup or fetch it on demand instead of depending on the default variant-change payload.

5. Audit apps and middleware. Confirm that reviews, search, merchandising apps and your ERP sync use Shopify's current GraphQL product APIs, as the changelog warns.

6. Decide what isn't a variant. Separate products by fabric grade, or line item properties for customer's-own-material orders, can beat a 900-variant product. Keep in mind that a line item property isn't an inventory-tracked variant.

7. Keep variant data honest across systems. Price, availability and lead time per variant should match what the ERP will actually promise.

My opinion: most furniture retailers shouldn't rush to 2,048. Model options around how customers actually choose, keep most products under 250, and reserve high-variant products for the few that truly need it, with a theme that's been tested for them. When a product does need the full range, plan the theme, apps and ERP sync together. That planning is the part we spend the most time on in Shopify development for complex catalogs.

FAQ

Will my store break if a product has more than 250 variants?

Not necessarily. Paul Reda's tests in #592 found some themes handled it and others showed later variants as unavailable. Shopify's guide explains why: product.variants stops at 250. Test your own theme before importing.

Do I need a headless storefront to support 2,048 variants?

No. Shopify's theme guide offers a Liquid path through the product_option_value object and the option_values URL parameter, and themes can also call the Storefront API. Headless storefronts already load variants through the Storefront API, but that alone isn't a reason to go headless.

Does the variant limit affect my ERP integration?

It can. Shopify's changelog warns that apps not using its current GraphQL product APIs may break past 100 variants, and that includes custom middleware. Variant-level metafields and webhooks also need specific testing.

How we know

This article summarizes the variant-limit segment of episode #592 from its published transcript and checks it against Shopify's changelog, theme documentation and help center, linked below. The theme test results are Paul Reda's. We didn't repeat his four-theme test. The Endertech examples come from our project work in 2025 and 2026, described without client names. The show is hosted by Kurt Elster of Ethercycle, and the hosts also sell a gift-with-purchase app, Promo Party Pro, which isn't a topic of this episode.

Last reviewed: October 23, 2026.

Limits

This article doesn't report our own test of a product past 250 variants, and it doesn't claim performance or conversion results for high-variant products. Shopify's theme APIs and webhook behavior change. Check the current documentation for your theme architecture before you commit to an option model.

Sources

• What's New in Shopify: November 2025, Unofficial Shopify Podcast #592, November 4, 2025 (accessed October 23, 2026).

• The product variant limit is now 2048 for all merchants, Shopify developer changelog, October 15, 2025 (accessed October 23, 2026).

• Support high-variant products, Shopify developer documentation (accessed October 23, 2026).

• Adding variants, Shopify Help Center (accessed October 23, 2026).

• More To Sell, Less To Manage: Introducing 2,048 Product Variants on Shopify, Tim Lombardo, Shopify, October 15, 2025 (accessed October 23, 2026).

Build to the ceiling that actually applies

The 2,048 number is real, but the 250 number is the one your theme has to respect. If your furniture catalog is heading past it, or your ERP sync was written for the 100-variant world, talk with Endertech about your option model. Our furniture ecommerce page covers how we approach catalog, theme and ERP work together.