> 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/ordering-stock-from-memberships.md).

# Ordering stock from a membership

## What this is

Moderators can create stock orders directly from a member's planning profile in the admin. This is in addition to the existing [accreditation form flow](/event/stock/orders/ordering-stock-from-accreditation.md).

## How it works

Navigate to a member's planning profile and open the stock orders section. From there you can create a new stock order on behalf of that member.

Stock orders created by a moderator are **automatically approved** — they do not need to go through the normal submit/review flow.

## Demand chart

From the stock orders overview you can view a **demand chart per stock type** to get an overview of how much of each item is being requested across all memberships.

## Managing orders

Moderators can view, edit, and delete stock orders directly from the membership profile. The same order statuses apply as elsewhere:

* **Not submitted**
* **Submitted**
* **Approved**
* **Rejected**


---

# 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/ordering-stock-from-memberships.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.