# Amazon FBM Order Reports vs the All Orders Report

Canonical page: https://www.kuudo.com/guides/seller-fbm-orders-reports/

Choose Amazon FBM order reports for shipping data, or All Orders reports for tracking and reconciliation. Know which report carries buyer details.

Author: Thomas Spicer
Updated: Oct 19, 2026

## Summary

When the warehouse needs buyer shipping data, use Seller Central's FBM Order Report or the restricted SP-API report GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING, which needs the Direct to Consumer Shipping (Restricted) role and a Restricted Data Token (RDT). For support and exception queues, request All Orders by last update through the Selling Partner MCP; for finance period cuts, All Orders by order date. Amazon says the All Orders reports are for tracking, not fulfillment: they carry no customer-identifying information and cannot be scheduled.

Amazon FBM order reports serve different jobs. To fulfill Fulfilled by Merchant (FBM) orders, use Seller Central's FBM Order Report or the restricted SP-API report `GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING`, which carry buyer shipping data. For tracking, support, reconciliation, or a finance period cut, have the [Amazon Selling Partner API (SP-API) MCP](/features/amazon-selling-partner-mcp/) request an All Orders report, which carries no customer-identifying information.

| Operator need | Request | Why |
| --- | --- | --- |
| Fulfill seller-fulfilled packages | Seller Central `FBM Order Reports` | Includes buyer information needed to fulfill FBM orders. |
| Fulfill through SP-API | `GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING` | Restricted. Merchant Fulfilled Network (MFN) orders from the previous 60 days, for shipping. |
| Ship only what is still open | `GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING` | Restricted. Only orders not confirmed as shipped, 38-day lookback. |
| Catch changed orders since the last sync | `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL` | All MFN and Fulfillment by Amazon (FBA) orders updated in the period. |
| Cut orders by purchase period | `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL` | All MFN and FBA orders placed in the period. |
| Backfill older placed orders | `GET_FLAT_FILE_ARCHIVED_ORDERS_DATA_BY_ORDER_DATE` | All archived orders placed in the period. |

A typical version of the question: *"We need a daily FBM order file for the warehouse and a support file for changed orders. Can the agent just pull the FBM report through SP-API?"* Yes for the support file. Yes for the warehouse file too, with a condition: the SP-API version is a restricted report, and the connection needs Amazon's restricted shipping role to open it.

[ChatGPT, Claude, Perplexity, Microsoft Copilot, and whatever comes next](/features/ai-clients/) know nothing about your business out of the box. Kuudo gives those same tools **your data**, **your rules**, and **the way your business operates**. The [Selling Partner MCP](/features/amazon-selling-partner-mcp/) requests and retrieves the reports, [Amazon Agent Atlas](/features/agent-atlas/) supplies Amazon's report rules, and your workspace approval policy decides whether a report request waits for you.

## Start with the fulfillment question: Atlas separates the dispatch file from the tracking file

Atlas retrieved Amazon's Seller Central **FBM Order Reports** article and the SP-API **order report type values** reference. Together they sort the reports into two jobs: files that carry buyer shipping data, and files built for tracking.

### The fulfillment files

- **Seller Central FBM Order Report.** A tab-delimited file of seller-fulfilled orders received in the days you select, including cancelled and shipped ones. It includes the buyer information needed to fulfill orders, but not billing address or credit-card information. Professional and Amazon Business sellers only.
- **Manual or scheduled.** Generate it for the past 1, 2, 7, 15, or 30 days, or schedule it. A scheduled report holds only new orders since the last one, and by default runs every 24 hours after 11:00 p.m. Pacific time.
- **SP-API equivalents.** `GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING` holds MFN orders from the previous 60 days and can be requested or scheduled. `GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING` holds only orders not confirmed as shipped.

Seller Central does not generate its FBM report beyond 30 days, and Amazon recommends archiving the daily reports. If that file is your warehouse record, archive it.

### The tracking files

Amazon describes the All Orders reports as order-tracking reports, available in all regions and for all sellers. They return every order regardless of fulfillment channel or shipment status. Amazon says they are intended for tracking, not to drive a seller's fulfillment process, because they do not include customer-identifying information and scheduling is not supported.

They do carry order ID, SKU, ASIN, order and item status, fulfillment channel, quantity, prices, and ship city, state, postal code and country. That is enough for a support or exception queue. It is not a shipping label.

> **The AI is shared. The moat is yours.**
> - **Your judgment, running every time.** Ask a chat for an "FBM orders report" and it may name an endpoint that does not exist, or hand you All Orders for dispatch. Atlas returns the fulfillment and tracking reports as separate sources.
> - **Your account, as it is right now.** A chat cannot see your marketplaces or your fulfillment mix. The Selling Partner MCP reads them through the authorized connection before choosing a report.

## Pull the warehouse file through the Selling Partner MCP only with the restricted role and an RDT

`GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING` is the SP-API route to the dispatch file. Amazon marks it restricted because it contains customer personally identifiable information (PII). Three conditions apply:

1. **The role.** The SP-API application needs the Direct to Consumer Shipping (Restricted) role, which requires passing an additional security review.
2. **The token.** When calling `getReportDocument` for a restricted report type, you must pass a Restricted Data Token (RDT). The Selling Partner MCP exposes `Tokens_createRestrictedDataToken` to request one.
3. **One schedule.** A seller can schedule only one `GET_ORDER_REPORT_DATA_SHIPPING` or `GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING` report at a time. Scheduling a new one cancels the existing schedule.

Confirm your connection holds the restricted role before routing the warehouse file this way. Without it, keep the Seller Central FBM Order Report as the dispatch file and use the MCP for the tracking reports below.

## Request All Orders by last update through the Selling Partner MCP when operations need changed orders

When support asks "what changed since the last sync," request `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL`. Amazon's reference says it contains all orders updated in the specified period, covers MFN and FBA, and returns a tab-delimited flat file. It can only be requested, and the date range is limited to 30 days.

For self-fulfilled orders in a pending state, Amazon notes that item price is not shown. Do not use this report as a pending-order revenue ledger.

It is the right feed for support queues, warehouse exception review, cancellations, shipment-status changes, and systems that reconcile on `last-updated-date`. An older order that is cancelled or ships today appears in today's last-updated report. An order-date report for today's placed orders misses it.

```json
{
  "mcp": "Amazon Selling Partner MCP",
  "tool": "Reports_createReport",
  "arguments": {
    "reportType": "GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL",
    "marketplaceIds": ["ATVPDKIKX0DER"],
    "dataStartTime": "2026-06-21T00:00:00Z",
    "dataEndTime": "2026-06-22T00:00:00Z"
  }
}
```

Start each run where the last completed one ended. `Reports_getReports` filters by report type and processing status, and each report it returns carries its `dataStartTime` and `dataEndTime`. No published Kuudo Skill covers order reports, so save this windowing rule as your team's own [Skill](/features/skills/) rather than retyping it in a prompt.

> **The AI is shared. The moat is yours.**
> - **Your account, as it is right now.** A chat cannot know your last completed report window. The agent can list recent reports through the MCP and request only the missing window.
> - **Your judgment, running every time.** "Order date" can sound like the natural choice. Amazon's reference makes last update the report for orders updated in the period, which is the support question.

## Request All Orders by order date through the Selling Partner MCP when finance needs a period cut

When finance or planning asks "what orders were placed in this period," request `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL`. It contains all orders placed in the specified period, with MFN and FBA rows in a tab-delimited file. Use it for daily sales cuts, month-to-date extracts, reconciliation against BI tables, and date-based audits.

For FBM-only analysis, request the same period cut and filter on the `fulfillment-channel` column afterward. Because the report holds both MFN and FBA orders, one extract serves FBM exception analysis and whole-account reporting.

```json
{
  "mcp": "Amazon Selling Partner MCP",
  "tool": "Reports_createReport",
  "arguments": {
    "reportType": "GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL",
    "marketplaceIds": ["ATVPDKIKX0DER"],
    "dataStartTime": "2026-06-01T00:00:00Z",
    "dataEndTime": "2026-06-22T00:00:00Z"
  }
}
```

For a historical backfill by order date, Amazon's reference lists `GET_FLAT_FILE_ARCHIVED_ORDERS_DATA_BY_ORDER_DATE`, which contains all archived orders placed in the specified period. Keep it as a deliberate backfill path, not the default daily workflow.

> **The AI is shared. The moat is yours.**
> - **Your judgment, running every time.** "Order date" and "last update" are not interchangeable. The report names encode different selection rules, so the wrong one drops the orders you meant to include.
> - **Your call, before anything changes.** `Reports_createReport` is a write tool on the Selling Partner MCP, so your workspace policy may require approval before the request reaches Amazon.

## Let the Selling Partner MCP poll, retrieve, and store the report under your approval policy

Atlas also pulled Amazon's Reports API tutorials for requesting a report, verifying processing, and retrieving a report document. The sequence is mechanical, which is why it belongs to the agent rather than to an operator.

1. Call `Reports_createReport` with `reportType`, `marketplaceIds`, and optional `dataStartTime` / `dataEndTime`. It is a write tool, so it runs under your workspace approval policy.
2. Poll `Reports_getReport` with the returned `reportId` until `processingStatus` is `DONE`, `CANCELLED`, or `FATAL`.
3. When `DONE` returns a `reportDocumentId`, call `Reports_getReportDocument`, with an RDT for a restricted report type.
4. Download the pre-signed `url` within five minutes, when it expires, and decompress when `compressionAlgorithm` is present.
5. Keep encryption at rest. Amazon's retrieve tutorial says unencrypted report content must never be stored on disk, even temporarily.

```json
{
  "mcp": "Amazon Selling Partner MCP",
  "tool": "Reports_getReport",
  "arguments": {
    "reportId": "amzn1.spapi-report.example"
  }
}
```

```json
{
  "mcp": "Amazon Selling Partner MCP",
  "tool": "Reports_getReportDocument",
  "arguments": {
    "reportDocumentId": "amzn1.spdoc.example"
  }
}
```

The terminal states matter. `CANCELLED` means someone cancelled the request before processing, or Amazon found no data to return. `FATAL` might include a `reportDocumentId` whose document explains why processing stopped. `IN_QUEUE` and `IN_PROGRESS` are not terminal, so the agent keeps polling instead of telling the operator the report is missing.

> **The AI is shared. The moat is yours.**
> - **Your call, before anything changes.** A chat cannot poll `getReport` or download the document before the link expires. It leaves the operator with a checklist.
> - **Your judgment, running every time.** Amazon distinguishes queued, in-progress, cancelled, done, and fatal. The agent treats only the last three as the end of processing.

## What happens next: match each order workflow to its report

In production, the [Selling Partner MCP](/features/amazon-selling-partner-mcp/), the [Amazon Ads MCP](/features/amazon-ads-mcp/), your team's [Skills](/features/skills/), and the [Amazon Agent Data Layer](/features/amazon-agent-flow/) sit behind one agent surface. A support request pulls the right SP-API order report, and Agent Flow lands Selling Partner and Amazon Ads data in a lake you own, so downstream teams read the same copy. [Amazon Listing Audit Checklist: Preview Every Patch](/guides/seller-listing-agentic-audit-to-patch/) applies the same approval pattern to listing writes.

For this guide, the narrow action is report selection. A warehouse dispatch workflow needs the Seller Central FBM Order Report, or the restricted SP-API shipping report when the connection holds the role. A support, finance, or reconciliation workflow asks the Selling Partner MCP for the All Orders report that matches its date logic.

*Next in the series: the common pitfalls of reading orders from the SP-API Orders API, one order at a time.*


## Frequently asked questions

### What is an Amazon FBM Orders Report?

Seller Central's FBM Order Report is a tab-delimited file of seller-fulfilled orders received in the days you select, including cancelled and shipped ones. It includes the buyer information needed to fulfill orders, but not billing address or credit-card information, and is available to Professional and Amazon Business sellers.

### Which SP-API report type should I request for FBM orders?

To ship orders, GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING, or GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING for orders not yet confirmed as shipped; both are restricted. To track changed orders, GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL. For orders placed in a period, GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL, then filter on fulfillment-channel, since the All Orders reports carry MFN and FBA rows.

### Why not use the SP-API All Orders report to drive fulfillment?

Amazon says the All Orders reports are intended for order tracking, not to drive a seller's fulfillment process, because they do not include customer-identifying information and scheduling is not supported. They carry ship city, state, postal code and country, but no recipient name or street address.

### How far back can I request the report?

The All Orders tracking reports are limited to a 30-day date range, though the start date can be any date. GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING contains orders from the previous 60 days. Seller Central's FBM Order Report can be generated for the past 1, 2, 7, 15, or 30 days, and Amazon recommends archiving the daily reports.

### Do I need a restricted role or an RDT?

Not for the All Orders reports, which need any one of several roles, including Inventory and Order Tracking. The FBM shipping and unshipped order reports need the Direct to Consumer Shipping (Restricted) role, which requires an additional security review, and you must pass an RDT when calling getReportDocument for them.

### How does the Selling Partner MCP retrieve the report after createReport?

The agent polls Reports_getReport with the reportId until processingStatus is DONE, CANCELLED, or FATAL. When DONE returns a reportDocumentId, it calls Reports_getReportDocument and downloads the pre-signed URL within its five-minute life, decompressing when compressionAlgorithm is present.

### What should I do if the report request returns a CANCELLED error?

CANCELLED is a terminal report status, not an API error. Amazon cancels a report automatically when there is no data to return, and a request can also be cancelled explicitly before processing starts. Confirm the date range is within the report's limits, the marketplaceIds are correct, and the report type matches the question before retrying.


## Sources

- [Order report type values](https://developer-docs.amazon.com/sp-api/docs/report-type-values-order) — Amazon Selling Partner API Docs

- [Role mappings for report types](https://developer-docs.amazon.com/sp-api/docs/role-mappings-for-types) — Amazon Selling Partner API Docs

- [Reports API tutorial: Request a report](https://developer-docs.amazon.com/sp-api/docs/request-a-report) — Amazon Selling Partner API Docs

- [Reports API tutorial: Verify that report processing is complete](https://developer-docs.amazon.com/sp-api/docs/verify-that-report-processing-is-complete) — Amazon Selling Partner API Docs

- [Reports API tutorial: Retrieve a report](https://developer-docs.amazon.com/sp-api/docs/retrieve-a-report) — Amazon Selling Partner API Docs