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.
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.
Compare the payment models
For pay-per-delivery plans, ask when the charge is attempted, when an order appears, and what happens if payment fails. Shopify's billing-attempt API says a successful attempt creates an order and associates transactions and errors with the attempt. That does not prove how a particular app is configured.
For prepaid plans, ask where later paid parcels remain visible and how the app links them to the initial payment. 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
Pros and Cons of Pay-Per-Delivery vs Prepaid Plans
- Pay-Per-Delivery ProsFlexibility to skip or cancel without loss; billing aligns with actual delivery.
- Pay-Per-Delivery ConsRisk of failed charges leading to missed deliveries; requires ongoing monitoring.
- Prepaid Plans ProsPredictable cash flow; customers pay upfront for multiple deliveries.
- Prepaid Plans ConsHarder to track remaining deliveries; potential for disputes if deliveries don’t arrive as expected.
Inspect what an edit changes
When an order or contract is edited, ask 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.
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?
Shopify's API documents idempotency keys to avoid duplicate execution when an API request is retried. 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.
Key Metrics to Monitor in Subscription Billing
- Billing Attempts
- Count of all charge attempts (successful or failed)
- Collected Payments
- Number of successful transactions linked to billing attempts
- Orders Created
- Total number of orders generated from subscription cycles
- Parcels Delivered
- Actual shipments sent to customers (may differ from orders)
