Update: Support for GPSR compliance in Listings Items API and JSON Listings Feeds
Amazon expanded the Listings Items API (version 2021‑08‑01) and JSON Listings Feed in early 2024 to include GPSR‑specific fields and allow a PDF certificate in the same request. Sellers have a 30‑day window from the announcement to submit the gpsrCompliance object or risk listing suppression or removal.
Overview
Amazon has expanded the Listings Items API (version 2021‑08‑01) and the JSON Listings Feed to accept safety‑related data required by the EU General Product Safety Regulations (GPSR). The update, rolled out in early 2024, lets sellers attach compliance attributes and the supporting certificates in a single request, helping them keep GPSR‑covered products visible on the marketplace. Prompt adoption is essential because listings that remain non‑compliant after the 30‑day grace period may be hidden or removed.
Key Points
- API & Feed Enhancement — The latest API version and JSON feed now recognize GPSR‑specific fields and allow a PDF document to be uploaded alongside those fields.
- Account Health Visibility — The Account Health console now flags every brand and offer that requires GPSR proof, giving sellers a ready‑made list of at‑risk ASINs.
- One‑Call Document Submission — Sellers can embed a safety certificate, test report, or CE‑mark file directly in the same payload used to update product attributes, removing the need for a separate upload step.
- Version Restriction — Only the 2021‑08‑01 endpoint supports the new GPSR fields; calls to earlier versions will return validation errors.
- Compliance Window — Amazon has set a 30‑day deadline from the announcement; listings that do not meet GPSR requirements after that date risk suppression or deletion.
- Targeted Error Codes — New response codes such as
GPSR_ATTRIBUTE_MISSINGandGPSR_DOCUMENT_INVALIDgive precise guidance on what is wrong, speeding up remediation.
How GPSR Support Works
- Locate Affected Items — Open the Account Health page, apply the “GPSR compliance required” filter, and record the ASINs, brand names, and SKU identifiers that appear. For example, a seller of educational toys might see ASIN B07XYZ1234 listed as missing a CE‑mark certificate.
- Build the Compliance Payload — In the body of the API call or within the JSON feed file, add a
gpsrComplianceobject that contains the required fields. Typical entries include set to “COMPLIANT,” set to “CE,” and a reflecting when the test was completed. A sample JSON fragment looks like:
Analysis & Recommendations
Why This Matters
The new GPSR fields let sellers attach safety certificates directly, eliminating a separate upload step and speeding up compliance verification. Failure to add the gpsrCompliance block within 30 days will cause Amazon to hide or delete the affected ASINs, impacting sales and account health.
Key Takeaways
- Only the Listings Items API endpoint 2021‑08‑01 supports GPSR fields; earlier versions return validation errors.
- A new gpsrCompliance object with fields complianceStatus, certificationType, certificationDate must be included in the payload.
- PDF certificates up to 5 MB are embedded as Base64 in a document sub‑field, e.g., "fileName": "CE_Certificate_B07XYZ1234.pdf".
- New error codes GPSR_ATTRIBUTE_MISSING and GPSR_DOCUMENT_INVALID provide precise feedback for remediation.
Recommended Actions
- →In Seller Central, go to Account Health > GPSR compliance required filter, export the list of affected ASINs/SKUs.
- →Update integration scripts to call PUT /listings/2021-08-01/items/{sellerId}/{sku} and embed the gpsrCompliance object plus Base64‑encoded PDF.
- →Add monitoring for GPSR_ATTRIBUTE_MISSING and GPSR_DOCUMENT_INVALID errors and create alerts or tasks when they appear.
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!