Framer Ecommerce: Shopify vs WooCommerce vs Simple Checkout (2026)

A client sends you a brief. They want to sell 40 products on their new Framer site. Shoppers should filter by size, color and price, and checkout should feel like part of the brand, not a widget from somewhere else.

You open Framer and find no cart, no checkout and no product pages. Framer ecommerce, as of October 2026, means connecting Framer to a platform that handles the money. There is no official Framer store feature, and the similarly named "Framer Commerce" is an independent Shopify plugin, not something Framer ships.

This guide compares every real way to sell on a Framer site: Shopify plugins, WooCommerce, Buy Button embeds and simple checkout links. For each one we cover what it does, what it costs you in setup and lock-in, and which client project it fits.

A disclosure before we start. We build two of the tools in this guide: FrameStoreKit (Shopify) and FrameWoo (WooCommerce). We also build sites for clients, and some of those projects are better served by a $0 Stripe link than by either of our plugins. We'll say so where that's true.

How Framer ecommerce works today

Every Framer store follows the same split.

1. A commerce backend is the system of record. Products, variants, prices, stock, orders, payments, tax and shipping live in Shopify, WooCommerce or a hosted checkout service.
2. Framer is the storefront. Your product grid, product pages, landing pages and brand story are designed on the Framer canvas, usually with product data stored in Framer CMS collections.
3. Something connects the two. That can be an embed script, a sync plugin, or custom code against the platform's API.
4. Checkout happens on the backend. The shopper pays on Shopify's checkout, WooCommerce's checkout, or the hosted page of Stripe, Gumroad, Lemon Squeezy or Polar. You never handle card data in Framer.

This split is good news for a designer. Pricing, tax and fulfillment logic stay with a platform built for them, and you can redesign the storefront without touching any of it. The trade-off is workflow. Your client edits products in the backend, not in Framer, so walk them through that before launch.

Here is what Framer itself gives you to work with:

• Framer CMS stores product content well: titles, prices, images, descriptions, categories. It does not process payments. Our covers collections and fields in depth.
• Embeds and code components let you add third-party scripts and React components. Every integration below uses one or both.
• Native forms collect leads. They don't take payment.

So the real question is which backend, and how it connects.

The five ways to sell on a Framer site

The catalog sizes are rules of thumb from client work, not hard limits. The bigger question is usually where the client already runs their business.

Option 1: Checkout links for a few products or services

A freelancer needs to take a project deposit. A designer sells one template pack. A coach sells three packages. None of them need a cart.

Link a Framer button to a hosted checkout page and you're done.

• Stripe Payment Links turn any product or price in your Stripe dashboard into a URL. Best for services, deposits and single physical items you ship yourself.
• Gumroad is the quickest path for creators selling downloads. It handles file delivery and can issue license keys.
• Lemon Squeezy acts as the merchant of record, so it collects and remits sales tax and EU VAT for you. That matters for software and digital goods sold worldwide.
• Polar handles payments, license keys and subscriptions for digital products. We use Polar for FramerHub's own checkout.

What you give up: no cart across multiple products, no stock tracking beyond what the checkout service offers, and no browsable catalog with filters. For a handful of offers, you don't need those.

Our take: start here whenever the product list fits on one page. A Stripe link that ships today beats a storefront integration that is still being configured next month.

Option 2: Shopify Buy Button embed

Your client has 12 products already in Shopify and wants a Framer site. They don't need a full catalog experience.

Shopify's Buy Button sales channel generates an embed script for a product or collection. Paste it into a Framer embed and you get a product card, a cart and Shopify's checkout.

Step by step:

1. In Shopify admin, add the Buy Button sales channel (check that the client's Shopify plan includes it). See Shopify's Buy Button docs.
2. Create a Buy Button for a product or a collection and set colors and fonts in Shopify's builder to roughly match your design.
3. Copy the embed code.
4. In Framer, add an Embed element, choose HTML, and paste the code. Size it with Framer's layout tools.
5. Design the rest of the page in Framer: photography, story, reviews, related products.
6. Place a test order on desktop and mobile before launch.

What works: Shopify keeps stock, tax and checkout in sync automatically, and setup takes an hour or two.

What doesn't: the product card and cart are Shopify's widget, styled in Shopify's builder, so they never fully match a custom Framer design. There are no product pages in Framer CMS, so no filtering, no search and no SEO-friendly product URLs on your domain.

Best for: brand sites selling a few physical products where the widget's look is acceptable.

Option 3: Shopify plugins for full Framer storefronts

This is what most people mean by "framer commerce" or "framer shopify". A plugin syncs your Shopify catalog into Framer CMS and gives you commerce components (product pages, variant pickers, cart drawer) that run on Shopify's Storefront API. Checkout redirects to Shopify's own checkout.

Your client keeps managing products, orders and discounts in Shopify admin. You get real product pages on the Framer domain, designed on the canvas.

There are three independent Shopify plugins you're likely to compare. None of them is made by Framer.

FrameStoreKit

FrameStoreKit is our Shopify plugin, built for designers and agencies who build stores for clients.

• Connects with a public Storefront token. No Admin token and no Shopify app install.
• One-click sync of the catalog into Framer CMS.
• A full store kit: product pages, variants and galleries, cart drawer, filters, search and sort, Shopify Markets multi-currency, subscriptions, Shop Pay express checkout, and customer accounts with order history and wishlist.
• Every component uses your project's Framer text styles and has full property controls, so the store follows your type system instead of a preset theme.
• Pricing: free up to 15 products, and paid licences are per store, so you can bill them to the client. Current plans are on the pricing page.

Framer Commerce

Framer Commerce is the best-known of the three. Despite the name, it is an independent product and not part of Framer. As of October 2026 it is sold as monthly or yearly plans tiered by product count, with a limited free plan.

Frameship

Frameship is another independent Shopify plugin. As of October 2026 it sells one-time licences per website, has a component library that covers accounts, subscriptions and bundles on its higher tier, and offers a done-for-you build service.

How to choose a Shopify plugin

Pricing models and feature lists change often, so check each pricing page on the day you scope the project. Then test against the client's real catalog, because demo stores hide the problems:

• Long product titles and many variants. Does the variant picker stay usable with 30 combinations?
• Metafields. Can you map the client's custom fields into Framer CMS?
• Design control. Do components pick up your text styles, or do you restyle every instance by hand?
• Billing model. A monthly plan the client pays forever, or a licence you add to the project invoice?
• Accounts and subscriptions. If the client needs logins, order history or recurring products, confirm they're supported on the plan you're quoting.

Pick one plugin and standardize on it across client projects. Supporting two different Shopify bridges doubles your troubleshooting.

Option 4: WooCommerce with Framer

Plenty of businesses already run WooCommerce. Their orders, payment gateways, shipping rules, tax setup and reporting live in WordPress, and moving all of that to Shopify would be a project in itself. What they want is a better storefront.

That's the case for keeping WooCommerce as the backend and designing the store in Framer. WooCommerce exposes products and orders through its REST API, so the same split works: Woo is the system of record and Framer is the front end.

Basic Woo-to-Framer plugins already exist, but they tend to be sync-only and render much of the page straight from WordPress, which leaves little room for design. is our design-first take on it:

1. Connect with a read-only WooCommerce REST API key. Nothing about the Woo setup changes.
2. Sync the catalog into Framer CMS: prices, stock, categories, tags, attributes, variations, ratings, images and galleries. Re-running the sync updates only what changed.
3. Design with 100+ commerce components: product pages, galleries, variant pickers, reviews, cart page and drawer, coupons, a free-shipping bar, filters, search, sort and pagination.
4. Customer accounts on pages you design: login, registration, addresses, order history, refund requests and wishlists.
5. Checkout stays native WooCommerce. FrameWoo writes nothing to orders, payments, tax or shipping.

What you need: a WordPress site with WooCommerce that you or the client host and maintain, plus a Framer plan for the storefront. If the client doesn't run WooCommerce today, this isn't the reason to start. Shopify is less to maintain.

Pricing: free for one store with up to 15 products and manual sync. Paid plans are one-time purchases per published store and include lifetime updates. Details are on framerwoo.com.

If you're weighing WordPress against Framer for the whole site, not just the store, our walks through that decision.

Option 5: A custom headless build

If you have developers, you can skip plugins and build directly against the Shopify Storefront API or WooCommerce's APIs using Framer code components and overrides.

You get total control over every interaction. You also own every bug: cart state, variant edge cases, token handling, inventory freshness and API changes. For most agencies a plugin covers most of the same ground for a fraction of the effort. Custom builds make sense when a client has unusual requirements no plugin supports, and a budget to maintain the code afterwards.

Shopify vs WooCommerce for a Framer store

Once a project needs a real catalog, the backend choice matters more than the plugin. Here is how the two compare from the storefront builder's side.

Our rule of thumb: use whatever the business already runs. If it runs neither, start with Shopify. A new store has less to maintain on a hosted platform, and the client's team will find Shopify help and staff more easily.

Product filtering for Framer stores

A store with 60 products needs filters. Shoppers want to narrow by category, size, color and price, and they want search.

FrameStoreKit and FrameWoo ship their own filter, search and sort components, and so do some other store plugins, so check those first. If your product data lives in a regular Framer CMS collection, for example a lookbook or a catalog you maintain by hand, you need a filtering layer on top of it.

Framer's native dynamic filters cover simple single-field cases. For multi-field combinations, price range sliders and real-time search, adds them to any CMS collection. The same patterns we use for real estate listings and job boards work for product catalogs.

When Framer is the wrong choice for a store

We'd rather lose a plugin sale than put a client on the wrong stack. Framer ecommerce is a weak fit when:

• Ecommerce is the whole business and the catalog runs to thousands of SKUs with complex inventory, bundles and fulfillment rules. A dedicated Shopify theme or a dedicated WooCommerce site is simpler to run.
• B2B features are required: net terms, customer-specific pricing, purchase orders. Check backend support first, and expect custom work on the storefront.
• The client's team can't manage two tools. A Framer storefront means editing the site in Framer and the products in Shopify or WordPress. Some teams won't want that.
• There is no design reason to use Framer. If the client is happy with a stock theme, the integration adds work without adding value.

It's a strong fit when the brand experience is the differentiator: fashion, design goods, creative studios, product launches, and content-led brands that sell alongside storytelling.

Real scenarios from client work

• A boutique brand leaving a generic Shopify theme. They keep Shopify admin, which their team knows, and get a storefront redesigned in Framer. Use a Shopify plugin.
• A WooCommerce store with years of orders and custom shipping rules. Moving to Shopify would mean migrating customers, orders and integrations. Keep Woo, and rebuild the front end in Framer with FrameWoo.
• A studio selling three service packages. Three Stripe Payment Links. Done in an afternoon.
• A designer selling a template pack. Gumroad, Lemon Squeezy or Polar, linked from a Framer landing page.
• A product launch with five SKUs and a waitlist. Shopify Buy Button now, and move to a plugin if the catalog grows.

Launch checklist for any Framer store

Whichever route you pick, run this list before handing the store to the client:

1. Place a test order on desktop and on a phone, using the backend's test mode.
2. Check that out-of-stock variants can't be added to the cart.
3. Confirm prices and currency match between the product page and checkout.
4. Test the cart after navigating between pages and after a refresh.
5. Confirm order confirmation emails arrive and come from the right sender.
6. Add analytics events for add-to-cart and begin-checkout, so you can see where shoppers drop off.
7. Make sure product pages have unique titles and meta descriptions, and are in the sitemap.
8. Write a one-page note for the client: where to edit products, where orders arrive, and who to call when checkout breaks.

Frequently asked questions

Does Framer have native ecommerce?

No. As of October 2026, Framer has no built-in cart, checkout, product inventory or payment processing. Every Framer store uses an outside platform for the transaction: Shopify, WooCommerce, or a hosted checkout such as Stripe Payment Links, Gumroad, Lemon Squeezy or Polar.

Is Framer Commerce made by Framer?

No. Framer Commerce (framercommerce.com) is an independent plugin that connects a Framer site to Shopify. Framer does not ship an official commerce product. Frameship and FrameStoreKit are other independent Shopify plugins.

Can I connect Framer to Shopify?

Yes. For a few products, embed Shopify's Buy Button. For a full storefront, use a Shopify plugin such as FrameStoreKit, Framer Commerce or Frameship, which sync the catalog into Framer CMS and hand off to Shopify's checkout. Developers can also build on the Shopify Storefront API.

Can I use WooCommerce with Framer?

Yes. FrameWoo syncs a WooCommerce catalog into Framer CMS and gives you components to design the storefront in Framer. Orders, payments, tax and shipping stay in WooCommerce. You need your own WordPress site with WooCommerce installed.

What is the easiest way to sell a few products on Framer?

Link a Framer button to a Stripe Payment Link for a single product or service, use Gumroad, Lemon Squeezy or Polar for digital goods, or embed Shopify's Buy Button for a few physical products. None of these need a plugin.

Where to start

• One to ten items or services: a checkout link from Stripe, Gumroad, Lemon Squeezy or Polar.
• A few physical products, already on Shopify: the Buy Button embed.
• A full catalog on Shopify, or starting fresh: a Shopify plugin. Try FrameStoreKit free with up to 15 products, and compare it with Framer Commerce and Frameship on the client's real catalog.
• A business already running WooCommerce: , free for up to 15 products.

Framer handles the design. Pick the backend your client already trusts, and connect it in the simplest way that covers the catalog.