> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages.md).

# Packages

**Available on:** Desktop · Web · Phone

A **package** is something a client buys in advance and uses over several visits. Packages bring clients back, and let them pay once instead of every time.

## Two kinds of package

| Kind               | What the client buys                                               | Example                                                              |
| ------------------ | ------------------------------------------------------------------ | -------------------------------------------------------------------- |
| **Fixed services** | A set number of particular services                                | *10 Hair Spas* for ₹8,000 — each hair spa booked uses one of the ten |
| **Value based**    | An amount to spend on any services, often with a free extra amount | Pay ₹10,000, get ₹1,000 free — ₹11,000 to spend on any services      |

## How packages work, start to finish

1. **Set up the package** — its price, how long it lasts, and for a fixed services package the services it includes. See [Setup Package](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/setup-package.md).
2. **Decide what to record** at each visit, if anything — weight, skin type, a photo. See [Package Parameters](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/package-parameters.md).
3. **Sell it to the client** and **take payment** — all at once or in parts. See [Customer Packages](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/customer-packages.md).
4. **The client books against it.** When booking, the client's packages are listed under **Packages** in Create Appointment, and each service booked uses one from the package — see [Creating and Changing Appointments](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/creating-and-changing-appointments.md).
5. **Billing** — services taken from a package are priced from the package, not charged again. See [Billing Appointments](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/billing-appointments.md).

> **Example.** Kavya buys *10 Hair Spas* for ₹8,000 and pays ₹4,000 today. She books her first hair spa for Saturday: in Create Appointment the **Packages** list shows the hair spa with 10 pending, and you add it from there — once the booking is saved, her package shows 9 pending. She pays the other ₹4,000 next month in **Customer Packages**.

## In this section

| Page                                                                                                                                                                   | Use it to                                                                 |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [Setup Package](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/setup-package.md)                                             | Define packages, the services in each, and batches for group courses      |
| [Package Parameters](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/package-parameters.md)                                   | Choose the details recorded about the client at each visit                |
| [Customer Packages](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/customer-packages.md)                                     | Sell packages to clients, take payments and refunds                       |
| [Value Packages and Discount Coupons](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/value-packages-and-discount-coupons.md) | Use a value based package for services, or turn its balance into a coupon |
| [Batch Manager](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/batch-manager.md)                                             | Run group sessions — classes or courses — for package clients             |

## Settings that affect packages

In **Configuration**: *Allow Package Use Without Balance*, *Allow Excess Package Payment*, *Hide Expired Packages*, *Package should always be sold*, *Confirm Agent Selection Before Save*, *Do not use branch wise customer packages*, and the **Discount Coupon** options. Each is explained on the **Configuration** page.

## On the web

All the package screens are on the web and phone, except **Direct Sale** of a package, which is desktop only.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
