> 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/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, but you turn on **Standalone** and add price, visibility, and how long purchased passes stay valid. Staff can also **grant** a standalone package 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 add-on packs (for example open play or reservation credits) as one-time purchases. **PLEASE NOTE:** Standalone packages must be turned on for your PodPlay site. If you do not see a **Standalone** switch in a package template, or you never see an **Availability** column on the **Package Templates** table, ask your PodPlay CSM to confirm the feature is enabled for your club. **PLEASE NOTE:** The **Package Templates** page itself is limited to PodPlay admins and facility owners. If you are an owner and cannot open **Package Templates**, your account may need self-serve packages access—contact your PodPlay CSM. ### 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 \[SCREENSHOT NEEDED: Package Templates page with Standalone tab selected and Available for Sale column visible] ### Turn a template into a standalone package * Open **Package Templates** * Click **Package Template** to create a new template, or click an existing template name to edit \[SCREENSHOT NEEDED: Details section with Standalone switch visible] * Under **Details**, turn **Standalone** **on** * Complete **Package Name** and **Package Name Plural** (Customers see this wording in purchase flows) ### 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)** * Choose **Fixed date** — then pick **Expiry Date** * Choose **Never expire** — passes from this purchase do not auto-expire by time \[SCREENSHOT NEEDED: Duration options with Duration (days), Expiry date, and Never expire] ### 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. \[SCREENSHOT NEEDED: Publish in package group field for homogeneous vs heterogeneous template] ### Add passes to the package * Open the **Passes** section * Click **Pass** and configure each row (reservation, event, guest passes, and so on), same as for membership package templates * If the bundle should include **wallet value** at purchase time, add **Virtual credits** (dollar amount) and/or **Replay credits** (free quick replay count) rows—the Customer receives those balances **when the standalone purchase or staff grant completes**, the same way membership packages apply those rows when the Customer is linked to the package. See [Create and Manage Package Templates](/play-passes/create-and-manage-package-templates.md) for how those rows work. * Use the drag handle to reorder passes if the order should match how you describe the bundle \[SCREENSHOT NEEDED: Passes list on a template with Standalone enabled] ### Save * For a new template, click **Create** * For an existing template, click **Update** If the template is also linked to memberships, an **Update** can still open **Confirm Package Updates** for subscribers. See [Choose How Package Template Updates Apply to Memberships](/play-passes/membership-packages/choose-how-package-template-updates-apply-to-memberships.md). ### Grant a standalone package to a Customer (charge on file) Use this when a Customer should receive a standalone bundle and you want the club to collect payment the same way as a normal package purchase—using the Customer’s **saved default booking payment method**, with subtotal, taxes, and total shown before you confirm. **PLEASE NOTE:** On an active Member’s profile, you may also see **Grant membership package** (Manager and above). That action grants the Membership’s linked template without charging the card. See [Grant a Membership Package to a Customer](/play-passes/play-pass-overview/grant-a-membership-package-to-a-customer.md). **PLEASE NOTE:** The **Grant standalone package** actions below only appear when standalone packages are enabled for your club (same as the **Standalone** switch on templates). You also need a saved template that has **Standalone** turned **on**. #### Start from the Customer’s profile * Open the Customer’s profile (for example from **Customers** search) * Open the **Packages** section * Click **Grant standalone package** * In the dialog, choose a package template that is enabled for standalone purchase, then click **Continue** \[SCREENSHOT NEEDED: Customer profile Packages section with Grant standalone package and template picker] #### Start from Package Templates * Open **Package Templates** and open the template you want to sell (name in the table) * Under **Details**, confirm **Standalone** is **on** and the template is saved * Scroll to the **Passes** section * Click **Grant standalone package** \[SCREENSHOT NEEDED: Package template drawer Passes section with Grant standalone package] #### Checkout and confirm * Confirm the package summary (name, list price, duration rules from the template, pass counts, and any **Virtual credits** or **Replay credits** shown as items—those amounts apply to the Customer’s balances when you complete the purchase) * If you started from the Customer profile, the recipient is already set. If you started from **Package Templates**, pick the Customer in **Recipient** * Optional (**administrator accounts only**): expand **Admin overrides** to set a different **Price override** or change how long passes last (**Expiry override**). Leave overrides alone to use the template’s price and expiry rules * Click **Proceed to checkout** * Review **Charges** (subtotal, taxes, total due) and the payment note that the Customer will be charged on their **default booking card** * If **Billing not ready** appears, open the Customer’s profile and add or fix payment methods before you try again * When everything looks correct, click **Confirm Purchase** \[SCREENSHOT NEEDED: Grant standalone package modal on checkout step showing totals and Confirm purchase] **PLEASE NOTE:** **Confirm purchase** stays disabled until the system confirms the Customer can be billed (they need a billing profile and a default booking payment method). Use the **Review payment methods** link on the checkout step, or the Customer’s profile, to resolve missing cards. ### 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**. ### Turn standalone off * Open the template and turn **Standalone** **off** * Save with **Update** (or **Create** on a new draft) PodPlay clears standalone-only fields (such as price and slug) when **Standalone** is off. If you only meant to pause sales temporarily, confirm with your CSM or internal process before switching it off. ### 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 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/standalone-packages.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.