Track GPSR compliance listing by listing, with a person deciding what counts as compliant
Updated · By Ecomsellertool editorial team
Keep one record per listing and EU store with the manufacturer, the EU responsible person, safety warnings, an identifier and a status. A rule table then checks each record, flags what is missing or stale, and sends it to a person. Rules find the gaps; a person, usually with legal counsel, decides what is correct. This is not legal advice.
- The EU General Product Safety Regulation has applied since 13 December 2024 and requires an economic operator in the EU to be responsible for each covered product (checked November 4, 2026).
- Shopify's help page says to include an identifying element and the manufacturer's contact details, an EU responsible person if the manufacturer is outside the EU, and warnings in the language of each EU country of sale.
- Shopify has no EU responsible person service of its own; legally required warnings go in the Disclosures product metafield, other details in the description or a metafield.
- Amazon says a responsible person established in the EU is mandatory for non-food products and that non-compliant listings risk removal.
- Amazon's Selling Partner API changelog lists GPSR listing attributes by level: manufacturer email at ASIN level, responsible party email at SKU level, a safety attestation, and compliance documents.
- Here rules check completeness and freshness; a person decides what is correct and whether a product is in scope.
The step map: who runs each step
Trigger: A new or changed listing for an EU store, a change to a manufacturer or responsible person record, a new compliance document, or a weekly sweep of every active EU listing.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | Each EU listing (SKU plus store) gets a record: manufacturer name, postal and electronic address, EU responsible person and contacts, product identifier, warnings and safety text per language, compliance documents, and the date each was last checked. | Rule |
| 2 | On every new or changed listing and once a week, the workflow compares the record with the status table and sets one status: complete, missing data, language gap, document gap, stale, or needs review. | Rule |
| 3 | For Amazon EU, the workflow reads the account's compliance or account health view and any listing issue for the SKU, and compares it with your record. It does not mark anything compliant on Amazon's behalf. | Rule |
| 4 | For Shopify, it checks that the Disclosures metafield and the description or metafield you chose hold the required text for each EU language you sell in, and flags blanks. | Rule |
| 5 | Gaps become tasks grouped by cause, such as one missing responsible person for a whole brand, not one ping per SKU. | Rule |
| 6 | A person fills in or approves the manufacturer, responsible person, warnings and translations, and decides whether a product is covered at all. | Person |
| 7 | Once approved, the workflow pushes the data to each channel, reads it back, and logs who approved what and when. | Rule |
6 rule steps · 0 AI model steps · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Deciding whether a product falls under the regulation and whether any exemption or other product law applies, with counsel where needed
- Choosing and appointing the EU responsible person, and signing the mandate
- Writing or approving safety information and warnings, and having each language checked by someone who reads it
- Accepting a listing as compliant after the workflow reports it complete
- Handling any accident report, recall or authority request, which never runs automatically
Which tools can run it
- A shared spreadsheet with one row per SKU and EU store, a status column and a weekly review, for a small catalog
- Your product information system or a Shopify metafield set, with the workflow checking for blanks
- Zapier, Make or n8n for the weekly sweep, the blank checks and the task creation
- Custom code on your accounts for large catalogs, many languages, brand-level submission and a full audit log
Systems it connects
- Product master record or product information system
- Amazon Seller Central EU and Listings Items API
- Shopify products, metafields and metaobjects
- Task tracker or approval queue
- Document storage for compliance files
Build size: Medium
The checks are simple; the work is clean source data, one record per listing and store, and clear ownership of who approves the text.
A brand ships a hundred SKUs into Germany, France and Italy. Months later one listing is pulled because a field is empty, and nobody can say which of the other 99 have the same gap. This recipe is the record that answers that question. It keeps the product data the GPSR asks for next to each EU listing, checks it on every change and every week, and puts each gap in front of the person who can fix it. It is not legal advice; your counsel decides what the rules require for your products. It is one page of our automation library.
For the wider market picture, including registrations, see our Amazon.de guide, which already covers the GPSR in short. This page is the tracker behind it.
What does each EU listing need under the GPSR?
The regulation, Regulation (EU) 2023/988, has applied since 13 December 2024, and the Commission says a responsible economic operator in the EU must be entrusted with safety tasks for each covered product (checked November 4, 2026). Its EU-OSHA summary adds that products should carry information that identifies the product and its manufacturer, to support traceability (checked November 4, 2026). We could not open the regulation's own article text today, so the field list below comes from the two marketplaces, which state it for sellers.
| Field | Shopify says | Amazon says (checked November 4, 2026) |
|---|---|---|
| Manufacturer | Name, trade name or trademark, physical address, email or other electronic contact, per Shopify's GPSR page | Enter manufacturer contact information in Seller Central first; the API changelog lists a manufacturer email attribute at ASIN level |
| EU responsible person | Required if the manufacturer is outside the EU; Shopify does not offer this service | Mandatory for non-food products; the API lists a responsible party email at SKU level |
| Identifier | An identifying element such as a picture, type, batch or serial number | Not stated on the pages we read |
| Warnings and safety information | In the language of each EU country of sale; legally required warnings go in the Disclosures metafield | A safety attestation attribute and compliance document types such as safety information, user manual and instructions for use, each with a language code |
| Documents | Not stated | Documents are given by URL, and Google Drive and Dropbox links are not allowed |
Two points matter for the tracker. Amazon's API changelog covers Spain, France, Belgium, the Netherlands, Germany, Italy, Sweden and Poland, and its forum post says UK listings need no GPSR submission but EU stores do. And the responsible person is entered per store, so one person for the whole EU still means several records.
How does the status table work?
This table is the core of the build, and you can run it today from a spreadsheet. Each row is a listing state the workflow can detect, the check that finds it, the action, and who decides. A status is a statement about completeness, never about compliance.
| Listing state | Check | Action | Who decides |
|---|---|---|---|
| New EU listing, no record | Listing exists in an EU store with no manufacturer or responsible person row | Creates the record, blocks the listing from going live if your process allows, opens a task | Compliance owner |
| Manufacturer or responsible person blank | Required field empty | Status "missing data"; groups tasks by brand and store | Compliance owner |
| Safety text present in only some languages | Language list for the store has a gap | Status "language gap"; drafts nothing, asks for text | Person who reads that language |
| Warning field empty on a product you marked as needing one | Product class says warnings apply | Status "needs review" | Compliance owner, with counsel if unsure |
| Document missing or link not allowed | No document of a required type, or a blocked host | Status "document gap" | Product owner |
| Record changed (address, person, document) | Change date newer than last check | Rechecks every linked listing, status "stale" until approved | Compliance owner |
| Channel shows an issue | Amazon listing issue or compliance view names the SKU | Task with the channel's message attached | Compliance owner |
| All fields filled and approved | Every row above clear | Status "complete"; logs the approver and date | The approver, not the rule |
| Product may be out of scope | Product class flagged by you | Status "needs review" | Counsel or compliance owner |
For example, a brand with 100 SKUs in four EU stores has 400 listing records. If its responsible person changes, one edit stales all 400 and creates one task, not 400.
How does the data reach Amazon and Shopify?
On Amazon, enter the manufacturer and responsible person details in Seller Central first. The changelog then lets Listings Items API and JSON feed submissions carry the attributes for supported product types, which you retrieve with the product type definitions operation (checked November 4, 2026). It also says to submit partial updates only, because full updates through legacy XML feed types override GPSR information a seller uploaded in Seller Central. Amazon's forum post says approved information appears on product pages within 24 hours of confirmation. Read the listing back afterward and compare it with your record; do not assume the push worked. Our marketplace listing error alerts recipe covers how to catch rejections.
On Shopify, the help page says legally required warnings go in the Disclosures product metafield and metaobject entries, and other required information goes in the product description or a metafield you add (checked November 4, 2026). The workflow checks those fields for blanks per language. It cannot judge the content. Build the GPSR fields into new SKU setup so a listing never launches without them.
What should stay with a person?
Nearly every decision. Rules can see an empty field, a missing language, a stale date or a blocked link. They cannot tell whether a warning is right, whether the responsible person's mandate is valid, or whether a product is covered. A person should approve the text and each translation, appoint and contact the responsible person, and handle any accident report, recall or authority request, which Shopify's page says sellers must report or cooperate on. Counsel should confirm scope. The tracker's value is that these people work from one record and see only real gaps, in the same queue as your other listing alerts.
Which tool should run it?
| Level | Fits when | What to watch |
|---|---|---|
| Spreadsheet with a weekly review | Under a few hundred listings, one or two EU stores | Someone must own the weekly check; add a last-checked date |
| Product information system or metafields | Data already lives there | Make required fields required, so blanks cannot be saved |
| Zapier, Make or n8n | Weekly sweep and task creation across Shopify and a sheet | Keep the status logic in one place; see our Zapier vs Make vs n8n comparison |
| Custom code on your accounts | Large catalogs, many languages, brand-level submission, audit log | Can run on Ecomsellertool Growth OS beside listing and catalog workflows |
Who builds a GPSR listing tracker for an ecommerce brand?
Ecomsellertool builds compliance and listing workflows like this on your own accounts. We have built on Amazon's seller APIs since 2017. We start with where your product data lives, who approves text, and which EU stores you sell in, then build the record, the status rules and the task queue. Send a project brief below, or read how our workflow automation service works.
The nearest shipped work is AccountDr, where we built rule-based automation that notifies sellers about listing faults, stranded inventory, hijackers and ASIN changes. A listing compliance gap is the same kind of event: detect it, name the cause and tell the right person.
You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you.
Get this workflow built
Send us your version of this workflow
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
What information does a listing need under the GPSR?
Shopify's help page lists an identifying element such as a picture, type, batch or serial number, the manufacturer's name, trade name, physical address and email or other electronic contact, an EU responsible person if the manufacturer is outside the EU, and warnings and safety information in the language of each EU country of sale. Marketplaces add their own fields, so check each one.
Do I need an EU responsible person to sell on Amazon in the EU?
Amazon states that a responsible person established in the EU is mandatory for non-food products sold in its EU stores, and that non-compliant listings risk removal. Who qualifies is a legal question, so confirm the options with counsel before you appoint anyone.
Does Shopify provide a GPSR responsible person or compliance fields?
Shopify's help page says it does not currently offer a responsible person service and points to third-party tools on its App Store. It says legally required warnings go in the Disclosures product metafield, and other required information in the product description or a product metafield.
Can a tracker make my listings compliant?
No. A tracker shows what is missing, stale or untranslated and keeps the evidence. Whether the content is correct, whether a product is covered and who should be the responsible person are decisions for you and your advisers. Treat a complete status as meaning the fields are filled in, not that the law is satisfied.
Can I send GPSR data to Amazon through the API?
Amazon's Selling Partner API changelog says sellers must first enter manufacturer and EU responsible person contacts in Seller Central, after which listings submissions can carry GPSR attributes for supported product types. It also warns that full legacy XML feed updates can override GPSR information uploaded in Seller Central.
How often should I recheck listings?
Check on every listing change and run a full sweep on a schedule you choose, such as weekly. Also recheck everything tied to a record when a manufacturer address, responsible person or document changes, because one change can affect many listings.
