Regulation (EU) 2023/988 does not specify a timeframe within which a marketplace must remove a listing when GPSR information is missing or incorrect. The marketplace determines that speed itself, through its own process. In practice, the processing time varies widely: from immediate blocking upon uploading a new product, to removal that only occurs after a complaint, a spot check, or a signal from a supervisory authority.
What mainly determines the processing time is the trigger. An automated check when creating a listing works almost instantly: if mandatory fields such as the name and address of the manufacturer or the responsible person in the EU are missing, the listing is refused or suspended immediately. Manual review, for example following a consumer complaint or a notification via Safety Gate, has no set rhythm and can take days to weeks before action is taken.
What determines the processing time
Three factors are always at play. First, the way the problem is flagged: an automated field check responds faster than a human reviewer working through complaints or external signals. Second, the severity of what is missing: an empty mandatory field is different from a product category that receives separate attention because of earlier signals in that category. Third, the platform's own policy, which varies by marketplace and is not publicly documented in detail. Anyone who wants to know precisely what role this plays for their own assortment can best clarify that first with the free role and obligation check, before the discussion about removal speed becomes relevant at all.
From signal to removal: the phases
The process typically consists of a few steps. First there is a signal: an automated check when uploading the product, a complaint, a spot check, or a message from a supervisory authority. Then comes an assessment, which with automated checks is virtually instant and with manual review can take longer. Next comes the action: the listing is taken offline temporarily or permanently, with a notice to the seller about what is missing. Only then does the remediation process begin, in which the seller can add the missing information.
This sequence explains why two similar products can be treated very differently. A product that passes the automated check when uploaded may be online without problems for months. Another product, whose information later turns out to be incomplete or about which a complaint is received, can suddenly and without warning go offline.
Where it breaks down in practice
Most delay and frustration does not occur when taking a listing offline, but when getting a listing back online. Sellers then discover that the requested information is not ready: there is no address for a responsible person in the EU on file, the risk analysis is missing, or the warnings are not available in the correct language. Adding that information takes time, especially if the underlying technical documentation still needs to be requested from a supplier outside the EU. Anyone who already has these documents structured per product can often resubmit a listing within a few days; anyone who has to start from scratch sees the lost revenue from a blocked product accumulate.
A second source of delay is unclear roles in the supply chain. A webshop that thinks it is merely reselling but is actually considered a manufacturer because there is its own brand on the product often discovers this only when a marketplace asks for documentation that does not exist.
Back online: how that process works
Recovery usually takes place through the seller account: missing fields are completed, any requested documents are uploaded, and the marketplace reassesses. With a simple, automated check, this can happen very quickly once the data is complete. With a listing that has been manually reviewed due to a complaint or signal, the reassessment usually takes longer, because a staff member must check the supplementary information again.
What you can do in advance
The fastest way to prevent delays is not to wait for a listing to go offline, but to have the underlying data in order per product before that happens. That means: knowing for each item what role you play, what information is required on the product page, and what documents are ready in the background. Read more about how that data is built and where it comes from on the page about how gpsria.eu works; a broader overview of related topics can be found in the knowledge base.
Are you unsure whether your situation falls under this, or do you want to know exactly what role you play before worrying about processing times at marketplaces? Take the free role check or browse the topics in the knowledge base; both require no account and provide immediate guidance.