Amazon Removal Data

Amazon FBA removal reports in DataHawk; removal Order Detail and Removal Shipment Detail, data availability, and table locations.

Your Amazon Removal data is sourced from Amazon FBA Reports, through the Amazon Selling Partner API (SP-API) for registered brands. This page provides an overview of the removal reports available through DataHawk.

Removal Order Detail

Overview

The Amazon Removal Order Detail Report provides a detailed breakdown of inventory removed from Amazon's fulfillment centers, whether it's due to damage, returns, expiration, long-term storage fees, or your own removal requests. It's especially useful for FBA sellers to track what's leaving Amazon's warehouses and why.

Requirements

  • Eligibility: Brand-registered sellers or vendors with Amazon Brand Registry.
  • Access: Must have connected your Seller account to DataHawk.

Data Availability

  • Frequency: Daily
  • Granularity: One row per item in a removal order, uniquely identified by order-id, sku and fnsku
  • Backwards history: 3 years
  • Lookback: Once, at D+30

Data Table

SELLING_PARTNER.FBA_REMOVAL_ORDER_DETAIL

Removal Shipment Detail

Overview

The Removal Shipment Detail Report gives you shipment-level visibility into removal orders, tracking how and when Amazon physically ships your removed inventory back to you (or disposes of it).

Requirements

  • Eligibility: Brand-registered sellers or vendors with Amazon Brand Registry.
  • Access: Must have connected your Seller account to DataHawk.

Data Availability

  • Frequency: Daily
  • Granularity: One row per shipped item in a removal order, uniquely identified by _unique_key (order-id, sku, fnsku, and shipment-date)
  • Backwards history: 3 years
  • Lookback: D+15 and D+30: The dataset is re-fetched at both 15 and 30 days after the initial download to capture late-arriving shipment data.

Data Table

SELLING_PARTNER.FBA_REMOVAL_SHIPMENT_DETAIL

💡

Deduplication note (January 28, 2026). The _unique_key definition was updated after we discovered that shipment_date can change over time, and the dataset was fully refreshed to remove historical duplicates. If you maintain joins or row-count comparisons against snapshots taken before that date, expect row counts to have changed. See the changelog entry.

Sources

On this page