> 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/pro/sales.md).

# Sales at a glance

Overview of the "Sales" area in Equipme Pro: manage customers, confirm incoming orders and view invoices to your customers.

**Path:** "Sales"

In the **"Sales"** area you work with everything that happens between you and your customers: you manage your customers, receive new orders and keep track of billing. Whatever you confirm here then continues in [Fulfillment](/pro/fulfillment.md).

## The pages in the "Sales" area

| Page              | What for                                                                                     | Details                                      |
| ----------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------- |
| **"Customers"**   | Customer list, creating and inviting customers, customer details, modules and order approval | [Customer management](/pro/customers.md)     |
| **"Order Inbox"** | Review, confirm or cancel your customers' new order items                                    | [Order Inbox](/pro/sales/order-reception.md) |
| **"Billing"**     | Monthly invoices to your customers with all invoice items                                    | [Billing](/pro/sales/billing.md)             |

Next to **"Order Inbox"**, a number shows how many order items are still waiting for your confirmation.

## Who sees what?

Which pages you see depends on your role (see [Roles](/pro/administration/roles-and-permissions.md)):

* You see **"Customers"** if your role is allowed to read customers, e.g. "Administrator", "Account Manager", "Sales" or "Reseller".
* You see **"Order Inbox"** only with the permission to confirm incoming customer orders. By default, the "Administrator" has it.
* You see **"Billing"** with read access to billing, e.g. as "Administrator" or "Billing reader".

{% hint style="info" %}
With Lite access, the "Sales" area consists only of **"Customers"**. Order Inbox and Billing are not available there. Learn more under [Business models and licenses](/pro/getting-started/business-models.md).
{% endhint %}

## How the pages fit together

1. A customer orders a service from your [portfolio](/pro/portfolio.md) in their customer portal.
2. The order item appears in the **"Order Inbox"** with the status "Ordered". If you have turned on automatic order confirmation for the customer, it is confirmed immediately.
3. After confirmation, the item moves to ["Open positions"](/pro/fulfillment/open-positions.md) and is provisioned.
4. As soon as the service is active, it is included in the customer's monthly **invoice** on their billing day.

## Frequently asked questions

**Why don't I see the "Order Inbox" menu item?**

You don't have the permission to confirm customer orders. An administrator can grant it to you via the [roles](/pro/administration/roles-and-permissions.md).

**Where do I set a customer's orders to be confirmed automatically?**

In the customer details, with the "Automatically confirm orders" switch. See [Customer details](/pro/customers/customer-details.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/pro/sales.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.