> 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/data-integrations/sales-channels/amazon-vendor-central.md).

# Amazon Vendor Central

How to connect Amazon Vendor Central (1P) in Drivepoint, and what data the first sync brings in.

Connect Amazon Vendor Central so Drivepoint can read your first-party (1P) business. Amazon buys your product at wholesale and sells it to shoppers. This is a different connection from Amazon Seller Central, where you are the seller of record.

A brand can have both. Seller Central orders are your own 3P sales. They do not include the units Amazon sold from inventory it bought from you.

## In Vendor Central

A Vendor Central admin for the vendor group signs in to Amazon and approves Drivepoint. Each vendor group is its own connection. If Amazon buys from you under more than one vendor group, connect each group separately.

You do not create keys or tokens. Amazon shows an approval screen during connect.

## In Drivepoint

1. Open Data Sources.
2. Find Amazon Vendor Central. This is not the Amazon Seller Central card.
3. Click Connect.
4. Sign in to Vendor Central and approve access for the vendor group.
5. Return to Drivepoint. The vendor group shows as connected, and the first sync starts.

Connecting Seller Central does not connect Vendor Central, and the other way around.

## What data you get

| Data                    | What it is                                                                            | First sync                                                                       |
| ----------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Vendor sales            | Units and dollars shoppers ordered, and what Amazon shipped. This is 1P sell-through. | Recent published days. Amazon is usually a few days behind.                      |
| Vendor traffic          | Glance views on the Amazon retail offer.                                              | Same days as vendor sales.                                                       |
| Net pure product margin | Amazon's catalog margin on the 1P offer.                                              | Same days as vendor sales.                                                       |
| Purchase orders         | Wholesale orders Amazon placed with you, including line items.                        | Recent orders. These are orders, not confirmed receipts.                         |
| Purchase order status   | Whether those orders are open or closed, and the status of each line.                 | Same orders as the purchase-order pull.                                          |
| Real-time inventory     | Highly available units Amazon is holding, by ASIN and hour.                           | About the last 30 days. Amazon does not serve older hours.                       |
| Retail forecast         | Amazon's weekly unit forecast for the retail offer.                                   | The latest forecast Amazon has published. Amazon does not serve older forecasts. |

Reports in Drivepoint use the last inventory reading of each day. You do not need to add up the hourly copies yourself.

Sales, traffic, and margin keep updating on later syncs. Drivepoint does not request the most recent few days, because Amazon has often not published them yet.

## How 1P and 3P fit together

| Question                                               | Where to look          |
| ------------------------------------------------------ | ---------------------- |
| What did shoppers buy on Amazon's retail offer?        | Vendor sales           |
| What did shoppers buy from our Seller Central account? | Seller Central orders  |
| What did Amazon order from us?                         | Vendor purchase orders |
| What is Amazon holding right now?                      | Real-time inventory    |
| What does Amazon expect to sell?                       | Retail forecast        |

Purchase-order dollars are not shopper sales. Amazon buys ahead of what it sells through.

## Known limitations

* Shipments to Amazon and vendor invoices are not available yet.
* Product titles appear when an ASIN matches one Seller Central product name. Other rows show the ASIN.
* The first inventory sync covers about 30 days, not the full history of the account.
* The forecast is one current snapshot. Later syncs replace it with Amazon's newest forecast.
* Seller Central fees, FBA shipments, and 3P orders stay on the Seller Central connection.

## FAQ

<details>

<summary>We already connected Seller Central. Do we need Vendor Central too?</summary>

Yes, if Amazon buys product from you as a vendor. Seller Central does not show that 1P sell-through.

</details>

<details>

<summary>Why are sales a few days behind?</summary>

Amazon publishes vendor sales, traffic, and margin after the day closes, and the newest days are often not ready. Drivepoint requests through about four days ago.

</details>

<details>

<summary>Why don't I see shipments or invoices?</summary>

Those are not part of this connection yet. Purchase orders, order status, sales, traffic, margin, inventory, and the retail forecast are.

</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 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/data-integrations/sales-channels/amazon-vendor-central.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.