Webflow Ecommerce Limits That Push Brands to Shopify in 2026

Webflow ecommerce works well for a small, design-led catalog and stops working well at a predictable point. A Webflow Ecommerce site plan is a per-site subscription that unlocks products, cart and checkout inside Webflow, and the cheapest tier caps you at 500 items with a 2% transaction fee on top of Stripe or PayPal processing. Past roughly 300 SKUs, or about $2,250 a month in sales, the plan's own economics start arguing for moving checkout to Shopify and keeping the design layer separate.

That threshold is arithmetic, not opinion, and it is the thing almost every Webflow ecommerce review leaves out. Below is the limits table the search results are missing, the three ceilings that actually force a migration, and the point where a Shopify backend with a designer-controlled frontend costs less than staying put.

The Webflow Ecommerce Limits That Actually Bite

Here is every published constraint side by side, with the threshold that should trigger a move. The figures come from Webflow's and Shopify's own pricing pages, read on 10 October 2026.

Two numbers in that table do the work. Webflow's Standard plan charges 2% while Plus charges nothing, so the $45 gap between them is covered by the fee alone at $2,250 of monthly revenue — every dollar above that is pure overpayment until you upgrade. And Shopify's Basic plan is $29 a month billed yearly and sells unlimited products, which means the entry Shopify tier costs the same as the entry Webflow Ecommerce tier and removes the item cap entirely.

The Localization Ceiling Nobody Advertises

The hardest limit is not the item count — it is that a Webflow Ecommerce site cannot be translated. Webflow's own Help Center, updated 1 July 2026, is unambiguous about it:

Ecommerce Site plan features do not support Localize.

— Webflow Ecommerce overview, Webflow Help Center

On a site with both enabled, products, categories and product pages cannot be localized. For a brand selling into more than one country that is a wall, not an inconvenience, and it arrives long before you hit 500 items. The same document adds a second one-way door: once Ecommerce is switched on, "you cannot deactivate or remove it," and the Products, Categories and SKUs collections can never be deleted.

Shopify treats the same problem as table stakes — multiple markets, currencies and domains are configuration, not a migration. If localization is what is forcing your hand, the mechanics of running currency and language on a design-led storefront are covered in our guide to Shopify Markets on a Framer storefront.

What Big Companies Use Webflow?

Large companies use Webflow heavily — for marketing sites. Webflow's own customers page features Amazon's Brand Innovation Lab, Spotify, TED, Dropbox Sign, Docusign, Reddit, Discord, monday.com and The New York Times, and its written case studies describe brand consolidation, WordPress migrations and multi-site marketing footprints. Hakim Group runs over 500 individually branded practice websites on it. Ebury moved 30 separate WordPress instances onto it.

What is absent is instructive: none of the flagship case studies is a storefront. The enterprise proof points are content and marketing teams, which is exactly where Webflow is strongest and exactly why its commerce tier stayed thin. If you are weighing the builders purely on design and CMS power, our Framer vs Webflow ecommerce benchmark compares them on the dimensions that actually differ.

Is Webflow Better or WordPress?

For a design-led team shipping a marketing site, Webflow is better — faster to build, no plugin surface to maintain, no hosting to patch. For commerce, the comparison is a trap, because both platforms hit a ceiling from opposite directions. Webflow caps items and taxes revenue at 2% on Standard; WordPress with WooCommerce is unlimited but hands you hosting, security updates and a plugin stack to babysit.

The question that matters is not which builder wins but which layer owns the money. Checkout is where conversion is won or lost — Baymard Institute puts the documented average cart abandonment rate at 70.22% across 50 studies — and a thin, un-extendable checkout is the most expensive thing in your stack. That is the argument for letting a commerce platform own checkout regardless of which tool draws the pages.

The Threshold: When to Move the Storefront

Three triggers, any one of which is sufficient:

1. Revenue over ~$2,250/mo on Standard. The 2% fee now costs more than the next plan up, and more than Shopify Basic.
2. More than one market. Webflow Ecommerce cannot be localized at all. There is no workaround on-platform.
3. Operations beyond a spreadsheet. POS, B2B price lists, multi-location inventory and a real app ecosystem are not on Webflow's roadmap at any ecommerce tier.

Note what is not a trigger. Hitting 400 items on Standard is not a reason to leave — it is a reason to upgrade. The migration case is about capability, not capacity.

Keeping the Design: Framer as the Frontend

Moving checkout to Shopify does not mean accepting a theme. The pattern design-led brands land on is Shopify for products, inventory, payments and markets, with the storefront built in a visual tool — Framer's Basic plan is $10 a month and holds 1,000 CMS items, which is cheaper than Webflow's entry Ecommerce plan while leaving commerce to a platform built for it. FramerLink syncs the Shopify catalog into Framer's CMS so product pages stay designed rather than templated; the full headless-Framer setup is documented here.

If you are not ready for a full backend move, a lightweight cart is the middle path — we compared Snipcart against Shopify for Framer sites on fees, catalog size and checkout control. The honest summary: Webflow ecommerce pricing is competitive for a 50-product shop with one currency, and indefensible for anything past that.