Elderly couple smiling while online shopping with a laptop and credit card.
Photo by Vitaly Gariev on Pexels

Billing Operations

Part of Subscription software selection

Comparing recurring order and subscription billing features

Compare subscription schedules, billing attempts, orders and prepaid deliveries by the records each app creates.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Subscription Operations.

Ask which delivery each record represents. A future parcel can be scheduled without a new charge; a failed billing attempt is not a collected payment. The app should trace the subscription promise through billing and into the order sent to fulfilment.

Shopify names the SubscriptionContract, SubscriptionBillingAttempt and generated Order. Stripe Billing names the Subscription, Invoice and PaymentIntent. The comparison is record by record: contract terms, billing attempt and payment outcome.

Compare the payment models

Shopify's named contract records are SellingPlan, SubscriptionContract and SubscriptionBillingAttempt. A SellingPlan defines billing, delivery and pricing policies; a SubscriptionContract specifies products, billing and shipping times, and price, and includes Subscription Billing Policy and Subscription Delivery Policy.

A SubscriptionBillingAttempt records an execution of the subscription billing process. Shopify's API says a successful attempt creates an Order; the attempt includes associated payment transactions and any errors, and billing attempts use idempotency keys to avoid duplicate order creation.

For pay-per-delivery plans, ask when the charge is attempted, when an order appears, and what happens if payment fails. That does not prove how a particular app is configured.

Stripe Billing's named records are Subscription, Invoice and PaymentIntent. Creating a subscription makes Stripe generate invoices, attempt payment collection and manage subscription status; the Subscription object contains the subscribed customer, product and price, and status.

When an immediate payment is required, Stripe also creates an Invoice and a PaymentIntent, and the subscription becomes active after the first invoice is paid. Stripe handles payment retry logic, dunning and status transitions.

For prepaid plans, compare where later paid parcels remain visible and how the app links them to the initial payment. Shopify's SellingPlan covers deferred purchase options, including pre-orders, and its Subscription Delivery Policy controls the frequency of fulfilments. Compare each platform's records; do not assume a shared order structure.

Demonstration question

Schedule
Which delivery is next after a change or skip?
Billing
Was the intended charge attempted and collected?
Order creation
Which order covers the paid delivery?
Prepaid deliveries
Which paid parcels remain due?
Change handling
Does an edit affect this order, later orders or both?

Evidence to inspect

Schedule
Subscription and affected cycle
Billing
Attempt and payment outcome
Order creation
Order and cycle reference
Prepaid deliveries
Scheduled fulfilments or queued orders
Change handling
Contract, current order and next cycle

For the schedule row, Shopify's SellingPlan and SubscriptionContract hold billing and delivery policies; Stripe's Subscription holds the recurring price and status.

For the billing row, Shopify's SubscriptionBillingAttempt records transactions and errors; Stripe's Invoice and PaymentIntent record collection.

For the order-creation row, Shopify's successful attempt creates an Order; Stripe's named chain for immediate payment is Invoice and PaymentIntent.

For the prepaid-deliveries row, Shopify's Subscription Delivery Policy controls fulfilment frequency. For change handling, Shopify's SubscriptionContract tracks generated orders; Stripe uses pro-rata adjustments.

Inspect what an edit changes

When an order or contract is edited, compare whether the change affects the current order, the subscription contract, later cycles, or some combination. Ask each provider to demonstrate the current order and a later cycle after a frequency or product change. One updated screen is insufficient evidence that both changed.

If the offer permits a product swap, compare the recurring selection, the first affected order and its price. Distinguish a replacement of the recurring product from a one-off item added to an order.

Shopify's SubscriptionContract includes Subscription Billing Policy and Subscription Delivery Policy, so an edit can touch billing frequency, delivery frequency or both. Subscription Line items define the products, quantities and pricing for each recurring Order.

Stripe's Subscription object contains the subscribed customer, product and price, and status. A mid-cycle change such as an upgrade or downgrade can result in a pro-rata charge; Stripe's example upgrades a £10 monthly plan to a £20 option halfway through the billing period and bills an additional amount. Ask whether a box business wants that behaviour at all.

Check exception visibility

Use a proposed failed-charge example: the first attempt fails and a later attempt succeeds for the same intended delivery. Can staff see the original cycle, payment outcome and resulting order without counting the retry as a separate delivery?

The retry rules differ. Stripe's Smart Retries reattempt the charge according to your specifications for the number of retries and the maximum duration; the recommended default is 8 tries within 2 weeks, and the attempt_count attribute on the invoice.payment_failed webhook indicates how many attempts have been made so far.

A hard decline code prevents Stripe from retrying invoice payment without a new payment method. Retries continue to be scheduled, and attempt_count continues to increment, but retries only execute after detecting a new payment method. Unexecuted retries do not create a new Charge.

A Shopify contract records each billing attempt, so ask the subscription app provider for its retry schedule. Shopify's SubscriptionBillingAttempt fields include paymentGroupId, shared between retried payment attempts, and paymentSessionId, shared between payment attempts with similar payment details. Its originTime can override the billing attempt date so fulfilment intervals are not pushed to the next anchor date.

Shopify's API says billing attempts use idempotency keys to avoid duplicate order creation, and the idempotencyKey field is a unique key generated by the client to avoid duplicate payments. That safeguard alone does not establish how a merchant app or manual action handles every duplicate risk.

Compare reports using the same definitions: attempts, collected payments, orders and parcels are different counts. If information is spread across files, check that identifiers let the records be joined.

Lifecycle of a failed billing attempt and retry process

  1. Step 1
    Initial billing attempt fails — First payment attempt for scheduled delivery fails; no order created.
  2. Step 3
    Retry scheduled (Shopify) — SubscriptionBillingAttempt records each retry; paymentGroupId links retried attempts; idempotencyKey prevents duplicate order creation.
  3. Step 4
    Successful retry — Payment succeeds; order is created for the original delivery date; no new delivery is triggered.
  4. Step 5
    Visibility check — Staff can view original cycle, failed attempt, and final successful outcome without counting retries as separate deliveries.

Key metrics for monitoring subscription billing performance

Failed billing attempts (last 30 days)
Check via Shopify SubscriptionBillingAttempt or Stripe Invoice.webhook.status
Successful payments per cycle
Compare collected payments against total expected billing attempts
Orders created per billing cycle
Should match successful billing attempts; verify using order references and cycle dates

More from Billing Operations