> 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/dokumentation/offer-management.md).

# Offer management

Offer management: offer your own services, manage suppliers, process internal orders and maintain templates.

In the **"Offer management"** menu, you build your **own internal company offering** and manage where your services come from.

| Menu item                                                                           | Content                                                                                                                    |
| ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| [**"Service portfolio"**](/dokumentation/offer-management/service-portfolio.md)     | Create your own services, products, add-ons and categories, e.g. IT services, self-procured hardware, software or training |
| [**"Suppliers"**](/dokumentation/offer-management/suppliers.md)                     | Connected suppliers and offline suppliers you maintain yourself                                                            |
| [**"Order processing"**](/dokumentation/offer-management/order-processing.md)       | Process and complete orders for your own services internally                                                               |
| [**"Template management"**](/dokumentation/offer-management/template-management.md) | Equipment packages for employees, locations and groups                                                                     |

## How does it all fit together?

```
Service portfolio ──► Marketplace ("Internal") ──► Approval ──► Order requests ──► Order processing ──► Inventory
     ▲                                                                              (or offline supplier)
     └── Supplier (optional) per offer
```

1. You create a service in the **service portfolio** and optionally assign each offer to a **supplier**.
2. The service appears in the **Marketplace** marked "Internal" and is requested, approved and ordered like any other.
3. The order lands in **order processing** (without a supplier, i.e. provided internally) or as a separate order with the **offline supplier**.
4. Your team completes the order; the service becomes **"Active"** and appears with its costs in the inventory and in controlling.

**Access:** Portfolio managers and administrators. With **restricted** roles, maintenance or processing can be limited to individual organizational units (see [Responsibilities](/dokumentation/offer-management/service-portfolio.md#responsibilities)).

{% hint style="info" %}
If the module is not enabled for your company, "Service portfolio" shows an information page. Hosted customers contact their provider to have it enabled.
{% endhint %}


---

# 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/dokumentation/offer-management.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.