California Automatic Renewal Law (ARL) for Shopify Merchants

If you bill US consumers on auto-renew — especially California shoppers — state automatic renewal / negative-option rules are live now. Here is what merchants usually need on the notice and evidence side, and what a Shopify app can (and cannot) do.

Not legal advice. Exact windows and duties vary by offer type and state. Have US e-commerce counsel review your checkout, consent, and cancel UX before you rely on any checklist.

Why CA ARL matters for Shopify stores

California’s Automatic Renewal Law (often discussed with other state ARLs such as New York and Colorado) targets recurring consumer subscriptions: disclosure near consent, affirmative consent, easy online cancellation, and renewal notices whose timing depends on the offer (trial/promo vs annual vs other terms).

Shopify merchants often assume “our billing app handles compliance.” Billing apps handle charging and customer-account cancel flows. They rarely give you a jurisdiction-aware notice schedule + exportable proof log that matches how chargeback teams and counsel think about auto-renew disputes.

Renewal notices merchants plan for

In practical merchant planning (always confirm with counsel for your exact SKU mix):

  • Annual / long-term renewals — advance notice in a statutory window before the charge (California’s annual window is commonly discussed as roughly mid-range days-before-renewal; do not publish a marketing “guarantee” of exact days without counsel).
  • Trials and promos — notice before the trial converts to paid, on a separate clock from ordinary renewal dates.
  • Notice content — renewal date, amount, billing frequency, and clear cancel instructions (not “email us if you remember”).

Other states add wrinkles (for example Connecticut’s calendar annual-reminder concepts). Treat multi-state selling as a matrix, not a single federal checkbox. The vacated 2024 FTC federal click-to-cancel rule does not replace state ARLs — see our state ARL vs FTC note.

What belongs in Recharge vs a notice layer

Duty Usually owned by
Checkout disclosure + express consent UI Theme + subscription app (Recharge, Loop, Skio, native Subs)
Click-to-cancel / customer portal cancel Subscription app customer account
Pre-renewal email on a legal-aware schedule Notice / compliance layer (or carefully configured ESP)
Exportable log of notices sent Notice / compliance layer
Published policy wording checks Policy readiness scan (heuristic)

Subnotice is built as that notice + audit layer: US/UK/EU policy packs, pre-renewal emails when dates sync, and a CSV trail. It does not redesign checkout or certify “ARL compliant.”

Evidence trail for disputes

When a cardholder claims “I didn’t know it would renew,” issuers look for contemporaneous notice — not a blog post written after the dispute. Keep:

  • Date/time the reminder was sent
  • Recipient and contract / order reference
  • Renewal amount and date stated in the email
  • Delivery / bounce status where your ESP provides it

That same trail also supports UK chargeback practice — see winning subscription chargebacks.

Honest readiness claims

Safe: “We send pre-renewal notices and keep an exportable audit trail to prepare for state ARL notice duties.”

Unsafe: “Install this app and you are California ARL compliant.” No SaaS outside your checkout and cancel UX can truthfully say that.

Next steps: run a free US policy scan, read the US merchants page, and install Subnotice if you want the notice log next to Recharge/Loop/Skio.

Informational only — not legal advice. MINISAGE TECH LTD · 17 July 2026.