Build or Buy an Embeddable Buy Button for Partner Sites?
Embeddable buy buttons are a WAIT, because Shopify's first-party Buy Button channel is free on every plan and there is nothing to buy. Shopify's documentation states the Buy Button sales channel is included in all Shopify subscription plans (verified Sep 2026). The Selling online category's 24 sales-channel apps contain zero embeddable-checkout alternatives. Build only when styling control blocks you, which means the Storefront API.
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's Buy Button documentation and its App Store listing, then worked through all 24 apps in Sales channels under Selling online, on 2026-09-03. Every one of them is a marketplace or social channel — TikTok, Shop, Google, Facebook, Faire and similar — and not one is an embeddable checkout widget for a third-party website. Shopify's own wording is that the Buy Button sales channel is included in all Shopify subscription plans, with no paid tier at any level. The channel generates HTML and JavaScript embeds for a product or a collection, syncs in real time from the admin, and requires a supported payment gateway whose availability varies by country. Buy Buttons created before October 10, 2016 are no longer supported, the only deprecation in close to a decade. This is not a thin market. It is an empty one, because the first-party channel already fills it at no cost.
- Reference scenario
- $20M–$100M GMV · products embedded on partner blogs and content sites · standard Shopify plan · no headless storefront
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| A handful of products on a partner blog or content site | WAIT | The native channel generates the embed in the admin, costs nothing on any plan and keeps checkout on Shopify. There is no decision here beyond switching the channel on. |
| Dozens of embeds across many partner pages, updated often | WAIT | Real-time sync from the admin is exactly what breaks a homegrown embed program: a price change reaches every partner page without anyone touching a partner's site. |
| Design control beyond the Buy Button's styling options | BUILD | Styling options are the ceiling and there is no higher tier to buy. Deeper UI control means the Storefront API, which is a real project rather than a snippet. |
| Partner commission or per-partner revenue attribution is the point | CUSTOMIZE | The widget sells and does not settle a revenue share. Keep the free channel for the checkout and build the attribution and payout layer around it. |
What Embeddable buy button for partner sites Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A product embedded inside the article a reader is already reading removes the trip to a storefront, which is the entire reason to sell on a partner page. |
| Operational efficiency | High | Real-time sync from the Shopify admin pushes a price or availability change to every partner embed without anyone editing a partner's site. |
| Customer experience | Medium | Checkout runs on Shopify's own infrastructure, so a shopper on a partner blog gets the same payment methods and order confirmation as on your storefront. |
| Data & insight | Medium | Per-partner attribution decides which content site is worth a commission, and the native widget completes the sale without settling that question. |
Spend ceiling: Spend nothing. The Buy Button sales channel is included in all Shopify subscription plans with no paid tier at any level (verified Sep 2026), so this capability has no budget line at all. A number only appears when the styling ceiling forces a Storefront API build at $18,000 to $50,000 (Deploi estimate, illustrative), which is a different project with a different name.
What buying enables (top apps)
- + Embeddable HTML and JavaScript for a single product or a whole collection, generated in the admin without writing code
- + Quick checkout links for social posts and direct messages alongside the site embeds
- + Real-time sync from the Shopify admin, so price and availability updates reach every embed with no partner involvement
- + Checkout on Shopify's own infrastructure, keeping payment handling off the partner's page entirely
What building additionally unlocks
- + UI beyond the styling options, including your own variant, quantity and cart behavior on the partner's page
- + Per-partner attribution carried through to the order, which turns commission settlement into a report
- + Control over script weight and loading on a partner's site, where a third-party embed is a cost they feel
- + One configurable embed reused across every partner instead of a separately generated snippet per placement
Find Your Verdict in 3 Questions
Is the target a site you do not control, such as a partner blog, a content site or a press page?
Yes: Go to question 2.
No: Your verdict: WAIT. Shopify cautions against Buy Buttons on your own store or blog because of checkout issues, so use normal storefront links there.
Do the Buy Button's styling options fit the partner page well enough?
Yes: Go to question 3.
No: Your verdict: BUILD. Deeper UI control means the Storefront API and a real project at $18,000–$50,000 (Deploi estimate, illustrative).
Does a partner need commission or per-partner revenue attribution?
Yes: Your verdict: CUSTOMIZE. Use the free channel for the checkout and build the attribution and settlement layer around it.
No: Your verdict: WAIT. The Buy Button channel is included on every Shopify plan and nothing on the App Store competes with it (verified Sep 2026).
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | The embed code is generated in the Shopify admin and pasted into a page, while a Storefront API embed takes an estimated 6–10 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Included in all Shopify subscription plans with no paid tier (verified Sep 2026), which is as good as a recurring cost gets. | ||
| Maintenance & upgrades | Shopify maintains the channel, and the single deprecation in close to a decade affected only buttons created before October 10, 2016. | ||
| Switching & exit | Embed code sits on pages you do not control, so removing or replacing it means asking every partner to edit their own site. | ||
| Risk | |||
| Vendor risk | A first-party sales channel maintained by Shopify itself carries about as little vendor risk as anything on this hub. | ||
| Security & compliance surface | Checkout stays on Shopify's own infrastructure, so payment handling never lands on a partner's page or in your custom code. | ||
| Platform-deprecation exposure | Storefront API versions ship quarterly with a 12-month minimum support window, so a custom embed on someone else's site needs version bumps on a schedule you do not set. | ||
| Value | |||
| Fit to requirement | Styling options cover most partner pages and stop where brand guidelines get specific, which is the one honest gap in the native lane. | ||
| Time to market | A partner page can be selling this afternoon, against a project measured in months for a result most readers cannot tell apart. | ||
| Performance & scale | Either lane puts a third-party script on somebody else's page, which is a performance cost the partner feels rather than you. | ||
| Data ownership & AI-readiness | Per-partner attribution is what decides which content site earns a commission, and the native widget sells without settling that question. | ||
| Focus & opportunity cost | Rebuilding a free first-party channel is the clearest example on this hub of engineering effort spent to arrive where you already were. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Buy Button channel | Native — First-party Shopify sales channel, developer Shopify. Generates embeddable HTML and JavaScript for an individual product or a whole collection, plus quick checkout links for social posts and direct messages, with customizable styling and real-time sync from the admin so updates need no code. Requires a supported payment gateway, and availability varies by country and region. Shopify's own guidance cautions against using Buy Buttons on your own Shopify store or blog because of checkout issues. Buy Buttons created before October 10, 2016 are no longer supported, the single deprecation in close to a decade. The listing shows 3.9★ across 183 reviews, which is a modest score and the only signal available given nothing competes with it. | Free — included in all Shopify subscription plans, with no paid tier (verified Sep 2026) | Selling a product or collection inside a partner site or blog post without sending the reader to your storefront |
| Selling online sales channels | Category — The App Store category a search for this lands in, and it holds no answer. All 24 listings in Sales channels under Selling online are marketplace and social channels — TikTok, Shop, Google, Facebook, Faire and similar — and not one is an embeddable checkout widget for a third-party website. Nothing here is a competitor to the native Buy Button, and nothing here should be installed for this requirement. | Marketplace and social channel apps priced per channel; none of them serves this requirement (illustrative) | Selling on a marketplace or a social platform, which is a genuinely different job from embedding checkout on a partner's own site |
| Storefront API embed (custom) | Build lane — The only real build lane, and it is much bigger than the ask. Cart and checkout driven through the Storefront API inside your own component, styled to the partner's page, with one configurable embed replacing many generated snippets. Worth it when brand guidelines outrun the Buy Button's styling options, or when per-partner attribution and revenue share have to be settled around the sale. | $18,000–$50,000 one-time plus upkeep (Deploi estimate, illustrative) | Brand-critical partner placements where the native styling ceiling is the actual blocker |
The Build Path
- Storefront API cart and checkout in your own component: Build the product display, variant selection and cart against the Storefront API, then hand off to Shopify's checkout. This is the same architecture as a headless storefront, scoped down to one embeddable component, which is why the effort lands closer to a headless project than to a snippet. Start by proving that the Buy Button's styling options genuinely cannot get there, because that is usually the whole justification.
- One configurable embed instead of many generated snippets: A generated snippet per placement means every change is a request to a partner. A single script tag whose per-placement configuration carries product, layout, theme and partner ID turns those requests into a change you make on your own side. This is the operational advantage of the build lane, and it matters more than pixels once the partner count passes a dozen.
- Attribution and settlement around the sale: Carry a partner identifier through to the order, so revenue per partner is a report rather than an argument at the end of the quarter. Discount codes and campaign parameters do part of this today; an owned embed lets you attach the partner to the order itself. Decide up front whether partners see their own numbers, because that changes the design more than anything on the storefront side.
- Effort band
- $18,000–$50,000 for a Storefront API embed with per-partner configuration and attribution — Deploi estimate (illustrative); lands in the $25–75K contact-form band, and is worth spending only when the styling ceiling or the attribution requirement is real
- Typical timeline
- 6–10 weeks, against an afternoon for the native channel (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $2,700–$10,000/yr (Deploi estimate, illustrative). Storefront API versions ship quarterly with a 12-month minimum support window, so an embed living on someone else's site needs scheduled version bumps.
- What you own — and what you take on
- You own: the embed's UI, per-partner configuration, script weight on the partner's page, and partner attribution carried through to the order. You take on: API version upkeep, payment edge cases the native channel currently absorbs, and a component that has to keep working on sites you do not control.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0 (included in all Shopify subscription plans) | $18,000–$50,000 |
| Years 1–3 (recurring) | $0 (no paid tier at any plan level) | $8,100–$30,000 (upkeep) |
| 3-year total | $0 | ≈$26,100–$80,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † The buy column here is the free first-party Buy Button channel rather than a purchase, since no third-party product serves this requirement; its only cost is the time to place embeds.
- † Build column covers a Storefront API embed with per-partner configuration and attribution, plus annual upkeep; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Embed code lives on pages you do not control, so replacing or removing it means asking every partner to edit their own site
- — Styling options are the ceiling and there is no higher tier to buy your way past them
- — The channel requires a supported payment gateway, and availability varies by country and region
- — Shopify's own guidance cautions against using Buy Buttons on your own Shopify store or blog because of checkout issues
On the build path
- — Storefront API versions ship quarterly with a 12-month minimum support window, so a partner-hosted embed needs scheduled version bumps
- — A custom script on a partner's page is a performance cost they feel, and a partner may eventually ask you to remove it
- — Replacing a free first-party channel means owning payment-gateway edge cases Shopify currently handles for you
- — ~$2,700–$10,000/yr in upkeep (Deploi estimate, illustrative)
What Merchants Say
The recurring surprise: a team scopes a headless project for one partner page, then finds the free first-party channel already generates the embed they needed.
The other pattern operators describe: the styling options run out before brand guidelines do, and there is no paid tier to upgrade into when that happens.
If You Change Your Mind Later
If you bought and outgrow it
The cost of leaving is other people's time. Embed code sits on partner pages, so removing or replacing it means a request to every partner, which argues for a short list of partners and a record of where every embed lives.
If you built and want out
Nothing strands on your side, though the same partner-page problem applies: a custom embed is code on someone else's site, and retiring it needs the same round of requests plus a version-support deadline you do not control.
When This Answer Changes
We're watching for:
- ▸ Any change to the Buy Button channel's styling options or its inclusion in every Shopify plan
- ▸ A third-party embeddable-checkout product actually appearing in the Selling online category, which has none today
- ▸ Partner commission arrangements becoming material enough that attribution, not pixels, drives the decision
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Is there an app for embedding Shopify checkout on another site?
No third-party app competes. Shopify's own Buy Button sales channel is the answer, and it is included in all Shopify subscription plans at no extra cost (verified Sep 2026). A review of the 24 apps in the Selling online sales-channel category turned up zero embeddable-checkout-widget alternatives. Nothing here needs buying.
What does the Shopify Buy Button cost?
The Buy Button sales channel costs nothing. Shopify's documentation states it is included in all Shopify subscription plans, with no paid tier at any level (verified Sep 2026). The channel requires a supported payment gateway, and availability varies by country and region. Its App Store listing shows 3.9 stars across 183 reviews, with Shopify as the first-party developer.
When is a custom embed worth building instead?
A custom embed is worth building when the Buy Button's styling options cannot match the partner page, or when per-partner revenue attribution matters. Shopify also cautions against using Buy Buttons on your own Shopify store or blog because of checkout issues. Both cases mean the Storefront API and a real project, at $18,000 to $50,000 (Deploi estimate, illustrative).
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Switch on the Buy Button sales channel and generate an embed for one product before scoping anything larger
- Confirm your payment gateway is supported in the countries the partner site reaches, since availability varies by region
- Test the styling options against the partner's actual page rather than against your brand deck
- Keep a record of which partner pages hold which embeds, because removing them later means asking each partner
- Use campaign parameters or dedicated discount codes to attribute partner revenue while the embed itself stays native
If you're going with BUILD
- Write down exactly which styling requirement the native channel cannot meet, and get it agreed before any code is written
- Design one configurable embed with a partner identifier rather than a generated snippet per placement
- Carry the partner identifier through to the order so revenue per partner is a report, not a quarterly argument
- Budget for quarterly Storefront API version bumps, since the embed lives on sites you cannot update on demand
Official Docs & Sources
- Buy Button sales channel — Shopify Help Center
- Metaobjects — Shopify Help Center
- Shopify Flow — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy a DTF Gang Sheet Builder and Nesting on Shopify?
Three young apps (33, 12 and 0 reviews) sell DTF gang sheets on Shopify. Buy one, export-test it, and keep production nesting in RIP software; build the handoff.
Build or Buy an Online Course and Certification Platform on Shopify?
Tevello covers courses, quizzes and completion certificates on one flat tier. A single listing carries this whole category, which is the risk worth pricing.
Should You Build or Buy Appointments & Booking on Shopify?
Appointments and booking on Shopify is a BUY: four rated apps cover availability, staff and reminders from free tiers to $299/month (verified Sep 2026).
Should You Build or Buy Auctions & Bidding on Shopify?
Auctions and bidding on Shopify is a BUY: niche apps run proxy bidding and winner checkout from free to $40/month (verified Sep 2026).
Should You Build or Buy Product Subscriptions on Shopify?
Product subscriptions are a genuine three-way call: native for simple replenishment, buy for retention depth, build the portal at scale.
Ready to sell on a partner's page without building anything?
Switch on the Buy Button channel first, because it is free on every Shopify plan and it does the job. Call us when the styling ceiling is genuinely blocking a brand-critical placement, or when partner commissions mean the sale has to carry an attribution you can settle on.
Contact us todayVerdict scored for the reference scenario above. The buy lane on this page is the free first-party Buy Button channel rather than a purchase — no third-party product serves this requirement. Estimates are not quotes; pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.