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

# How to connect

> How to connect the Amazon Vendor Central data source to Adriel: enter Login with Amazon credentials, choose the vendor sales report and marketplaces, and import daily ASIN sales.

Amazon Vendor Central is the portal Amazon uses for first-party (1P) vendors — brands and manufacturers that sell their products wholesale to Amazon, which then resells them to end customers. Connecting it brings daily vendor sales reports into Adriel dashboards — shipped revenue, shipped COGS, shipped units, and customer returns broken down by ASIN.

## Before you connect

The following are required:

* An Amazon Vendor Central account with Selling Partner API (SP-API) access.
* An Amazon developer application configured for SP-API access in the vendor's own Amazon developer account.
* Three credentials from that developer application: a **Refresh Token** (the Login with Amazon token from the consent flow), a **Client ID**, and a **Client Secret**. Vendor Central uses manual credential entry rather than an OAuth pop-up.

To retrieve the Client ID, Client Secret, and Refresh Token from the Amazon developer application:

1. Go to [Amazon Vendor Central](https://vendorcentral.amazon.com) and sign in to the Amazon account.
2. Open **API Integration** > **Develop your Apps** > **LWA Credentials**, then click **View**.
3. Copy the **Client Identifier** (the Client ID) and the **Client Secret**.
4. Open **API Integration** > **Develop your Apps** > **Edit App**, then click **Authorize**.
5. Click **Authorize app** and copy the **Refresh Token** shown on the page. The Refresh Token is viewable only when the app is first authorized or after it is revoked; revoking the app invalidates the previous token.

## Connect Amazon Vendor Central

<Steps>
  <Step title="Authorize the Amazon Vendor Central account">
    On the **Data Sources** page, search for **Amazon Vendor Central** and select it. Enter the three credentials gathered in the previous section — **Refresh Token**, **Client ID**, and **Client Secret**. The credentials are validated by exchanging the refresh token for an access token; the connection is created only if that exchange succeeds.
  </Step>

  <Step title="Configure the data source">
    On the data source settings, fill in the required fields:

    * **Report Name** — a readable name that distinguishes this data source from others.
    * **Report Type** — select from the dropdown. Only **Vendor Sales Report** is currently supported.
    * **Marketplace ID(s)** — select one or more marketplaces from the dropdown.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. Initial data availability can take up to one business day, after which up to 180 days of historical sales are available.
  </Step>
</Steps>

## What gets imported

The connector reads the vendor sales report at ASIN and daily granularity: shipped revenue (from `shippedRevenue.amount`), shipped COGS (from `shippedCogs.amount`), shipped units, and customer returns, plus a cache-layer row count used as a completeness check. ASIN can be used as a breakdown or as a metric, the report date is available as a breakdown, and each row's currency is preserved from the Amazon response.

For the complete list of metrics, breakdowns, refresh cadence, and limits, see the [Amazon Vendor Central data reference](/data-sources/a-f/amazon-vendor-central/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="The most recent 3 days are missing">
    Amazon enforces a 3-day minimum data lag on the vendor sales report — sales for the most recent 3 days are not yet available from the SP-API and appear once Amazon releases them. Rolling "last N days" views should exclude or visibly mark the trailing 3-day window.
  </Accordion>

  <Accordion title="Initial backfill or a large sync is slow">
    The SP-API is rate-limited to 1 request per minute per account. The 180-day initial backfill and large catalog syncs progress gradually as a result; this is Amazon's API limit and is respected by the connector. The sync continues in the background, and once a day is cached its data stays available.
  </Accordion>

  <Accordion title="Credentials are rejected at submit time">
    The most common causes are an expired refresh token (regenerate it through the consent flow), a developer application still in Draft state rather than published, or a Client ID and Client Secret that do not match the application that issued the refresh token.
  </Accordion>

  <Accordion title="Connecting a third-party seller account">
    This connector is for first-party vendor accounts only. Third-party marketplace sellers use Amazon Seller Central, which exposes a different SP-API report surface and requires a separate connector.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Amazon Vendor Central data reference" href="/data-sources/a-f/amazon-vendor-central/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for Amazon Vendor Central.
  </Card>

  <Card title="Amazon Vendor Central FAQs" href="/data-sources/a-f/amazon-vendor-central/faqs">
    Common questions and expected behaviors for the Amazon Vendor Central data source.
  </Card>

  <Card title="How to connect Amazon Seller Central" href="/data-sources/a-f/amazon-seller-central/how-to-connect">
    Connect third-party marketplace seller sales.
  </Card>

  <Card title="How to connect Amazon Ads" href="/data-sources/a-f/amazon-ads/how-to-connect">
    Connect Amazon retail advertising performance.
  </Card>
</CardGroup>