> 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/grant-a-membership-package-to-a-customer.md).

# Grant a Package

### Overview

Managers can grant the membership-linked package template to a subscribed Customer without waiting for the next automatic monthly grant. Use this when a Customer needs their membership passes refreshed early, was missed by an automated grant, or should receive a new package tied to their membership benefit.

This action does **not** charge the Customer’s card. It uses the package template already linked to the Customer’s Membership plan.

{% hint style="info" %}
You need **Manager** role or higher. Staff do not see **Grant membership package**.

The button only appears when the Customer has an **active** membership subscription and that Membership includes a linked monthly package template. It is hidden for canceled memberships and for memberships with no package template configured.
{% endhint %}

### Grant Membership Package

* In the Dashboard, search for the Customer and open their **Customer Profile**
* Open the **Packages** section
* Click **Grant membership package**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FnGxaAFiPl3TQ7DrKMegH%2FScreenshot%202026-08-24%20at%2022.23.47.png?alt=media&amp;token=97893151-a17b-4b74-8079-e0480f1eec5f" alt=""><figcaption></figcaption></figure>

* Review the **Grant membership package** modal:
  * Package name and pass items from the Membership’s linked template
  * **Next automatic grant date** (for recurring Memberships)
  * A note that any active membership package for this Customer will be canceled before the new package is granted
* Under **Grant schedule**, choose one option:
  * **Keep schedule** (default): Grant now and leave the Membership’s automatic grant calendar unchanged. For standard monthly packages, passes expire on the current next grant date. For long-duration packages (more than 31 days), passes expire a set number of days after you grant—not on the next grant date.
  * **Reset grant schedule to today** (recurring Memberships only): Sets last grant to today, recalculates the next automatic grant date, then grants the package
* Click **Confirm grant**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FuOKS0fPxDeoM0J1ssAMe%2FScreenshot%202026-08-24%20at%2022.24.42.png?alt=media&amp;token=08435358-242c-41a5-ba0c-5c267e3c5e9e" alt=""><figcaption></figcaption></figure>

When you confirm, the Customer receives a success message and the **Packages** list refreshes with the new package.

#### What happens when you confirm

* Any active membership package for this Customer is canceled first
* A new package is created from the Membership’s linked template
* **Virtual credits** and **Replay credits** rows apply to the Customer’s balances when the grant completes (same as automatic monthly grants)
* Expiration depends on the template:
  * **Short monthly packages** (31 days or less): aligned to the Membership grant cycle (typically the next grant date)
  * **Long-duration packages** (more than 31 days): expire after the template’s duration from the grant date, even when that is beyond the next charge or grant date
  * **Never expire** templates: passes do not auto-expire by time

### How this differs from other package actions

| Action                              | When to use                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Regrant** (icon on a package row) | Refresh that package to match the latest template items while keeping grant-cycle expiration     |
| **Grant membership package**        | Issue a fresh package from the Membership template; cancels the current membership package first |
| **Grant standalone package**        | Sell a one-time standalone bundle and charge the Customer’s default booking payment method       |

For bulk grants across many Memberships at once, see [Grant a Package Template to Membership Subscribers](broken://pages/c5D5qP9hNfGn4OyT4t7x).

### Grant Standalone Package

Use this when a Customer should receive a Standalone Package and you want the Club to collect payment the same way as a normal purchase: using the Customer’s saved default booking payment method, with subtotal, taxes, and total shown before you confirm.

{% hint style="info" %}
The `Grant standalone package` button and actions below only appear when [Standalone Packages](/play-passes/play-pass-overview/standalone-packages.md) are enabled for your Club (same as the **Standalone** switch on templates) and when a Standalone Package created.
{% endhint %}

#### 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**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FgvYL9siNK7vLhI9DgLkL%2FScreenshot%202026-09-01%20at%2021.56.52.png?alt=media&amp;token=cbe6eba3-7c6f-47b3-a352-0934108efc8a" alt=""><figcaption></figcaption></figure>

#### 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)

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FCiCKmAqS5bYS42C81lQW%2FScreenshot%202026-09-01%20at%2022.00.01.png?alt=media&amp;token=9a375ced-d917-4084-8b20-5dcf0dc66d4a" alt=""><figcaption></figcaption></figure>

* 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**

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2Fr17eby8BcdUCuvoKPlxY%2FScreenshot%202026-09-01%20at%2022.00.31.png?alt=media&amp;token=c754c705-b936-4291-b43b-243c15bdd998" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FIrgjn2WUN8kWfBEys1t4%2FScreenshot%202026-09-01%20at%2022.00.48.png?alt=media&amp;token=ee573639-af4e-4ecc-bf3b-4441850678cd" alt=""><figcaption></figcaption></figure>


---

# 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/grant-a-membership-package-to-a-customer.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.