> 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/owners-playbook/new-to-podplay/pricing-models.md).
# Pricing Models
### Overview
The system offers pricing models to fit your Club's needs.
#### Court+ Pricing (Bill Splitting)
The Reservation Holder books a court at the full hourly rate, then invites friends in the App to split the cost. Each participant pays the court rate divided by the number of participants, and the Reservation Holder can elect to cover any portion of the invitee shares.
* [Court+ Model](https://podplay.gitbook.io/docs/owners-playbook/new-to-podplay/pricing-models/court+-model) — what Court+ is and how it solves the free-rider problem.
* [Court+ advantages and disadvantages](https://podplay.gitbook.io/docs/owners-playbook/new-to-podplay/pricing-models/court+-advantages-and-disadvantages) — Customer and Club trade-offs.
* [Bill Splitting](https://podplay.gitbook.io/docs/payments/customer-payments/bill-splitting) — mechanics of the bill split.
* [Cancellations with Bill Splitting](https://podplay.gitbook.io/docs/payments/what-is-a-cancellation-policy#cancellations-with-bill-splitting) — what happens when an invitee cancels.
* [Failed Charges with Bill Splitting](https://podplay.gitbook.io/docs/payments/charge-errors/failed-charges-with-bill-splitting) — what happens when an invitee's card fails.
#### Day Pass Non-member Fee
The mechanism inside Court+ that closes the free-rider gap. When a Member invites Non-member friends to a Reservation, the Non-member is charged a Club-defined fee at check-in (once per day, regardless of how many Reservations they join).
{% hint style="danger" %}
The Day Pass Non-member Fee is not available for EU or UK Clubs due to 3DS security protocols.
{% endhint %}
#### Spot+ Pricing
Spot+ was a per-spot dynamic pricing model where each participant paid for their own spot rather than splitting the court. It is no longer available — Clubs should use Court+ instead.
* [Spot+ model](https://podplay.gitbook.io/docs/owners-playbook/new-to-podplay/pricing-models/spot+-model) — how the legacy model worked.
* [Spot+ advantages and disadvantages](https://podplay.gitbook.io/docs/owners-playbook/new-to-podplay/pricing-models/spot+-advantages-and-disadvantages) — Customer and Club trade-offs of the legacy model.
### Choosing the Right Model for Your Club
Most Clubs are best served by Court+. It resolves the free-rider problem, gives the Club the greatest certainty in per-hour yield, is the least operationally intensive for staff, and introduces a "Carrot" experience for Reservation Holders (per-person cost goes down as more invitees accept). For broader Membership-pricing context, see [Membership Models](https://podplay.gitbook.io/docs/owners-playbook/build-your-club/build-a-membership/membership-models).
### FAQs
How do Events impact pricing?
When an Admin creates an Event, every Event is uniquely priced. This means that when an Admin creates an Event, they set the price of the Event. There are no hardcoded prices for Events, and if a price is not set when creating an Event, the Event will be $0.
How do Memberships impact pricing?
A Membership can change the pricing of a booking for Customers. How a Membership influences pricing is that Memberships have perks and these perks, if the Club chooses, can discount the cost of a Reservation.
For example:
* A Membership can have perk that offers 50% off Reservations, Monday to Friday, 6 am to 2 pm. If the Club’s pricing is a court pricing of $40, then a Customer with this Membership will pay $20 for the court during these hours and days. When this Member invites other Members, they split the cost of the Reservation in the App. When this Member invites other Non-members, there is a [**Non-member fee**](https://help.podplay.app/en/articles/5944385) added during Check-in (via [**QR Code**](https://help.podplay.app/en/articles/4406721) or [**Unlock Door button**](https://help.podplay.app/en/articles/2352449) for Autonomous venues).
And you can read more about [\*\*Memberships here](https://help.podplay.app/en/categories/151937-membership).\*\*
How do Promo Codes impact pricing?
Any Customer can use Promo Codes during the Reservation booking flow. It doesn’t matter if the Customer is a Member or a Non-member. The Promo Code can either be based on a percentage or a dollar amount. When a Promo Code is applied to a Reservation or an Event, the details of the Promo Code are applied secondary to the Customer’s Membership or Non-membership.
* This means that if a Customer is a Member and receives 50% off a Reservation during specific hours, and they have a Promo Code that offers 50% off a Reservation, they can apply the Promo Code and receive 75% off the Reservation’s original price.
To learn more, read about [**Promo Codes here**](https://help.podplay.app/en/categories/131073-promo-codes-and-gift-cards).
---
# 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/owners-playbook/new-to-podplay/pricing-models.md?ask=&goal=
```
`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.