> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/integrations-and-data-exchange/imports-exports/imports/sample-import-files/product-catalog.md).

# Product Catalog

How to import product catalog into Open Loyalty using CSV files.

The Product Catalog import lets a client load their product catalog into Open Loyalty from a single CSV file. Open Loyalty is not the source of truth for products - the client's e-commerce/PIM is; the catalog in OL is a copy used for reference and as the data source for SKU-based campaigns. The catalog is populated by this import (there is no manual product CRUD in the admin panel).

**File format:** CSV

### Sample file

{% file src="/files/18lFqvJBoWre7ZZIIX9U" %}

{% code title="products-sample.csv" %}

```csv
action,sku,name,category,brand,unit,unit_base_price,unit_cost,attr_color,attr_size,attr_material,attr_warranty_months
upsert,NOV-1001,Nova Spark 5,Smartphones,Nova,pc,543.89,337.72,black,6.1in,polycarbonate,24
upsert,NOV-1002,Nova Spark 5 Pro,Smartphones,Nova,pc,330.78,203.12,black,6.1in,polycarbonate,24
upsert,NOV-1003,Nova Edge 8,Smartphones,Nova,pc,1015.02,715.79,white,6.1in,polycarbonate,12

```

{% endcode %}

### Import your catalog

1. Download the sample file.
2. Add or update one product per row.
3. Save the file as UTF-8 CSV.
4. Upload it in **Imports & Exports → Imports**.

The first row must contain column names. You can change their order.

### Column reference

<table><thead><tr><th width="198">Column</th><th width="133.34765625">Required</th><th>Use</th></tr></thead><tbody><tr><td><code>sku</code></td><td>Yes</td><td>Unique product identifier.</td></tr><tr><td><code>action</code></td><td>No</td><td>Use <code>upsert</code> to create or update. Use <code>delete</code> to remove.</td></tr><tr><td><code>name</code></td><td>No</td><td>Product name.</td></tr><tr><td><code>category</code></td><td>No</td><td>Product category path.</td></tr><tr><td><code>brand</code></td><td>No</td><td>Product brand.</td></tr><tr><td><code>unit</code></td><td>No</td><td>Unit of measure.</td></tr><tr><td><code>unit_base_price</code></td><td>No</td><td>Product price. Use a dot for decimals.</td></tr><tr><td><code>unit_cost</code></td><td>No</td><td>Product cost. Use a dot for decimals.</td></tr><tr><td><code>attr_&#x3C;name></code></td><td>No</td><td>Custom product attribute, such as <code>attr_color</code>.</td></tr></tbody></table>

Fixed column names are case-insensitive. Custom `attr_` columns are case-sensitive.

Use non-negative prices with up to two decimal places.

{% hint style="warning" %}
**Check your SKUs before uploading.**

A missing SKU column or duplicate SKU rejects the complete file.
{% endhint %}

{% hint style="info" %}
**Importing does not replace your full catalog.**

Products absent from the file remain unchanged. Empty optional cells clear existing values.
{% endhint %}

### If an import fails

Some file issues reject the whole upload. These include a missing header, missing `sku` column, duplicate header, duplicate SKU, or unknown column.

Other issues affect individual rows only. The valid rows still import. Review the import report for invalid SKUs, prices, categories, or actions.

<details>

<summary>Custom attribute rules</summary>

Start every custom column with `attr_`. For example, use `attr_color`.

Attribute names can use letters, numbers, underscores, and hyphens. Each product supports up to 50 attributes.

</details>


---

# 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://help.openloyalty.io/integrations-and-data-exchange/imports-exports/imports/sample-import-files/product-catalog.md?ask=<question>&goal=<endgoal>
```

`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.