> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Catalog

> Upload and maintain your product catalog to improve extraction accuracy and automate product matching in Flow.

## Overview

Your product catalog is the master list of all products your organisation sells or distributes. It is the primary source of truth for product matching during extraction — when Go Autonomous processes a request, it looks up extracted product numbers against your catalog to auto-populate names, prices, units of measure, and other details.

The better your catalog is maintained, the more accurate and complete your extractions will be.

## How the product catalog improves extraction

A well-maintained catalog enables several powerful features in Flow:

* **Auto-completion** — when editing a product number, the system suggests matches from your catalog as you type.
* **Validation** — extracted values are checked against the catalog. Mismatches are flagged for review.
* **Enrichment** — once a product number matches, related fields (name, price, unit of measure) are auto-populated automatically.

> [!WARNING]
>
> Outdated catalog data can cause incorrect auto-completions and missed validations. Schedule regular catalog updates to keep your data current.

## Catalogs and areas

Product catalogs can be uploaded per [area](https://knowledge.goautonomous.io/knowledge-base/administration/areas.md). This lets different teams or regions work with their own product data — for example, different price lists or product ranges per business unit.

When Go Autonomous processes a request, it uses the catalog assigned to the request's area. If no catalog has been uploaded for that area, it falls back to the **Default** catalog automatically.

> [!TIP]
>
> Always maintain a Default catalog as a fallback. Any area without its own catalog will use the Default.

## The Product Catalog page

Navigate to **Administration > Company Settings > Product Catalog** to manage your catalogs. The page shows one **card per catalog** in a grid layout. Each card displays:

* The **area name** the catalog belongs to. The fallback catalog is labelled **Default**.
* An **emoji or icon** — the area's emoji when set, otherwise a generic package icon.
* A **column-mapping count** — how many columns of the uploaded file are mapped to platform fields (e.g., `12 / 20 columns mapped`). Click the info icon next to the count to open a **column mappings popover** that lists every mapped source column from your file and the platform field it maps to (e.g., `sku → Product Number`). Use this to verify a catalog's mapping without opening the edit drawer.
* A **delta badge** when the catalog has a unique field configured for delta uploads. Hover the badge to see which unique field is used. See [Setting up delta loads](https://knowledge.goautonomous.io/knowledge-base/administration/product-catalogs/delta-loads.md).

Click any card to open the edit drawer for that catalog. Cards for areas you don't have access to are shown in a muted state and can't be opened.

### Find a catalog

Use the toolbar at the top of the page to narrow down what you see:

* **Search** — type in the search field to filter cards by catalog name.
* **Sort** — click the sort icon to switch between **Name A—Z** and **Name Z—A**.

The **Default** catalog always sorts to the top of the grid regardless of the active sort direction, so the fallback is easy to find.

### Select and bulk-manage catalogs

Hover a card to reveal a checkbox in its top-right corner. Tick the checkbox on any card you have access to — you can select as many as you need across the grid.

As soon as at least one card is selected, the toolbar shows a **selection action bar** with:

* **Download** — export each selected catalog as a CSV file. Each area is downloaded as a separate `product-catalog-<area>.csv` file.
* **Delete** — permanently delete the selected catalogs. Deletion is confirmed via a dialog and cannot be undone. Viewers don't see this action.
* **Clear** — deselect everything and hide the action bar.

> [!WARNING]
>
> Bulk delete permanently removes the selected product catalogs. There is no undo — re-uploading the file is the only way to restore them.

## Upload a catalog

**1. Open the Product Catalog page**

Navigate to **Administration > Company Settings > Product Catalog** in the left sidebar under Data.

**2. Prepare your data file**

Format your catalog as a CSV or Excel file with defined column headers. The catalog typically includes: product numbers (SKUs/part numbers), product names, descriptions, pricing, units of measure, and categories.

**3. Select an area**

Choose which area this catalog applies to, or select **Default** to upload a catalog used as the fallback across all areas.

**4. Upload the file**

Click the upload button and select your file. The platform validates the data format and reports any errors before importing.

**5. Map your columns**

The platform auto-maps columns whose headers match a field in your configured field settings — these are marked with a ✨ sparkle indicator. Hover the indicator to see which fields a column will map to (and under which configuration). Review the mappings and adjust any column the platform couldn't match automatically.

**6. Review and confirm**

Review the uploaded data for accuracy. New entries are added and existing entries are updated based on matching product numbers.

## Auto-mapping of columns

When you upload a catalog, the platform inspects each column header and tries to match it to a field defined in your [field settings](https://knowledge.goautonomous.io/knowledge-base/administration/fields-manager). Matches are normalised — case, spaces, and separators are ignored — so headers like `Product Name`, `product_name`, and `productName` all resolve to the same field.

Auto-mapped columns are marked with a sparkle icon (✨) in the column mapping step. Hover the icon to see:

* **Which field** the column maps to (its display name).
* **Which configuration** the field belongs to — useful when the same field ID is reused across multiple field configurations for different areas.

You can override an auto-mapping by selecting a different field from the dropdown, or leave it as-is to accept the suggestion. Columns that don't match anything in your field settings stay unmapped until you map them manually.

> [!TIP]
>
> Standardise your CSV/Excel headers to match the field IDs in your field settings. The closer your headers are to the canonical names, the more columns are auto-mapped — leaving you with fewer manual mappings to review on every upload.

## What's next

* [Configure field settings](https://knowledge.goautonomous.io/knowledge-base/administration/fields-manager)
* [Send vendor requests for quotes](https://knowledge.goautonomous.io/knowledge-base/flow/vendor-quotation.md)
