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

# Portfolio Management at a glance

Overview of Portfolio Management in Equipme Pro: from product master data through services, options and offers to releasing them for customers and partners.

**Path:** "Portfolio Management"

In Portfolio Management you build what your customers can order in their marketplace. Your portfolio has two levels: the **products** you purchase yourself and the **services** you sell to your customers. With **offers** you define the prices and conditions at which a service is available to which customers or partners.

## The pages in Portfolio Management

| Page                      | What for                                                                      | Details                                                  |
| ------------------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------- |
| **"Service portfolio"**   | Your sellable services, add-ons, basic services, categories and blueprints    | [Service portfolio](/pro/portfolio/service-portfolio.md) |
| **"Product master data"** | Products you source from suppliers, plus your suppliers and manufacturers     | [Product master data](/pro/portfolio/products.md)        |
| **"Partner Connect"**     | Partner directory, partnerships, activating partner offers for your customers | [Partner Connect](/pro/portfolio/partner-connect.md)     |

In addition:

* [Importing products and services](/pro/portfolio/product-import.md): mass import via file, bulk update and import from a connected distributor catalog.
* [Offers and pricing](/pro/portfolio/offers-and-pricing.md): offer types, prices, terms and availability for customers and partners.

## From product to offer in the marketplace

```
Product master data      Service portfolio                   Customers / partners
(purchasing)             (sales)
─────────────────        ─────────────────────────────       ──────────────────────
Product + supplier   ─►  Service                        ─►   Customer's marketplace
Purchase price           ├ Details, context, images           (direct customers, selected
Stock item               ├ Options & variants                 customers, partners)
                         ├ Mapping (bill of materials) ◄─ Products
                         ├ Offers (price, term, customers)
                         └ Add-ons, linked services
```

1. **Maintain product master data:** Create the products you purchase for your services, with supplier and purchase price. Optionally as a stock item.
2. **Create a service:** Create a service in the service portfolio, e.g. "Notebook workstation". Define the category, context (e.g. employee and location), images and description.
3. **Define options:** For configurable services, you define options and variants, e.g. color or storage size.
4. **Define the mapping:** Specify which products from the product master data are needed for an order (bill of materials) and release the mapping. This later controls purchasing, the warehouse and fulfillment.
5. **Create offers:** Define prices, terms and the offer type, and determine which customers see the offer.
6. **Activate:** Only an active service with at least one available offer appears in your customers' marketplace.

{% hint style="warning" %}
Release the mapping of every service, even if the bill of materials stays empty (e.g. for pure services). Without a release, orders remain in fulfillment in the status "Waiting for mapping approval". With a released, empty mapping, the instance is activated directly without purchasing, warehouse or shipping.
{% endhint %}

## Terms

| Term                              | Meaning                                                                                                                                                          |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Product (product master data)** | An item you source from a supplier. Customers don't see it directly.                                                                                             |
| **Service**                       | What your customer orders. Either as a **"Product"** (simple, without options, one offer) or as a **"Service"** (configurable, with options and several offers). |
| **Add-on**                        | An extra that is booked onto another service, e.g. insurance, return or device replacement.                                                                      |
| **Basic service**                 | A service a customer must have before they can order services that depend on it, e.g. a tenant setup before the licenses.                                        |
| **Blueprint**                     | A service template that you provide internally or to your partners. Real services are created from blueprints.                                                   |
| **Offer**                         | Price, term and conditions of a service, tailored to all direct customers, selected customers or partners.                                                       |
| **Partner offer**                 | An offer from another provider that you activate for your customers via Partner Connect.                                                                         |

## Permissions

* Read: "Portfolio Controller" ("Portfolio controllers have read access to the supplier's service offering.")
* Edit: "Portfolio Manager" and "Administrator"
* "Partner Connect": users with read access to partners, e.g. "Administrator"

Details under [Roles](/pro/administration/roles-and-permissions.md).

## What the customer sees

In the marketplace of their customer portal, your customers see the active services with the offers released for them. Product master data, purchase prices and mappings remain invisible to them. See the customer guide, chapter Marketplace.

## Frequently asked questions

**Do I have to create product master data for every service?**

No. You only need product master data if you want to control purchasing, warehouse or shipping via Equipme Pro. You still have to release the service's mapping.

**Why doesn't a customer see my new service?**

Check whether the service is active, whether there is an offer for this customer (e.g. "Offer available to all direct customers") and whether the offer's country restriction and currency match the customer.


---

# 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/portfolio.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.