> 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/reviewing-and-moderating-orders.md).

# Reviewing and moderating orders

## Where you can review stock orders

There are two common places where your event team can review stock orders:

### 1) On the list (all forms)

Use this when you want an overview of all stock orders across the full list.

### 2) Inside one form (form-specific)

Use this when you’re handling a specific form and want to see only that form’s orders.

## Status tabs

Stock orders are organized in tabs by status:

* **Submitted**: needs review
* **Approved**
* **Rejected**
* **Not submitted**: draft orders that haven’t been sent to the event yet

## Approving or rejecting an order

When reviewing a submitted order, you can:

* **Approve** (optionally add a comment)
* **Reject** (optionally add a comment / reason)

If notifications are enabled, the form responsible will receive an email when a decision is made.

See: Notifications.

## Bulk approve/reject

You can approve or reject multiple orders at once from the list overview.

{% hint style="info" %}
Bulk actions are useful after you’ve filtered down to “Submitted” orders.
{% endhint %}

## Creating orders as a moderator

Moderators can also create stock orders manually from admin.

{% hint style="warning" %}
Orders created by moderators are automatically approved, and non-moderators may not be able to change orders that moderators created/edited (depending on your configuration).
{% endhint %}

## Assignments in admin

You can view and manage assignments for an order in admin (who will pick up the ordered items).


---

# 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/reviewing-and-moderating-orders.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.