> ## 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.
</Warning>

## Catalogs and areas

Product catalogs can be uploaded per [area](/knowledge-base/administration/areas). 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.
</Tip>

## Upload a catalog

<Steps>
  <Step title="Open the Product Catalog page">
    Navigate to **Administration > Company Settings > Product Catalog** in the left sidebar under Data.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Select an area">
    Choose which area this catalog applies to, or select **Default** to upload a catalog used as the fallback across all areas.
  </Step>

  <Step title="Upload the file">
    Click the upload button and select your file. The platform validates the data format and reports any errors before importing.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Review and confirm">
    Review the uploaded data for accuracy. New entries are added and existing entries are updated based on matching product numbers.
  </Step>
</Steps>

## 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](/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.
</Tip>

## What's next

* [Configure field settings](/knowledge-base/administration/fields-manager)
* [Send vendor requests for quotes](/knowledge-base/flow/vendor-quotation)