> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/neo/guides/what-product-mapping-is.md).

# What product mapping is

Product mapping rolls the same product from every channel and store into one shared catalog.

The same product can have a different name or SKU in each channel and store. Product mapping ties those rows to one product identity. Planning, reporting, and operations then all count the same product the same way.

## Where it lives

Open **Products** in the sidebar. The page shows:

| Count               | What it means                                     |
| ------------------- | ------------------------------------------------- |
| Source product rows | Product rows Drivepoint pulled from your sources. |
| Confirmed           | Rows matched to a product and confirmed.          |
| New since review    | Rows that appeared after the last review.         |
| Kits                | Products made of other products.                  |

{% hint style="info" %}
Not confirmed yet: what a kit means for a customer, beyond the count on the page.
{% endhint %}

## Match statuses

Each source row has one status:

| Status     | What it means                                  |
| ---------- | ---------------------------------------------- |
| Confirmed  | The match is approved.                         |
| AI matched | Drivepoint suggested a match. It needs review. |
| Unmapped   | No match yet.                                  |
| Rejected   | A suggested match was turned down.             |

## How you change a match

Mapping happens in chat. There is no table editor. Choose **Review mappings in chat**, or open chat from one product's row. Changes wait for your explicit approval.

{% hint style="info" %}
Not confirmed yet: what adds a new product row on its own. This page does not say mappings publish themselves.
{% endhint %}

## Next

Map products. That page is not in this preview.


---

# 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://docs.drivepoint.io/neo/guides/what-product-mapping-is.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.
