Migration assurance
Orders API v2026 includedData uppercase
Orders API v2026 includedData uppercase is a real Amazon SP-API troubleshooting query. This page explains the likely cause, how to check code evidence, how to validate the fix, and where API Migration Guard can catch the pattern.
- Target keyword: Orders API v2026 includedData uppercase
- Removed: includedData enum serialization
- Replacement: send exact uppercase includedData values such as BUYER, RECIPIENT, PROCEEDS and PACKAGES
- Removal date: March 27, 2027
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| includedData enum serialization | March 27, 2027 | send exact uppercase includedData values such as BUYER, RECIPIENT, PROCEEDS and PACKAGES | Lowercase includedData values can cause missing buyer, recipient, proceeds or package data while the migration appears code-complete. | AMZ-ORD-INCLUDED-DATA-001 |
Official status
Amazon documentation lists includedData enum serialization 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. |
Quick answer
Orders API v2026 includedData uppercase usually means includedData is treated as a free-form string and the integration sends lowercase or legacy aliases. The fastest check is: Log the final URL/query/body sent to Amazon and inspect includedData casing.
| Symptom | Fast check | Likely owner |
|---|---|---|
| includedData is treated as a free-form string and the integration sends lowercase or legacy aliases. | Log the final URL/query/body sent to Amazon and inspect includedData casing. | API/platform owner plus finance, orders or support reviewer as applicable. |
Why this happens
This troubleshooting page is tied to includedData enum serialization, not a generic SP-API failure.
| Cause | What to verify |
|---|---|
| Cause 1 | The code accepts buyerInfo, recipientAddress or mixed-case enum values. |
| Cause 2 | Generated clients or validation schemas do not constrain includedData values. |
| Cause 3 | Search and getOrder requests use different casing rules. |
| Cause 4 | The app reports missing data as redaction without inspecting the request. |
How to detect it in your code
Search the source, scheduled jobs, generated clients, report configuration and sample fixtures before assuming the issue is only live data.
const includedData = ['BUYER', 'RECIPIENT', 'PROCEEDS', 'PACKAGES'];
assert(includedData.every(v => v === v.toUpperCase()));Fix checklist
- Centralize includedData values in an enum or constant list.
- Reject lowercase aliases at the API boundary.
- Test getOrder and searchOrders serialization.
- Validate one buyer, recipient, proceeds and package sample.
- Document legitimate redaction separately from request-casing bugs.
- Re-scan source for lowercase includedData strings.
Migration risk
Lowercase includedData values can cause missing buyer, recipient, proceeds or package data while the migration appears code-complete.
| Production surface | Risk if ignored |
|---|---|
| Accounting/order/support workflow | Lowercase includedData values can cause missing buyer, recipient, proceeds or package data while the migration appears code-complete. |
| Release gate | The migration can look complete while the runtime job still fails or silently loses data. |
| Audit evidence | Without a preserved sample, reviewers cannot distinguish an accepted limitation from a migration bug. |
How API Migration Guard checks it
API Migration Guard scans for exact operation names, report type constants, endpoint strings, query parameters, parser assumptions and token/window loops. Paid reports add file-level findings, remediation notes, sample validation steps, CSV/JSON/SARIF exports and an evidence package.
| Rule | Evidence | Validation |
|---|---|---|
| AMZ-ORD-INCLUDED-DATA-001 | includedData enum serialization | Re-scan source for lowercase includedData strings. |
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| includedData enum serialization | send exact uppercase includedData values such as BUYER, RECIPIENT, PROCEEDS and PACKAGES | March 27, 2027 | Lowercase includedData values can cause missing buyer, recipient, proceeds or package data while the migration appears code-complete. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Runtime or source evidence points at includedData enum serialization. |
| Payload or schema | includedData is treated as a free-form string and the integration sends lowercase or legacy aliases. |
| Permission or data access | The code accepts buyerInfo, recipientAddress or mixed-case enum values. |
| Pagination, status or field mapping | The app reports missing data as redaction without inspecting the request. |
Before/after example
The example is intentionally small so the migration shape is visible in a code review.
Before:
const includedData = ['BUYER', 'RECIPIENT', 'PROCEEDS', 'PACKAGES'];
assert(includedData.every(v => v === v.toUpperCase()));
After:
// Fix path: send exact uppercase includedData values such as BUYER, RECIPIENT, PROCEEDS and PACKAGES
// Validate with API Migration Guard, sample evidence and a re-scan.Scanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-ORD-INCLUDED-DATA-001 | HIGH for runtime error evidence; BLOCKER when tied to removed resources | includedData enum serialization | Documentation, comments, generated clients or test fixtures can require manual review. | Centralize includedData values in an enum or constant list. |
Migration checklist
- Centralize includedData values in an enum or constant list.
- Reject lowercase aliases at the API boundary.
- Test getOrder and searchOrders serialization.
- Validate one buyer, recipient, proceeds and package sample.
- Document legitimate redaction separately from request-casing bugs.
- Re-scan source for lowercase includedData strings.
Common mistakes
- Treating Orders API v2026 includedData uppercase as a transient Amazon outage before checking the request shape.
- Changing code without preserving a sample request, response and report evidence.
- Closing the ticket without re-scanning source and validating the affected sample.
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
How do I fix Orders API v2026 includedData uppercase?
Confirm the request evidence, apply the send exact uppercase includedData values such as BUYER, RECIPIENT, PROCEEDS and PACKAGES path, validate the sample and re-scan.
Can API Migration Guard detect Orders API v2026 includedData uppercase?
It detects source patterns related to AMZ-ORD-INCLUDED-DATA-001 and shows evidence, remediation notes and validation steps.
Does the free scan call Amazon?
No. It scans uploaded or pasted source statically and can validate pasted samples without Amazon credentials.
When should this become a paid report?
When the free scan finds matching production evidence and the team needs file-level findings, SARIF, CSV or handoff artifacts.
Official sources
Validate Orders API v2026 includedData uppercase in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.