> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/sales/order-inbox.md).

# Order Inbox

A customer has ordered something. Before anyone picks a device off a shelf or places an order with a distributor, this is where you look at it.

Order Inbox is that pause. Each entry is one position from an order rather than the order as a whole, so a customer ordering three different things arrives as three entries.

## What the review is for

Three things are worth checking, and only one of them is obvious.

**The price it was ordered at.** The customer bought against a specific offer. If that offer is wrong, this is the last moment before the wrong price becomes a contract.

**Whether the mapping is released.** A position reading Waiting for mapping approval cannot be fulfilled at all, and confirming it does not change that; releasing the mapping does. While the mapping is unreleased you can still change what the service consists of, which is no longer possible once it is released.

**Whether the route is right.** **Change delivery type** switches a position between in-house and dropshipping before it enters fulfillment. When stock or timing makes the usual route the wrong one, changing it here costs nothing.

Confirming releases the position into fulfillment. Rejecting cancels the order.

## Why your inbox may always be empty

Two settings on the customer decide whether orders come through here at all, and they are easy to confuse.

**Grant order authorization** lets the customer place orders through their portal in the first place. With it on, orders arrive here for you to accept or reject.

**Automatically confirm orders** removes that step. The customer gets an order confirmation immediately and the position goes straight into fulfillment without appearing on this page.

Both are set per customer, so you can review orders from a new account while a long-standing one runs untouched. If nothing ever reaches your inbox, the second setting is almost always the reason.

Neither of these has anything to do with approvals inside the customer's own organisation. That is a separate mechanism, configured on their side, and an order only passes through it if they have set one up.

## Not the same as Purchasing, Orders

Two menu items, both about orders, opposite ends of the same chain.

**Order Inbox** holds what customers ordered from you. [Orders](/documentation/purchasing/orders.md) holds what you ordered from your distributors.

## After confirming

The position appears in [Open positions](/documentation/fulfillment/open-positions.md) and takes whichever route its configuration defines. If something has to be bought, it waits at Awaiting purchase and shows up as demand in [Order proposals](/documentation/purchasing/order-proposals.md).


---

# 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://hub.equipme.io/documentation/sales/order-inbox.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.