> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/services/product-pricing-and-availability-by-service.md).

# Product Pricing and Availability by Service

Each product can be tailored per service type.

### Service-Based Pricing

A product can have different prices depending on the selected service.  VAT can also be adjusted depending on the service type.

> For example, a Pepperoni Pizza may cost €12 for Table, but €13.50 for Delivery to cover packaging fees.

### Service-Based Availability

Products can be unavailable for specific services.

> For example, Chocolate Ice Cream may be available for Table and Takeaway, but disabled for Delivery.

### Removing Product Availability for a Service

If you want to make a product **unavailable** for a specific service, you can either **delete** or **deactivate** its pricing entry for that service.

1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Menu >** **Products**.
2. Select the product.
3. Go to the **Prices** tab.
4. Select the pricing entry and click on **Delete** if you want to delete it, or untick the **Active?** box to deactivate it.


---

# 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://docs.bossithq.com/services/product-pricing-and-availability-by-service.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.