> 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/getting-started.md).

# What is Equipme Pro?

What Equipme Pro is: the service ERP for providers with multi-tenancy. Basic concepts, how provider, customer and partner interact, and an order's path from portal to invoice.

Equipme Pro is the **service ERP** for providers. It covers the entire path of your services: from the product to the offer for your customers, the order, purchasing and warehousing, all the way to delivery, activation and monthly billing. Your customers order in their customer portal, and you process the orders in Equipme Pro. Both sides see the same status in real time.

## Multi-tenancy: one provider, many customers

equipme is **multi-tenant**. Your company is a separate tenant in Equipme Pro. Every customer you look after is its own, cleanly separated tenant with its own employees, locations, inventory and orders.

* **You as the provider** work in **Equipme Pro**. Here you see all your customers, orders and services.
* **Your customers** work in the **customer portal** (the equipme app). There they order, manage employees and inventory, and approve requests.
* With **"Open customer portal"**, as an authorized provider employee you switch into the portal of a Hosted customer and see it from the customer's perspective, e.g. to help them with setup. Learn more under [Customer details](/pro/customers/customer-details.md).

{% hint style="info" %}
**Your own company is also a customer.** Every provider is automatically created as its own customer as well. In the customer list you can recognize it by the suffix "(Own organization)". Changes made there affect your supplier data.
{% endhint %}

## Provider, customer and partner

| Role                                   | Who is that?                                                                                   | Where do they work?              |
| -------------------------------------- | ---------------------------------------------------------------------------------------------- | -------------------------------- |
| **Provider**                           | You: IT service provider, reseller, lessor or supplier                                         | Equipme Pro                      |
| **Direct customer (Hosted customer)**  | A company you look after as a sub-tenant in a customer portal                                  | Customer portal that you provide |
| **End customer (Standalone customer)** | A company with its own equipme license that has connected with you                             | Its own equipme                  |
| **Partner**                            | Another provider you are connected with via Partner Connect, e.g. as a distributor or reseller | Its own Equipme Pro              |
| **Partner customer**                   | A customer referred to you by a partner                                                        | The partner's customer portal    |

How these relationships differ in business terms and which license you need for them is described in [Business models and licenses](/pro/getting-started/business-models.md).

## The path of an order

1. **Build your portfolio:** You maintain [product master data](/pro/portfolio/products.md) and combine it into services in the [service portfolio](/pro/portfolio/service-portfolio.md).
2. **Offer:** With [offers and prices](/pro/portfolio/offers-and-pricing.md) you define which customer sees which service at which price in the marketplace of their portal.
3. **Order:** The customer orders in the marketplace, after internal approvals if required.
4. **Confirm the order:** The order appears in the [Order Inbox](/pro/sales/order-reception.md). You confirm or reject it. For customers with automatic order confirmation, this step is skipped.
5. **Procure and store:** If needed, you order the goods from your supplier via [order proposals](/pro/procurement/order-proposals.md) and book them in at [goods receipt](/pro/warehouse/receiving.md).
6. **Deliver and activate:** In [Fulfillment](/pro/fulfillment.md) you pick, produce and ship, and activate the service for the customer.
7. **Bill:** Active services appear in [Billing](/pro/sales/billing.md) and are invoiced regularly.

## Roles in your team

You control what your employees may see and do in Equipme Pro through roles. Typical roles are "Administrator", "Account Manager", "Sales", "Reseller", "Portfolio Manager", "Purchasing Manager", "Warehouse Manager" and "Fulfillment Manager". The full overview is under [Roles and permissions](/pro/administration/roles-and-permissions.md).

## Frequently asked questions

**Do I need a separate installation for each customer?**

No. All your customers run as separate tenants in equipme. You create them in Equipme Pro and manage them centrally.

**Does my customer see Equipme Pro?**

No. Your customer works exclusively in their customer portal. Equipme Pro is only for you and your employees.

**Can I offer the customer portal in my own design?**

Yes. You set the logo, colors, title, legal texts and other content under [Customer portal settings](/pro/customers/customer-portal.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/getting-started.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.