# Integration Specifications The Daasity integration for Amazon Vendor Central provides daily insights into sales, traffic, and inventory at the product level ("ASIN"), and provides comprehensive analysis of product performance on Amazon. *** **Availability:** all Enterprise merchants **Refresh Cadence:** daily *** ### **Where to Find This Data** **Dashboards** * Omnichannel Sales Dashboard * Amazon Vendor Central Dashboard **Explores** * Amazon Vendor Central Sales Explore * Amazon Vendor Central Traffic Explore * Amazon Vendor Central Inventory Explore [For more on how to use this data and best practices - see "How to use"](/core-concepts/data-integrations/setup-guides/retail-integrations/amazon-vendor-central/how-to-use.md) *** ## Data Model **Entity Relationship Diagram (ERD)** The integration leverages multiple source tables that are interconnected within Daasity’s data model. The ERD for this integration illustrates how sales, traffic, and inventory data are joined by ASIN and date keys across different reports. Click here to view the ERD for Amazon Vendor Central Integration ## **Source Schemas** These tables are available through the Amazon Vendor Central API, extracted daily. * [Vendor Sales Report](#vendor-sales-report-report) * [Vendor Traffic Report](#vendor-traffic-report) * [Vendor Inventory Report](#vendor-inventory-report) ### **Vendor Sales Report** Sales, COGS, and return metrics by product ASIN and date. * Endpoint: [Vendor Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#vendor-retail-analytics-reports) * Update Method: UPSERT * Table Name: \[`amazon_vendor_central.get_vendor_sales_report`] | CSV Column | Database Column | | -------------------------------- | -------------------------------- | | start\_date | start\_date | | asin | asin | | distributor\_view | distributor\_view | | customer\_returns | customer\_returns | | end\_date | end\_date | | ordered\_revenue\_amount | ordered\_revenue\_amount | | ordered\_revenue\_currency\_code | ordered\_revenue\_currency\_code | | ordered\_units | ordered\_units | | report\_run\_date | report\_run\_date | | selling\_program | selling\_program | | shipped\_cogs\_amount | shipped\_cogs\_amount | | shipped\_cogs\_currency\_code | shipped\_cogs\_currency\_code | | shipped\_revenue\_amount | shipped\_revenue\_amount | | shipped\_revenue\_currency\_code | shipped\_revenue\_currency\_code | | shipped\_units | shipped\_units | *** ### **Vendor Traffic Report** Consumer web traffic to product pages at the ASIN and day-level, measuring consumer interest (number of views) and the effectiveness of the product listing (conversion rate of views > transactions). * Endpoint: [Vendor Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#vendor-retail-analytics-reports) * Update Method: UPSERT * Table Name: \[`amazon_vendor_central.get_vendor_traffic_report`] | CSV Column | Database Column | | ----------------- | ----------------- | | start\_date | start\_date | | asin | asin | | end\_date | end\_date | | glance\_views | glance\_views | | report\_run\_date | report\_run\_date | *** ### **Vendor Inventory Report** Provides inventory metrics by product and date, detailing stock levels, aging inventory, lead times, sell-through rates, and unhealthy inventory. The data is organized by ASIN and distributor view. * Endpoint: [Vendor Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#vendor-retail-analytics-reports) * Update Method: UPSERT * Table Name: \[`amazon_vendor_central.get_vendor_inventory_report`] | CSV Column | Database Column | | --------------------------------------------------------------- | --------------------------------------------------------------- | | start\_date | start\_date | | asin | asin | | distributor\_view | distributor\_view | | selling\_program | selling\_program | | aged\_90\_plus\_days\_sellable\_inventory\_cost\_amount | aged\_90\_plus\_days\_sellable\_inventory\_cost\_amount | | aged\_90\_plus\_days\_sellable\_inventory\_cost\_currency\_code | aged\_90\_plus\_days\_sellable\_inventory\_cost\_currency\_code | | aged\_90\_plus\_days\_sellable\_inventory\_units | aged\_90\_plus\_days\_sellable\_inventory\_units | | average\_vendor\_lead\_time\_days | average\_vendor\_lead\_time\_days | | end\_date | end\_date | | net\_received\_inventory\_cost\_amount | net\_received\_inventory\_cost\_amount | | net\_received\_inventory\_cost\_currency\_code | net\_received\_inventory\_cost\_currency\_code | | net\_received\_inventory\_units | net\_received\_inventory\_units | | open\_purchase\_order\_units | open\_purchase\_order\_units | | procurable\_product\_out\_of\_stock\_rate | procurable\_product\_out\_of\_stock\_rate | | report\_run\_date | report\_run\_date | | sell\_through\_rate | sell\_through\_rate | | sellable\_on\_hand\_inventory\_cost\_amount | sellable\_on\_hand\_inventory\_cost\_amount | | sellable\_on\_hand\_inventory\_cost\_currency\_code | sellable\_on\_hand\_inventory\_cost\_currency\_code | | sellable\_on\_hand\_inventory\_units | sellable\_on\_hand\_inventory\_units | | unfilled\_customer\_ordered\_units | unfilled\_customer\_ordered\_units | | unhealthy\_inventory\_cost\_amount | unhealthy\_inventory\_cost\_amount | | unhealthy\_inventory\_cost\_currency\_code | unhealthy\_inventory\_cost\_currency\_code | | unhealthy\_inventory\_units | unhealthy\_inventory\_units | | unsellable\_on\_hand\_inventory\_cost\_amount | unsellable\_on\_hand\_inventory\_cost\_amount | | unsellable\_on\_hand\_inventory\_cost\_currency\_code | unsellable\_on\_hand\_inventory\_cost\_currency\_code | | unsellable\_on\_hand\_inventory\_units | unsellable\_on\_hand\_inventory\_units | | vendor\_confirmation\_rate | vendor\_confirmation\_rate | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.daasity.com/core-concepts/data-integrations/setup-guides/retail-integrations/amazon-vendor-central/integration-specifications.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.