fork 01
Pure brand or marketing site.
No shop, or a "buy now" link to an external marketplace. Editor velocity, animation, and CMS-driven content are the brief. Design is the product.
recommendation
→ Webflow.
§§ · compare
Webflow vs Shopify. A use-case fork, not a fight.
Webflow is a designer's website builder with an ecommerce module bolted on. Shopify is a commerce engine with a website builder bolted on. Pick by what you sell, how many SKUs, and how much design freedom you actually need.
in short
- Webflow wins for brand sites and boutique shops under 30 SKUs where design freedom is the job.
- Shopify wins for catalog-driven stores above 30 SKUs, subscriptions, or multi-region tax.
- Subscription fees are similar; app stack and operating hours drive the real cost gap.
- The hybrid play (Webflow front-end, Shopify cart) is real and ships in 1 to 6 weeks depending on path.
- Most audits we run conclude "stay where you are" because migration cost rarely beats the platform delta.
§ 01 · the decision tree
Three forks. One honest answer per project.
The Webflow vs Shopify decision splits on three forks: a pure brand or marketing site with no shop, a boutique catalog under 30 SKUs with design as the primary value, and a scale store with 30 plus SKUs, recurring billing, or multi-region operations. Webflow wins the first two; Shopify wins the third. Most teams overweight design ambition and underweight commerce depth, then migrate inside 18 months. The decision tree below sorts the project before the build starts.
start here
What is the project?
fork 02
Boutique catalog, 30 SKUs or fewer.
Brand-led DTC, simple variants, no subscriptions, single-region tax, design freedom matters more than apps. Hosted checkout is fine.
recommendation
→ Webflow Ecommerce.
fork 03
Catalog above 30 SKUs, or recurring, or multi-region.
Subscriptions, multi-warehouse inventory, B2B pricing tiers, tax across 3 plus regions, or a serious app stack. Operations is the moat.
recommendation
→ Shopify or Shopify Plus.
If two forks describe the project, weight by SKU count: under 30 picks Webflow, over 30 picks Shopify. The hybrid play (§10) covers the genuinely ambiguous middle.
§ 02 · origin stories
What each platform was actually built for.
Webflow was founded in 2013 as a visual website builder for designers who wanted production HTML and CSS without writing it by hand; ecommerce was added in 2018 and remains a secondary surface. Shopify was founded in 2006 as a checkout and inventory engine for catalog merchants; the website builder is real but is a feature of the commerce platform, not the other way around. That heritage still shapes which jobs each one does well in 2026.
platform 01
Webflow: a visual builder for designers.
Built so a design team can produce a production-ready site without an engineer. The Designer mirrors the canvas pattern of Figma with HTML and CSS produced underneath. Hosting is included, the CMS is editable in plain English, and Interactions deliver scroll and hover animation without code. Ecommerce was a 2018 add-on; the commerce engine is real but the platform's center of gravity is design and content. See the official Webflow site and Webflow University for the platform's framing.
platform 02
Shopify: a commerce engine for operators.
Built so a small merchant can take payments, manage inventory, ship orders, and pay tax without standing up infrastructure. The admin is a logistics tool with a website attached. Themes are produced in Liquid, the platform's template language. Checkout, tax, multi-region, and B2B are first-class; the design surface is competent but not Webflow-grade. See shopify.com and shopify.dev for product surface and developer surface.
§ 03 · webflow's column
Where Webflow genuinely wins.
Webflow wins where design freedom, editor velocity, and animation primitives matter more than commerce depth. Five places stand out: per-page design control through the Designer, the most flexible visual CMS of any hosted platform, native scroll and hover animation through Interactions, included managed hosting on AWS with a Cloudflare edge, and per-page SEO controls including granular schema and meta editing for content sites.
01 · design
Per-page design freedom.
Every page can be its own canvas. No theme constraint, no Liquid section limit, no shared header rule unless the team chooses one. Design teams ship bespoke layouts in days, not weeks.
02 · cms
CMS depth for editors.
Reference fields, multi-reference fields, and the Editor mode let non-technical staff add and edit content without touching design. Up to 10,000 items per Collection on Enterprise.
03 · motion
Interactions and animation.
Scroll-triggered animation, hover states, page-load reveals, all configured visually with no JavaScript. The closest thing to Framer Motion in a no-code tool.
04 · hosting
Managed hosting included.
AWS plus Fastly CDN, free SSL, automatic backups, no separate hosting bill. Sites cold-start fast and stay fast at moderate traffic. Read the Core Web Vitals doc for the targets.
05 · seo control
Granular per-page SEO controls.
Title, meta, OG tag, canonical, and schema can be set per page or per CMS item without templating tricks. For content-heavy brand sites, this is faster than the Shopify equivalent and closer to a custom Next.js setup.
§ 04 · shopify's column
Where Shopify decisively wins.
Shopify wins where commerce depth, operational reliability, and ecosystem reach matter more than design surface. Five places stand out: payments, tax, and shipping handled at scale through Shopify Payments and Shopify Shipping, an app store with 8,000 plus apps, native subscriptions and recurring billing through Shopify Subscriptions, B2B with company accounts and NET-30 terms on Plus, and Shopify Markets for multi-region currency, language, and tax.
01 · commerce ops
Payments, tax, shipping at scale.
Shopify Payments handles card processing in 22 countries, automatic tax calculations across US states and EU VAT, and live shipping rates from major carriers. The platform absorbs the operational tax that breaks small WooCommerce shops.
02 · apps
8,000 plus app ecosystem.
Subscriptions (Recharge), reviews (Judge.me), email (Klaviyo), helpdesk (Gorgias), upsells, loyalty, fulfillment, all available as plug-ins. Webflow's app market is roughly 100 integrations.
03 · subscriptions
Native subscriptions and recurring.
Shopify Subscriptions plus Recharge cover most recurring-billing needs out of the box. Webflow has no native subscription module; you wire Stripe Billing yourself with custom code, which works but adds engineering load.
04 · b2b
B2B with company accounts.
Shopify Plus B2B covers per-customer pricing, NET-30 payment terms, company-level role-based access, and quote flows. Webflow has no B2B layer; B2B on Webflow means a custom Xano or Airtable backend.
05 · multi-region
Shopify Markets for multi-region.
One backend, multiple storefronts in different currencies, languages, and tax regimes. Built-in geolocation routing, regional pricing, and IOR options for cross-border. Webflow Multilingual is a localization layer with no native multi-currency or regional tax pipeline.
§ 05 · feature parity
Thirteen commerce features. Scored side by side.
At the ecommerce layer, Shopify has more depth on most features and Webflow Ecommerce has more design control on the storefront. The table below scores 13 commerce-relevant features. "Yes" means native, "Partial" means available with a workaround or limit, "No" means the platform does not offer the feature without a third-party integration. Read it as a feasibility map, not a verdict.
| commerce feature | Webflow Ecommerce | Shopify | notes |
|---|---|---|---|
| Hosted checkout | Yes | Yes | Both PCI-compliant |
| Product variants | Yes (3 options) | Yes (3 options, 100 variants) | Tie below 100 variants |
| Inventory management | Basic | Multi-location, native | Shopify |
| Subscriptions / recurring | No (custom Stripe) | Yes (native + Recharge) | Shopify |
| Discounts and codes | Yes | Yes (with Functions) | Shopify deeper on Plus |
| Abandoned cart recovery | Yes (Plus tier) | Yes (all tiers) | Shopify |
| Tax automation (US, EU) | Partial | Yes (native + Avalara) | Shopify |
| Multi-currency | No | Yes (Shopify Markets) | Shopify |
| B2B / company accounts | No | Yes (Plus) | Shopify |
| Apps / extensions | ~100 | 8,000 plus | Shopify |
| Customizable checkout | Limited | Yes (Plus, Checkout Extensibility) | Shopify |
| Storefront design freedom | Excellent (per-page) | Good (Liquid, Hydrogen) | Webflow |
| CMS for content + product | Excellent (visual) | Good (metaobjects) | Webflow |
§ 06 · design + motion
Design surface and motion. The biggest gap.
Design freedom and animation primitives are the place Webflow opens the largest lead. Webflow Interactions cover scroll, hover, page-load, and time-based animation visually with no code. Shopify themes either accept whatever Liquid sections the theme author shipped or require a Hydrogen rebuild to add custom motion. The table below maps eight design and motion primitives across both platforms. The pattern is consistent: Webflow wins on visual design output, Shopify catches up only when the team adopts Hydrogen and writes React.
| design / motion primitive | Webflow | Shopify themes | Shopify + Hydrogen |
|---|---|---|---|
| Per-page custom layout | Native | Theme sections only | Full |
| Scroll-triggered animation | Native (Interactions) | Custom JS | Full (Framer Motion) |
| Hover and interaction states | Native | CSS only | Full |
| Custom typography pairing | Native, granular | Theme-locked unless edited | Full |
| Asymmetric grid layouts | Native | Hard without theme rewrite | Full |
| 3D and Lottie embeds | Native | Custom embed | Full |
| Editor surface for non-devs | Excellent | Good (Liquid sections) | Devs only |
| Time-to-ship custom animation | Hours | Days (custom JS) | Days (React) |
The honest read: a Webflow site can match a hand-coded design system in days; the same look on Shopify needs either a paid theme that already has it or a Hydrogen build with React engineering. For brand-led sites, Webflow's lead is decisive. For commerce-led brands, the design gap is real but it pays for the operational depth on the other side.
§ 07 · seo surface
SEO surface. Where each one bends.
On SEO, both platforms can rank when configured correctly; neither is structurally compromised. Webflow gives more granular per-page control over schema, canonical, and meta, which helps content-heavy brand sites. Shopify ships stronger ecommerce-specific schema and faster mobile defaults, which helps catalog pages. The seven-row table below maps the practical control surface. Read the schema.org reference and SEO entry on Wikipedia for the underlying spec.
| seo control | Webflow | Shopify | edge |
|---|---|---|---|
| Per-page schema control | Native (custom code blocks) | Theme JSON-LD edits | Webflow |
| Native product schema | Manual | Native (since 2023) | Shopify |
| Canonical control | Per-page editable | Auto + theme override | Tie |
| Sitemap control | Auto, granular toggles | Auto, less granular | Webflow |
| hreflang for multi-locale | Manual (custom code) | Native (Markets) | Shopify |
| 301 redirect engine | Native, bulk import | Native, bulk import | Tie |
| robots.txt control | Editable (paid plan) | Editable (since 2021) | Tie |
§ 08 · performance
Core Web Vitals. Field reality, not lab marketing.
Both platforms can pass Core Web Vitals; both can also fail badly when overloaded with apps or unused theme code. Typical 75th-percentile field data on a decently built Webflow site lands at LCP 2.0 to 2.4 seconds, INP 100 to 180 milliseconds, CLS 0.05 to 0.10. A typical Shopify site with 6 to 10 active apps lands at LCP 2.4 to 3.2 seconds, INP 150 to 220 milliseconds, CLS 0.08 to 0.15. The variance is driven more by app and image discipline than by platform. The targets in the web.dev Core Web Vitals doc are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 at p75.
typical p75
Webflow
LCP 2.0 to 2.4s
INP 100 to 180ms
CLS 0.05 to 0.10
Cleaner out of the box; less app overhead.
typical p75
Shopify (light)
LCP 2.2 to 2.6s
INP 130 to 200ms
CLS 0.06 to 0.12
3 or fewer apps, optimized theme.
typical p75
Shopify (heavy)
LCP 2.8 to 3.6s
INP 200 to 280ms
CLS 0.10 to 0.20
8 plus apps, default theme, no audit.
The single biggest performance lever on Shopify is the active app count, not the theme. Halving app count usually moves p75 LCP by 400 to 600 milliseconds.
§ 09 · 24-month tco
24-month TCO for a $1M brand. Honest math.
For a brand doing $1M per year with a moderate app and engineering footprint, total cost of ownership over 24 months runs within 15 percent either direction across Webflow Ecommerce Plus and Shopify Basic to Advanced. Subscription line is small; payment processing, app stack, and developer hours dominate. The table below breaks the line items so the team can plug in real numbers. Numbers below are illustrative ranges, not quoted prices.
| cost line | Webflow Ecommerce Plus (24mo) | Shopify Advanced (24mo) | delta |
|---|---|---|---|
| Platform subscription | $74/mo × 24 = $1,776 | $299/mo × 24 = $7,176 | Webflow saves $5,400 |
| Payment processing (2.9 percent) | ~$58,000 | ~$48,000 (Shopify Payments) | Shopify saves $10,000 |
| App stack | $1,200 to $4,800 | $7,200 to $16,800 | Webflow saves $6k to $12k |
| Theme / design system | $0 (built in Designer) | $300 to $500 (paid theme) | Webflow saves up to $500 |
| Developer hours / month | 8 to 12 hours | 12 to 20 hours | Webflow lighter |
| Migration cost (one-time, if applicable) | $8k to $25k (rebuild) | $15k to $40k (rebuild) | Webflow lighter |
| Total (range, 24-month TCO) | ~$72k to $95k | ~$78k to $115k | Within 15 percent typical |
The TCO gap is usually smaller than founders expect; the operational gap is usually larger. For a brand with a serious app stack or multi-region tax, Shopify's higher cost is a discount on operating hours.
§ 10 · the hybrid play
Webflow front-end, Shopify cart. When both win.
The hybrid play pairs Webflow as the marketing and content surface with Shopify as the cart, checkout, tax, and shipping engine. Useful when design freedom matters but commerce depth is non-negotiable, or when a brand wants Webflow's editor surface without giving up Shopify Payments and the app ecosystem. Two paths: Buy Button SDK for catalogs under 50 SKUs (1 to 2 day setup) and Storefront API for full design control over product pages (2 to 4 week build). Both keep cart and checkout on Shopify, which is the value.
01
Buy Button SDK path.
Embed a Shopify product card and checkout into any Webflow page via a JavaScript snippet from shopify.dev. Setup takes 1 to 2 days for a small catalog. Limits: catalog of about 50 SKUs is the practical ceiling because each product needs its own snippet, and analytics fragment between Webflow and Shopify. Fine for a brand site with a "buy" CTA, less suitable for a 200-SKU store.
02
Storefront API path.
Use Shopify's GraphQL Storefront API to render product data inside Webflow with custom JavaScript. Build runs 2 to 4 weeks for a typical catalog. Gives full design control over product detail pages, product cards, collection listings, and search. Cart hand-off goes to Shopify checkout, which keeps payments, tax, shipping, and apps inside the commerce engine. The design wins of Webflow plus the operational wins of Shopify.
03
The common gotchas.
Three places hybrid setups break: cart attribution (UTMs need to pass through to Shopify or the analytics is wrong), inventory sync (Webflow product CMS and Shopify inventory drift if both are edited), and SEO duplication (canonical and product schema must point to one source of truth). Solve all three at the API integration layer, not at runtime. We have shipped this pattern for four brands; the pattern works when the data flow is designed up front.
§ 11 · questions
Seven honest answers.
Is Webflow good for ecommerce?
Webflow Ecommerce is good for boutique catalogs under roughly 30 SKUs where design freedom is the primary requirement. You get product CMS, variants, hosted checkout, Stripe and PayPal payments, and the same Interactions and animation tools as the rest of Webflow. Past 30 SKUs the surface gets thin: no native subscriptions, limited tax automation, no app store the size of Shopify's, and slower add-of-features cadence. For a brand site with a small shop, Webflow Ecommerce is fine. For a store-first business above $250K per year, Shopify saves operating hours every week.
Can you sell on Webflow without Shopify?
Yes. Webflow Ecommerce sites accept payments natively through Stripe, PayPal, and Apple Pay, with hosted checkout and order management in the Webflow Designer. The trade-offs vs Shopify: Webflow charges 0 percent transaction fees on Plus, 2 percent on Standard, and 0 percent on Advanced (subscription tiered), tax handling is basic outside the US, no native subscriptions, and the ecosystem of plug-and-play apps is small. Many brands run Webflow standalone for catalogs under 30 SKUs and only adopt Shopify once recurring billing, multi-region tax, or a 500-app stack become necessary.
What does a Webflow Ecommerce site cost vs Shopify in 2026?
Webflow Ecommerce: Standard $29 per month with 2 percent transaction fee, Plus $74 per month with 0 percent fee, Advanced $235 per month with 0 percent fee, plus the workspace seat. Shopify: Basic $29 per month, Grow $79, Advanced $299, Plus from $2,300 per month. The platform fee delta is small. The real difference shows up in app subscriptions: a typical $1M Shopify store runs $300 to $700 per month in apps; a comparable Webflow setup runs $50 to $200 per month because the app market is smaller. Net 24 month TCO for a $1M brand is usually within 15 percent either direction; pick by features, not subscription line.
Can I use Webflow as a front-end for Shopify?
Yes, the hybrid play is well documented. Two paths exist. The Buy Button SDK embeds Shopify product cards and checkout into a Webflow page via a JavaScript snippet, takes 1 to 2 days to wire, and works for catalogs under 50 SKUs. The Storefront API path uses Shopify's GraphQL API to render product data inside Webflow with custom code, gives full design control, but is a multi-week build that needs a developer. Both keep cart, checkout, tax, and shipping inside Shopify, which is the value: design-system flexibility from Webflow, commerce reliability from Shopify.
Which has better SEO: Webflow or Shopify?
Both are competitive when configured correctly. Webflow ships clean HTML, supports custom title and meta fields, schema via custom code blocks, and renders server-side, which crawlers prefer. Shopify since 2023 has improved canonical management, automatic product schema, sitemap generation, and Core Web Vitals out of the box. The practical edge: Webflow gives more granular control over per-page schema and URL patterns, useful for content-heavy brand sites; Shopify gives stronger ecommerce-specific schema and faster mobile defaults, useful for catalog pages. Neither blocks ranking; the build quality matters more than the platform.
How hard is a Webflow to Shopify migration?
Moderate. Products, customers, and order history export from Webflow via CSV or the API and import cleanly to Shopify. Design does not migrate because Webflow output is proprietary HTML and CSS not portable to Liquid; the new Shopify theme is a fresh build. The longer pole is SEO: a full URL map, 301 redirect plan, title and meta preservation across ranking pages, and schema continuity across product and collection templates. A typical Webflow Ecommerce to Shopify migration runs 8 to 12 weeks including a redesign. Custom CMS-driven Webflow sites with deep page templates can run 12 to 16 weeks.
When should I pick Webflow over Shopify?
Three scenarios. One: pure brand or marketing site with a small shop, under 30 SKUs, where design freedom and editor velocity matter more than commerce depth. Two: a content-led media or SaaS brand where the website is the primary growth channel and ecommerce is secondary. Three: a design studio shipping client sites that need to be editable by a non-technical team, where Webflow's visual CMS is the value. If any of these describe the project, Webflow wins. If the brand is store-first, has subscription products, sells in three or more regions, or runs above $1M per year, Shopify is the safer pick.
§ 12 · audit before you build
Platform audit. Then build.
A 30-minute audit, a written recommendation, no platform allegiance. Most audits we run end with "stay where you are"; we get paid the same either way.
related services + reading
Published .