What people actually mean by "integrate ecommerce"
You've got a website. A marketing site, a portfolio, a blog, maybe a Webflow or Squarespace build. It works. It does what you want visually. But now you need to sell something from it.
The wrong move is to throw it away and rebuild on Shopify. The right move depends on three things:
- What you're selling. One product or a catalogue? Physical or digital? Subscription or one-off?
- What your site runs on. Anything you can paste a script tag into, the options open up.
- How much of the checkout experience you want to own.
This post walks through what "integration" actually looks like in 2026 for each of those axes. No replatforming required if you pick correctly.
The three real integration patterns
Pattern 1: Redirect to a hosted checkout
The simplest. Your site has buy buttons. Click a button, the customer leaves your site for the checkout (Stripe Payment Links, Gumroad, Payhip, Lemonsqueezy). Payment happens on their domain, they return to your thank-you page afterwards.
Pros: zero JS integration, works on literally any website, low maintenance. Cons: the UX break (leaving your site) hurts conversion. Branding is inconsistent. Cart-abandonment flows and analytics get harder.
Good fit for: single-product creators, low volume, technical distaste for embedding anything.
Pattern 2: Embed a widget in-page
An embedded widget runs inside your site. Customer never leaves. Cart, product details, checkout all render inside your pages.
This is what Shoprocket, Snipcart, Ecwid, and similar platforms offer.
Typical integration:
<!-- EXAMPLE ONLY. Grab your real snippet from Sales channels → Embeds in your dashboard -->
<script src="https://cdn.shoprocket.io/loader.js" data-pk="pk_yourkey"></script>
<div data-shoprocket="catalog" data-embed-id="emb_xxx"></div>
One line, one paste, done. The widget auto-syncs with your dashboard: products, pricing, images, tax rules, shipping options, payment methods. Customers stay on your domain from "browse" through "thank you for your order".
Pros: consistent UX, brand control, fewer conversion leaks. Cons: your site now has a JS dependency. Most are lightweight (~20-50KB) but it's non-zero.
Good fit for: any site that wants a real shop without replatforming.
Pattern 3: Headless (API) integration
You build the UI yourself and call a commerce API (Stripe API, Shopify Storefront API, BigCommerce, Commercetools) for the commerce mechanics. Fully custom, fully yours.
Pros: complete control, no visual compromise, scales to custom flows. Cons: real engineering work. You're building checkout, cart state, tax calculation, inventory sync, webhooks. Months of time, not minutes.
Good fit for: teams with a dedicated dev on commerce full-time, or products that couldn't fit a pre-built widget.
The decision tree
Start with "do you want your customer to leave your site":
- Yes: Pattern 1 (hosted checkout link). Stripe Payment Links or Gumroad, 10 minutes to set up.
- No: go to next question.
Do you want to write custom code?
- Yes, we have dev capacity: Pattern 3 (headless).
- No, we want pre-built: Pattern 2 (embedded widget). This is where most sites land.
For Pattern 2, the next decision is the platform choice. That's covered in our separate piece: embeddable shopping cart platforms compared.
What a real Pattern 2 integration looks like on common platforms
WordPress
Drop the embed snippet into a Custom HTML block (block editor) or a text widget (classic sidebar). No plugin install required.
Squarespace
Add a Code Block on any page. Paste. The widget respects your Squarespace theme's width and spacing.
Webflow
Embed Element → paste. Webflow's static export still includes the embed on publish.
Framer
Embed element → paste. Framer's dev tools make it easy to drop the snippet on a specific section.
Carrd
Custom code component (paid plan feature). Single-page sites with a shop tab, straightforward.
Notion
Use a public Notion page as your site, embed via a service like Super or Potion, and paste the snippet. Becomes an actual store.
Static HTML / Jekyll / Hugo / 11ty
Paste the snippet into whichever template renders your shop page. Nothing else.
What changes on your site after integration
Less than you think.
- Your existing pages stay as they are. No theme edits required.
- The script loads async, so page speed is effectively unchanged (Lighthouse scores hold steady).
- Products, prices, and inventory live in your commerce dashboard, not your CMS.
- Customer data (orders, emails, addresses) flows to the commerce platform. Your CMS doesn't need to handle any of that.
What you do NOT need to do:
- Rebuild your site
- Install a CMS plugin
- Migrate content
- Hire a developer
- Buy a new domain
Tip: Test the widget on a staging page first. It shouldn't conflict with anything but it's worth verifying against your specific theme before pushing it to a production shop page.
When to actually replatform
Sometimes the answer IS "move to a full commerce platform". Signs:
- You're doing $100k+/month and your site's core job has become selling, not brand.
- You have POS integration needs (physical retail + online).
- Your product catalogue is >1,000 SKUs with constant updates.
At that scale, Shopify Plus or similar starts paying for itself. For most independent sites under that threshold, embedding is cheaper, faster, and keeps the site you already have.
TL;DR
- Hosted checkout link: fastest, breaks UX at payment. Good for single products.
- Embedded widget: keeps customer on your site, no replatforming. Good default.
- Headless API: build-your-own, months of work. Only worth it at scale.
Try Shoprocket's embed on your existing site. Free trial, no card required. Pricing: $29 onward, zero transaction fees on every plan.
Building ecommerce tools for independent sellers since 2013.
