Klaviyo Shopify Setup on a Framer Storefront: What Breaks
Yes, a Klaviyo Shopify setup keeps working when your storefront is built in Framer — but only about half of it survives untouched. Everything Klaviyo pulls out of Shopify's backend (orders, customers, checkouts, your product catalog) keeps syncing exactly as before, because that data moves server-side over the API and never touches your theme. What breaks is the onsite layer: viewed-product tracking, signup forms, review widgets and back-in-stock buttons were all written to inject themselves into a Liquid theme you no longer have.
The onsite layer is simply the set of Klaviyo features that run in the shopper's browser rather than on Shopify's servers. On a stock theme, the Klaviyo Shopify app installs all of it for you. On a Framer storefront, you install it yourself — and knowing which half is which is the difference between a two-hour job and a month of wondering why browse abandonment is empty.
This matters commercially, not just technically. Klaviyo's FY2025 annual report puts about 77.9% of its annual recurring revenue with customers who also use Shopify, so the integration gets serious engineering attention — and the headless path is documented, not improvised.
What the Klaviyo Shopify integration still does for free
Everything that originates in Shopify keeps flowing without a line of frontend code. Klaviyo's own developer documentation is explicit that for a headless Shopify store, every component except website activity syncs normally because it is
"fetched server-side via API"
That covers Placed Order, Ordered Product, Fulfilled Order, Canceled Order, Refunded Order and Checkout Started, plus customer profiles, email and SMS subscriber status, and your full product catalog. Your Klaviyo email marketing for Shopify keeps running on real purchase data from day one.
One catalog caveat is worth fixing early: product URLs sync as yourstore.myshopify.com links. Klaviyo support can rewrite them to your live Framer domain, and you want that done before a single email goes out with the wrong link in it.
The Klaviyo feature audit for a Framer storefront
Here is the whole surface, feature by feature, with the fix for each one.
| Klaviyo feature | On a Framer storefront | What you actually do |
|---|---|---|
| Order & customer sync | Works unchanged | Nothing. Connect the native integration |
| Placed / Fulfilled / Refunded Order | Works unchanged | Nothing |
| Checkout Started (abandoned checkout) | Works unchanged | Turn off Shopify's own abandoned-checkout emails first |
| Product catalog | Works, one fix | Ask Klaviyo support to swap myshopify.com URLs for your domain |
| Email & SMS subscriber sync | Works unchanged | Enable it in integration settings |
| Active on Site | Needs Framer-side work | Load klaviyo.js on every page |
| Viewed Product / browse abandonment | Needs Framer-side work | Push a Viewed Product event from the product page |
| Added to Cart | Needs Framer-side work | Push the event; the profile must already be cookied |
| Signup forms | Needs Framer-side work | Free once klaviyo.js loads; retarget rules by URL |
| Back in stock | Needs Framer-side work | Build your own button, POST to the subscriptions endpoint |
| Reviews | Needs Framer-side work | Install the Reviews app, embed widget divs with product IDs |
Nothing in that table is unavailable. That is the real headline: in 2026 there is no Klaviyo feature a Framer storefront simply cannot have. There are only features you have to wire up yourself.
Does the Klaviyo abandoned cart flow still work?
It does, and this is the single most reassuring thing about the whole setup. Checkout Started fires from Shopify's hosted checkout, which you keep when the storefront moves to Framer, so the event reaches Klaviyo server-side with the cart contents and a restore link attached. Your highest-revenue flow survives the migration untouched.
The nuance is upstream. A Klaviyo abandoned cart flow triggered on Added to Cart — catching people who never reached checkout — depends on an event your storefront emits. Until you send it, that flow sits silent. The same logic governs every pixel on the site, which is why getting Shopify's Meta Pixel events firing from Framer tends to land in the same sprint. We covered the full recovery sequence in our guide to abandoned cart email on Shopify from a Framer storefront.
Flows are where the money is: across six DTC Shopify brands measured over 90 days in 2026, Forge Digital Marketing found a median 27.28% of store revenue attributed to Klaviyo, with automated flows producing 51.09% of it. Losing browse and cart abandonment quietly is expensive.
Do Klaviyo forms work without a Shopify theme?
Yes — and this trips people up, because Shopify's own Forms app does not support headless storefronts, so merchants assume Klaviyo's don't either. Klaviyo.js does double duty: it records Active on Site and it renders your Klaviyo forms. Load that one script and every popup, flyout and embed you build in Klaviyo publishes to your Framer site without a redeploy.
Targeting changes shape slightly. Instead of theme templates, you write rules against your live URLs, which in practice is cleaner. Embedded forms need a container element on the page where the form should appear.
Reviews: the answer changed in 2026
This is the part most older advice gets wrong. For years the honest answer was that Klaviyo Reviews worked only through the native Shopify app, with no path for a custom frontend. That is no longer true. Klaviyo now publishes a documented headless install for Reviews, last updated in October 2026, covering star ratings, review summaries, review lists, a featured carousel and an SEO all-reviews page.
The mechanics are straightforward with one catch. You add Klaviyo.js, then drop widget containers into your Framer page, and you must pass each product's numeric Shopify product ID into the widget — for example data-id="123456789" — because there is no Liquid product.id to read. Your product data already has to reach Framer for the page to exist, so this is usually a field you are passing anyway. If reviews are a deciding factor in your stack, compare the alternatives in our review app roundup for Shopify on Framer.
Back-in-stock follows the same pattern: Klaviyo exposes client-side and server-side subscription endpoints, and you supply the variant as a composite ID in the form $shopify:::$default:::VARIANT_ID. You own the button and the modal; Klaviyo owns the notification.
The build order that saves you a week
Do it in this sequence and nothing blocks anything else. Connect the native integration and let the historical sync run. Fix the catalog URLs. Add klaviyo.js sitewide — that single step unlocks forms, reviews widgets and Active on Site at once. Then add Viewed Product and Added to Cart on the product page, identify logged-in customers, and only then embed review and back-in-stock widgets.
The pattern underneath all of this is the one that defines headless work generally: Shopify stays the system of record, your frontend becomes responsible for telling the rest of the stack what shoppers are doing. Tools like FramerLink exist to keep that product data flowing into Framer so the IDs those snippets need are already on the page.
Treat the onsite layer as part of the build, not an afterthought, and a Framer storefront costs you nothing in retention revenue. Skip it, and you will ship a beautiful store whose best-performing emails never send.
Frequently asked questions
Does Klaviyo work with a headless Shopify store?
Yes. Klaviyo's native Shopify integration syncs orders, customers, checkouts and your product catalog server-side over the API, so none of it depends on your theme. Only website activity breaks, because onsite tracking, forms and widgets were written to inject into a Liquid theme a headless storefront no longer has.
Will my Klaviyo abandoned cart flow still work on a custom storefront?
Yes, if it triggers on Checkout Started. That event fires from Shopify's own hosted checkout and reaches Klaviyo server-side, untouched by your frontend. Flows triggered on Added to Cart are different: that event comes from your storefront, so you have to send it yourself before the flow will run.
Do Klaviyo signup forms work on a non-Shopify frontend?
They do, once Klaviyo's onsite JavaScript is loaded on the page. Klaviyo.js both tracks activity and renders forms, so popups, flyouts and embeds publish from Klaviyo as normal. Targeting rules still work, but they match on your live storefront URLs rather than Shopify theme templates.
Can you use Klaviyo Reviews on a headless Shopify store?
Yes. Klaviyo documents a headless install: add Klaviyo.js, then place widget containers for star ratings, review lists and carousels in your own templates. The one requirement is supplying each product's numeric Shopify product ID to the widget, since there is no Liquid object to read it from.
What does Klaviyo cost you in setup time on a custom frontend?
Budget for five pieces of frontend work: loading Klaviyo.js, sending Viewed Product, sending Added to Cart, identifying logged-in customers, and embedding any review or back-in-stock widgets. Everything else is configuration inside Klaviyo. Most teams finish the tracking layer well before they finish designing the product page.
Sources
- Integrate with a Shopify Hydrogen store — Klaviyo Developers
- How to install Klaviyo Reviews on Shopify (vintage themes and headless) — Klaviyo Help Center
- Set up back in stock via API — Klaviyo Developers
- Klaviyo, Inc. Annual Report on Form 10-K (fiscal year 2025) — U.S. Securities and Exchange Commission
- How Much Revenue Should Klaviyo Generate for a Shopify Store? — Forge Digital Marketing