getOrderItems replacement: migration guide and scanner checklist

Official status

Amazon documentation lists getOrderItems as in-scope for this migration. Use the official source before code freeze because deadlines and replacement details can change.

Amazon Orders API migration guide Amazon SP-API deprecation schedule

Production Orders validation plan

Orders migrations need same-order parity checks because the v2026 model consolidates data that v0 teams often fetched through separate buyer, address and item calls. Treat each finding as a prompt to validate a captured order before code freeze.

Removed resource and replacement

What breaks

Before/after example

The example is intentionally small so the migration shape is visible in a code review.

Before:
const items = await client.getOrderItems(orderId);

After:
const order = await client.getOrder({ orderId, includedData: ['ITEMS'] });

Scanner detection

Migration checklist

• Confirm the code path is production runtime, not only docs, comments or generated vendor output.
• Replace the legacy operation with the v2026 operation and required includedData.
• Compare same-order v0 and v2026 payloads in the Orders Payload Parity Validator.
• Re-scan and confirm Orders rule IDs are fixed or explicitly accepted as manual risk.

Common mistakes

• Treating includedData as a search filter instead of response data selection.
• Assuming RDT migration alone restores buyer or recipient fields.
• Stopping pagination or mapping enums without comparing representative order payloads.