Shopify Plus Agency Workflow: Where a Framer Build Fits
Yes, a Shopify Plus agency can build the storefront in Framer. Plus keeps checkout, B2B catalog pricing and Shopify Functions running server-side, while Framer owns the front end and reads catalog data through the Storefront API. The Plus contract does not change, the admin does not change, and the merchant's operations team keeps working in exactly the same place.
What changes is the scope document. Most Plus engagements are written assuming a Liquid theme, so when a Framer front end enters the picture, nobody has agreed who owns the product template, who owns QA, or which line of the retainer pays for ongoing design work. That ambiguity is what burns margin on the second month, not the technology.
What a Shopify Plus agency owns in a Framer build
The cleanest way to scope this is layer by layer. Below is the same Plus engagement written two ways: a conventional Liquid theme build, and a Framer front end over the same Plus store.
| Layer | Liquid theme build | Framer + Shopify Plus build |
|---|---|---|
| Catalog and inventory | Shopify admin (merchant) | Shopify admin (merchant) — unchanged |
| Checkout | Shopify, customized via Plus | Shopify, customized via Plus — unchanged |
| B2B pricing and catalogs | Shopify admin (merchant) | Shopify admin (merchant) — unchanged |
| Shopify Functions | Agency devs, server-side | Agency devs, server-side — unchanged |
| Front end / templates | Agency devs in Liquid | Designers in Framer |
| Marketing CMS and pages | Theme sections, dev-gated | Framer CMS, marketing team owns |
| QA surface | Theme + checkout | Front end + data sync + checkout |
Five of the seven rows do not move. That is the point worth putting in front of a client early: a Framer front end is a change to one layer, not a re-platform. The two rows that do move are where the commercial conversation actually lives.
Why Plus and a non-Liquid front end don't conflict
Shopify builds for this directly. Its public pricing page lists 25 headless storefronts on Plus against one on Basic, Grow and Advanced — a 25x allowance that only makes sense if Shopify expects enterprise merchants to run custom front ends. The same page gives Plus full checkout customization where lower plans get limited, and API rate limits up to 10x on select APIs.
Plus is, in other words, the plan most ready for a decoupled front end, not the one most threatened by it. Agencies that frame Framer as a departure from Plus have the relationship backwards.
Checkout is the line that worries clients most, and it is the line that does not move. Shopify's own Hydrogen documentation is blunt about where it lives:
"checkout stays on Shopify" — Shopify, Hydrogen documentation
The buyer leaves the Framer storefront and lands on the same Shopify-hosted checkout they would reach from a theme. Shop Pay, accelerated wallets, fraud analysis and the Plus checkout customizations all behave as configured.
What happens to B2B pricing and Shopify Functions?
Both stay server-side, which is why they survive the front-end swap untouched.
B2B is the sharper example because it changed recently. On April 2, 2026 Shopify extended core B2B features to Basic, Grow and Advanced — company profiles, payment terms, volume pricing — while keeping unlimited catalogs, direct catalog assignment, partial payments and deposits exclusive to Plus. The Help Center's plan comparison puts the gap plainly: three active B2B catalogs on lower plans, unlimited on Plus.
That matters for scoping because per-customer negotiated pricing is a Plus-only capability, and it resolves in Shopify, not in the front end. A Framer storefront asks the Storefront API for prices in the buyer's context and renders what comes back. If an agency is pitching a custom storefront to a B2B client, this is the reassurance that closes it.
Shopify Functions behave the same way. The Discount Function API documentation lists Storefront as a supported surface alongside checkout, cart, B2B and POS. Discount logic written as a Function runs in Shopify's backend and applies regardless of what rendered the product page.
How does this change the retainer?
Honestly, less than agencies expect — but the shape shifts. Three lines move:
The line that shrinks. Theme maintenance. Section development, template edits, and the "can you move this block" tickets that fill a Liquid retainer largely disappear, because the marketing team edits Framer directly.
The line that appears. Front-end ownership and sync monitoring. Someone has to own the integration layer, watch for catalog drift, and handle Framer platform updates. This is real recurring work and it should be priced, not absorbed.
The line that stays. Plus platform work — Functions, checkout extensions, B2B catalog structure, app integrations. Unchanged, because the backend is unchanged.
Platform cost is its own line and belongs to the merchant, not the agency. Shopify lists Plus starting at $2,300 USD per month, with higher-volume merchants quoted a variable fee instead. When a client raises Shopify Plus cost alongside agency fees, separating the two early prevents the build budget from being judged against a platform invoice it has nothing to do with. For agencies comparing engagement models, the custom theme cost comparison breaks the build side down further.
When a Framer front end is the wrong call for a Plus client
Three situations where a Liquid build is still the better recommendation:
- Heavy theme-app dependence. If the merchant runs several apps that inject theme blocks, each one needs a replacement path. Count them before quoting.
- In-house Liquid teams. A merchant with Liquid developers on staff loses leverage by moving to a tool they do not maintain.
- Migration mid-peak. A Shopify migration agency scheduling a front-end cutover through Q4 is taking on risk with no upside. Launch in a quiet quarter.
For Shopify agency partners, the honest framing is that Framer is a front-end decision made inside a Plus engagement, not an alternative to one. Write the ownership table into the SOW, price the integration line, and the rest of the Plus scope stands exactly as it always did. FramerLink handles the catalog sync layer so the integration line stays a maintenance item rather than a build project.
Frequently asked questions
Can a Shopify Plus agency build the storefront in Framer?
Yes. Shopify Plus keeps checkout, B2B catalog pricing and Shopify Functions running server-side, while Framer renders the front end using catalog data from the Storefront API. The Plus contract and admin are unchanged. What changes is which team owns the presentation layer and how the retainer is structured.
Do you lose Shopify Plus checkout if the storefront is built in Framer?
No. Checkout remains on Shopify regardless of what renders the storefront. Plus still provides full checkout customization, while lower plans are limited to partial customization. The buyer moves from the Framer front end to the same Shopify-hosted checkout they would reach from a Liquid theme.
How much does Shopify Plus cost in 2026?
Shopify lists Plus as starting at $2,300 USD per month on its public pricing page, with higher-volume merchants quoted a variable platform fee instead. That figure covers the platform only. Agency build fees, apps and payment processing are separate lines in any Plus engagement budget.
Is Framer a replacement for Shopify Plus?
No. Framer replaces the theme layer, not the commerce platform. Shopify Plus still handles the catalog, inventory, orders, taxes, B2B company accounts and checkout. Framer handles design, page structure and marketing content. Agencies scope them as two layers of one build, not as competing platforms.
Sources
- Shopify Pricing: Find the Right Plan for Your Business — Shopify
- Key B2B features now available on non-Plus plans — Shopify Changelog
- Discount Function API — Shopify Functions — Shopify Developer Documentation
- Hydrogen — Shopify Developer Documentation
- Shopify B2B features by plan — Shopify Help Center