Shopify subscription compliance UX is the set of storefront, checkout, and customer portal patterns that show a subscription's material terms before billing details are collected and record express consent at checkout. The same patterns give the subscriber a cancel path as simple as the signup.
Counsel decides what the terms must say and the cancel path must do under ROSCA and the California and New York laws. Liquid Lemon builds the PDP selling-plan selector, cart line, checkout policy text, portal cancel flow, and Klaviyo notices that carry those decisions for supplement brands on Shopify. This article describes implementation patterns. It is not legal advice.
Mechanics are in how Shopify subscriptions work; supplement setup has its own piece.
What do ROSCA and the state auto-renewal laws require of a subscription store?
ROSCA requires clear and conspicuous disclosure of the material terms before the business obtains the consumer's billing information. It also requires the consumer's express informed consent, and a simple mechanism for stopping the recurring charges.
The FTC's click-to-cancel rule is not in force. The Eighth Circuit vacated the 2024 Negative Option Rule amendments on July 8, 2025, leaving the older rule that covers prenotification plans only. On March 13, 2026 the FTC published an advance notice of proposed rulemaking, which is a request for public comment ahead of any proposed rule. As of November 2026, ROSCA, Section 5 of the FTC Act, and state auto-renewal laws govern.
State law carries the live requirements. California's AB 2863, effective July 1, 2025: express affirmative consent to the automatic renewal, online cancellation that works exclusively online, at will, and without further steps, fee-change and trial-end notices, an annual reminder, and consent records kept three years or one year past the contract's end, whichever is longer. New York's GBL 527-a, effective November 5, 2025: affirmative consent before charging, a retainable acknowledgment promptly after consent, material-change and price-increase notice, cancellation as easy to use as, and through every medium in which, the business accepts consent, and a renewal reminder on qualifying longer terms. The patterns below assume the strict reading; counsel trims what does not apply.
Where does the disclosure have to surface on a Shopify store?
Four places, carrying the same numbers. On the PDP, the selling-plan selector shows the frequency, the first-cycle and recurring prices, a renewal sentence under the subscribe option ("renews every 30 days until you cancel"), and a policy link.
In the cart drawer, the subscription line repeats the frequency and renewal price, with the policy link. At checkout, Shopify shows its own subscription disclosure on every plan, and it cannot be removed. Editable on any plan: the cancel sentence and cancellation instructions, in the theme content editor, and the cancellation policy the disclosure links to, in Settings > Policies (shop.subscription_policy, at /policies/subscription-policy). The agreement label and the consent text itself are editable on Shopify Plus only. The order confirmation email carries the terms, charge amount and frequency, deadline, cancel mechanism, and a manage link: New York's retainable acknowledgment. Counsel writes the terms once; we place the same text in all four spots.
How is consent captured in Shopify checkout?
By Shopify's checkout, as a capture mechanism. The storefront or app submits the variant ID plus selling plan ID through the Cart API; Shopify's checkout handles the pricing, messaging, payment method vaulting, and customer consent for the subscription line, and creates the subscription contract itself when the order completes. The app is notified by webhook and owns renewals from there; the contract is detached from the selling plan, so later plan edits do not change existing contracts.
Shopify records that the customer completed a checkout showing the disclosure. Whether the terms, their wording and placement, and the cancel path satisfy ROSCA and each state law is counsel's judgment, and the merchant stays responsible for it. Two extension points sit around checkout: a thank-you page block (purchase.thank-you.block.render) linking to subscription management, and, for a post-purchase subscription offer, Shopify's BuyerConsent component, required between the money summary and the offer buttons as a second, separate consent.
What does a cancellation flow need on Shopify?
A path the subscriber can find and finish without contacting anyone, in every medium the brand accepts signup through. Cancel, pause, and skip are separate contract API operations, so any app or custom portal can expose each. The free Shopify Subscriptions app lets customers skip, pause, resume, or cancel. Recharge adds a portal cancellation toggle and an optional three-duration pause step. Built for Shopify apps must use Customer Account UI extensions for self-service, so the cancel path sits inside the Shopify account. Counsel decides what sits between the cancel button and the cancelled contract.
| Pattern | Subscriber sees | Build | Who decides |
|---|---|---|---|
| Direct cancel | Cancel button, one confirmation screen, done | Cancel mutation, confirmation screen and email | Counsel confirms wording |
| Pause offered beside cancel | Pause durations next to a cancel control of equal prominence | Pause mutation; cancel completes from the same screen, no further step | Counsel decides whether it meets California's "exclusively online, at will, without further steps" test |
| Save offer beside cancel | A discount or swap, with a cancel link or button displayed prominently, continuously, and next to the offer | Offer rendered from the app; cancel control stays live while the offer is on screen | California permits an online save offer only with that cancel control alongside it; counsel reviews copy and placement |
Four build rules hold regardless. Cancel takes no more steps than subscribe did. The save offer never blocks the cancel. The flow completes at the same depth on mobile. The subscriber gets an on-screen confirmation and an email with the end date. Olipop, a soda brand, is the reference for self-service: on the Recharge to Stay AI rebuild, subscribers swap and skip upcoming orders without a ticket. That example shows what a portal can do. Compliance is a separate question for counsel. Portal notes are in subscription customer portal UX.
How do renewal reminders and price-change notices run as Klaviyo flows?
As notices keyed to subscription events. The pre-renewal reminder fires a set number of days before each charge with the amount, date, products, and skip and cancel links into the portal. Statutory sends sit on top: New York's reminder 15 to 45 days before the cancellation deadline when an initial term of a year or longer renews for six months or longer; California's annual reminder in the enrollment medium, and a notice 3 to 21 days before a trial longer than 31 days ends. Counsel sets the day counts.
The price-change notice follows Shopify's own UX guidance: explain the current payment and how payments will change. California: 7 to 30 days before the fee change, with cancel instructions. New York: 5 business days to 30 days before a material change, and for a price increase either fresh affirmative consent or the right to cancel with a prorated refund within 14 days of the first increased charge. The build is a Klaviyo flow triggered by a profile property the app writes, with the consent action in the portal and the new price withheld from any contract without a recorded response. Failed-payment notices live in the same account. For Parkside, a dog treat brand, we built the subscription reminder flows before the site existed; scope is on our email page.
What is on the pre-launch checklist, and who signs it?
Counsel signs it. We produce it from the staging store, each item a dated screenshot or recording.
- PDP selector and cart line show frequency, both prices, renewal sentence, and policy link.
- Cancellation policy matches the approved version and the checkout disclosure links to it; on Plus, the edited consent text is captured.
- Test order placed; checkout summary, thank-you page manage link, and confirmation email with the acknowledgment terms captured.
- Cancel completed from the portal on mobile, step count recorded, cancel path listed per signup medium; pause, skip, and save-offer screens show the cancel control beside each.
- Where the app stores consent records, and for how long, confirmed against California's retention period.
- Klaviyo pre-renewal and price-change flows previewed with counsel's copy and day counts.
- Post-purchase offer, if used, shows BuyerConsent between the money summary and offer buttons.
When should you build custom, does it need Plus, and when shouldn't you?
Don't build custom when the app's portal already exposes cancel and pause and its settings remove the friction counsel objects to. Configure the app and publish the policy. The build hours go to the PDP and cart surfaces and to Klaviyo.
Five checks decide custom: the disclosure on every required surface, the exact cancel and pause operations counsel approved, a price-change consent recorded against the contract, a portal inside the Shopify customer account rather than on the app's hosted domain, and a required checkout extension available on the brand's plan. Any no is custom work, and none of it starts before counsel has written the terms; a portal built against drafts gets rebuilt.
Two platform limits sit outside UX and custom code. Shopify's native bundles cannot be sold with selling plans; a subscription multipack uses the subscription app's own bundling or a selling plan on a bundle product. B2B does not support subscriptions; the flow above is DTC only.
None of the core pattern needs Plus. Public App Store subscription apps that contain Functions run on any plan, and so does every surface above. Plus gates edits to the checkout agreement label and consent text. It also gates checkout UI extensions on the information, shipping, and payment steps, and custom (single-store) apps that contain Shopify Functions. If counsel wants the consent wording changed, or the terms restated as a block on the payment step, that is Plus work in our checkout development scope.
What does subscription compliance UX cost on Shopify?
Liquid Lemon builds custom-coded Shopify stores in a 30-day Sprint at a flat price: $9,500 for new brands and $12,500 for established brands, with catalog, customers and apps carried over. Shopify Plus and enterprise builds are scoped separately. Subscription disclosure and cancellation UX delivered inside a Sprint is part of that scope when the subscription app is an App Store app we configure: the four surfaces, editable policy text, portal and cancel settings, and the counsel checklist. Klaviyo email design and flows are a one-time $5,000 add-on to a Sprint, or $7,500 on their own. Standalone compliance UX work, or anything larger than a Sprint, is scoped and quoted up front as a fixed figure with no hidden fees. Larger than a Sprint: a Customer Account UI extension portal, a price-change consent step, payment-step extensions on Plus, or a subscriber migration. Counsel's and app fees are separate.
What should you send to scope the work?
Your subscription app, selling plans and prices, the states you ship to, your subscription policy text, your plan, and your Klaviyo setup, through Start Your Sprint. We return a surface and integration map covering disclosure through cancellation, and a configure-the-app versus build-custom recommendation. The reply also says whether the work fits a Sprint or needs a fixed quote.
Written by Andrew Zam, co-founder of Liquid Lemon, a Shopify / Shopify Plus design + development studio for DTC brands.



