Recurring Orders overview

Ask about this Page
Copy for AI
View as Markdown

Overview of the concepts related to Recurring Orders and the checkout process.

A Recurring Order automates the reordering process for a customer. It defines the schedule and configuration for automatically creating and placing future Orders at regular, predefined intervals on behalf of the customer, and acts as the base for generating those Orders.

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.

Learn more about using Recurring Orders for B2B replenishment in our self-paced Implement B2B purchase flows module.

General concepts

Recurrence Policies

A Recurrence Policy lets you define a schedule for selling recurring products at specific prices. The recurring order can occur on a specific day of every month, or at fixed intervals. You define Recurrence Policies on individual Line Items and Custom Line Items as well as individual prices (both Standalone and Embedded).

A Project can have multiple Recurrence Policies at the same time and they can be reused across different Recurring Orders.

A Recurrence Policy can also define a minimum number of days between Orders to limit how soon after the last Order an early Order can be requested. It does not change the schedule.

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

Line Items and Custom Line Items carry information about possible recurrence. For each recurring item, you define when or how often the item should be ordered, as well as the pricing mode using a Recurrence Policy.
For how to set recurrence on Line Items and Custom Line Items, see Recurring Orders APIs overview.

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.

The price selection mode determines whether Recurring Orders should retain the original item price or adopt the new price going forward. For how to set the price selection mode with the API, see Recurring Orders APIs overview.

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.

For example, for a Recurring Order using an SKU with a 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:

For how to set recurrence on prices with the API, see Recurring Orders APIs overview.

Recurring Carts

A recurring Cart is used as the source to create all subsequent orders generated by a specific Recurring Order. A recurring Cart contains only Line Items and Custom Line Items that are linked to a Recurrence Policy.
For how long recurring Carts are kept, see Recurring Orders APIs overview.
To learn how recurring Carts are created, see Initial creation.

Recurring Orders

Initial creation

For how to create a Recurring Order with the API, see Recurring Orders APIs overview.

Example

A customer wants to buy four different products (SKUs). Their Cart has the following items:

ItemPurchase intervalShip to
SKU1One-time purchaseHome
SKU2WeeklyHome
SKU3MonthlyOffice
SKU4MonthlyOffice

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.
Each Recurring Order holds a link to the recurring Cart that contains the items which share the same schedule.

Subsequent Orders

Once a Recurring Order is created, the platform automatically creates new Orders based on the defined schedule. For the information that a Recurring Order holds, see Recurring Orders APIs overview.

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.

DateStatusOrder createdNext Order date
1 Jul 2025Active✓8 Jul 2025
8 Jul 2025Active✓15 Jul 2025
15 Jul 2025Active✓22 Jul 2025
22 Jul 2025Active✓29 Jul 2025
29 Jul 2025.........
For the API Extensions and Messages that run for each new Order, see Recurring Orders APIs overview.

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.

DateStatusOrder CreatedNext Order date
1 Jul 2025Active✓8 Jul 2025
6 Jul 2025Paused by the user✗None
19 Jul 2025Reactivated by the user✗22 Jul 2025
22 Jul 2025Active✓29 Jul 2025
29 Jul 2025Active......

Failed Recurring Orders

Errors prevent subsequent Orders from being created and cause the Recurring Order's state to change to Failed.
Recurring Orders do not retry automatically. A Recurring Order stays in the Failed state, and generates no Orders, until you resolve the issue and set it back to Active.
For the Message that reports the failure, see Recurring Orders APIs overview.

Order now

You can create the next Order of a Recurring Order immediately instead of waiting for the next scheduled Order. The request is rejected if the Recurring Order is not eligible, for example, if it is paused or the minimum gap between Orders has not passed. For how to request an early Order with the API and all eligibility conditions, see Recurring Orders APIs overview.

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.

DateEventOrder createdNext Order date
1 Oct 2025Scheduled Order✓1 Nov 2025
20 Oct 2025Early Order (the November Order)✓1 Dec 2025
1 Dec 2025Scheduled Order✓1 Jan 2026

Payments BETA

By default, a subsequent Order is created as soon as it is due, and collecting payment for it is your responsibility afterwards. Alternatively, you can have payment collected by commercetools Checkout before the Order is created, so that a subsequent Order only exists if its payment succeeded.
The recurring payment configuration on Carts and the integration of Recurring Orders with Checkout are in public beta.
For how to configure recurring payments with the API, see Recurring Orders APIs overview.