Two Minute Reports Logo
Connectors

Amazon Seller

Connect Amazon Seller to Google Sheets or Google Data Studio

The Amazon Seller connector gets your Amazon Seller data into Google Sheets and Google Data Studio. Use it to track your key metrics in a spreadsheet or a Google Data Studio report.

What you can report on

  • Product sales, revenue, and units ordered
  • Order counts, returns, and refunds
  • Order-level product breakdown: units and revenue by SKU or ASIN, taken from your orders
  • Inventory levels and stock health
  • Buy Box win rate and pricing data
  • Traffic, conversion rates, and listing performance

Prerequisites

  • An Amazon Seller Central account
  • Admin access to the marketplace you want to report on

How to create a connection

  1. In the Hub, open Connections & accounts.
  2. Select Create connection.
  3. Select Amazon Seller in the connector list.
  4. Select Next.

  1. In Name the connection, enter a name.
  2. In Seller region, select your region.
  3. Sign in with Amazon. Then allow Two Minute Reports access.

  1. Enable the accounts you want to report on.
  2. Select Done.

Only enabled accounts fetch data, and only enabled accounts count toward your plan. You can enable or disable accounts at any time on the Connections & accounts page.

How to get Amazon Seller data into Google Sheets or Google Data Studio

To get Amazon Seller data into Google Sheets:

  1. In the Two Minute Reports sidebar, open Data Queries.
  2. Select Add.
  3. Select the accounts you want to report on. You can select more than one.
  4. Select your metrics and dimensions.
  5. Select the date range.
  6. Set sorting and filters if you need them.
  7. Select Run query. Two Minute Reports adds the data to your sheet.

ASIN, Child ASIN and SKU

On Amazon, one product can have variations, for example different sizes or colors. Amazon keeps these variations in one variation family. The family has one parent ASIN, and each variation has its own child ASIN.

The Product group has three fields that identify a product. Each field gives different rows:

FieldOne row is
ASINWith Sales and Traffic metrics, one variation family. The field shows the parent ASIN, and Two Minute Reports adds the metrics of all the variations in the family together.
Child ASINOne listing. Each variation has its own row.
SKUOne seller SKU. This is the most detailed level.

If a product has no variations, its parent ASIN and its child ASIN are the same. For this product, ASIN and Child ASIN give the same rows.

The order fields Order ASIN and Order SKU come from your orders. Order ASIN shows the child ASIN of each item in an order, not the parent ASIN.

Inventory data has no parent ASIN. In a query with only Inventory metrics, ASIN and Child ASIN both show the ASIN of each listing.

Data freshness by source

Amazon does not keep all of this data in one source, and the sources do not update at the same speed. Two Minute Reports selects the Amazon source from the fields in your query. Because of this, the fields that you select set how recent your data is.

Fields you selectAmazon sourceHow recent the data is
Sales and Traffic metrics, also when grouped by SKU or ASINSales and traffic business reportOne to three days old. The delay changes by account and by day.
Order fields and metrics, including Order SKU and Order ASINOrdersLess than one hour old. Usually, the data for yesterday is complete.
Inventory metricsFBA inventoryThe current stock only. There is no history, so you cannot group these metrics by a date dimension.
The order data for a day that ended recently can still change a small quantity. Orders with the Pending status continue to arrive after midnight. Also, the time zone of your query sets where the day starts and ends. Because of this, the total for the same day can be different in US/Eastern and in US/Pacific.

Troubleshooting

A query for yesterday is empty

Your query can show units by SKU or ASIN, with a metric such as Total units. These fields come from the sales and traffic business report. Amazon publishes this report one to three days late. Because of this, a query for yesterday can be empty, also when you had orders on that day.

To get the data for the most recent day, use the order fields:

  1. Replace Total units with Order quantity.
  2. Replace SKU or ASIN with Order SKU or Order ASIN.
  3. Run the query again.

The order fields come from your orders, which are less than one hour old. They do not give traffic or conversion data. For that data, keep Total units by SKU or ASIN, and use a date range that ends three or more days before today. See Data freshness by source.

Order quantity is different from Seller Central or other tools

Order quantity by Order SKU or Order ASIN can be different from the units that Seller Central or other seller tools show for the same day. Usually, one of these items is the cause:

  • Order status. Order quantity adds the units of your orders of all statuses, also orders that are still pending. Cancelled orders show in your query, but with 0 units. Because of this, a tool that does not count pending orders shows fewer units. A tool that counts the units of cancelled orders shows more units. To see the units for each status, add Order status to your query.
  • Time zone. The time zone of your query sets where each day starts and ends. To get the same days, select the same time zone as the tool that you compare with. For example, if the tool shows Pacific time, select America/Los Angeles. For Amazon Seller, Provider Timezone uses UTC.
  • Sales channel. Order quantity includes the orders of all the sales channels in your Amazon orders. This includes orders that Amazon fulfilled for a different store, for example Multi-Channel Fulfillment orders. These orders show with a Sales channel such as Non-Amazon or Non-Amazon US. To see the units for each channel, add Sales channel to your query. To keep only one marketplace, add a filter on Sales channel.
  • Orders that come late. Amazon continues to add orders to a day after the day ends. So the total for yesterday can go up a little. Run the query again some hours later.
  • A different Amazon source. The business reports in Seller Central use the sales and traffic business report, not your orders. To compare with a business report, use Total units, with a date range that ends three or more days before today. To compare row by row with the report by child item, group by Child ASIN, not ASIN. With Sales metrics, ASIN shows the parent ASIN. You cannot add Order status or Sales channel to this query.
  • Parent ASIN. Order ASIN shows the child ASIN. A tool that shows the parent ASIN adds the units of all the variations in one row. See ASIN, Child ASIN and SKU.

To find the cause:

  1. Set the date range of your query to one day.
  2. Add a filter on Order SKU for one SKU.
  3. Add Order status and Sales channel to your query.
  4. Run the query.
  5. Compare each row with the number that the other tool shows.

If no row explains the difference, contact [email protected]. Send the day, the Order SKU, the time zone of your query and the number that the other tool shows.

You cannot use Sales fields with Order or Inventory fields

Sales fields come from a different Amazon source than Order fields and Inventory metrics. If you select Sales fields together with Order fields or Inventory metrics, an error shows. For example:

Cannot use Metric group 'Sales' along with Dimension group 'Order'

In Google Sheets, you cannot run the query until you remove one of the two groups. In a Hub dashboard, you cannot save the widget. If you need the data from the two groups, make one query for each group.

A report shows fewer ASINs than you have listings

With Sales and Traffic metrics, such as Sessions, Page views or Total units, the ASIN field shows the parent ASIN. All the variations of a product are in one row, and their metrics are added together. Because of this, your report can have fewer rows than you have listings.

To get one row for each listing, replace ASIN with Child ASIN. See ASIN, Child ASIN and SKU.

Products with sessions but no orders do not show

At SKU level, Amazon gives a row only for a SKU that had one or more units ordered. A SKU that had sessions or page views, but no orders, does not show. No option in your query or in Amazon changes this.

This applies to these queries:

  • A Metrics & Dimensions query with Sales or Traffic metrics by SKU, ASIN or Child ASIN. In the Hub, this query type has the name Metrics and dimensions.
  • A standard report with a SKU granularity: SKU, Daily - SKU, Weekly - SKU or Monthly - SKU.
  • A standard report with Daily - Child ASIN, for an account with Speedboost.

Because of this, the total of Sessions in these rows can be less than the total in Seller Central.

To get all the child ASINs that had traffic, including the ASINs with no orders, use a standard report with the Child ASIN granularity. The report gives one row for each child ASIN, with the metrics for the full date range. It is the same data as the Detail Page Sales and Traffic By Child Item report in Seller Central, under Reports > Business Reports.

  1. In the sidebar, open Data Queries.
  2. Select Add.
  3. In Name, enter a name for the query.
  4. Select your Amazon Seller accounts.
  5. In Date, select a date range that ends three or more days before today.
  6. In Query Type, select Standard Report.
  7. In Report Type, select Sales & traffic business report.
  8. In Granularity Type, select ASIN.
  9. In ASIN Granularity, select Child ASIN.
  10. Select Run query.

Weekly - Child ASIN and Monthly - Child ASIN also show the ASINs with no orders, with one row for each child ASIN in each week or month. Daily - Child ASIN shows them only for an account without Speedboost.

Amazon publishes traffic data one to three days late. See Data freshness by source.

Copyright © 2026