Wix Ecommerce Limitations: What Wix Cannot Do in 2026

Wix's defining constraint in 2026 is not a missing feature but an architectural philosophy. The platform is a closed, hosted SaaS builder: every site runs exclusively on Wix's servers, the checkout is a locked component, and hard catalog caps apply on every plan. That design makes Wix one of the fastest ways to launch a store — and it creates predictable pressure points for merchants who grow into complex catalogs, multiple storefronts, or headless commerce architectures.

The pattern repeats across the stack. The drag-and-drop editor offers unusual design freedom for nearly every page, yet the checkout cannot be restyled at all. The Velo serverless layer adds real programmability, yet operates inside per-minute request quotas and plan-gated database ceilings. Wix Headless exposes commerce APIs, yet still redirects shoppers to a Wix-hosted checkout page. Each capability extends the platform without actually opening it.

None of this makes Wix a poor product; it serves small and mid-sized merchants who want an all-in-one stack remarkably well. But the ceilings are specific, documented, and in most cases not removable at any price. Knowing exactly where they sit is the difference between choosing Wix deliberately and discovering its limits mid-growth.

Key Takeaways

• The Wix checkout page cannot be edited from the site editor — only dashboard settings such as form fields and policy checkboxes are adjustable — and even Wix Headless storefronts must redirect shoppers to a Wix-hosted checkout page.
• Hard catalog caps apply on every plan: 6 product options, 100 choices per option, 1,000 variants per product, and 50,000 products per store, with higher limits still open feature requests marked as collecting votes.
• Premium plans cover a single site only, so each additional storefront requires its own paid plan, and keeping inventory in sync across stores takes a third-party app from roughly $6.50 per month as of publication.
• Native product subscriptions exclude digital products, cannot be reactivated after cancellation, and force a full cancel-and-repurchase cycle when switching payment providers; Pricing Plans sales also carry an extra 4% fee on Core and 2% on Business as of publication.
• Multi-currency checkout works only for Wix Stores with Wix Payments, PayPal, or Stripe, uses automatic daily XE rates with no per-currency price lists, and the display converter is gated to the Business plan and above.
• A Wix site cannot be exported or hosted elsewhere — product, contact, and order data leaves as CSV files, but the storefront itself must be rebuilt on any new platform.

Checkout Lockdown and the Limits of Conversion Optimization

Dashboard settings instead of design control

Wix's own documentation is direct about it: "you can't customize the checkout page from your editor." What merchants can change lives in dashboard settings — custom form fields, a logo or business name in the header, policy and agreement checkboxes, checkout validations, and extra fees. The checkout's design, layout, and styling are off limits, and the restriction applies across Wix Stores, Bookings, Restaurants, Donations, and Pricing Plans checkouts alike.

For a growing store, this forecloses an entire discipline. Checkout is where conversion optimization pays best, and a page that cannot be redesigned cannot be tested for layout, trust signals, or branding beyond a header logo.

Why Velo cannot unlock it

The limitation survives Wix's own developer tooling. Velo code can add checkout validations and custom fields, but backgrounds, fonts, colors, and button design remain fixed — customizing the checkout's design is itself an open feature request in Wix's help center as of publication. Developers who need full checkout control must leave the standard Wix Stores flow entirely.

This is where the contrast with API-first architecture is sharpest. Swell publishes a Checkout API that lets teams build fully custom checkout and payment flows using the same APIs that power Swell's own hosted checkout — checkout becomes a capability developers can extend, not a sealed component.

Catalog Ceilings That Constrain Complex Merchandising

Six options, 1,000 variants, no exceptions

A Wix Stores product supports at most 6 product options, 100 choices per option, and 1,000 variants — hard limits that no plan upgrade removes. For comparison, Shopify's variant ceiling now sits at 2,048 and BigCommerce allows 600. An apparel product spanning sizes, colors, fits, and lengths can exhaust Wix's matrix quickly.

Both caps look durable. Raising the variant limit and the option limit are open feature requests in Wix's help center, each marked as collecting votes — the lowest status on Wix's roadmap, meaning neither is planned nor in development as of August 2026.

Store-wide limits, recently improved but still fixed

At the catalog level, a store caps at 50,000 products — a platform stability limit rather than a plan tier. The new product catalog Wix rolled out through 2025 and 2026 did raise several ceilings: product media grew from 15 to 50 files per product, categories now reach 1,000 in total, and nesting extends five levels deep. These are genuine improvements; they are also still fixed numbers.

Merchants modeling complex products handle this differently on API-first platforms. Swell supports unlimited variants and options through both the dashboard and the API, and its model editor and custom fields extend every data model — the catalog schema adapts to the product, not the reverse.

Headless Commerce That Still Routes Through Wix

APIs with a hosted checkout at the end

Wix Headless, launched in 2023 and expanded through 2026 with Wix-managed Astro hosting and an AI toolkit, exposes stores, bookings, events, pricing plans, CMS, and members through SDK and REST interfaces. But the transactional core stays on Wix: headless storefronts must redirect shoppers to a Wix-hosted checkout page via a redirect session, and member login works the same way.

The redirect has a visible seam. Wix hosts those pages as a separate website with its own Wix domain that does not match the storefront's domain — attaching a custom subdomain requires a premium plan. Shoppers on a self-managed headless build change domains at the moment of purchase.

Missing components and a fixed data model

Component-level headless support does not exist — adding headless components is an open developer request in Wix's help center — and the backend data model, the OAuth-based visitor and member authentication, and the business logic all remain Wix's, consumed rather than customized.

An API-first platform inverts that relationship. Swell's unified Backend API — the same API that powers its own dashboard and checkout — offers full CRUD access to all data models over both REST and GraphQL, so a headless build on any frontend framework can replicate or replace any native behavior, checkout included, rather than redirecting around it.

Subscription Constraints and the Cost of Recurring Revenue

What native product subscriptions cannot do

Wix Stores product subscriptions carry several hard restrictions: digital products cannot be sold as subscriptions, free subscriptions are not possible, a canceled subscription cannot be reactivated — the customer must purchase it again — and each product supports at most 6 subscription options. Prepaid, pay-upfront subscriptions remain an open feature request.

Provider choice is equally narrow. Recurring payments work only with a fixed list of roughly 15 providers — Wix Payments, Stripe, and PayPal plus regional processors — most limited to card payments; Square is absent from the list entirely. Most consequentially, switching payment providers requires canceling every active subscription and asking customers to repurchase.

The Pricing Plans transaction fee

Recurring memberships sold through Wix's Pricing Plans app carry an additional Wix fee on top of payment processing: as of publication, 4% on Core, 2% on Business, and 0% only on the $159-per-month Business Elite plan, per Wix's own plan comparison table. A Core-plan merchant selling a $50 monthly plan gives up roughly 7.5% of each charge once card processing is added.

Subscription-first merchants tend to compare this against platforms where recurring billing is core infrastructure. Swell includes native subscriptions on every plan: physical or virtual products, flexible billing intervals, separate invoicing and fulfillment schedules, automatic payment retries, trials, and mixed carts combining subscription and one-time items — all managed from one dashboard, with payments running through an encrypted card vault directly with the gateway.

Per-Site Licensing and the Multi-Store Penalty

Every storefront is a separate paid site

Wix's billing terms are explicit: premium plans are "valid for a single site only," so a second storefront means a second paid plan. There is no shared catalog, shared inventory, or unified commerce administration across sites in core Wix — Wix Studio's enterprise tier manages sites and teams for agencies, not one commerce catalog across stores.

For a brand running regional storefronts, or an operator managing several brands, cost and administration multiply linearly: every site carries its own subscription, its own catalog, and its own settings.

Inventory sync and wholesale run through third parties

Keeping stock aligned across those sites requires the App Market: a third-party inventory sync app (from roughly $6.50 per month, billed yearly) exists precisely because no native cross-store inventory feature appears in current Wix Stores documentation. B2B follows the same pattern — Wix's documented route to wholesale pricing, net terms, and account-based buying is the third-party SparkLayer app, while native bulk selling remains an open feature request as of publication.

Multi-store operation is part of Swell's core architecture instead: multiple storefronts and brands run from a single account, marketplace models with split payments are built into the platform, and native B2B features cover customer group-based pricing, custom payment terms, and quotes through the API.

International Selling and the Display-Only Currency Problem

Multi-currency with narrow eligibility

True multi-currency checkout on Wix applies only to Wix Stores — not Bookings or Events — and only with Wix Payments, PayPal, or Stripe. Currencies a provider does not support fall back to display-only, with the customer charged in the store's main currency. Manually created orders are not supported in multi-currency, gift cards are always issued in the main currency, and subscription renewals stay locked to the exchange rate at initial purchase.

The display-side tool is plan-gated too: the currency converter changes only what prices look like, never the transaction currency, and requires the Business or Business Elite plan.

Exchange rates without pricing strategy

Rates arrive automatically from the XE Currency Converter, updated daily. Merchants cannot set independent per-currency price lists, which rules out market-specific pricing strategy — a product cannot list at a clean €29 in Europe by choice; it lists at whatever the day's conversion produces.

Swell approaches localization as a pricing system rather than a converter: explicit price rules per currency with automatic conversion as the fallback, across 230 currencies, plus content localization in 170 languages. Tax follows the same native pattern, with Avalara AvaTax and TaxJar integrations and custom tax rule groups by location and product.

Processor Restrictions That Exclude Regulated Merchants

The Wix Payments prohibited list

Wix's in-house processor publishes a prohibited and restricted list for US merchants that bars products containing CBD or THC, tobacco and e-cigarettes, weapons and firearm parts, and adult content and services, and restricts supplements — banning those with prescription ingredients or unsupportable claims. Outside the US, restrictions follow Wix's processing partners, Adyen and Stripe, and their own lists.

The platform's structural preference for its own processor compounds the issue: Wix's POS solutions require Wix Payments and are limited to US, Canada, and UK merchants (elsewhere, mobile card payments run through Square or SumUp), and multi-currency eligibility is likewise tied to Wix Payments, PayPal, or Stripe.

The CBD carve-out and what it costs

US businesses can sell hemp-derived CBD on Wix, but only after submitting a declaration that automatically disconnects and permanently closes their Wix Payments account. Processing must then run through one of four approved providers — Square, Bankful, Priority Payments, or Evergreen Payments Northwest — and sales are unsupported in six states: Hawaii, Idaho, Iowa, Mississippi, New Hampshire, and South Dakota.

For regulated categories, gateway flexibility becomes the deciding factor in platform choice. Swell's payment abstraction layer integrates with Stripe, PayPal, Braintree, Authorize.Net, and Amazon Pay, with Swell handling PCI compliance — third-party gateway support that matters most to merchants whose products require a specific processor.

Developer Quotas, Data Caps, and the One-Way Exit

Velo's compute and data envelope

Velo's backend runs inside tight, partly unpublished boundaries. Data requests are quota-limited per minute — exceeding them returns error WDE0014, and Wix does not publish the exact per-plan numbers, so teams discover ceilings only when quota errors appear in production logs. Payloads cap at 512 KB per item and 4 MB for bulk operations, data queries time out at 5 seconds on most plans, and backend containers provide 1 vCPU and 400 MB of memory (2 vCPU and 600 MB on the standard tier).

Database capacity is plan-gated just as sharply: 1,500 CMS collection items on Light, 4,000 on Core, 20,000 on Business, and 10 million only on the Elite tiers, with 10 GB of storage on lower plans against 100 GB on Elite tiers (effective January 7, 2026), and only Business Elite sites receive dedicated databases. The app ecosystem cannot fully fill these gaps either — independent 2026 counts place the Wix App Market at roughly 500 to 1,000 apps, against roughly 20,000 active apps on Shopify's store.

A site that cannot leave Wix's servers

The exit is the final constraint. Wix states plainly that sites must run on Wix's servers and that its SaaS architecture does not support external hosting. Product CSVs, contacts, and order exports travel; the domain can move to another registrar; templates, pages, and site code cannot. Migration means rebuilding the storefront from scratch.

That asymmetry is worth pricing in from the start. Swell remains a managed platform — hosting, scaling, and security patching are its responsibility, not the merchant's — but everything above that layer stays open: full API access to every data model over REST and GraphQL, and a directory of Swell experts.

Frequently Asked Questions

Can I customize the Wix checkout page to match my brand?

No. Wix's documentation states the checkout page cannot be customized from the editor; merchants can adjust dashboard-level settings only — custom form fields, a header logo or business name, policy checkboxes, validations, and extra fees. Velo code cannot restyle the checkout either, and Wix Headless projects must redirect shoppers to a Wix-hosted checkout page, which requires a premium plan even to sit on a custom subdomain.

Teams that need a fully branded, fully controlled checkout typically look to platforms with a checkout API — Swell's exposes the same APIs behind its hosted checkout for building custom flows.

Does Wix charge transaction fees on top of payment processing?

Not on standard product sales — Wix adds no platform commission whether a store uses Wix Payments or a third-party gateway. US processing runs 2.9% + $0.30 for most cards, 3.7% + $0.30 for Amex, 3.49% + $0.49 for PayPal, and 6% + $0.30 for buy-now-pay-later options, plus a 1.5% cross-border surcharge and 1% currency-conversion fee where applicable, with $15 chargebacks.

The exception is the Pricing Plans app: as of publication, memberships and recurring plans sold through it carry an extra 4% fee on Core and 2% on Business, waived only on Business Elite at $159 per month.

How many products and variants can a Wix store handle?

The official limits are 50,000 products per store and, per product, 6 options, 100 choices per option, 1,000 variants, and 50 media files, with up to 1,000 categories nested five levels deep. Raising the variant and option caps are open feature requests still collecting votes as of August 2026.

Stores with large option matrices — apparel spanning sizes, colors, fits, and lengths — or catalogs beyond 50,000 SKUs will hit these walls on any plan. Platforms with unlimited product modeling, Swell among them, remove the ceiling at the schema level rather than raising it.

If I outgrow Wix, can I export my store and move it to another platform?

The site itself cannot be exported: Wix's architecture requires sites to run on its servers, and external hosting is unsupported. What travels is data — product CSVs, contact lists, and order exports — plus the domain, which can be managed through or transferred to another registrar.

The storefront, its templates and pages, and any Velo code must be rebuilt on the destination platform, so migration cost scales with how much design and logic has accumulated inside Wix.

Does Wix support selling internationally in multiple currencies or running multiple stores?

Partially. Multi-currency checkout works only for Wix Stores and only with Wix Payments, PayPal, or Stripe; unsupported currencies become display-only, rates are set automatically each day from XE with no independent per-currency price lists, and the display converter requires the Business plan or above.

Multiple stores means multiple sites: premium plans cover a single site, each additional store needs its own paid plan, and cross-store inventory sync requires a third-party app at roughly $6.50 per month as of publication. Merchants running several brands or regions on one catalog generally need a platform with native multi-store architecture.