> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/reservations/rules-limits-and-settings/how-much-are-customers-charged-for-booking-a-reser.md).

# Peak vs Reduced vs Off-Peak

### Overview

There are three different Reservation price-types that can be used for private Reservations:

1. **Peak** (no flag)
2. **Reduced** (flag visible)
3. **Off-peak** (flag visible)

<figure><img src="/files/qG6pnK3qwJRehu0j2qzr" alt=""><figcaption></figcaption></figure>

### How Reservation price-types Work

Each of these three options can have unique rates. The unique rates can be set for:

* Non-members
* Members
* And by Membership tier (if desired)

Depending on how pricing is set in your App, this means that:

* Non-member can have a unique rate for Peak times, Reduced times, and Off-peak times
* Members can have a different rate for each of these same times
* And unique pricing can be set by Membership tiers

The hours can also change depending on a Membership tier, so that:

* Non-members have Peak hours from 3 pm to closing on weekdays and all day on weekends
* Membership A has Peak hours from 4 pm to closing on weekdays and from 8 am to 10 pm on Friday and Saturday
* Membership B has Peak hours all day, every day, except for 5 am to 8 am
  * Useful for selling a Membership that drives Customers toward certain hours of the day

Etcetera, for as many unique prices a Club wants to set.


---

# 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.podplay.app/reservations/rules-limits-and-settings/how-much-are-customers-charged-for-booking-a-reser.md?ask=<question>&goal=<endgoal>
```

`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.