> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/getting-started/fast-tutorial/send-out-orders.md).

# Step 7: Generate Orders

With your catalog, channels, and inventory loaded, Mo has everything it needs to tell you what to order.

**Time required:** 5–10 minutes

***

## Ask Mo What to Order

Open a **Mo chat session** and ask:

> *"Based on my current inventory and recent sales, what should I order next?"*

> *"Which SKUs are at risk of stocking out in the next 60 days? Generate draft orders for those."*

> *"Create purchase orders for everything that needs replenishment in the next 90 days."*

Mo will analyse your catalog and stock levels, then generate draft purchase orders for you to review. No suppliers need to be set up first — you can add supplier details to the orders later.

***

## Reviewing and Activating Orders

All Mo-generated orders start in **Draft** status.

1. Go to the **Orders** section in the left nav
2. Review each order — quantities, SKUs, and any supplier details
3. Click **Activate PO** to confirm and move the order to active

For full order management, see [Order Management](/planning-and-execution/orders.md).

***

## While You're in Mo: Ask for a Report

You're already in a Mo chat session — this is the fastest way to get a full picture of your inventory health before those orders go out.

Try these prompts:

> *"Show me which SKUs are at risk of stocking out in the next 60 days."*

> *"Give me a weeks of supply breakdown by product."*

> *"What's my slowest-moving inventory right now?"*

> *"Build me a dashboard showing sales velocity by channel."*

Mo pulls from your live Moselle data and returns a structured report you can refine conversationally or export to CSV. No report builder. No configuration. Just ask.

{% content-ref url="<https://github.com/Moselle-io/moselle-docs/blob/master/mo/key-capabilities/building-reports-with-mo/README.md>" %}
<https://github.com/Moselle-io/moselle-docs/blob/master/mo/key-capabilities/building-reports-with-mo/README.md>
{% endcontent-ref %}

***

## You're Done

You've completed the fast tutorial. Here's where you are:

* ✅ Products loaded in your catalog
* ✅ Channels and inventory configured
* ✅ Purchase orders ready to review
* ✅ Inventory health visible in Mo

**Where to go next:**

{% content-ref url="/pages/zf1JJggt2bvFRz0Q00cz" %}
[Key Capabilities](/mo/key-capabilities.md)
{% endcontent-ref %}

{% content-ref url="/pages/5l1isZUpoJlB9dV2sixp" %}
[Forecasting](/planning-and-execution/forecasting.md)
{% endcontent-ref %}

{% content-ref url="/pages/UmgHhqsyR7iNv67hNlad" %}
[Replenishment](/planning-and-execution/replenishment.md)
{% endcontent-ref %}

{% content-ref url="/pages/zJTX33Agu64EJnWEBenj" %}
[Orders](/planning-and-execution/orders.md)
{% endcontent-ref %}


---

# 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://learn.moselle.io/getting-started/fast-tutorial/send-out-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.