Migration assurance
Orders API v2026 no RDT
Orders API v2026 no RDT focuses on migration mapping and reconciliation evidence, not generic API copy. Use it to turn a vague migration into a reviewable test case.
- Target keyword: Orders API v2026 no RDT
- Removed: RDT-specific Orders PII workflow
- Replacement: role-gated includedData PII access
- Removal date: March 27, 2027
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| RDT-specific Orders PII workflow | March 27, 2027 | role-gated includedData PII access | Teams can delete RDT code too early and discover later that roles or includedData are not configured for production sellers. | AMZ-ORD-RDT-001 |
Official status
Amazon documentation lists RDT-specific Orders PII workflow 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.
| Validation area | Production proof to collect |
|---|---|
| includedData | Record which paths require BUYER, RECIPIENT and ITEMS and confirm role approval for each marketplace. |
| Payload parity | Compare one shipped, one unshipped and one cancelled order against the legacy consumer contract. |
| Pagination | Exercise paginationToken with the original search filters and confirm retry behavior for expired tokens. |
| Downstream jobs | Re-run tax, fulfillment, notification and support workflows that consume order fields. |
Mapping table
Orders API v2026 no RDT should be implemented as a small, reviewable mapping table before release.
| Old field or behavior | New field or behavior | Validation rule |
|---|---|---|
| createRestrictedDataToken | not required for Orders v2026 PII access | Remove only after role approval is verified. |
| getOrderBuyerInfo | getOrder/searchOrders includedData=BUYER | Validate buyer fields by role and marketplace. |
| getOrderAddress | getOrder/searchOrders includedData=RECIPIENT | Validate recipient redaction cases. |
Validation scenario
Compare one old RDT-gated buyer/address workflow with one v2026 role-gated workflow and document expected redactions.
| Input evidence | Expected proof |
|---|---|
| Source scan finding | AMZ-ORD-RDT-001 points to the old implementation. |
| Sample data | The migration sample covers the field, status, amount or identifier in this page. |
| Reviewer output | A short reconciliation note explains every accepted delta. |
Parser or reconciliation example
Use this as the shape of the unit test or review snippet; adjust names to your codebase.
await getOrder({ orderId, includedData: ['BUYER', 'RECIPIENT'] });
assertNoTokenApiDependency('orders-pii-flow');Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| RDT-specific Orders PII workflow | role-gated includedData PII access | March 27, 2027 | Teams can delete RDT code too early and discover later that roles or includedData are not configured for production sellers. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Code still assumes RDT-specific Orders PII workflow. |
| Payload or schema | The migration target is role-gated includedData PII access, so shape, naming or grouping changes. |
| Permission or data access | Field visibility, role access or accounting availability can differ by marketplace and workflow. |
| Pagination, status or field mapping | Mapping mistakes can hide under successful HTTP responses unless samples are reconciled. |
Before/after example
The example is intentionally small so the migration shape is visible in a code review.
Before:
// Old assumption
RDT-specific Orders PII workflow
After:
await getOrder({ orderId, includedData: ['BUYER', 'RECIPIENT'] });
assertNoTokenApiDependency('orders-pii-flow');Scanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-ORD-RDT-001 | HIGH when mapping drift affects accounting, PII or order state | RDT-specific Orders PII workflow | Documentation, comments, generated clients or test fixtures can require manual review. | Capture one production-like sample for RDT-specific Orders PII workflow. |
Migration checklist
- Capture one production-like sample for RDT-specific Orders PII workflow.
- Normalize it into role-gated includedData PII access.
- Run the mapping table against the sample and record unmatched fields.
- Reconcile the expected totals, statuses, identifiers or access flags.
- Attach the mapping output to the migration ticket.
- Re-scan source and keep the sample evidence with the release gate.
Common mistakes
- Mapping field names without proving semantic equivalence.
- Using one happy-path sample instead of boundary samples.
- Skipping re-scan after the mapper or parser is patched.
Sample report preview
The public sample report shows the same evidence shape used by paid reports: rule ID, severity, file location, redacted evidence, migration mapping, validation step and quality gate.
FAQ
What should Orders API v2026 no RDT prove?
It should prove that RDT-specific Orders PII workflow maps safely to role-gated includedData PII access for the tested workflow.
What evidence belongs in the ticket?
The source finding, mapping table result, sample input, normalized output and reconciliation note.
Can the page replace production validation?
No. It gives the mapping contract and sample gate; production rollout still needs staged validation.
How does the scanner help?
It flags AMZ-ORD-RDT-001 evidence and links findings to the relevant mapping or validator page.
Official sources
Validate Orders API v2026 no RDT in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.