---
title: "Framer Commerce: How to Sell Products on a Framer Site"
description: "Framer doesn't have a native shopping cart, but there are real ways to sell products on a Framer site today. An honest look at every current option."
canonical_url: "https://framerhub.io/blog/framer-commerce-guide"
last_updated: "2026-10-20T00:00:00.000Z"
---

Framer is a design-first website builder, not a commerce platform — it never claimed to be one. If you're trying to sell products on a Framer site, the honest starting point is: there's no native cart, no native checkout, no native inventory system. Everything that works today routes through an external commerce backend, most commonly Shopify. Here's what actually exists right now, what each option is good for, and what's still missing.

## Framer Commerce (Shopify-Backed, Live)

**Framer Commerce** is a real, currently live integration connecting a Framer-designed storefront to a Shopify backend — you design the site visually in Framer while Shopify handles products, inventory, cart state, and checkout. It's listed on Framer's own marketplace and has a dedicated site at framercommerce.com. This is not a FramerHub product; it's worth naming clearly so you're not confused about who built or supports it.

What it's good for: teams who want Framer's design flexibility on the front end without giving up Shopify's mature commerce backend — payment processing, tax calculation, shipping rules, and inventory management that would take significant engineering effort to rebuild natively.

What to check before committing: like any Shopify-Framer bridge, verify current pricing, supported Shopify plan tiers, and exactly which storefront features (variants, discount codes, subscriptions) are supported before you scope a client project around it. Integration depth between two separate platforms tends to have edge cases that only show up with real product catalogs.

## Frameship (Independent Alternative)

**Frameship** is a separately built Shopify-to-Framer integration solving the same core problem — Shopify backend, Framer front end — through an independent implementation. If you're evaluating options, treat this as a genuine alternative to Framer Commerce rather than a duplicate: different teams, different implementation details, and potentially different feature coverage or pricing.

The practical evaluation approach: if you already have Shopify data (products, variants, existing customers), test both integrations against a copy of your real catalog before committing. Integration behavior with real-world messy data — long product titles, many variants, custom metafields — reveals differences that a demo store won't show you.

## Embeds and Third-Party Checkout Widgets

If you don't need a full storefront — just a way to sell one, five, or a dozen products without managing inventory or building a browsable catalog — a full Shopify integration is often more infrastructure than the project needs. Lighter options:

- **Stripe Payment Links** embedded via an HTML component — fastest to set up for a handful of fixed-price products or a single offer.
- **Gumroad or Lemon Squeezy embeds** — well-suited for digital products (templates, courses, downloads) where you want built-in licensing and delivery without a full ecommerce backend.
- **Shopify's Buy Button** embedded directly — a middle ground: you get Shopify's checkout and inventory without adopting a full Framer-Shopify integration plugin, useful if you only need a small product grid rather than a complete storefront experience.

These approaches trade storefront sophistication (filtering, faceted search, cart persistence across pages) for setup speed. For a client selling three consulting packages or a handful of physical products, this is very often the right call over a full Shopify integration.

## How These Integrations Actually Work

It helps to understand the basic architecture before you scope a project, because it explains both the strengths and the limits. In a typical Shopify-Framer setup:

1. **Shopify remains the system of record** for products, variants, pricing, and inventory. You keep managing catalog data in Shopify's admin, the same way you would with any Shopify storefront.
2. **The integration plugin pulls product data into Framer** so you can lay out product grids, detail pages, and collection pages using Framer's visual design tools instead of Shopify's more rigid theme editor.
3. **Checkout typically redirects to or embeds Shopify's checkout flow**, since Shopify's PCI compliance, tax handling, and payment processing are what you're paying to keep rather than rebuild.

This split matters for two reasons. First, it means your product content updates happen in Shopify, not in Framer's CMS — if you're used to editing everything inside Framer, this is a workflow shift worth walking clients through before launch, not after. Second, it means design changes in Framer don't touch your commerce logic at all, which is actually a feature: you can redesign the storefront without ever touching pricing, inventory, or checkout configuration.

## Real Scenarios We See From Client Work

A few patterns come up repeatedly with freelancers and agencies building commerce sites in Framer:

- **A boutique brand migrating off a generic Shopify theme** wants Framer's design quality without giving up Shopify's operational tooling their team already knows. This is the clearest case for a full Shopify-Framer integration — the backend stays familiar, the front end gets a redesign.
- **A service business wants to sell a handful of fixed packages or add-ons** alongside an otherwise content-driven site. Here, a full commerce integration is overkill; an embedded Stripe Payment Link or two gets the job done in an afternoon instead of a multi-day integration setup.
- **A course creator or digital-product seller** doesn't need inventory or shipping at all — Gumroad or Lemon Squeezy handle licensing and delivery natively, which a general Shopify integration doesn't add value over for purely digital goods.
- **An agency managing several client stores** cares less about which specific integration and more about consistency across projects — picking one integration and standardizing on it across client work reduces the support burden of troubleshooting two different Shopify bridges.

Matching the scenario to the right tool up front avoids the common failure mode: building a full Shopify storefront integration for a client who only ever needed to sell three things.

## What's Still Genuinely Missing

Being honest about the ceiling here matters more than the pitch. Even with a mature Shopify integration:

- **Beyond Shopify, backend options are thinner.** For **WooCommerce**, the plugins that have existed are basic — they sync your Woo products and render much of the page straight from WordPress, so there's little room to customize the design. A more capable Framer↔WooCommerce integration (see our [WooCommerce plugin](/plugins/woocommerce)) lets you keep Woo for products, orders, payments, and checkout while actually designing the storefront in Framer. For other platforms (BigCommerce, a custom backend), you're still building a custom embed or API integration yourself.
- **Catalog-level filtering still depends on your CMS setup, not the commerce integration.** A large product catalog with multi-field filtering (category, price range, availability) needs the same filtering layer a directory site needs — Shopify integrations solve checkout, not discovery. If your store needs real filtering across dozens or hundreds of products, pair the commerce integration with [CMS Filter](/plugins/framer-cms-filter) on the CMS layer that mirrors your product data, rather than expecting the commerce plugin to handle search and filtering on its own.
- **Subscription and membership commerce is a separate problem.** Selling recurring access (a membership tier, a subscription product) overlaps with commerce but usually needs different tooling than a one-time-purchase Shopify storefront.

## Where FramerHub Fits Today

We don't have a live Shopify integration yet — it's on our roadmap and **coming soon**. If you want to be notified when it ships, the [Shopify integration waitlist](/plugins/shopify) is the place to do that. Until then, Framer Commerce and Frameship are the real, live options for Shopify-backed storefronts, and the embed approaches above cover simpler product-selling needs without a full integration.

For the broader landscape of ecommerce approaches in Framer — including WooCommerce and headless setups beyond Shopify specifically — our [Framer ecommerce guide](/blog/framer-ecommerce-guide) covers the wider picture.

## Choosing the Right Path

A quick way to decide, based on what we see across client projects:

<table>
<thead>
  <tr>
    <th>
      Situation
    </th>
    
    <th>
      Best fit
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Full product catalog, existing Shopify store
    </td>
    
    <td>
      Framer Commerce or Frameship
    </td>
  </tr>
  
  <tr>
    <td>
      A handful of fixed-price products or services
    </td>
    
    <td>
      Embedded Stripe Payment Links or Gumroad
    </td>
  </tr>
  
  <tr>
    <td>
      Digital products (templates, courses, downloads)
    </td>
    
    <td>
      Gumroad or Lemon Squeezy embed
    </td>
  </tr>
  
  <tr>
    <td>
      Large catalog needing filtering/search
    </td>
    
    <td>
      Shopify integration + CMS Filter on the product-browsing layer
    </td>
  </tr>
  
  <tr>
    <td>
      Recurring membership or subscription access
    </td>
    
    <td>
      Separate membership tooling, not a commerce plugin
    </td>
  </tr>
</tbody>
</table>

Match the tool to the actual catalog size and complexity, not to what looks most impressive in a demo. A three-product embed setup that ships this week beats a full storefront integration that's still being configured a month later.

Whichever path you pick, budget time for testing the actual checkout flow with a real card in test mode before launch — commerce is one of the few areas of a Framer build where a visual bug is annoying but a broken checkout step is a lost sale. Walk through the entire path yourself, on both desktop and mobile, before handing it to a client for their own review.

## FAQ

**Does Framer have a native shopping cart?**
No. Framer doesn't have a built-in cart, checkout, or inventory system. Commerce on a Framer site today happens through a Shopify-backed integration (like Framer Commerce or Frameship) or an embedded third-party checkout, not a native Framer feature.

**What is Framer Commerce?**
Framer Commerce is a marketplace plugin that connects a Framer site to a Shopify backend, letting you design storefronts in Framer while Shopify handles products, inventory, cart, and checkout. It's a real, live integration — not a FramerHub product.

**Is Frameship different from Framer Commerce?**
Yes. Frameship is an independently built Shopify-to-Framer integration, functionally similar in that it also connects Shopify's backend to a Framer front end, but built and maintained by a separate team.

**Will FramerHub have its own Shopify integration?**
A Shopify integration is on our roadmap and coming soon — join the waitlist on the plugin page to be notified when it ships. Today, Framer Commerce and Frameship are the live Shopify options.

**What if I only need to sell 2-3 products, not a full store?**
For a handful of products, an embedded checkout widget (Stripe Payment Links, Gumroad, or Shopify's Buy Button) inside an HTML embed component is usually faster to set up than a full Shopify-backed storefront integration.