Migration assurance
includedData buyerInfo not working
includedData buyerInfo not working 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: includedData buyerInfo not working
- Removed: includedData buyerInfo request value
- Replacement: use uppercase includedData=BUYER and validate role-gated buyer fields
- Removal date: March 27, 2027
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| includedData buyerInfo request value | March 27, 2027 | use uppercase includedData=BUYER and validate role-gated buyer fields | A casing bug can look like a permissions issue and waste seller authorization review time. | AMZ-ORD-INCLUDED-DATA-001, AMZ-ORD-RDT-001 |
Official status
Amazon documentation lists includedData buyerInfo request value 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
includedData buyerInfo not working usually means the request uses the wrong includedData value or casing, so buyer data is not returned as expected. The fastest check is: Search for buyerInfo, BuyerInfo, buyer_info and lowercase includedData arrays.
| Symptom | Fast check | Likely owner |
|---|---|---|
| the request uses the wrong includedData value or casing, so buyer data is not returned as expected. | Search for buyerInfo, BuyerInfo, buyer_info and lowercase includedData arrays. | API/platform owner plus finance, orders or support reviewer as applicable. |
Why this happens
This troubleshooting page is tied to includedData buyerInfo request value, not a generic SP-API failure.
| Cause | What to verify |
|---|---|
| Cause 1 | The code sends buyerInfo instead of uppercase BUYER. |
| Cause 2 | The SDK wrapper lowercases or transforms includedData values. |
| Cause 3 | BUYER is present but the role/order conditions still redact specific fields. |
| Cause 4 | Tests only assert HTTP 200 and do not inspect the buyer object. |
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.
await getOrder({ orderId, includedData: ['buyerInfo'] });
// Fix: includedData: ['BUYER']Fix checklist
- Replace buyerInfo-style values with uppercase BUYER.
- Add a unit test that rejects lowercase or legacy aliases.
- Validate buyer.buyerEmail and buyer.buyerName against role expectations.
- Check SDK serialization does not lowercase enum values.
- Run payload parity for one eligible and one redacted order.
- Re-scan and close AMZ-ORD-INCLUDED-DATA-001 findings.
Migration risk
A casing bug can look like a permissions issue and waste seller authorization review time.
| Production surface | Risk if ignored |
|---|---|
| Accounting/order/support workflow | A casing bug can look like a permissions issue and waste seller authorization review time. |
| 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, AMZ-ORD-RDT-001 | includedData buyerInfo request value | Re-scan and close AMZ-ORD-INCLUDED-DATA-001 findings. |
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| includedData buyerInfo request value | use uppercase includedData=BUYER and validate role-gated buyer fields | March 27, 2027 | A casing bug can look like a permissions issue and waste seller authorization review time. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Runtime or source evidence points at includedData buyerInfo request value. |
| Payload or schema | the request uses the wrong includedData value or casing, so buyer data is not returned as expected. |
| Permission or data access | The code sends buyerInfo instead of uppercase BUYER. |
| Pagination, status or field mapping | Tests only assert HTTP 200 and do not inspect the buyer object. |
Before/after example
The example is intentionally small so the migration shape is visible in a code review.
Before:
await getOrder({ orderId, includedData: ['buyerInfo'] });
// Fix: includedData: ['BUYER']
After:
// Fix path: use uppercase includedData=BUYER and validate role-gated buyer fields
// 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, AMZ-ORD-RDT-001 | HIGH for runtime error evidence; BLOCKER when tied to removed resources | includedData buyerInfo request value | Documentation, comments, generated clients or test fixtures can require manual review. | Replace buyerInfo-style values with uppercase BUYER. |
Migration checklist
- Replace buyerInfo-style values with uppercase BUYER.
- Add a unit test that rejects lowercase or legacy aliases.
- Validate buyer.buyerEmail and buyer.buyerName against role expectations.
- Check SDK serialization does not lowercase enum values.
- Run payload parity for one eligible and one redacted order.
- Re-scan and close AMZ-ORD-INCLUDED-DATA-001 findings.
Common mistakes
- Treating includedData buyerInfo not working 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 includedData buyerInfo not working?
Confirm the request evidence, apply the use uppercase includedData=BUYER and validate role-gated buyer fields path, validate the sample and re-scan.
Can API Migration Guard detect includedData buyerInfo not working?
It detects source patterns related to AMZ-ORD-INCLUDED-DATA-001, AMZ-ORD-RDT-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 includedData buyerInfo not working in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.