# Orders

## What are stock orders?

A **stock order** is a request for a certain **stock type** (for example keys, radios, or other items you manage in the [Stock](/event/stock/inventory-categories.md) module).

Stock orders are typically created from the **accreditation** [**form**](/event/accreditation/lists/forms.md) by the form responsible. After that, your event team can review and approve/reject the request.

## How it works (high level)

* **Event sets up what can be ordered**: you choose a **stock order configuration** and the allowed stock [types](/event/stock/inventory-categories/types.md).
* **Form responsible creates one or more orders**: they pick a stock type, amount, a **lease start** and (if applicable) **lease end**.
* **They assign the order (optional)**: they can assign the ordered items to visitors/vehicles that will pick them up.
* **They submit the order**: submitted orders are “sent to the event”.
* **Event reviews the request**: you approve or reject (optionally with a comment).
* **Everyone gets updates by email** (if notifications are enabled).

{% hint style="info" %}
If stock orders are “not open”, it usually means the stock order configuration has a submission window and it is currently closed.
{% endhint %}

## Order statuses you’ll see

Stock orders move through a simple flow:

* **Not submitted**: the order exists but hasn’t been sent to the event yet.
* **Submitted**: the order has been sent to the event for review.
* **Approved**: your event approved the request.
* **Rejected**: your event rejected the request (usually with a reason).

## Assignments (who gets what)

Assignments let the form responsible decide **who will pick up the ordered items**.

Common examples:

* Assign to specific **visitors** (people)
* Assign to **vehicles**

## Notifications (submission + decision)

If notifications are enabled, emails are sent:

* to your event team when orders are submitted
* to the form responsible when you approve or reject an order


---

# Agent Instructions: 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:

```
GET https://docs.eventication.com/event/stock/orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.