> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/core-product-structure/product-catalog-offering.md).

# Product Catalog Offering

Policy and configuration reference for plans, promotions, and catalog governance on Reach Platform.

### Overview

This document is the **end-to-end policy and configuration reference** for brands onboarding to the Reach Platform. It acts as a **single source of truth** for how the product catalog offering works and how it can be configured and used.

#### Audience

* **Brand operations teams**
* **Catalog and promotions owners**
* **Care teams and onboarding leads**

#### Scope

* Defines standard **BAU policies** and **configuration inputs**
* Highlights **constraints** and **governance rules**
* Flags items that require **custom work**

### Browse topics

* [Promotions](/core-product-structure/product-catalog-offering/promotions.md)
* [Plan configuration](/core-product-structure/product-catalog-offering/plan-configuration.md)
* [Account and customer management](/core-product-structure/product-catalog-offering/account-and-customer-management.md)
* [Payments, fees, and compliance](/core-product-structure/product-catalog-offering/payments-fees-and-compliance.md)
* [Content and branding](/core-product-structure/product-catalog-offering/content-and-branding.md)

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/core-product-structure/product-catalog-offering.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.