Systems and records
Ecommerce subscription pause dataset: keep pause, skip, cancel and refund apart
By SourceX Editorial · Updated
10 sections
Short answer
Subscription data should treat pause, skip, cancel and refund as four different facts. Pause is a temporary contract state, skip is an event on one billing cycle while the contract stays active, cancel ends the contract now or at a scheduled date, and refund is a money movement on one payment that changes no state. Label each from its source record, never from a single status field.
System export
Ecommerce subscription pause
Key takeaways
- Separate contract states from events; a skip or a refund never changes the state by itself.
- Platform status fields are observations: Stripe keeps a subscription active while collection is paused.
- Each label needs a proving record, an actor and a timestamp.
- Record stock, plan type and promotion rules at decision time, because they change which action was valid.
- A refund on the day of a cancellation is two events, not one.
- Reconcile final labels against platform counts and explain every difference by a written rule.
How should subscription data distinguish pause, skip, cancel and refund states?
Treat pause, skip, cancel and refund as four different kinds of fact, recorded on different objects. Pause is a temporary state of the subscription contract. Skip is an event on one billing cycle or order while the contract stays active. Cancel is the end of the contract, either scheduled for the end of a period or immediate. Refund is a money movement on a payment, and on its own it changes nothing about the contract.
A dataset that collapses these into one churn flag or one status column teaches a model the wrong lesson. A customer who skipped two deliveries is not a customer who left. A refund issued for a damaged box is not a cancellation. The label guide below gives each state and event its own name, the evidence that proves it and the label it is most often confused with, so the history can be rebuilt from source records rather than from a status snapshot.
Why the platform status field cannot be your label
The status field on a subscription is a snapshot that platforms define differently, and several important events never touch it. Labels built from it inherit every one of those gaps.
Stripe is the clearest example. When you pause payment collection on a Stripe subscription, the subscription status stays active, invoices continue to be generated and the customer keeps access; the pause_collection behavior decides whether those invoices are kept as drafts, marked uncollectible or voided. A status-only dataset would record that customer as an ordinary active subscriber. Stripe documents a separate full pause that stops service and invoice generation, so the same word covers two different situations.
Skips are invisible to status everywhere. On Shopify, subscriptionBillingCycleSkip acts on one billing cycle of a contract, and the contract remains active. Refunds are separate too: Stripe sends a charge.refunded event, including for partial refunds, and its subscription webhook guide treats a refunded subscription charge as something the integration must resolve with its own logic.
So labels should come from events and objects: the contract's state history, the billing cycle or order record, and the payment and refund records, joined by their IDs.
How three billing platforms record the same customer intent
Each platform models the same customer intent with different objects and names. The table maps them to one label vocabulary. It reflects documentation checked on the date of this article; confirm against the API version your store actually uses.
| Customer intent | Stripe | Shopify subscription contracts | Chargebee | Label |
|---|---|---|---|---|
| Stop deliveries for a while | Full subscription pause, separate from pause collection | Contract status PAUSED, expected to resume | Status paused; does not renew while paused | PAUSED_SERVICE |
| Keep access, stop charging for a while | pause_collection; status stays active | No direct equivalent; record the app's action | Not a distinct status; record the action | PAUSED_BILLING_ONLY |
| Miss one delivery | No native skip; often modeled by the app | subscriptionBillingCycleSkip on one cycle | Record the app or API action | SKIPPED_CYCLE |
| End at the period end | cancel_at_period_end; can be reversed until the period ends | Record the scheduled date from the app | Status non_renewing | CANCEL_SCHEDULED |
| End now | Immediate cancel; invoices stop | Status CANCELLED | Status cancelled | CANCELLED |
| Money back | Refund object; partial refunds allowed | Refund on the order | Refund or credit note | REFUND_PARTIAL or REFUND_FULL |
The subscription state transition label guide
The guide has two layers: contract states, which last for a period, and events, which happen at a moment. Every record gets exactly one state at any time and zero or more events. The table lists each label, what it means, the evidence that proves it and the label it is most often mistaken for.
At a glance
The subscription state transition label guide
- Always record the actor for state changes and skips: customer, merchant staff, an automation rule or the billing system.
- Keep the platform's own status value in a separate column as an observation, never as the label.
- When a cancellation reason was captured, store it as a field on the event, not as a label of its own.
| Label | Layer and meaning | Required evidence | Do not confuse with |
|---|---|---|---|
| ACTIVE | State: billing and fulfilling on schedule | Contract state record and the latest successful billing | PAUSED_BILLING_ONLY, which can also show active |
| PAUSED_SERVICE | State: deliveries and billing stopped, resumption expected | State change record with start date; resume date if set | CANCEL_SCHEDULED |
| PAUSED_BILLING_ONLY | State: access or deliveries continue, collection stopped | Pause collection setting and its invoice behavior | ACTIVE |
| CANCEL_SCHEDULED | State: active until a stated end date, then ends | Cancellation request with the scheduled date | CANCELLED |
| CANCELLED | State: contract ended by customer or merchant | State change to cancelled with timestamp and actor | EXPIRED or FAILED_BILLING |
| EXPIRED | State: ended because its term or cycle count ran out | Contract term or cycle limit reached | CANCELLED |
| FAILED_BILLING | State: ended after billing failed with no further retries | Failed billing attempts and the terminal state | CANCELLED by the customer |
| SKIPPED_CYCLE | Event: one cycle or order omitted, contract unchanged | Skip action on a specific cycle, with actor | PAUSED_SERVICE |
| REFUND_PARTIAL / REFUND_FULL | Event: money returned on a specific payment | Refund record linked to the original charge | CANCELLED |
| RESUMED | Event: paused contract returned to active | State change from paused to active | A new subscription |
Which transitions are valid, and which signal a data error?
Valid transitions follow from what the platforms allow, and a transition outside them usually means a missing record, not unusual customer behavior. Check every history against the rules below before labeling.
- SKIPPED_CYCLE should occur only during ACTIVE. A skip during PAUSED_SERVICE suggests the pause was recorded late or the skip came from a different contract.
- CANCEL_SCHEDULED can return to ACTIVE before its end date. Stripe documents that cancel_at_period_end can be set back to false at any time up to the end of the period, so a reversal is a valid event, not noise.
- On Chargebee, scheduling a cancellation on an active subscription moves it to non_renewing, while a subscription in trial stays in trial until the term ends and then becomes cancelled. Map those to the same labels but keep the trial flag.
- RESUMED follows PAUSED_SERVICE. Shopify's subscriptionContractActivate mutation accepts contracts that are active, paused or failed, so check which prior state a reactivation came from.
- CANCELLED, EXPIRED and FAILED_BILLING are terminal for that contract. A later order for the same customer is a new contract with its own ID, linked as a successor.
- Refund events can occur in any state, including after CANCELLED. They never change the state on their own.
Which item, rule or inventory change alters the valid action?
The right action depends on more than the customer's request: stock, promotion terms, the billing model and the timing rules of the platform all change which transition is valid. Record those conditions on the event so a model can learn when, for instance, a skip was offered instead of a pause.
Inventory is the most common driver. If the subscribed item is out of stock at the cycle date, the merchant might skip that cycle, substitute an item or pause the contract. Each is a different label with a different customer outcome, so store the inventory state that applied at the decision time, not today's.
Billing model matters too. Shopify's documentation says billing cycles cannot be edited on prepaid subscriptions and that edits are limited to the current cycle and cycles up to a year ahead. A request to skip a prepaid delivery therefore resolves differently from a skip on a pay-per-delivery plan, often through a credit or a refund. Promotions add a third constraint: an introductory discount tied to a number of cycles may or may not count skipped cycles, depending on the merchant's rule. Record which rule version applied.
| Condition at decision time | Where it is recorded | How it changes the valid action |
|---|---|---|
| Item out of stock on the cycle date | Inventory snapshot or order hold reason | Skip, substitute or pause instead of a normal order |
| Prepaid plan | Plan or selling plan type | Cycle edits unavailable; credit or refund instead of a skip |
| Promotion tied to cycle count | Discount rule and its version | Determines whether a skip extends or consumes the promotion |
| Order already fulfilled for the cycle | Fulfillment record with timestamp | Skip no longer possible; refund or return instead |
| Payment method failing | Billing attempt records | Retries or FAILED_BILLING rather than a customer cancellation |
Worked example (illustrative): one coffee subscription over five months
This example is illustrative; the merchant, dates and counts are invented. A customer subscribes to a monthly coffee delivery on a store whose subscription app writes to the platform's contract and billing cycle records.
- Month 1: contract created. State ACTIVE. First order billed and fulfilled.
- Month 2: the customer skips the next delivery in the customer portal. Event SKIPPED_CYCLE, actor customer. State stays ACTIVE; no order is created for that cycle.
- Month 3: the roast is out of stock on the cycle date. The merchant pauses the contract for one cycle and emails the customer. State PAUSED_SERVICE, actor merchant, with the inventory hold recorded as the reason.
- Month 4: the contract resumes. Event RESUMED, state ACTIVE. The order arrives with one damaged bag out of two; support issues a refund for that bag. Event REFUND_PARTIAL linked to the month 4 charge. State unchanged.
- Month 5: the customer requests cancellation at the end of the current period. State CANCEL_SCHEDULED, then CANCELLED at the period end, actor customer, reason captured as moving abroad.
- Status-only view of the same history: active, active, paused, active, cancelled. It misses the skip, the merchant's role in the pause, the inventory cause and the refund, and it would label the month 4 refund as nothing at all.
Edge cases: a refund that looks like a cancellation, and the reverse
Two patterns break naive labeling, and both need a rule written down before labeling starts.
First, a refund issued alongside a cancellation. Stripe documents that it does not refund automatically when a subscription is cancelled; negative prorations are not refunded automatically, and refunds are issued separately. So a full refund on the same day as a cancellation is two events, REFUND_FULL and CANCELLED, with their own timestamps and actors. Do not merge them, and do not infer a cancellation from a full refund when no state change exists.
Second, a cancellation that never produced a refund or a final order, such as a customer who cancels mid-cycle on a plan where the current period has already been paid. Label CANCELLED or CANCEL_SCHEDULED according to the effective date, and record that no refund occurred rather than leaving the refund field empty. Stripe also allows several partial refunds on one charge until it is fully refunded, so total refunded per charge should be computed from all refund records, not from the latest one.
Limits of the guide: it covers recurring physical or digital product subscriptions on a billing platform. It does not settle accounting treatment, chargebacks or disputes, or consumer protection rules on cancellation, which vary by jurisdiction and need their own review.
Checks before an ecommerce subscription pause dataset leaves the company
Before a labeled history goes anywhere, check that the labels reconcile with the source and that the records carry no more personal information than the use needs.
- Reconcile counts: contracts by final label against the platform's own counts by status, explaining every difference by a documented rule such as PAUSED_BILLING_ONLY.
- Reconcile money events by count, not amount: every refund event links to exactly one charge, and every charge with refunds has matching refund records.
- Check timestamps share one time zone and that state intervals do not overlap for the same contract.
- Remove or replace names, emails, phone numbers and street addresses; keep a coarse region only if the use needs it.
- Exclude payment card details entirely; keep only the platform's charge and refund IDs, pseudonymized.
- Free-text cancellation reasons and support notes need the same screening as any customer message before they are kept.
Licensing labeled subscription histories
Subscription histories labeled this way show how customers and merchants actually manage recurring orders: when skips replace cancellations, how stock problems lead to pauses and how refunds relate to retention. A subscription merchant can license histories labeled this way through SourceX, which covers the rights review, contracting, preparation and delivery.
A merchant decides which subscription records are in scope and signs off on the terms before a single file moves. To check whether your records could qualify, start with a short company assessment; no data upload is needed.
Frequently asked questions
What should a subscription state transition label guide include?
Separate state labels, such as active, paused, scheduled to cancel and cancelled, from event labels such as skipped cycle, resumed and refund. For each label, give its meaning, the source record that proves it, the actor and the label it is most often confused with, plus rules for which transitions are valid.
Is a paused subscription counted as churn?
Not by itself. A pause is a temporary state with resumption expected, so treat it separately from cancellation and decide in your analysis whether a long pause without resumption should be reviewed as a separate outcome. Keep the pause and any later cancellation as distinct records.
Why does my Stripe data show active subscriptions that were paused?
Stripe's pause payment collection keeps the subscription status active while it stops collecting payment, and invoices continue to be generated under the chosen behavior. Read the pause collection setting on the subscription and label those periods separately from ordinary active billing.
How do I record a skipped delivery on Shopify?
Shopify's subscription APIs skip a specific billing cycle on a contract while the contract itself stays active. Record the skip as an event on that cycle with its actor and date, and leave the contract state unchanged.
Should refunds be part of a subscription state model?
Refunds belong in the event layer, linked to the specific charge they reverse, not in the state layer. A refund can happen while a contract is active, paused or already cancelled, and it does not change the contract state by itself.
Sources
- Stripe says pausing payment collection leaves the subscription active with invoices still generated, offers keep_as_draft, mark_uncollectible and void behaviors, and distinguishes it from a full pause. Source
- Stripe says a subscription set to cancel at period end can be reactivated until the period ends, and that it does not automatically refund negative prorations on cancellation. Source
- Stripe's Refunds API allows refunding part of a charge, multiple times, until the entire charge has been refunded. Source
- Stripe's subscription webhook guide treats a full or partial refund of a subscription invoice charge as an event the integration must resolve separately. Source
- Shopify's Admin API lists subscription contract statuses ACTIVE, CANCELLED, EXPIRED, FAILED and PAUSED, with PAUSED meaning the contract is expected to resume. Source
- Shopify's subscriptionBillingCycleSkip mutation skips a specific billing cycle of a subscription contract. Source
- Shopify says billing cycles cannot be edited on prepaid subscriptions and edits are limited to the current cycle and cycles up to one year ahead. Source
- Chargebee lists subscription statuses future, in_trial, active, non_renewing, paused and cancelled, and moves an active subscription to non_renewing when cancellation is scheduled. Source
- Shopify's subscriptionContractActivate mutation requires the contract status to be active, paused or failed. Source
See if your company qualifies
A short company assessment. No data uploads are needed.