> 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/using-the-web-app/reports/amazon-reports.md).

# Amazon Reports

Find below important information on the Amazon data feeding into Drivepoint.

## New vs. repeat customers

Amazon's order reports do not include a buyer identifier. [How new vs. repeat customers are calculated on Amazon](/using-the-web-app/reports/amazon-reports/new-vs-repeat-customers.md) covers the methodology, including why the last couple of weeks get revised down.

## Explanation of Amazon Seller Fees

**Commission Fees** *(otherwise known as referral fee)*: variable sales fees for the privilege of selling on Amazon.

**Amazon Fulfillment Fees:** variable fees to pay Amazon for fulfilling the product storage and shipment.

**Other Fees:** Everything else that is not grouped within Amazon's Comissions and Fulfillment Fees.

{% hint style="info" %}
Check out [this](https://www.webfx.com/blog/marketing/amazon-seller-fees/) list of an overview of all fees *(although we have not seen the relevance of breaking it out across our customer analysis).* If you do want certain fees to be broken out individually, please submit a request by emailing <support@drivepoint.io>
{% endhint %}

*\***Shipping fees** are netted out in Shipping Income*

**Do you have more questions?** *We're here for you!*

{% content-ref url="/spaces/GWP01Uan8w7wePRkCAQS/pages/JIL9p5hP3IZ9pTXZcuqP" %}
[Contact Us](/help-1/contact-us.md)
{% endcontent-ref %}


---

# 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/using-the-web-app/reports/amazon-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.