Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 (and related order subscription items) and repeat this process according to a specified frequency (must be one of those available for the market, as set at the subscription model level).

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.

Payment sessions

As part of each recurring copy, a new payment session is created automatically on the target order using the payment details stored on the order subscription:

  • If the subscription has a payment wallet, the session is created with that wallet and its associated payment setting.

  • If no wallet is present but a payment setting is configured, the session is created with that setting alone.

  • If the configured payment setting is a gift card 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 is attempted automatically against it.

Last updated