> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/pricing-and-codes/pricing-setup/item-master.md).

# Item Master

Keep delivery times, weights and dimensions for every item code in one place. Learn which fields Item Master stores and how they feed delivery estimates and Shopify.

**Item Master** is a central repository for item details. An "item" is uniquely defined by a specific code.

**Examples:**

* `SOFA-2SEATER-BED`
* `SOFA-2SEATER-NOBED`
* More detailed: `SOFA-2SEATER-BED/FABRIC-RED74`

Item Master allows an unlimited number of entries, each tailored to your needs.

{% hint style="info" %}
To learn how to import from a CSV file, see [CSV Import Templates - Pricing and Item Master](/pricing-and-codes/pricing-setup/csv-templates.md).
{% endhint %}

***

## What information can be added to Item Master?

The table below lists the fields available in Item Master, with example entries, and whether each field is available in the API and the embed.

{% hint style="info" %}
The values are primarily in metric units, but you can treat them as imperial units. Similarly, delivery days can be treated as hours, weeks or months.
{% endhint %}

| Field                     | Example entry    | API | Embed |
| ------------------------- | ---------------- | --- | ----- |
| **ITEM MASTER CODE**      | SOFA-2SEATER-BED | ✅   | ✅     |
| **DELIVERY TIME \[DAYS]** | 25               | ✅   | ✅     |
| **M3**                    | 0.60             | ✅   | ✅     |
| **COMMERCE ID**           | 42853746589754   | ✅   | ✅     |
| **WIDTH \[CM]**           | 170              | ✅   | ✅     |
| **HEIGHT \[CM]**          | 75               | ✅   | ✅     |
| **DEPTH \[CM]**           | 80               | ✅   | ✅     |
| **WEIGHT \[KG]**          | 85               | ✅   | ✅     |

{% hint style="info" %}
**🆕 Commerce ID** is a new field that supports dynamic product bundles. It stores external e-commerce resource IDs (such as Shopify variant IDs) that can be used to map variants dynamically. Learn how to create bundles and map variants with Shopify in [Shopify Add to Cart Methods](/commerce-and-integrations/shopify/add-to-cart.md).
{% endhint %}

***

## Example use cases

### Delivery information

* The standard UI calculates delivery information in working days when the **Delivery information from Item Master** checkbox is ticked in the product's **Pricing and Codes** tab.
* It takes the longest lead time from the Item Master entries of the configured product and shows it on the configurator's finish screen.

![Configurator finish screen showing the delivery time calculated from Item Master](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2Fdxf1x2CrjuFQ9CmZIMTE%2Fitem-master-article_7xwlmk.png?alt=media)

### Weights

* The configurator always passes weight information to the front end for potential use in custom UIs.
* Weights are also passed to the products created in Shopify. See [Shopify Admin Settings](/commerce-and-integrations/shopify/admin-settings.md).

**Example:** Mimeeq adds weight data to Shopify cart products. It sums the weights of all item codes and attaches the total to the configured product in Shopify.

**Modular products:** in modular configurations, the weights of individual components are combined to calculate the total product weight. For example, the weight of three centre pieces and one corner unit is three times the weight of a centre piece plus the weight of the corner unit.

***

## Upcoming features

Mimeeq is developing custom fields for Item Master to extend dynamic data referencing and consumption. Contact us with feedback or additional use case suggestions.

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CSV Templates</strong></td><td>Download templates to import Item Master data and market cost prices.</td><td><a href="/pricing-and-codes/pricing-setup/csv-templates.md">CSV Templates</a></td></tr><tr><td><strong>Shopify Add to Cart Methods</strong></td><td>Choose how configured products and bundles reach the cart.</td><td><a href="/commerce-and-integrations/shopify/add-to-cart.md">Shopify Add to Cart Methods</a></td></tr><tr><td><strong>Shopify Admin Settings</strong></td><td>Connect your API key, products and cart settings.</td><td><a href="/commerce-and-integrations/shopify/admin-settings.md">Shopify Admin Settings</a></td></tr><tr><td><strong>Pricing Overview</strong></td><td>Set up currencies, markets, price lists and quantity breaks.</td><td><a href="/pricing-and-codes/pricing-setup/pricing-overview.md">Pricing Overview</a></td></tr></tbody></table>


---

# 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://help.mimeeq.com/pricing-and-codes/pricing-setup/item-master.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.