Change or upgrade your plan

When to use this

Change plan when your business outgrows Pro’s single-site limit, when you need Growth-only features, or when downsizing after consolidating brands. GDPRChecker uses Stripe subscriptions; plan changes flow through checkout upgrade paths or the billing portal depending on UI version.

Upgrades from Free start a new paid subscription. Upgrades from Pro to Growth typically modify the existing Stripe subscription item with proration. Downgrades may require removing extra sites first so you comply with Pro limits.

Entitlements refresh after webhook events such as invoice.paid—if features look stale, read troubleshooting below before repeating payment.

Finance teams should align Growth upgrade timing with contract renewals; mid-cycle upgrades often produce proration lines on the next invoice that differ from list price on marketing pages.

Engineering should freeze publishes during Pro→Growth upgrade windows if your process requires replay verification baselines—re-run verification after webhook sync completes.

Tax and VAT displays on Stripe checkout follow Stripe configuration; plan tier in dashboard is authoritative for feature access, not invoice SKU labels alone.

Coupon or promotion codes entered at checkout do not change feature matrices—only successful subscription tier assignment matters for entitlements.

Step-by-step instructions

1. Open Dashboard → Billing and note current plan, renewal date, and payment method on file.
2. For Free → paid, use /pricing or in-app upgrade CTA to start Stripe Checkout.
3. For Pro → Growth, select upgrade; review upgrade preview if the UI shows next invoice delta.
4. Complete Stripe steps and return to success or billing page.
5. Confirm plan badge shows GROWTH and subscription status is active.
6. If downgrading Growth → Pro, archive sites until only one active verified site remains.
7. Remove or export Growth-only configs you will lose (custom rules, extra locales).
8. Trigger billing portal change if dashboard directs you there for self-serve tier changes.
9. Reload dashboard and verify locked features match new plan.
10. Run runtime verification on primary site after major tier changes.
11. Screenshot Billing page showing new tier for internal compliance folder.
12. Update internal wiki links from Pro-only runbooks to Growth feature list if applicable.
13. Notify finance of new MRR after Growth upgrade for budget forecasting.
14. Email finance distribution list with new plan name and next invoice date from Stripe portal.

Expected result

Stripe subscription matches selected tier. Dashboard entitlements align: site limits, feature flags, and billing history update. No PLAN_REQUIRED errors on features included in new plan.

Invoices email to billing contact on file; download copies from portal.

Internal change management should record plan tier, effective date, and engineer who verified runtime after upgrade. Auditors comparing invoices to live behavior appreciate a single ticket linking Stripe receipt PDF to runtime verification screenshot.

Troubleshooting