> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/reporting/how-can-i-see-the-current-point-balance-for-all-customers.md).

# How can I see the current point balance for all customers?

Use the **Customer Details report** to view or export the current point balance for each customer in your Perkville program.

### Run the report

1. From the Perkville administrative dashboard, go to **Reports**.
2. Select **Customer Details**.
3. Apply any applicable filters, such as locations.
4. Run the report.

The report includes each customer’s current point balance. You can also export the results for further review or analysis.

Learn more about the [Customer Details report](https://docs.perkville.com/features/reports/customer-details).

### View point balances by location

To see point balances summarized by location rather than listed for each individual customer, use the **Points by Location report**.

Leave the report’s start and end dates blank. When no date range is selected, the **Change in Point Balance during Queried Time Period** column represents the current point balance for the selected location or locations.

Learn more about the [Points by Location report](https://docs.perkville.com/features/reports/points-by-location).


---

# 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.perkville.com/faqs/reporting/how-can-i-see-the-current-point-balance-for-all-customers.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.
