> 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/core-concepts/seat-based-rendering-type/stock-feature.md).

# Stock Feature

Enables participant management for offerers when seat-based rendering type is activated

* [Why](#id-1.14.x-stockbundle-businessrules-why)
* [Which context](#id-1.14.x-stockbundle-businessrules-whichcontext)
* [Interfaces](#id-1.14.x-stockbundle-businessrules-interfaces)
* [Configurations](#id-1.14.x-stockbundle-businessrules-configurations)
* [Workflows](#id-1.14.x-stockbundle-businessrules-workflows)
  * [Stock management](#id-1.14.x-stockbundle-businessrules-stockmanagement)
* [Special rules](#id-1.14.x-stockbundle-businessrules-specialrules)

## Why <a href="#id-1.14.x-stockbundle-businessrules-why" id="id-1.14.x-stockbundle-businessrules-why"></a>

The stock feature will bring participant management to the Seat-Based rendering type.

Offerors will be able to define the number of participants per session.

Asker can now select a number of participants, within the limit of the remaining number of participants, for an available session.

The price will be calculated automatically according to the number of participants.&#x20;

## Which context <a href="#id-1.14.x-stockbundle-businessrules-whichcontext" id="id-1.14.x-stockbundle-businessrules-whichcontext"></a>

The stock bundle will bring two major changes to sessions:

* The price will no longer be per session but per participant
* Each session will have its own number of participants.

## Interfaces <a href="#id-1.14.x-stockbundle-businessrules-interfaces" id="id-1.14.x-stockbundle-businessrules-interfaces"></a>

Please, find all interface documentation related to the Stock bundle, here:

**Front:**

* [Listing deposit (Seat-Based Rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/create-a-listing-seat-based.md)
* [Listing page (Seat-Based Rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/show-a-listing-seat-based.md)

**Dashboard:**

* [Listings dashboard (Seat-Based rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/edit-a-listing-seat-based.md)

## Configurations <a href="#id-1.14.x-stockbundle-businessrules-configurations" id="id-1.14.x-stockbundle-businessrules-configurations"></a>

This feature is enabled automatically when the Seat-Based rendering type is activated.

## Workflows <a href="#id-1.14.x-stockbundle-businessrules-workflows" id="id-1.14.x-stockbundle-businessrules-workflows"></a>

### Stock management <a href="#id-1.14.x-stockbundle-businessrules-stockmanagement" id="id-1.14.x-stockbundle-businessrules-stockmanagement"></a>

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/pQbAascOeofkz2rSG12i/6956193286" alt=""><figcaption></figcaption></figure>

## Special rules <a href="#id-1.14.x-stockbundle-businessrules-specialrules" id="id-1.14.x-stockbundle-businessrules-specialrules"></a>

The session’s stock can be set and modified by the offeror at any time. He can manually increase it or decrease it.

When a booking of X participants is accepted, the system will decrease the stock by this number.

When a booking of X participants is canceled then the system will increment the stock by this number.

The system checks each time the stock and if it is 0 then the session becomes unavailable.


---

# 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/core-concepts/seat-based-rendering-type/stock-feature.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.
