> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/stock/orders/stock-order-configurations.md).

# Stock order configurations

## What is a stock order configuration?

A **stock order configuration** determines:

* **Which stock types** people can order
* **Whether stock orders are open** (optional submission window)
* **Where orders can be placed** (for example from accreditation forms)

If you don’t select a configuration for a list or form, stock orders won’t be visible there.

## Where you can attach a configuration

You can set a configuration at two levels:

* **List level**: applies to all Forms in that list by default
* **Form level**: overrides the list configuration for a specific Form

## Which configuration is used (list vs form)

When someone opens stock orders from an accreditation Form, Eventication will use:

1. The **Form configuration** (if one is selected)
2. Otherwise the **List configuration**

## Open/closed for submissions

You can optionally set a “submission window” on the configuration:

* From when can people submit stock orders?
* Until when can people submit stock orders?

{% hint style="info" %}
If stock orders are closed, people can still view existing orders, but they won’t be able to create new ones or submit changes.
{% endhint %}

### Setup checklist (what you need to do)

At minimum:

1. Create a **stock order configuration** for your event.
2. Add the **stock types** you want people to be able to order.
3. Attach the configuration to:
   * the **list** (recommended for most setups), and/or
   * a specific **Form** (if that form needs different rules).

{% hint style="warning" %}
If orders already exist for a configuration, changing the configuration can cause existing orders to become locked for non-moderators (because the new configuration might have different stock types or availability rules).
{% endhint %}


---

# 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.eventication.com/event/stock/orders/stock-order-configurations.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.