Standard Recurring
7 min
overview a standard (recurring) subscription is an ongoing subscription that automatically reorders and rebills on a set schedule — for example, every 3 weeks — and continues indefinitely until it's canceled or reaches an end date this is the most common subscription type, and it gives the customer the most control it can be paused, resumed, and skipped at any time while it's active this section outlines the statuses a standard subscription can occupy throughout its lifecycle and explains what causes it to move into each one as described on the main overview page, a subscription's status is captured by two things that move independently state — where the subscription sits in its lifecycle (active, paused, canceled, or inactive) processing state — the health of the most recent order and payment attempt (pending, success, or failed) a standard subscription can use every state value, since it's the only type that can be freely paused, resumed, and skipped the sections that follow walk through each state, what places a subscription into it, and how the customer or store moves it from one to the next state a standard subscription moves through the following states over its lifetime each entry below explains what the state means and what causes a subscription to enter it active the subscription is live and will place its next order automatically on the scheduled date this is the normal, healthy operating state a subscription is active when it was just created — every subscription starts out active the customer skipped an upcoming order — skipping only pushes the next order date out by one cycle; the subscription stays active throughout a previously canceled subscription was reactivated paused the subscription is active but has its upcoming orders temporarily on hold no orders are placed and no charges are made while it's paused a subscription becomes paused when the customer or an admin uses the pause action — this holds all upcoming orders until the subscription is resumed a payment fails and automatic retries are turned off for the store when a scheduled order's payment fails, the store's automatic retry setting determines what happens next if automatic retries are turned on , the system reschedules the charge and tries again later, leaving the subscription active it only stops retrying — and cancels the subscription — once it exceeds the store's maximum number of retry attempts if automatic retries are turned off , there is no retry the system pauses the subscription on the very first failed payment, holding all future orders until it's resumed resuming a paused subscription returns it to active and schedules its next order date note paused subscriptions are still active "paused" isn't a separate stage in the subscription's lifecycle — it's an active subscription whose orders have simply been put on hold the status badge displays "paused" so you can see at a glance that an active subscription is on hold because of this, only an active subscription can be paused (a canceled or ended subscription cannot), and resuming it returns the badge to "active " unlike canceled or inactive , which are final end states, a paused subscription is still live and waiting to be resumed canceled the subscription has ended early and will no longer place orders this is a final state a subscription becomes canceled when the customer or an admin cancels it — this takes effect immediately and stops all future orders it is automatically canceled after too many failed payments — if the store has automatic retries enabled and the subscription exceeds the store's maximum number of failed payment attempts, the system cancels it inactive the subscription has ended on its own — not canceled early — and will no longer place orders this is a final state a subscription becomes inactive when it reaches its end date — if the subscription was set up with a fixed end date, it automatically ends once that date passes an admin manually ends it note a standard subscription only becomes inactive if it has an end date open ended subscriptions run indefinitely and never go inactive on their own — they end only by being canceled