Migration assurance
Orders API v0 to v2026-01-01 migration
On March 27, 2027 Amazon removes six Orders API v0 operations. The destination is Orders API v2026-01-01, which consolidates multi-call workflows via includedData and changes several parameters and enums.
- Removed operations: getOrders, getOrder, getOrderItems, getOrderBuyerInfo, getOrderAddress, getOrderItemsBuyerInfo
- Replacement: Orders API v2026-01-01 (searchOrders / getOrder with includedData)
- Removal date: March 27, 2027
- Deprecated since: January 28, 2026
Breaking changes
Multi-call PII workflows collapse into includedData=BUYER and includedData=RECIPIENT. OrderStatuses maps to fulfillmentStatuses; MFN/AFN fulfillment codes map to MERCHANT/AMAZON. NextToken becomes a 24-hour paginationToken. A Restricted Data Token is no longer required; PII access is role-gated.
Exact scanner coverage
The scanner flags the six in-scope operations (AMZ-ORD-OPERATION-001), the v0 endpoint (AMZ-ORD-ENDPOINT-001), parameter renames and no-replacement parameters (AMZ-ORD-PARAM-001/002), status and fulfillment remaps (AMZ-ORD-STATUS-001, AMZ-ORD-FULFILL-001), boolean-flag to programs[] moves (AMZ-ORD-PROGRAM-001), RDT workflows (AMZ-ORD-RDT-001) and NextToken pagination (AMZ-ORD-PAGINATION-001). Out-of-scope v0 operations such as confirmShipment are never flagged.
Example finding
BLOCKER AMZ-ORD-OPERATION-001: Deprecated Orders v0 operation getOrderBuyerInfo. Mapping: getOrderBuyerInfo -> getOrder(includedData=BUYER).
Functional parity before staged rollout
Amazon recommends comparing v0 and v2026-01-01 results for the same orders, then rolling out by seller or workload. Static code migration alone cannot establish payload parity.
- Capture v0 and v2026-01-01 payloads for the same representative order IDs.
- Compare required fields, enum meanings, includedData sections and monetary semantics.
- Stage rollout with reconciliation metrics and a rollback boundary.
Query parameters with no direct replacement
These are v0 search parameters, not response attributes. Buyer email remains available in response data through includedData=BUYER, but BuyerEmail is not a v2026 search filter.
| v0 query parameter | v2026-01-01 replacement | Required decision |
|---|---|---|
| PaymentMethods | None | Remove the filter and validate downstream payment assumptions |
| BuyerEmail | None as a query filter | Use includedData=BUYER only for response data |
| ActualFulfillmentSupplySourceId | None | Remove the filter and document the lost selection behavior |
Pricing and tax semantic differences
v2026-01-01 introduces product.price.unitPrice and explicit proceeds/expense breakdowns. Item price can be tax-exclusive when TAX is separate, or tax-inclusive when it is not. Do not compare flat v0 monetary fields by name alone.
| Concept | v0 | v2026-01-01 |
|---|---|---|
| Unit price | Flat item monetary fields | product.price.unitPrice as displayed on Amazon retail |
| Tax treatment | Inclusion could be ambiguous | TAX breakdown is explicit when separated |
| Financial detail | Flat values | PROCEEDS and EXPENSE nested breakdowns |
Sample same-order payload comparison
v0: { AmazonOrderId, OrderStatus: 'Canceled', ItemPrice }
v2026: { orderId, fulfillmentStatus: 'CANCELLED',
orderItems[].product.price.unitPrice,
orderItems[].proceeds.breakdowns[] }
assert: same order identity, required business fields and reconciled totalsFrequently asked questions
When is Orders API v0 removed?
Amazon removes the six in-scope Orders v0 operations on March 27, 2027. They were deprecated on January 28, 2026.
Do I still need a Restricted Data Token?
No. In v2026-01-01, buyer and recipient PII is gated by application roles via includedData, not by an RDT.
Will you flag confirmShipment?
No. Only the six in-scope operations are flagged. Other v0 operations are deliberately left alone.
Official sources
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/orders