Prepaid Subscriptions Overview
How prepaid subscription data is represented on a subscription, and what each field means
A prepaid subscription bills the customer for several shipments at once, then delivers those shipments without charging again until the cycle renews.
Once prepaid subscriptions are enabled for your store, you can use the prepaid endpoints to read and control them.
Prepaid subscription data
Subscription objects carry a prepaid_subscription_context field describing what the customer prepaid for. On a subscription that isn’t prepaid, the field is null.
Renewal behavior
renewal_behavior takes one of three values:
autorenew— bills the customer for a full prepaid cycle once all orders are placed. The renewal happens when the first order of the next cycle is placed.cancel— cancels the subscription once all orders are placed. Customers can reactivate it to start a new prepaid cycle.downgrade— converts the subscription to a standard subscription once all orders are placed. The next order is priced as a single shipment.
New subscriptions use autorenew unless you’ve changed the default for your store. For how to set a different default, or a custom behavior on an individual subscription, see Managing Prepaid Renewal Behaviors.
Related endpoints
- Update Prepaid Subscription Context — change the prepaid cycle on a subscription
- Change Prepaid Subscription Renewal Behavior — change what happens at the end of a cycle
- Upgrade to Prepaid Subscription — convert a standard subscription to prepaid