> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/2026-05/recurring_order_copies.md).

# Recurring order copies

The recurring order copy object and the allowed CRUD operations on the related resource endpoint

Recurring order copies asynchronously generate a target order from the associated source order and [order subscription](/core-api-reference/2026-05/order_subscriptions.md) (and related [order subscription items](/core-api-reference/2026-05/order_subscription_items.md)) and repeat this process according to a specified frequency (must be one of those available for the market, as set at the [subscription model](/core-api-reference/2026-05/subscription_models.md#subscription-frequencies) level).

{% hint style="info" %}
When copying an order repeatedly, the source order is never reused to generate any next runs, which are built on top of the associated order subscription and related order subscription items only. Recurring order copies never compute promotions or apply gift cards. That means you can apply promotions only to the source order, not to the automatically generated recurring target orders.
{% endhint %}

{% hint style="warning" %}
Recurring order copies cannot be used standalone — they must always be associated with an automatic order subscription.
{% endhint %}

## Payment sessions

As part of each recurring copy, a new [payment session](/core-api-reference/2026-05/payment_sessions.md) is created automatically on the target order using the payment details stored on the order subscription:

* If the subscription has a [payment wallet](/core-api-reference/2026-05/payment_wallets.md), the session is created with that wallet and its associated payment setting.
* If no wallet is present but a [payment setting](/core-api-reference/2026-05/payment_settings.md) is configured, the session is created with that setting alone.
* If the configured payment setting is a [gift card](/core-api-reference/2026-05/payment_setting_gift_cards.md) one, the session is created with the subscription's gift card code, after checking that the card covers the target order in full.
* If neither is set, no payment session is created and the target order remains unpaid.

Free target orders are skipped entirely, and no payment session is created for them. Otherwise, immediately after the session is created, a [payment authorization](/core-api-reference/2026-05/payment_authorizations.md) is attempted automatically against it.

{% hint style="warning" %}
A gift card that falls short of the target order total fails the copy before the session is saved — the order is left unplaced and the card's balance untouched, and the subscription drops to `pending`. More on this [here](/core-api-reference/2026-05/order_subscriptions.md#gift-card-coverage).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.commercelayer.io/core-api-reference/2026-05/recurring_order_copies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.