> For the complete documentation index, see [llms.txt](https://docs.received.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.received.ai/subscription-billing/the-subscription-billing-process/set-up-subscriptions.md).
# Set Up Subscriptions
## Step 1: Create Products and Define Pricing
Navigate to the **Pricing Tab** to create products and define their pricing models. Use **ready-made templates** or start from scratch to create your model.
Click **'Use this Pricing'** and use our **‘Spreadsheet-in-a-System’** to edit your pricing. Edit line items, change prices and ranges, connect usage products, define billing logic and more. Once you're done, click on **'Publish'** to save the product and add it to your products catalog.
## Step 2: Create a Subscription
Navigate to **Pricing > Subscriptions** to create your subscription plans. You can add multiple products with varying pricing models to each plan. Once you're done, click on **'Update Subscription'.** \
\
Once you update a subscription plan, the platform automatically generates an **embeddable URL** for your website. This URL must be embedded in the specific plan's CTA, to ensure accurate billing.
## Step 3: Embed Subscription URLs into Your Website
Now that you have a specific URL for each plan, you can **embed the appropriate link** in the right call-to-action button **on your website**. \
\
Once customers sign up for a subscription, they will be directed to a **specific checkout page** where they will enter their payment information. The information collected will be used to **automatically charge customers** based on their specific plan and billing logic.
---
# 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.received.ai/subscription-billing/the-subscription-billing-process/set-up-subscriptions.md?ask=&goal=
```
`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.