Skip to main content

​
Historical Data and Backfills

Historical availability depends on the Amazon feed and connector used. SourceMedium’s current Orders and Finance connector can request up to 364 days of history. Other Amazon report types can have different lookback limits, so their availability does not guarantee the same history in your order tables. SourceMedium retains history already ingested as the request window moves forward. Missing periods within the connector’s window can be requested again after access is restored. Older missing history requires historical exports or another import path; ask your SourceMedium team to confirm the options for your account. Connected confirms authorization and lets syncing begin. Historical ingestion fills in progressively: order headers, item details, and finance records arrive separately, and reporting depends on those records being available together. Check the dates that have appeared in your dashboard or warehouse to assess progress. If an expected period is missing, contact your SourceMedium team with the marketplace, date range, and report you are comparing.

​
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. SourceMedium adds the most recent ~3 days of orders to your Managed Warehouse order tables from Amazon’s live order feed, before they appear in Amazon’s settled reports. Until an order settles it carries is_pending = TRUE, no revenue, and is_order_sm_valid = FALSE, so dashboards and any query that keeps valid orders leave it out. Count is_pending orders for a pacing read of the newest days. Settled data always takes precedence: as soon as an order settles, its settled values replace the live ones and the usual validity rules apply.
  • 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 adds recent orders to the warehouse as pending rows that dashboards leave out until they settle. 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. Near-real-time rows cover the most recent days only (about 3). Settled order and finance records replace them when they arrive. Longer history comes from the Orders and Finance requests above, not from this live feed.
  • 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 capture these delays, SourceMedium re-reads prior FBA returns reports on a lookback schedule. Amazon can retroactively post updates to older reports, so alongside the current report SourceMedium re-reads the reports from 7 and 35 days earlier. For example, on July 30th it re-reads the FBA returns reports for July 23rd and June 25th and updates any return data Amazon 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.