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

# Customer product numbers

> Upload and manage customer-specific product number mappings for accurate product matching.

## Overview

Customer product numbers (CPNs) let you map the product identifiers your customers use to your internal product catalog numbers. When a customer sends an order using their own product codes, Go Autonomous uses these mappings to automatically match them to the correct products in your catalog.

## Why use customer product numbers

Customers often use their own numbering systems for your products. Without CPN mappings, your team would need to manually look up each customer product number during order processing. CPN mappings automate this step, improving accuracy and speed.

## Catalogs and areas

Customer product number catalogs can be uploaded per [area](/knowledge-base/administration/areas). This allows different teams or regions to maintain their own customer-specific mappings.

When Go Autonomous processes a request, it uses the CPN catalog assigned to the request's area. If no catalog exists 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 CPN catalog will use it.
</Tip>

## The Customer Product Catalog page

Navigate to **Administration > Company Settings > Customer Product Catalog** to manage your CPN data. The page shows a list of catalogs, organized by area (or a Default catalog). Each catalog card displays the column mappings:

* **Customer Product Number** — the product code used by the customer.
* **Customer ID** — which customer uses this mapping.
* **Product Number** — your internal product catalog number.

## Upload a catalog

<Steps>
  <Step title="Click Upload Catalog">
    Click the **Upload Catalog** button in the top toolbar.
  </Step>

  <Step title="Select an area">
    Choose which area this catalog applies to (or use the Default area).
  </Step>

  <Step title="Upload a CSV file">
    Select a CSV file containing your customer product number mappings. Configure the delimiter and encoding if needed.
  </Step>

  <Step title="Map columns">
    Map the columns in your CSV to the required fields: Customer Product Number, Customer ID, and Product Number.
  </Step>

  <Step title="Complete upload">
    Finalize the upload. The mappings are immediately available for product matching.
  </Step>
</Steps>

## Review and edit catalog entries

Click any catalog card to open a review drawer showing all entries. From here you can:

* **Search** entries to find specific mappings.
* **Add** new entries manually.
* **Edit** existing entries to correct mappings.
* **Delete** entries that are no longer needed.

## Download catalogs

Select one or more catalogs using the checkboxes and click **Download** to export them as CSV files. This is useful for backup or for editing in a spreadsheet before re-uploading.

## Delete catalogs

* **Single delete** — hover over a catalog card and click the delete icon.
* **Bulk delete** — select multiple catalogs and click **Delete Selected**.

<Warning>
  Deleting a catalog removes all its customer product number mappings. Orders relying on these mappings will no longer auto-match until the catalog is re-uploaded.
</Warning>

## What's next

* [Review and confirm orders in Flow](/knowledge-base/flow/review-and-confirm) to see how product matching works during processing.