How are you storing and organizing Amazon MWS data in my target data destination?

This doc details the source tables and views that are created. We always suggest using the views for analytics as they are the parents and the source tables are children.

Note: If you need to, you can export a schema for any views or tables in your data destination.

What are the differences between the different order, returns, FBA...feeds?

In terms of what collection of data each feed reflects, we suggest looking at the Amazon docs. Amazon provides the most current description of these data feeds:

For example, here is what Amazon says different order feeds:

  • orders by last update is "all orders updated in the specified period"
  • orders is "all orders that were placed in the specified period"

orders by last update may have an older order that had some update applied to it.

This means an order from last month may show up on recent orders by last update feeds because it had an update.

orders are just orders on specific to the date an order was placed.

Do you have published schemas for the Amazon MWS data?

Detailed table schemas are defined by Amazon. If we detect a change we version the source tables and views that we store in your data destination. Asa result, we suggest checking the Amazon documentation for the latest information on the data feeds.

Amazon "generally" keeps their schemas up to date:

How do I JOIN data across tables and views?

You have a number of options for JOIN though each will depend on your query objective. In some cases, it might be ASIN or SKU if you are trying to understand product level transactions or trends. It might be a DATE if you are trying to explore behaviors within a specific time period.

Ultimately, your query would be a function of the types of questions you are asking of the data. If you are looking for help with modeling the data to optimize for analytic efforts, reach out to our professional services team.

Do you sync all the account history?

No, currently we do not sync all history. Largely, this is due to limits within the Amazon API on the number of times their service can be called. We sync a limited subset of data feeds for thirteen months of historical data. For PRO or TEAM plan, customers will custom sync back as far back as Amazon allows.

How long does it take to generate historical data for MWS?

For MWS API data feeds, there are seven feeds that sync approximately thirteen months of historical data.

  1. mws_orders_by_order_date
  2. mws_orders_by_last_update
  3. mws_fba_returns
  4. mws_fba_reimbursements
  5. mws_all_listings
  6. mws_fba_customer_shipment
  7. mws_returns

Amazon places significant limits on the MWS API which is 60 API calls an hour. Completing a typical historical run (1 year) can require over 10,000 API requests. Given the limits, we can generate one day of historical data per hour for all seven feeds. As a result, this equals about 390 hours of processing.

Also, we have to pull daily, go-forward data feeds in addition to historical backfill. There can be up to 30+ daily data feeds, depending on the marketplace, that leverage the same Amazon API limits.

As a result, collecting the historical data listed above can take 16-24 business days depending on API availability, successful responses to all our requests, retries for failures, and so forth.

Can you make the MWS historical backfill processing go faster?

The cadence and timing are set by Amazon API limits, not Openbridge. The Openbridge system is optimized to work within those limits, maximizing available Amazon API capacity. For example, to regenerate close to over 2,700 reports (7 reports, by day, for 390 days), we have to carefully sequence requests to the MWS API to avoid Amazon system throttling, which would slow any requests and responses by Amazon.

How does historical data work for Amazon Advertising?

For Amazon Advertising, we provide a 60-day "lookback" window. This aligns with the attribution window defined by Amazon for advertising data. What this means is we are updating a rolling 60 days from the current date. For example, if today were June 30, we would update every day backward to June 1. This reflects the fact that Amazon will back update previous days with new attribution data.

For more details on Amazon Advertising, see http://docs.openbridge.com/en/articles/4208366-amazon-advertising-attribution-definitions-and-timing

How frequently are you getting data from Amazon MWS?

Currently, we are pulling MWS reporting data once a day. This largely a function of when data is available and the limits Amazon has on how frequently calls to their API can occur. Given we are pulling a broad cross-section of reporting data, making those calls more frequently would cause Amazon to throttle our connection to your account.

Note that the MWS API uses UTC while Amazon internally reconciles data in PST. This can create temporary shifts in data availability. Normally this self-corrects itself within 24-48 hours. For example, there may be a shift due to timezones on Jan 3. However, on Jan 4 or Jan 5, the data for Jan 3 would be "settled". This means any gaps due to timezone variations are reconciled.

How frequently does Amazon update data within its MWS system?

Based on our testing, Amazon does not consistently have data available when we call the MWS API. For example, we may call the API for export "X". Amazon will respond to our request saying there is no data available for "X". We will attempt a series of retries over a number of hours, within API limits, to retrieve "X". As a result, there may be some inconsistency in how Amazon is making data available which limits our ability to collect it on your behalf.

This is why our schedule calls to the reporting API for the prior day's data. For example, on January 2, we will ask Amazon for the January 1 data. If we attempted to call the reporting API on January 2 for January 2 data, the response from Amazon is often empty, partial, or incomplete. As a best practice, calling for the prior day delivers the most consistent and accurate data.

If you need more current data, we do offer an MWS real-time orders data feed. This process occurs hourly and syncs orders as they occur in Amazon to your target data destination.

There is no data in various tables on certain days. Why?

In some cases, Amazon will not return any data because there is no data. For example, if there are no customer returns, Amazon will not return any data for the customer returns data feed. Likewise, if all your listings are inactive, your active listings feed would not contain any data.

Another cause may be some system outage, API errors, or updates at Amazon which can cause delays. In the event of errors like this, we queue our requests for data until we know Amazon can process them.

How do you download the report which contains Amazon Sales Rank? Is there a report that shows sales rank?

Yes, within our current Amazon MWS Advanced Reporting data feeds, there is something called mws_fba_inventory_health. Within this data feed, there is a column called sales_rank. The data feed will contain the sales rank for a product as provided by Amazon.

Which Amazon MWS and Advertising API integrations do you support?

The Openbridge Amazon MWS application offers a ready-to-go, automated, and code-free connectors to your data.

  • Amazon MWS Advanced Reporting — The most complete Amazon MWS API data integration delivers a complete view of your seller operations. Over 50 data feeds for listings, inventory, fees, orders, FBA, returns, and many others
  • Amazon MWS Basic Reporting — Take control of your data by building a Seller reporting and analytics foundation. Our MWS Basic Reporting API connector delivers a core set 7 data feeds
  • Amazon MWS Real-time Orders — Hourly feeds of MWS order data for use in your local ordering system, researching issues, answering customer questions, and using your own fulfillment system (FBM)
  • Amazon MWS Settlements — Settlement reports provide a detailed breakdown of account activity for a given settlement period

Learn more here: https://www.openbridge.com/amazon-mws

Did this answer your question?