> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/reporting-and-integrations/reporting/explore-custom-pricing.md). # Explore customers and properties with custom pricing > **Where to find it:** **Reports → Financial → Custom pricing**. Click the item, customer, or property count at the top of Custom pricing to open its list. You can also click the summary card values, including **Rate sheets in use** and **Waived items**. Search or sort the list, then choose **Download CSV** to export the matching records across all pages. Customer and property lists show each record once, with counts of its custom and waived prices. Click a customer or property row to open its record. Close the list to return to your report filters. Customer, property, item, and rate-sheet lists cover the full report, even when the price-detail table reaches its limit. If the waived-price list is limited to loaded details, the list states that clearly. Empty lists have downloading disabled. These lists help audit existing prices. To change a price, open the relevant customer, property, or rate sheet. See [Custom pricing](/administration/basics/custom-pricing-a-special-price-for-an-item-per-customer-or-property.md). --- # 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://learn.withessential.com/reporting-and-integrations/reporting/explore-custom-pricing.md?ask=&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.