> 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/play-passes/play-pass-overview/standalone-packages.md).

# Standalone Packages

Standalone packages are pass bundles that **Customers can buy directly** from your club’s packages page, without signing up for a Membership. You build them from the same **Package Templates** area you use for membership benefits, and you turn on **Standalone** and add price, visibility, and how long purchased passes stay valid.

Staff can also [**grant** a standalone package](/play-passes/play-pass-overview/grant-a-membership-package-to-a-customer.md) to a single Customer from the Dashboard (for example when you are selling a pack at the desk and need to charge the Customer’s card on file). That flow uses a short checkout preview, then charges the Customer’s **default booking payment method** and creates the package.

Use this when your club sells packs or punch cards (for example Open Play Passes or Credits) as one-time purchases.

{% hint style="info" %}
You must have the [Owner role](https://docs.podplay.app/overview/the-dashboard/admin-roles#owner-role) to see the **Package Templates** page.
{% endhint %}

### See which templates are sold standalone

* Navigate to **Package Templates** in the Dashboard
* Click the **Standalone** tab
* Look at the **Available for Sale** column — templates showing **Yes** are currently offered for direct purchase

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FOgchiYmudrFjnjFJwWlm%2FScreenshot%202026-09-01%20at%2021.41.10.png?alt=media&amp;token=d63c2ff6-760a-4228-9354-47dfee021dd1" alt=""><figcaption></figcaption></figure>

### Set how standalone purchases expire

After **Standalone** is on, the **Duration** section explains how long passes last **after a Customer buys this package standalone** (read the help text on the screen for each choice).

* Choose **Days** — then enter **Duration (in days)**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FPKpPuvUmrSxpJofopcgw%2FScreenshot%202026-09-01%20at%2021.42.17.png?alt=media&amp;token=3c06e3e2-65dc-4604-ab6c-78ab909eb113" alt=""><figcaption></figcaption></figure>

* Choose **Fixed date** — then pick **Expiry Date**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2Flh2MOWbnk0bX27Kgocsa%2FScreenshot%202026-09-01%20at%2021.42.32.png?alt=media&amp;token=86ea02f5-96ff-4347-9682-c05b0e278875" alt=""><figcaption></figcaption></figure>

* Choose **Never expire** — passes from this purchase do not auto-expire by time

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FHYxp6U6caitzwdP1kH4G%2FScreenshot%202026-09-01%20at%2021.42.42.png?alt=media&amp;token=d4b3e208-b298-4cef-8b3b-59ec8e3d8238" alt=""><figcaption></figcaption></figure>

### Price, shop order, and links

* Enter **Price** — this is what the Customer is charged to purchase this package when buying standalone (required when **Standalone** is on)
* Optional: set **Display Priority** — controls order on the club packages page (**lower numbers appear first**, per the field help)
* Enter **Slug / Deep link URL** — short text used in links; it should be unique. It often fills in from the display name—you can edit it for clean sharing
* Set **Send charges to Area** — stores the area (not a Stripe account id); charges use that area’s linked Stripe account. This is separate from **Tax Region** (which taxes apply) and from **Available at** (where the package is sold). Required when more than one area is available. When your club or account only has one area (or you can manage only one), PodPlay selects that area automatically and hides this field.

### Package groups (variants vs mixed bundles)

When **Standalone** is on, **Publish in package group** controls how the package appears on the customer **Packages** page:

* **Same pass type only (homogeneous)** — All rows in **Passes** are the same kind (for example only open play passes). You **must** pick a package group. Use one group for size variants (3-pack, 5-pack, 10-pack). Every template in that group must use the same pass type.
* **Mixed pass types (heterogeneous)** — The bundle includes more than one pass **type** (for example court reservations **and** replay passes). Group selection is locked to **Uncategorized**. Customers see each bundle as its own card with a breakdown of what is inside.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FRvTDLWIFhAos4NpFqhDM%2FScreenshot%202026-09-01%20at%2021.47.27.png?alt=media&amp;token=576558d3-3296-4e1a-98da-ca3eddd22cf5" alt=""><figcaption></figcaption></figure>

If a package group is used for multiple offerings, Customers will have the option to select from the different package choices once on the Order Summary page of the purchase flow.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2Fz9aBk29DYliRJlcgioq6%2FScreenshot%202026-09-01%20at%2021.49.51.png?alt=media&amp;token=10943094-e449-43d1-b972-e991d910ac7a" alt=""><figcaption></figcaption></figure>

### Archive a standalone package template

If you want to retire a standalone template without deleting it, use **Archive**. Archived templates:

* Are hidden from the public packages page and from the grant picker on customer profiles
* Cannot be purchased or granted until you unarchive them
* Can be found in the **Package Templates** board by enabling **Show archived** in Filters, where they appear with an **Archived** tag

To archive:

* Open the standalone template in **Package Templates**
* Click the **⋯** (actions) button in the drawer footer, then select **Archive**

If **Archive** is greyed out, the template is still linked to at least one membership — unlink it first.

To restore, open the archived template from the board (with **Show archived** on), then open the **⋯** menu and click **Unarchive**.

### Tips

* Match **Display Name** to what you want Customers to read at checkout
* Keep **Slug** short and unique if you share direct links to a specific package
* Use **Display Priority** to put your most important bundles at the top of the packages page (lower numbers appear first — 0 is before 10)
* When granting Standalone Packages from the Dashboard, double-check the **Checkout** totals before **Confirm purchase**—taxes can differ from the template list price alone
* On a Customer’s profile under **Packages**, you can use the pencil icon to adjust **pass** counts for some item types. **Virtual credits** and **Replay credits** rows do **not** offer that edit control—changing those numbers on the profile would not change the Customer’s actual virtual credit or replay balance; fix mistakes by following your club’s support or billing process.
* Changing **Virtual credits** or **Replay credits** amounts on a template only affects future purchases; it does not reclaim value from Customers who already received a grant.
* For general template setup (membership-focused fields, regrant, delete rules), see [Create and Manage Package Templates](/play-passes/create-and-manage-package-templates.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 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/play-passes/play-pass-overview/standalone-packages.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.