> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based.md).

# Seat Based

The **Seat-Based** rendering type is a standardized option that administrators can enable within SCND. When activated, vendors can create listings based on the number of participants who will benefit from the service.

For example, in the case of a training class, customers specify the number of participants at the time of booking. The system then calculates the total cost based on the number of seats selected.

**Example:**

* A class offers **10 available seats**.
* The customer booked **4 seats**.
* Each seat costs **10 euros**.
* The total booking cost is **40 euros**.

This pricing model ensures that customers are charged based on actual usage, making it suitable for services where capacity is limited.

To learn more about this feature, access

* [How to Create a listing in Seat Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/create-a-listing-seat-based)
* [How to edit a listing in the Seat Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/edit-a-listing-seat-based)
* [How to show a listing in the Seat Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/show-a-listing-seat-based)
* [How to book a service in the Seat Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/book-a-listing-seat-based)

This process follows a structural backbone with slight differences depending on the following rendering type:

* [Time-Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/35/v2.0-draft/business-rules/time-based-rendering-type/~/overview)
* [Flat-Rate rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/35/v2.0-draft/business-rules/flat-rate-rendering-type/~/overview)
* [Seat-Based rendering type](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/35/v2.0-draft/business-rules/flat-rate-rendering-type/~/overview)
* [Request for Proposal rendering type](https://features.scnd.com/v2.0/core-concepts/request-for-proposal-bundle-rfp.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 by asking a question.

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

```
GET https://features.scnd.com/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based.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.
