> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/daton/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/ecommerce/amazon-vendor-central/daily-reports.md).

# Daily Reports

Daily Reports populate data on a daily level. We have observed that most Vendor Central Daily Reports can populate data for up to T-7 and that data for T-3 is the most recent data available on the current day.  

You can find the schema of each table [here](https://sarasanalytics0-my.sharepoint.com/:x:/g/personal/sanjna_chilakapati_sarasanalytics_com/EbRguG4YvwRKvczZCri4aOcBmAHM80hRXb4S4sgKLBC84g?e=kYtiRL)

<table><thead><tr><th width="353">Table Name</th><th width="283">Description</th><th>Availability Constraints</th><th>History</th><th>Incremental Data</th></tr></thead><tbody><tr><td>DailyVendorInventoryReportBySourcing</td><td>Inventory and operational health metrics such as sellable on hand units and vendor confirmation rate. Mutually exclusive from inventory reports of weekly and monthly granularities. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>DailyVendorInventoryReportByManufacturing</td><td>Inventory and operational health metrics such as sellable on hand units and vendor confirmation rate. Mutually exclusive from inventory reports of weekly and monthly granularities. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>VendorTrafficReport</td><td>Key retail traffic metrics such as detail page views. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>VendorSalesReportBySourcing</td><td>Key retail sales metrics such as ordered/shipped revenue and units. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>VendorSalesReportByManufacturing</td><td>Key retail sales metrics such as ordered/shipped revenue and units. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>NetPureProductMarginReport</td><td>Data on Amazon's net pure product margins for selling a vendor's items. </td><td>All marketplaces</td><td>1460 days</td><td>D-7 to D-3</td></tr><tr><td>PromotionsPerformanceReport</td><td>Data from promotion campaigns to help vendors optimize their promotions and adjust their advertising strategies. The report includes sales from promotions, the types of discounts that were offered, the discount amounts, and how many items were sold as a result of the promotions.</td><td>All marketplaces</td><td>24 months</td><td>D-1</td></tr><tr><td>MarketBasketAnalysisReport</td><td>Items that are most commonly purchased in combination with the items in the customer's basket (cart) at checkout.</td><td>All marketplaces</td><td>365 days</td><td>D-2</td></tr></tbody></table>


---

# 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://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/ecommerce/amazon-vendor-central/daily-reports.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.