# Page Not Found

The URL `how-do-i-set-up-product-selling-pans` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Selling Plans](https://help.smartrr.com/docs/support/subscription-setup/selling-plans.md)
- [Welcome to Smartrr help docs](https://help.smartrr.com/docs/welcome-to-smartrr-help-docs.md)
- [Will updating product prices in Shopify reflect in Smartrr?](https://help.smartrr.com/docs/support/shopify-questions/will-updating-product-prices-in-shopify-reflect-in-smartrr.md)
- [Why did my customer's subscription automatically pause?](https://help.smartrr.com/docs/support/troubleshooting/why-did-my-customers-subscription-automatically-pause.md)
- [Maximum/minimum (finite) subscription plans](https://help.smartrr.com/docs/support/subscription-setup/maximum-minimum-finite-subscription-plans.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://help.smartrr.com/docs/support/subscription-setup/selling-plans.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://help.smartrr.com/docs/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://help.smartrr.com/docs/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/docs/support/subscription-setup/selling-plans.md`).

You may also use `Accept: text/markdown` header for content negotiation.
