Shopify Limitations: 12 Platform Limits and How to Work Around Them

A growing catalog, custom checkout requirements, and ERP integrations can expose Shopify limitations that affect your architecture, budget, and launch timeline.

Understanding them early helps you scope the build and choose the right approach.

At craftberry, a Shopify Premier Partner, we plan and build stores around these requirements through custom Shopify development, Shopify migrations, and integrations.

This guide covers 12 platform limits, their practical implications, and the available workarounds.

Key takeaways

• ✓Shopify supports 2,048 variants and three options per product. Plan which attributes need separate inventory and which belong in metafields or customer input fields.
• ✓Shopify Plus unlocks UI extensions on the information, shipping, and payment steps, custom apps containing Shopify Functions, and higher API throughput.
• ✓Check catalog structure, promotion rules, and ERP dependencies before scoping a migration or rebuild. The right solution may involve restructuring data, improving an integration, using an app, or upgrading to Plus.
• ✓Headless changes the storefront architecture. Shopify’s backend limits and checkout rules still apply.

Shopify limitations at a glance

The linked documentation is the reference for each section. Figures were checked on October 23, 2026; availability can depend on rollout, API version, and configuration.

Catalog limitations: products, collections, and filters

1. Product variants and options

Shopify products support up to 2,048 variants and three options, according to the variant documentation.

The options limit can matter before the variant limit. A product sold by size, color, material, and finish needs four purchasing attributes, even if the total number of combinations is modest.

Start by distinguishing what each attribute does:

• ✓Variants: choices requiring distinct SKUs, stock, or pricing.
• ✓Metafields: specifications and descriptive attributes.
• ✓Line item properties: customer inputs such as engraving text, without separate inventory.

Moving an inventory-tracked choice into a text field does not preserve its stock behavior.

For related products, Shopify Plus offers Combined Listings. These have separate constraints, including 60 child products and 2,000 variants across those children.

craftberry use case: On On's UAE store, we built unified product pages with color and gender selection, while combined listings exposed variations individually in collections. The product structure supported both selection on the product page and discovery in the collection grid.

2. Daily variant creation

Once a store reaches 500,000 variants, Shopify limits new variant creation to 10,000 per day through the affected APIs. Shopify Plus is exempt from this additional resource throttle. See Shopify's API limits.

This matters during large catalog migrations and launches with substantial SKU expansion.

Plan imports against the final variant count. Run the initial transfer early, then synchronize changes before cutover. A launch schedule should account for upload time, failed-row retries, and validation.

If the daily allowance makes the required launch window impossible, assess Plus before committing to that date. First confirm that this throttle is the actual bottleneck; a slow source export or inefficient integration needs a different fix.

3. Automated collection rules

Legacy smart collections allow up to 60 selection conditions. The new collections model, introduced in API version 2026-07, combines multiple sources within a collection.

Matrixify documents a maximum of 10 sources per collection and 5,000 sources containing conditions across the store. These limits apply to sources and should be counted separately from legacy smart collections.

Before generating a collection for every attribute combination, decide which combinations need a permanent landing page and which belong in filters.

Check integration compatibility as well. Shopify says API versions before 2026-07 cannot represent new-model collections and filter them out. An app can therefore miss collections without the store reaching a numeric cap.

4. Native filtering

Shopify Search & Discovery supports 25 filters per store. A storefront filter displays up to 100 values, and collections containing more than 5,000 products do not display filters.

For a broad catalog, an oversized collection can remove the navigation shoppers need most.

Divide large collections into useful categories, consolidate near-duplicate values, and reserve filters for attributes that influence selection. If native filtering cannot support the required experience, assess a dedicated search solution against catalog size, localization, indexing, and ongoing cost.

Test realistic catalogs before choosing the approach. A prototype with 50 products will not expose the same constraints as a live collection containing thousands.

Data and integration limitations

5. Fixed URL paths and redirect limits

Native Shopify storefronts use paths such as /products/ and /collections/. A migration from another platform often requires URL changes.

Shopify allows 100,000 URL redirects, increasing to 20 million on Plus. Its redirect documentation also identifies reserved paths and other restrictions. Native redirects generally apply when the source URL no longer serves a valid page.

Build the redirect map before launch. Include indexed pages, backlinks, campaign destinations, and market subfolders, then test the relevant destinations and remove redirect chains.

craftberry use case: For Biotrade's WooCommerce migration, we defined the destination data structure, mapped URLs, and validated the transfer. Planning the URL structure alongside the data transfer made SEO requirements part of the migration scope.

Our Shopify migration checklist covers the broader validation and cutover process.

6. Shopify API rate limits

The GraphQL Admin API uses calculated query cost rather than a simple request count. Published throughput is:

These limits apply per app and store combination. A single query cannot exceed 1,000 cost points, even on Plus.

For ERP and warehouse integrations, start with selective queries, webhooks, bulk operations where supported, and queues that handle retries. Define which system owns each field and how failures become visible to the operations team.

craftberry use case: Enhance Automotive needed a custom SmartERP connection because its provider had no Shopify integration. We co-developed the connection around inventory, orders, and fulfillment workflows. The connection had to support the business workflow as well as transfer records.

Upgrade when measured throughput requires it, after removing avoidable API work.

Checkout and promotion limitations

7. Checkout customization without Plus

Apps adding UI extensions to the information, shipping, and payment pages require Shopify Plus. Basic and higher plans support other extension surfaces, including thank-you and order-status pages.

The distinction is between the checkout surface and the capability you need. Adding a block beside payment options is different from changing payment-method behavior through a supported app.

Some payment customizations are available without Plus, subject to restrictions including those affecting credit-card methods in the US and Canada.

Write the exact requirement before evaluating plans: what should change, where should it appear, and which buyers should see it? That gives you a practical basis for comparing an app, a supported setting, and a Plus extension.

8. Checkout tracking and session visibility

Shopify's web pixels operate in a sandbox. They can subscribe to supported customer events, but cannot freely inspect or modify the checkout DOM.

That separates three questions:

• ✓Did the customer reach a checkout stage?
• ✓Did a supported event fire?
• ✓What did the customer see, click, or struggle with?

Event tracking can help answer the first two. It does not automatically provide session recordings or explain abandonment.

Define the questions your measurement setup must answer, then verify the analytics tool's supported checkout capabilities and consent behavior. Test event delivery with representative transactions.

If recordings are unavailable, combine funnel analysis with customer feedback, support issues, and controlled tests. A high abandonment count establishes where to investigate, not why shoppers left.

9. Discount combinations

Shopify allows customers to use up to five product or order discount codes and one shipping discount code per order. Stores can have 25 active automatic discounts, including app-based discounts.

Combination rules also determine which offers can coexist. Being below the code limit does not mean every promotion will stack.

Before implementing promotions, document eligibility, product exclusions, quantity thresholds, subscription behavior, and interaction with loyalty rewards. Test mixed carts and both code-entry sequences.

For more complex requirements, assess native discounts, a compatible public app, or custom Functions. Avoid using several overlapping apps before checking whether their rules conflict.

The acceptance test should describe the customer's final price and the merchant's expected margin, rather than whether a code appeared to apply.

International selling and B2B limitations

10. Payment-provider and Markets dependencies

Shopify Payments eligibility and Shopify Markets functionality are separate checks.

Markets documentation says accepting payments in multiple currencies requires Shopify Payments or Adyen. With another processor, customers in all markets pay in the store's default currency.

Before defining an international architecture, confirm the legal entity, selling regions, product category, processor eligibility, settlement requirements, and currencies required at checkout.

A translated storefront displaying local prices is not sufficient proof that the customer can complete payment in that currency.

Test the complete transaction for each priority market, including payment, refunds, and reconciliation. Evaluate separate regional stores when the operating requirements justify them, and include the cost of synchronizing content, stock, and reporting in that decision.

11. B2B catalogs outside Plus

Native Shopify B2B is available on Basic, Grow, Advanced, and Plus. Outside Plus, stores can assign three active catalogs across their B2B markets. Direct catalog assignment to companies and locations is a Plus capability.

Three catalogs can suit a small number of shared pricing tiers. They are a different proposition from negotiated pricing for individual company locations.

Map the commercial model before choosing the plan: who owns prices, how frequently they change, which buyers share a tier, and whether an ERP supplies contract terms.

If individual company assignments are essential, evaluate Plus and the integration needed to maintain them. A wholesale label alone does not establish the requirement.

Shopify Plus limitations: Functions still have boundaries

12. Shopify Functions execution limits

Shopify Functions extend backend logic, but access depends on the app and API.

Public App Store apps containing Functions can serve stores on any plan; custom apps containing Functions require Plus.

For carts with up to 200 line items, published resource limits include 11 million instructions, 128 kB input, and 20 kB output. Certain limits scale for larger carts.

External network access is restricted and depends on the Function API and approved access. Do not assume a Function can call your ERP during checkout.

Prepare required data ahead of execution, keep inputs focused, and test large carts and overlapping promotions. The implementation must fit both the supported business operation and the execution budget.

Plus gives developers more extension options. It does not provide unrestricted access to Shopify's commerce engine.

How to choose the right workaround

Classify the requirement before choosing a tool or plan.

Headless deserves the same scrutiny. It can change content delivery and storefront experience, but it does not automatically remove Shopify checkout rules, Admin API limits, or product-model constraints.

Before approving a workaround, establish who will maintain it, how failure is detected, and what happens when an app or API version changes. A solution that works in a demo still needs an operating model.

How we researched this guide

We checked the platform limits in this guide against Shopify’s Help Center, developer documentation, and API references on October 23, 2026. Where availability depends on the plan, API version, or configuration, we identify those conditions. Collection-source limits attributed to Matrixify come from its published limits documentation.

The craftberry examples draw on our published case studies for On UAE, Biotrade, and Enhance Automotive. Each illustrates the product architecture, migration planning, or integration work delivered on that project. Our recommendations combine these project examples with Shopify’s documented capabilities.

This guide describes published platform limits rather than results from controlled stress testing. Check the linked documentation before making implementation or plan decisions, as Shopify updates its limits and feature availability.

Shopify limitations holding your store back?

Understand which limits affect your business and what it takes to work around them.

At craftberry, we assess your catalog, checkout, custom business logic, and ERP connections before development starts.

We identify where native Shopify features fit and where custom development will better support your operations.

Talk to our Shopify experts