Connect Shopify subscriptions to your systems (ERP, support, BI, revenue ops)
Enable this ShopifyConnector Extension to run subscriptions as an event-driven business: contract lifecycle (create/update/pause/cancel) plus recurring billing (attempts, success/failure, 3DS challenges, cycle edits, skip/unskip).
Shopify provides webhook topics for subscription_contracts/*, subscription_billing_attempts/*, subscription_billing_cycles/*, and subscription_billing_cycle_edits/*
Why enable this extension?
In subscriptions, orders are an outcome—not the system. You need signals for:
The contract (what is delivered, when, at what price)
The billing cycle (next-cycle changes, skip/unskip).
The billing attempt (success/failure/challenged.
And the downstream reaction (CS, finance, support, BI).
Shopify models this with SubscriptionContract, SubscriptionBillingCycle, and SubscriptionBillingAttempt.
Keep your CRM/ERP aligned
With account lifecycle changes.
Enforce B2B governance
Locations, billing, tax registration, exemptions, and access roles.
Automate B2B onboarding
With fewer manual steps.
Improve reporting
By company / location / contact, not only by individual customers.
Real-world business use cases
1) Revenue Ops & BI: true MRR, churn, and cohorts
Systems: BigQuery/Snowflake, Looker/Power BI, CDPs.
Why: MRR/ARR and churn require contract + billing signals, not only orders.
Example: use sc.subscription_contracts/create/update for plan changes and sc.subscription_billing_attempts/success/failure to separate voluntary vs involuntary churn.
2) Dunning & failed payment recovery (involuntary churn)
Systems: CRM, email/SMS (Klaviyo/Braze), CS workflows.
Why: failed renewals can silently destroy retention if you don’t react immediately.
Example: on sc.subscription_billing_attempts/failure, start a recovery flow (notify customer, prompt payment update, schedule retries, escalate to support).
3) 3D Secure challenges: prevent “stuck” renewals
Systems: support, CX workflows, risk ops.
Why: 3DS challenges can block a renewal until the customer completes the step.
Example: sc.subscription_billing_attempts/challenged creates a high-priority case and triggers customer instructions until completion.
4) Customer Success lifecycle: pause, reactivate, upgrade/downgrade
Systems: HubSpot/Salesforce, CS tooling, helpdesk.
Why: pause/reactivation and plan changes are core retention levers and must be tracked across systems.
Example: sc.subscription_contracts/pause triggers retention tasks; …/activate marks reactivation; …/update logs upgrades/downgrades.
5) Finance & ERP: cashflow forecasting and recurring reconciliation
Systems: ERP/accounting, reconciliation, finance ops.
Why: you need billing attempt outcomes to forecast cash and close books accurately.
Example: route success to “collected”, failure to “at risk”, and cancel/expire to stop forecasting future cycles.
6) Next-cycle control: skip/unskip and billing cycle edits
Systems: CS/support, BI, operations.
Why: many subscription businesses allow skipping or changing an upcoming cycle without changing the base contract.
Example: track sc.subscription_billing_cycles/skip / …/unskip and sc.subscription_billing_cycle_edits/create/update/delete to keep downstream systems aligned.
Connect Shopify with your system
FAQ
What’s the difference between contract, billing cycle, and billing attempt?
- SubscriptionContract defines the recurring relationship.
- SubscriptionBillingCycle represents a specific cycle and can be skipped/unskipped.
- SubscriptionBillingAttempt represents the charge attempt for a cycle (success/failure/challenged).
How do I reduce involuntary churn?
Start recovery workflows on sc.subscription_billing_attempts/failure and track outcomes in BI.
Real-world business use cases
Which events does this ShopifyConnector Extension enable?
Subscription contracts
sc.subscription_contracts/create
sc.subscription_contracts/update
sc.subscription_contracts/activate
sc.subscription_contracts/pause
sc.subscription_contracts/cancel
sc.subscription_contracts/expire
sc.subscription_contracts/fail
Billing attempts
sc.subscription_billing_attempts/success
sc.subscription_billing_attempts/failure
sc.subscription_billing_attempts/challenged
Billing cycles
sc.subscription_billing_cycles/skip
sc.subscription_billing_cycles/unskip
Billing cycle edits
sc.subscription_billing_cycle_edits/create
sc.subscription_billing_cycle_edits/update
sc.subscription_billing_cycle_edits/delete
Required scope: read_own_subscription_contracts
sc.subscription_contracts/create
sc.subscription_contracts/update
sc.subscription_contracts/activate
sc.subscription_contracts/pause
sc.subscription_contracts/cancel
sc.subscription_contracts/expire
sc.subscription_contracts/fail
Billing attempts
sc.subscription_billing_attempts/success
sc.subscription_billing_attempts/failure
sc.subscription_billing_attempts/challenged
Billing cycles
sc.subscription_billing_cycles/skip
sc.subscription_billing_cycles/unskip
Billing cycle edits
sc.subscription_billing_cycle_edits/create
sc.subscription_billing_cycle_edits/update
sc.subscription_billing_cycle_edits/delete
Required scope: read_own_subscription_contracts
Tell us your systems.