Skip to main content

Historical Data: Amazon Sales Report

For historical data, we rely on the Amazon Sales report, which provides us with up to 24 months of past order data. However, due to Amazon’s reporting processes, this data is subject to a 2-day delay, as stated in their documentation: “Business Reports will have a lag of 24 hours” before the data becomes available.

Data Freshness: Real-Time vs. Settled Data

Recent Amazon days settle over time rather than landing complete. Order volume firms up first, within a few days, while revenue, refunds, and customer detail keep adjusting for longer. Use the windows in the table below, and treat the most recent days as directional. To keep your most recent Amazon days from looking artificially empty, SourceMedium fills the most recent ~3 days of your Managed Warehouse order tables from Amazon’s live order feed, surfacing recent orders before they appear in Amazon’s settled reports. Settled data always takes precedence: as soon as an order settles, its settled values replace the live ones.
Data ageWhat it’s good for
0-3 daysStill filling in. Order volume firms up over the first 2-3 days; gross revenue lags behind it (the newest 1-2 days can show orders with little or no revenue). Directional only.
4-7 daysGenerally stable enough for operating reads on order volume and gross revenue, such as directional CAC and MER.
8-14 daysConservative operating window for sales reporting.
Month-closeUse for final financial reporting and customer-count-sensitive reporting.
  • Net revenue keeps moving after order volume and gross revenue settle, because Amazon refunds and returns post later than the original order (see FBA Returns below). Shipping, taxes, discounts, and promotions can lag the initial live order view the same way.
  • Customer counts and new-vs-repeat splits settle later than order volume and gross revenue, so customer-level reporting should use a more settled window or your normal month-close period.
  • Order date, shipment date, and settlement date are different timeframes, so the same date range can legitimately differ between Seller Central, live order data, and settled finance reporting.
Do not treat the most recent 1-3 Amazon days as final. The ~3-day live-order buffer keeps recent order tables from looking empty; it is not a guarantee that the data has settled. Order volume is still filling in, and revenue, refunds, shipping, taxes, and discounts settle later than the initial order.
Amazon exposes order and financial data through several surfaces, each with different freshness:
  • Live order data (real-time): Near-real-time order activity, available within hours of purchase. Useful for current operational visibility, but it can change as Amazon updates order status, fulfillment, pricing, item detail, or cancellation state. For the newest orders it may include the order header and some item or amount fields, while pricing, taxes, shipping, promotions, customer identifiers, and cancellation/refund state are still incomplete. Live order data is only available from the date you integrated your Amazon account forward, not for historical periods covered by the Sales report.
  • Settled order reporting: Amazon’s bulk order reports are more complete for order and item detail, but they arrive on a delay (daily for the prior full day), and same-day or prior-day reports can be empty or partial.
  • Finance, settlement, and returns data: Amazon’s finance, settlement, shipping, tax, discount, refund, and return details arrive on their own later schedules. These are better for final financial reporting, but they are not real-time and should not be expected to match the newest live order view.

Amazon Subscribe & Save Classification

Amazon does not provide full subscription lifecycle data through Seller Central, such as subscription IDs, active subscriber status, cancellation dates, or active subscription counts. However, when Amazon provides order-item promotion or program signals that identify Subscribe & Save activity, SourceMedium uses those signals to classify eligible Amazon Seller Central orders and order lines as subscription. This improves subscription-vs-one-time reporting for Amazon, but should still be interpreted as order-level Subscribe & Save classification rather than a complete subscriber lifecycle dataset.

FBA Returns: Delayed Reporting and Lookback Schedule

Amazon’s reporting of FBA (Fulfilled by Amazon) customer returns follows a specific process that introduces additional delays. The FBA return data that Amazon provides reflects returns that have been received at a fulfillment center. This means that a return will not appear in the report until it has been physically received and processed by Amazon, which can take over 30 days from the initial return request date due to Amazon’s 30-day return window. To account for these delays and ensure accurate return data, our data ingestion partner employs a lookback schedule for FBA Returns. While they request the current FBA returns report, Amazon may retroactively post updates to older reports with return information. To capture these updates, they check for changes to prior reports 7 and 35 days from the current date. For example, on July 30th, they request prior FBA return reports for July 23rd and June 25th, updating any return data that Amazon may have backdated.

Amazon Multi-Channel Fulfillment

Orders fulfilled through Amazon’s Multi-Channel Fulfillment program, which allows you to sell products on non-Amazon platforms while utilizing Amazon’s fulfillment services, are classified under the “Amazon Multi-Channel Fulfillment” sales channel.

Amazon Removal Orders

Amazon Removal Orders, which represent instances where products are removed from Amazon’s fulfillment centers, are automatically categorized under the “Excluded” channel with a dedicated sales channel name of “Amazon Removal Order.” This separation ensures that removal orders are clearly distinguished from active sales transactions.