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

# Product master data

In the product master data you maintain products you source from suppliers: attributes, purchase and selling price, stock items, suppliers, manufacturers and use in service mappings.

**Path:** "Portfolio Management" → "Product master data"

"Manage the products you purchase to provide your services here. You can then use service mapping to define which product is required as a component of a service."

Product master data is your **purchasing side**: notebooks, monitors, licenses, cables, but also production steps such as "Imaging". Your customers don't see these products directly. They order [services](/pro/portfolio/service-portfolio.md), and via a service's mapping you define which products are needed for it. This later results in [order proposals](/pro/procurement/order-proposals.md), reservations in the [warehouse](/pro/warehouse.md) and picking in [fulfillment](/pro/fulfillment.md).

The page has three tabs: **"Products"**, **"Suppliers"** and **"Manufacturers"**.

## "Products" tab

The list shows all products with "Manufacturer part number", "Manufacturer", "EAN", "External ID", "Source", "Name", "Category", "Stock item", "Supplier", "Purchase price", "External offer ID", "Supplier warehouse stock" and "Selling price". Use the export to download the list.

Actions above the list:

| Button                                | Effect                                                                                                   |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **"Add"**                             | Create a new product (see below)                                                                         |
| **"Import"**                          | Import products from a CSV file, see [Importing products and services](/pro/portfolio/product-import.md) |
| **"Create service"**                  | Build **one** service from the selected products. The products form the base bill of materials.          |
| **"*****n*****&#x20;Offer products"** | Create a separate service for **each** selected product                                                  |
| **"Delete"**                          | Delete the selected products                                                                             |

### Creating a product

1. Click **"Add"**. The "Create product" dialog opens with three steps.
2. **"Product details"**:
   * "Name" (required)
   * "Manufacturer": choose from the list or type a new name. New manufacturers are created automatically.
   * "Category" (required), e.g. "Notebook", "Monitor", "License" or "Production step"
   * "Manufacturer part number", "EAN"
   * "Stock item" with "Minimum stock": only visible if you use the warehouse module. Can only be checked once at least one warehouse has been created.
3. **"Attributes"**: Define which values are recorded per device during provisioning, e.g. serial number. There are no attributes for the "Production step" category.
4. **"Default offer"**:
   * "Supplier" (required): choose from the list or type a new name
   * "Purchase price"
   * "External offer ID", e.g. the supplier's item number
   * "Supplier warehouse stock"
5. **"Save"**. The product details open.

## Product details

Clicking a product opens the details with up to four tabs. Use the trash icon next to the name to delete the product.

### "Details" tab

* **"Product details"**: "Name", "Manufacturer", "Category", "Product URL", "EAN", "Manufacturer part number", "External ID", "Stock item" and "Minimum stock", "Description".
* **"Source"**: Only visible if you have connected a distributor catalog under [Integrations](/pro/administration/integrations.md). If you select a source and enter the "External ID", purchasing and sales information is automatically synchronized with the catalog. Use **"Update offers"** to trigger the synchronization manually.
* **"Attributes"**: Add, rename, remove. If values have already been recorded for an attribute in product instances, Equipme Pro asks before deleting, because these values will be lost.
* **"Default procurement & sales"**: "Supplier", "Purchase price", "Selling price", "Supplier warehouse stock", "External offer ID".

{% hint style="info" %}
If a source is set, the offer data comes from the catalog. The purchasing and sales fields are then locked: "The offers are synchronized via an external source. Therefore, no changes can be made."
{% endhint %}

The **"Selling price"** is your recommended price for the product. It is used when you turn on **"Price synchronization"** in a service offer. The service price is then derived from the selling prices of the products in the bill of materials (see [Offers and pricing](/pro/portfolio/offers-and-pricing.md#price-synchronization)).

### "Offers" tab

All purchase offers for the product, i.e. from which "Supplier" you source it at which "Purchase price", with "External offer ID" and "Created on". A product can have several suppliers. The default offer is your preferred source in [Purchasing](/pro/procurement.md).

### "Service mappings" tab

Shows in which services the product is part of a bill of materials, with "Service name", "Type", "Customized for" (customer-specific mappings), "Mapping status" and "Service status". Use the "Only customized" or "not customized" filter to narrow down the list. This way you can see which services are affected before making a change.

### "Active instances" tab

All provisioned instances of this product at your customers. This tab doesn't exist for products in the "Production step" category.

## "Suppliers" and "Manufacturers" tabs

Here you see all suppliers and manufacturers you've used when creating products. New entries are created automatically when you enter a new name in the product dialog.

Clicking one opens the edit dialog with "Name", "Customer number" (your customer number with the supplier), "Contact", "Phone", "Mail", "Address" and "Comment".

Important for suppliers is **"Send automatic order email"**: "When activated, an email is automatically sent to the stored supplier address when an order is created." You customize the template under [Email notifications](/pro/administration/email-notifications.md). You create the orders themselves in [Purchasing](/pro/procurement/purchase-orders.md).

{% hint style="info" %}
These suppliers are your sources in purchasing. They have nothing to do with partners from [Partner Connect](/pro/portfolio/partner-connect.md), nor with the offline suppliers your customers manage themselves in their customer portal.
{% endhint %}

## Creating services from products

### One service from several products

1. Select the products that together make up a service, e.g. notebook, docking station and bag.
2. Click **"Create service"**.
3. In the "Create service" dialog, you go through "Service details", "Product master data" (the bill of materials, prefilled with each selected product once), "Pricing model" and "Images".
4. After saving, the new service opens in the [service portfolio](/pro/portfolio/service-portfolio.md).

### A separate service per product

1. Select the products.
2. Click **"*****n*****&#x20;Offer products"**.
3. In the "Create services from master data products" dialog, you choose the "Category" (you can type a new one directly) and decide:
   * "Activate (offer in the marketplace)"
   * "Enable price synchronization": the price follows the product's selling price.
   * "Offer available to all direct customers"
4. **"Save"**. You receive a message saying how many individual services were created.

## Deleting products

Select the products and click **"Delete"**. The dialog lists all products once more and warns: "If a product is part of a service mapping, it will be removed from it." So check the product's "Service mappings" tab beforehand.

## Frequently asked questions

**Why can't I check "Stock item"?**

There is no warehouse for your company yet. Create one first, see [Warehouse](/pro/warehouse.md).

**How do I create a new supplier?**

When creating a product, simply type the new name in the "Supplier" field. You then add the remaining details in the "Suppliers" tab.

**What's the difference between purchase price and selling price?**

You pay the purchase price to your supplier. The selling price is your recommended price toward customers and serves as the basis for the price synchronization of services. What the customer actually pays is set in the service's [offer](/pro/portfolio/offers-and-pricing.md).

**Can I import products via file?**

Yes, see [Importing products and services](/pro/portfolio/product-import.md#importing-product-master-data).


---

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