Amazon Opens Fulfillment Inbound API to Turkey Marketplace
In late January 2025 Amazon added the Turkish marketplace (tr‑TR) to the SP‑API Fulfillment Inbound endpoints and introduced a new optional districtOrCounty field for source addresses. The change enables create, update, list and track inbound plans for Turkish FBA centers and is supported in the sandbox.
Overview
In late January 2025 Amazon added Turkey to the list of marketplaces that support the Selling Partner API (SP‑API) Fulfillment Inbound endpoints. The change lets sellers and software providers create, update, and track inbound shipments to Turkish fulfillment centers through code instead of manual entry. Sellers targeting Turkey can now embed the same automation they use for North America or Europe, cutting manual effort and improving inventory visibility.
Key Points
- Turkey now on the Fulfillment Inbound API — All inbound‑plan, shipment‑creation, and tracking operations are available for the tr‑TR marketplace, matching the feature set of the US, EU, and JP regions.
- New districtOrCounty field — Source‑address objects now accept a districtOrCounty property (e.g., “Kadıköy” for Istanbul) to satisfy Turkey’s postal hierarchy, preventing address‑validation errors.
- No new authentication flow — Existing SP‑API credentials, IAM roles, and LWA tokens continue to work; developers only need to adjust payload schemas.
- Sandbox support added — The Amazon SP‑API sandbox environment now returns the districtOrCounty field in mock responses, enabling safe testing before production rollout.
- Forward‑compatible schema — The new field is optional; adding it to data models prevents future parsing failures even for integrations that do not yet ship to Turkey.
- Parity with other regions — Turkish sellers gain the same programmatic control over inbound logistics that US, EU, and JP sellers have enjoyed for years, eliminating a long‑standing functional gap.
- Impact on multi‑marketplace tools – Third‑party shipment‑management platforms can expose a single “Create Inbound Plan” UI that now works for Turkish FBA, simplifying onboarding for their customers.
How the Fulfillment Inbound API Changes Work
- Create an inbound plan with a Turkish address — When calling
createInboundPlan, include asourceAddressobject that contains , , and the new (e.g., ). The API returns a plan ID that references a Turkish fulfillment center such as FTZ‑IST‑01.
Analysis & Recommendations
Why This Matters
Developers can now programmatically ship to Turkish fulfillment centers, eliminating manual UI entry and reducing address‑validation rejections. The optional districtOrCounty field improves data accuracy and allows reporting on inventory movement by Turkish district.
Key Takeaways
- Turkey (tr‑TR) is now supported for all Fulfillment Inbound API operations as of January 2025.
- A new optional sourceAddress property districtOrCounty (e.g., "Beşiktaş") is required for Turkish addresses to pass validation.
- Sandbox endpoints now echo the districtOrCounty field, enabling automated testing before production deployment.
Recommended Actions
- →Update your address model to include an optional String field named districtOrCounty and populate it when marketplaceCode = 'tr-TR'.
- →Run a sandbox test: call createInboundPlan for tr‑TR with districtOrCounty set, verify the response includes the field, then promote the change to ...
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!