Amazon Reverses Course: Legacy Feeds API Now Supports GPSR Compliance Attributes
On January 3 2025 Amazon announced that legacy XML and CSV/TSV feeds now accept all GPSR‑required attributes, adding tags such as <ResponsiblePersonAddress> and columns like ManufacturerEmail. This removes the forced migration to the JSON Listings Items API for EU sellers.
Overview
Amazon has reversed its earlier position that would have required sellers using legacy XML or flat‑file feeds to switch to JSON‑based formats for General Product Safety Regulation (GPSR) compliance. The change, announced on January 3 2025, confirms that the older feed types can now accept all GPSR‑required attributes, sparing thousands of EU sellers from a costly integration overhaul.
Key Points
- Legacy feeds now accept GPSR data — The XML schema and CSV/TSV templates have been updated to include every mandatory GPSR field, eliminating the need for a forced migration.
- Announcement date — Amazon published the correction on January 3 2025, clarifying that legacy and newer feed formats are now functionally equivalent for GPSR submissions.
- Full EU marketplace coverage — The update applies to Germany, France, Italy, Spain, the Netherlands, Sweden, Poland, and Belgium, ensuring consistent compliance across all major EU sites.
- Multiple submission options — Sellers may embed GPSR attributes in XML XSD tags, add dedicated columns in flat‑file CSV/TSV uploads, or continue using the Listings Items API with JSON payloads.
- No mandatory code rewrite — Existing integration pipelines that rely on legacy feeds can remain unchanged while still meeting the new safety documentation requirements.
How Legacy Feeds Support GPSR
- Add responsible‑person address in XML — Insert the
<ResponsiblePersonAddress>element with the EU‑based contact’s street, city, and postal code; for example, a French seller adds<ResponsiblePersonAddress>10 Rue Lafayette, 75009 Paris, FR</ResponsiblePersonAddress>. - Populate flat‑file columns for manufacturer info — Include “ManufacturerName”, “ManufacturerAddress”, and “ManufacturerEmail” columns in the CSV; a German seller would fill “Hersteller GmbH”, “Musterstraße 12, 10115 Berlin”, and “[email protected]”.
- Attach compliance documents via file‑type fields — Use the “ComplianceDocURL” column (CSV) or tag (XML) to reference a PDF hosted on a secure server; a Polish seller links .
Analysis & Recommendations
Why This Matters
EU sellers can keep their existing integration pipelines and avoid costly rewrites, yet must update feed templates to include new GPSR fields. Compliance errors will be caught by the same feed‑processing reports, preserving familiar workflows across eight marketplaces.
Key Takeaways
- Announcement made on Jan 3 2025, confirming legacy XML and CSV/TSV feeds now support GPSR data.
- New GPSR fields include <ResponsiblePersonAddress>, ManufacturerName, ManufacturerEmail, ComplianceDocURL, SafetyWarning_EN/DE, BatchNumber, etc.
- The change applies to eight EU marketplaces: DE, FR, IT, ES, NL, SE, PL, and BE.
- No code rewrite is required; sellers only need to add the new columns or tags to existing feed templates.
Recommended Actions
- →Download the updated XML XSD and CSV schema from the Amazon developer portal and add the new GPSR columns (e.g., ResponsiblePersonAddress) to your ...
- →In Seller Central, go to Inventory > Add Products via Upload > Download Template, update your flat‑file with the new GPSR columns, and re‑upload.
- →Submit a small test batch to the “Test” feed environment via MWS/Sp API to verify that Amazon accepts the new attributes before full rollout.
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!