> For the complete documentation index, see [llms.txt](https://help.checkoutchamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutchamp.com/crm/crm-setup/campaign-setup/subscribe-and-save-profiles.md).

# Subscribe & Save Profiles

**Subscribe & Save profiles** are used to offer subscription versions of an existing product. Products within a profile are matched using the same **base product**, ensuring consistency between one-time and recurring purchase options.

When creating a Subscribe & Save profile, the following requirements apply:

* A **one-time product** and a **recurring product** must both exist within the **same campaign**.
* Both products must share the **same base product**.
* You may associate **multiple one-time products** with a **single recurring product**, allowing different one-time variations (such as bundles or sizes) to convert into a common subscription option.

This setup enables customers to seamlessly switch from a one-time purchase to a subscription while maintaining a unified product experience across the storefront and checkout.

<figure><img src="/files/0CgPj3amGrluD3jX8dR6" alt=""><figcaption></figcaption></figure>

**Choose the following:**

* Campaign Product: The one time offer to add a subscription to.
* Recurring Product: The recurring offer used to add a subscription.
* Default Product: Used for subscribe and save elements so that one option will be chosen by default.
* Subscription Options: Used to provide a list of frequencies for the customer to choose. The options must include the words day, week, or month. This can be seen in the example below If none are set, then the cycles used on the offer will be set to the subscription (shown as default).

<figure><img src="/files/2JVJWqL2XO9I8lpighkC" alt=""><figcaption></figcaption></figure>


---

# 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://help.checkoutchamp.com/crm/crm-setup/campaign-setup/subscribe-and-save-profiles.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.
