Overview of the concepts related to Recurring Orders and the checkout process.
You define the Cart containing the products to be ordered, the reorder frequency, and the start and end dates. Once a customer creates a Recurring Order, Orders are generated automatically at the specified interval until the Recurring Order is paused, skipped, canceled, or has expired. Recurring Orders can also be modified to accommodate changes in demand.
General concepts
Recurrence Policies
A Project can have multiple Recurrence Policies at the same time and they can be reused across different Recurring Orders.
You have two options for choosing a schedule:
-
Standard schedule: daily, weekly, or monthly
-
Day of month schedule: a specific date of each month
For how to define schedules with the API, see Recurring Orders APIs overview.
Recurring items
Define a price selection mode
A Recurring Order can span several months, resulting in the generation of multiple scheduled orders over time. When selling a product over an extended period, it's common for its price to change—sometimes more than once.
You can choose one of the following price selection modes:
- Fixed price: the price set at the time the Recurring Order was created remains the same. With this configuration, any changes made to the Product's price will not affect existing Recurring Orders.
- Dynamic price: each time a new order is generated from a Recurring Order, the platform retrieves and applies the current Product price. With this configuration, any updates to a Product's price will affect all existing Recurring Orders going forward.
Prices
Prices (both Embedded and Standalone) carry information about possible recurrence. Each price that is defined on a recurring item must be connected to a Recurrence Policy.
When selecting a price for a Recurring Order, the platform will use the standard price selection rules, along with the specified Recurrence Policy, to determine the correct price for the given SKU and recurrence. If no such price is found, the platform defaults to using the standard one-time purchase price.
monthly recurrence, the platform will attempt to locate a price explicitly tied to that monthly policy.You only need to set recurrence information on prices if you intend to offer special pricing for recurring items; otherwise, no changes to your existing pricing configuration are needed.
For example, to sell yogurt in 3 different intervals, you set a price for each interval:
Recurring Carts
Recurring Orders
Initial creation
Example
A customer wants to buy four different products (SKUs). Their Cart has the following items:
| Item | Purchase interval | Ship to |
|---|---|---|
| SKU1 | One-time purchase | Home |
| SKU2 | Weekly | Home |
| SKU3 | Monthly | Office |
| SKU4 | Monthly | Office |
The customer completes the checkout process and receives an email with the confirmation.
Internally, the following steps happen:
- A new Order is created with all four items.
- The platform determines that three of the four items are recurring and groups them by their recurrence interval:
- Group A: SKU2 (weekly)
- Group B: SKU3 and SKU4 (monthly)
- For each group, a new Recurring Order and a new recurring Cart are created.
- The new recurring Carts inherit the base configuration of the original Cart.
This results in the following:
- Recurring Order A: SKU2 is shipped weekly to the home address.
- Recurring Order B: SKU3 and SKU4 are shipped monthly to the office address.
Subsequent Orders
Delays can occur due to application or server-side processing.
The following example shows when the next orders are created for a Recurring Order configured with a weekly interval.
| Date | Status | Order created | Next Order date |
|---|---|---|---|
| 1 Jul 2025 | Active | ✓ | 8 Jul 2025 |
| 8 Jul 2025 | Active | ✓ | 15 Jul 2025 |
| 15 Jul 2025 | Active | ✓ | 22 Jul 2025 |
| 22 Jul 2025 | Active | ✓ | 29 Jul 2025 |
| 29 Jul 2025 | ... | ... | ... |
Paused Recurring Orders
You can pause a Recurring Order at any time. When paused, subsequent Orders will not be created until the Recurring Order is reactivated.
The following example shows when the next orders are created for a Recurring Order configured with a weekly interval that has been paused and then reactivated.
| Date | Status | Order Created | Next Order date |
|---|---|---|---|
| 1 Jul 2025 | Active | ✓ | 8 Jul 2025 |
| 6 Jul 2025 | Paused by the user | ✗ | None |
| 19 Jul 2025 | Reactivated by the user | ✗ | 22 Jul 2025 |
| 22 Jul 2025 | Active | ✓ | 29 Jul 2025 |
| 29 Jul 2025 | Active | ... | ... |
Failed Recurring Orders
Failed.Failed state, and generates no Orders, until you resolve the issue and set it back to Active.Order now
The early Order consumes the upcoming occurrence. It is not an additional Order, and it does not move the schedule to the date of the request. The customer receives the same number of Orders over time, and only the timing of one Order changes.
The following example shows a Recurring Order configured with a monthly interval on the first day of the month. An early Order is requested on 20 October 2025, while the next Order is scheduled for 1 November 2025.
| Date | Event | Order created | Next Order date |
|---|---|---|---|
| 1 Oct 2025 | Scheduled Order | ✓ | 1 Nov 2025 |
| 20 Oct 2025 | Early Order (the November Order) | ✓ | 1 Dec 2025 |
| 1 Dec 2025 | Scheduled Order | ✓ | 1 Jan 2026 |