> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ordergroove.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ordergroove.com/_mcp/server.

# Prepaid Subscriptions Overview

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](https://help.ordergroove.com/hc/en-us/articles/13542233192467-Enabling-Prepaid-Subscriptions-from-start-to-finish), 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`.

| Field                              | Type    | Description                                                                                                                                                                                                       |
| ---------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `prepaid_orders_remaining`         | integer | How many shipments the customer is still owed before the subscription renews. When this reaches `0`, the next order containing an item for this subscription renews it.                                           |
| `prepaid_orders_per_billing`       | integer | The length of the prepaid cycle, counted in shipments per charge. A value of `3` means the customer is billed for three shipments each time they're charged, and receives the remaining two at no further charge. |
| `renewal_behavior`                 | string  | What happens once the customer has received their last prepaid shipment. See [Managing Prepaid Renewal Behaviors](/advanced/prepaid-renewal).                                                                     |
| `last_renewal_revenue`             | float   | How much the customer paid in the most recent prepaid renewal order. That order is either the checkout order that captured the initial funds, or a later prepaid renewal order.                                   |
| `prepaid_origin_merchant_order_id` | string  | The merchant order ID — your ecommerce platform's order ID — for the order that captured the funds for the current prepaid cycle.                                                                                 |

---

## 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](/advanced/prepaid-renewal).

---

## Related endpoints

* [Update Prepaid Subscription Context](/reference/rest-rpc-api/subscriptions/update-prepaid-subscription-context) — change the prepaid cycle on a subscription
* [Change Prepaid Subscription Renewal Behavior](/reference/rest-rpc-api/subscriptions/change-prepaid-subscription-renewal-behavior) — change what happens at the end of a cycle
* [Upgrade to Prepaid Subscription](/reference/rest-rpc-api/subscriptions/upgrade-to-prepaid-subscription) — convert a standard subscription to prepaid