> 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/documentation/portfolio-management/service-portfolio/product-master-data/adding-products.md).
# Adding products
There are two ways to get products into your master data: one at a time through a dialog, or in bulk from a file. Which one you want depends less on preference than on how many entries you are dealing with.
***
## Adding a single product
**Add** on the Products tab opens the **Create product** dialog, which walks through three steps.
### Product details
This is where the identity of the product lives. **Name** and **Category** are required. Alongside them you can record the **Manufacturer**, the **Manufacturer part number** and the **EAN**.
The **Stock item** checkbox also sits here, and it is the most consequential field on the page. It determines whether the article runs through your logistics at all: a stock item gets purchased when needed, booked into the warehouse, picked and shipped. An article without the flag skips all of that, which is what you want for a production step or a licence assignment.
### Attributes and Default offer
**Attributes** and **Default offer** follow. The default offer supplies the commercial side of the entry — the supplier and the prices that then appear in the product list, which is why a product created without it looks incomplete in the catalogue.
***
## Importing products
For anything more than a handful of entries, **Import** is the faster route. It runs as a four-step wizard: **Source**, **Connection & assignment**, **Preview**, and finally **Import**.
Source currently means a **CSV file**. In the assignment step you match the columns of your file to the fields in equipme, which is what makes an export from a supplier or from another system usable without reformatting it by hand first. The preview then shows what will be created before anything is written.
Two things make an import go smoothly. Have your suppliers and manufacturers set up beforehand, so the assignment step has something to match against. And include the manufacturer part number in your file — it is the field that keeps near-identical variants apart once they are all in the catalogue.
***
## Products created from a service mapping
There is a third route that does not start here at all. While you are configuring a service mapping, **Add new product** opens the same **Create product** dialog described above, so you can create a missing variant without leaving the mapping.
The result is identical either way: the product lands in your master data catalogue. Creating it mid-mapping saves a detour, nothing more.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hub.equipme.io/documentation/portfolio-management/service-portfolio/product-master-data/adding-products.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
