Overview

Amazon is updating the Selling Partner API (SP‑API) Orders v0 so that the buyerName attribute returned by the getOrderAddress operation will no longer be guaranteed. The change takes effect on June 24 2025 and applies to every Amazon marketplace. Sellers and developers who rely on the field must adjust their code to handle a possible null value, or risk processing failures.

Key Points

• Field status shifts to optional — After the enforcement date, buyerName may be omitted from the address payload, mirroring the behavior already observed in live responses.
• Global reach — The modification impacts all Amazon marketplaces, from the United States and Canada to Germany, Japan, and Australia.
• No new data added — Amazon is only aligning the schema with existing production output; no additional fields or functionality are introduced.
• Compliance window — Developers have roughly twelve months to locate every reference to buyerName and implement safe‑guard logic before the deadline.
• Potential downstream effects — Systems that generate shipping labels, send order confirmations, or store buyer details in databases may encounter null‑pointer errors if they continue to assume the name is always present.

What's Changing

1. Specification update — The official OpenAPI definition for getOrderAddress will mark buyerName as a nullable string. For example, a response for order #112‑233‑4455 might now look like { "addressLine1": "123 Main St", "city": "Seattle", "buyerName": null }.
2. Runtime behavior stays the same — Amazon’s backend already omits the name for certain privacy‑sensitive orders; the change simply makes that outcome documented. A seller who previously received { "buyerName": "Jane Doe" } for a domestic order may now receive { "buyerName": null } for an international order where the buyer opted out of sharing personal details.