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

# Importing products and services

Create or change products and services in bulk: CSV import for product master data, Excel import and bulk update for the service portfolio, import from a distributor catalog.

**Path:** "Portfolio Management" → "Product master data" → "Import" or "Portfolio Management" → "Service portfolio" → "Import" / "Bulk update"

Instead of creating every product and every service individually, you can import data from files and update your portfolio in one step. Equipme Pro offers several ways to do this:

| Way                                                                     | What for                                                                           | Format        |
| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------- |
| [Importing product master data](#importing-product-master-data)         | Create or update purchase products with supplier and prices                        | CSV           |
| [Importing services](#importing-services-add-ons-and-blueprints)        | Create new services, add-ons or blueprints                                         | Excel (.xlsx) |
| [Import from a distributor catalog](#import-from-a-distributor-catalog) | Create services based on EAN/GTIN or catalog IDs                                   | List of IDs   |
| [Bulk update](#bulk-update-of-the-service-portfolio)                    | Change existing services, offers, options and variants in bulk                     | Excel (.xlsx) |
| [Obtain product information](#obtain-product-information)               | Add names, descriptions, images and features of existing services from the catalog | –             |

## Importing product master data

**Path:** "Portfolio Management" → "Product master data" → "Products" tab → **"Import"**

"Import products by selecting a source and defining the data mapping." The import runs in three steps:

1. **"Source"**: Choose "CSV import" ("Import your data using a .csv file.").
2. **"Connection & assignment"**: Load the file with "Load CSV" and map the columns of your file to the fields. Only "Name" is required. You can download a sample file ("Example file Product master data") here. Mappable fields include "Name", "Category", "Manufacturer", "Manufacturer part number", "EAN", "Description", "External ID", "Is stock item", "Minimum stock", "Supplier", "Purchase price (€)", "External offer ID", "Supplier warehouse stock" and "Sales price (€)".
3. **"Preview"**: Check the records. Double-click a cell to change a value. Use the "Category" selection in the toolbar to set a category for all selected rows at once. Select the rows to be imported and click **"Next"**.

After the import, the "Status" column shows the result for each row.

{% hint style="info" %}

* If the supplier is missing from your file, Equipme Pro automatically enters your own company as the supplier.
* If a product already exists, it is updated ("The product already exists! The product is being updated.").
* If a manufacturer part number is already assigned to another product of the same manufacturer, the row is rejected.
* Products whose offer data is synchronized with a distributor catalog don't receive any new offer information from the file.
  {% endhint %}

## Importing services, add-ons and blueprints

**Path:** "Portfolio Management" → "Service portfolio" → "Services", "Add-ons" or "Blueprints" tab → **"Import"**

The import runs in four steps:

1. **"Action"**: Choose "Create products/services" (or "Create add-ons" or "Create blueprints"). In the "Services" tab, the [import from a distributor catalog](#import-from-a-distributor-catalog) is also available if you have connected a catalog.
2. **"Data mapping"**:
   * **"(Optional) Preselection"**: Choose a category if you only want to import services of one category. The standard features of this category are then automatically included in the sample file.
   * Download the sample file (e.g. "Sample file Service portfolio"), fill it in and upload it with "Load XLSX". The column names should match those of the sample file. Similar column names are mapped automatically.
   * You can take over additional columns as your own features. They don't affect the service's category.
3. **"Preview"**: "Please check that all data has been assigned completely and correctly." Fix errors directly in the table and select the rows you want to import.
4. **"Import"**: A progress bar shows the status. Afterward, you see the result for each row.

Typical fields of the sample file: "Name", "Category", "Context", "Description", "Service description", "EAN", "External ID", "Active", "Offer type", "One-time price", "Monthly price", "Term", "Term extension", "Currency", "Available to all direct customers", "Customers", "Region/country restriction (ISO-2, comma-separated)", "Different invoice issuer", "Display order" and image URLs in three sizes.

{% hint style="warning" %}
If you want to import images, provide a link for **each** size ("Large image URL (min. 1200px)", "Image URL Medium (recommended: 600px)", "Small image URL (recommended: 200px)"). The images must be permanently accessible at the URL.
{% endhint %}

### Customer-specific import

If you start the import from a customer's [customer details](/pro/customers/customer-details.md), it is called "Create new products/services for *customer*". The imported services and offers are then exclusive to this customer.

## Import from a distributor catalog

If you have stored the access data for a connected distributor catalog under [Integrations](/pro/administration/integrations.md), you can take over product data directly from there:

* **When importing in the "Services" tab**: In the "Action" step, choose the catalog's card and, in the next step, enter the identification numbers of the products (EANs/GTINs or catalog IDs). Equipme Pro fetches the product data from the catalog and shows it in the preview.
* **When creating a single service**: In the "Create service" dialog, the "Import product" section appears. Search by "EAN" or "Manufacturer part number" (several values comma-separated) and choose the product from the result. Name, description, EAN, external ID and category are prefilled.
* **In the product master data**: If you set the "Source" and the "External ID" on a product, purchase and selling prices are synchronized automatically (see [Product master data](/pro/portfolio/products.md#details-tab)).

If the access data is missing, Equipme Pro tells you so and offers you "Store access data". The link opens the "Integrations" page in a new tab.

## Bulk update of the service portfolio

**Path:** "Portfolio Management" → "Service portfolio" → "Services" or "Blueprints" tab → **"Bulk update"**

This is how you change many services at once, e.g. a price adjustment:

1. **"Action"**: Choose "Update services" or "Update blueprints".
2. **"Data mapping"**: Click **"Export data"**. You receive an Excel file with your current portfolio. Edit it and upload it again via **"Load XLSX"**.
3. **"Preview"**: Check the changes and select the rows to be updated.
4. **"Import"**: You see the result separately for "Services", "Offers", "Options", "Variants" and "Surcharge for this variant".

{% hint style="info" %}
Columns with the suffix "(Unchangeable)" in their name are ignored when reading in. If you leave price fields for variants empty, the current portfolio price is kept.
{% endhint %}

## Obtain product information

**Path:** "Service portfolio" → select services → "Actions" → **"Obtain product information"** (or in a service's ⋮ menu)

This lets you enrich existing services with data from a connected distributor catalog:

1. **"Select a source"**: the connected catalog.
2. **"Check EANs"**: Matching to the catalog is done via the EAN. You enter missing EANs directly or insert them with "Paste from clipboard". At least one service needs an EAN. For services without a matching catalog entry, the status column shows "No product with the specified EAN could be found."
3. **"Select information"**: Define what is overwritten for all selected services:
   * "Replace product/service names", "Replace EANs", "Replace external IDs"
   * "Replace description", "Replace service description"
   * "Import images", "Apply preview image"
   * "Import features", optionally "Remove all previous features"
4. **"Update"**. If a name from the catalog is too long, you're asked to shorten it ("Abbreviate product names").

## Frequently asked questions

**Which format do I need?**

For product master data a CSV file, for services, add-ons and blueprints an Excel file (.xlsx). The safest way is to start with the respective sample file.

**Can I change add-ons via bulk update?**

No. Bulk update is only available for services and blueprints. Via file, you can only create new add-ons.

**Why doesn't the catalog card appear?**

It only appears in the "Services" tab and only if the catalog's access data is stored under [Integrations](/pro/administration/integrations.md).

**Are imported services shown in the marketplace immediately?**

Only if they are active and have a matching offer. Control this via the "Active" and "Available to all direct customers" columns or afterward in the [service portfolio](/pro/portfolio/service-portfolio.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/portfolio/product-import.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.