Daily product-level details on completed customer orders, including purchase price, quantity, tracking, and shipping information. The following report types are included:
GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL
GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_SALES_DATA
GET_AFN_INVENTORY_DATA
This results in a collection of datasets in a destination:
sp_fba_afn_inventory
sp_fba_customer_shipment_sales
sp_fba_fulfilled_shipments
Amazon Fulfillment connector leverages the Amazon Reporting API for the above report types. This API provides preset, Amazon-defined FBA business reports. See Amazon's docs for more details on the various report types below.
Frequency
While the FBA Fulfillment reports are considered near-real time, API limits precluded requesting more frequently than daily. However, understanding report behavior can provide context:
Settlement Window: Data in these reports is not "settled" immediately. Amazon continuously updates prior reporting periods as new information becomes available. This means that reports are not complete when first generated, and data continues to evolve over time.
Date Behavior: When requesting a report for a specific date range (e.g., 5/17 to 5/17), Amazon may include records with reporting dates outside that range (e.g., 5/18 data). This is by design and reflects how Amazon's settlement process works. This means a report output is not limited to the reporting date set in a request. This is true in the UI and the API alike.
Back-Dating Updates: Amazon back-updates prior dates as new information becomes available. For example, a report requested on 8/1 will return the current state of the data, but requesting the same report on 8/4 for 8/1 may show additional fulfillment records that have been settled after the initial request. This means a report you downloaded in the UI on 8/2 for the 8/1 report date will have different data if you request the 8/12 report again on 8/4
Request vs. Reporting Date: The ob_date reflects when the report was requested, while reporting_date reflects when Amazon attached a record to the report. These can differ significantly, which explains why data appears to shift across dates.
To handle this dynamic nature, we implement a comprehensive lookback strategy to ensure data completeness (see Lookbacks section).
Lookbacks
Trailing fulfillment records may appear later for a prior reporting period. For example, on 8/1, a request is made for the fulfillment report. The data is returned. However, on 8/3, if a request is made for 8/1 again, additional fulfillment records will be updated at Amazon for the 8/1 date. As a result, we use a -1, -2, -7, and -30 look back to care for this behavior.