FAQEU DSA

DSA marketplace trader traceability what must marketplaces do?

Online platforms that let consumers in the Union conclude distance contracts with traders must collect trader identity and compliance information before traders offer products or services.

The practical workflow is seller onboarding, reliability checks, consumer-facing disclosure, secure retention, and suspension when required trader information is missing or not fixed.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Questions
5

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

Under the EU Digital Services Act, an has a seller-onboarding, disclosure, and maintenance duty called marketplace traceability. Article 30 applies to online platforms that allow consumers to conclude distance contracts with traders, subject to the Article 29 exclusion for qualifying micro and small providers and its post-loss and VLOP rules. Covered providers collect specified trader information, make best efforts to check that it is reliable and complete, show key trader information to consumers, keep the records securely for the required period, and suspend trader access where missing or defective information is not remedied.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

What does DSA marketplace trader traceability require?

For an in scope of Article 30, first record whether Article 29 excludes the marketplace section because the provider qualifies as micro or small. Where Article 30 applies, a should not be able to promote messages about products or services, or offer products or services to consumers located in the Union, until the platform has obtained the required trader information.

The marketplace also has to make best efforts to assess whether the information is reliable and complete before the uses the service. That assessment can use freely accessible official databases or online interfaces made available by a Member State or the Union, or supporting documents from reliable sources requested from the trader.

Article 30 gave covered marketplaces 12 months from 17 February 2024 to obtain the required information from traders already using the service. That transition ended on 17 February 2025, so a covered marketplace should not treat a pre-existing as exempt from the current onboarding and maintenance control.

  • Collect the 's name, address, telephone number, and email address where applicable.
  • Collect a copy of the 's identification document or qualifying electronic identification.
  • Collect payment account details and, where applicable, trade-register details and registration number or equivalent identifier.
  • Collect the 's self-certification committing to offer only products or services that comply with applicable Union law.
  • Block marketplace use for EU consumer offers until the Article 30 information has been obtained and checked for reliability and completeness through best efforts.

How should an handle traceability under the EU Digital Services Act?

Treat it as a seller-onboarding and seller-maintenance control. Before a can offer products or services to consumers in the Union, collect the Article 30 identity, contact, payment, register, and self-certification information; make best efforts to check that the information is reliable and complete; show the required trader identity, register, and compliance self-certification information where the product or service is presented; store the collected information securely during the trader relationship and for six months afterward; and suspend the trader if missing or inaccurate information is not remedied.

Citations
Question 2

What must be visible to consumers?

Article 30 separates internal collection from consumer-facing disclosure. The marketplace does not publish every collected item, but it must make the 's name and contact information, trade-register information where applicable, and the trader's compliance self-certification available to recipients of the service in a clear, easily accessible, and comprehensible way.

The marketplace must make that information available on the online interface where the product or service is presented. Identification documents and payment-account details belong in the internal traceability record, not the Article 30(7) consumer disclosure.

  • Show the name, address, telephone number, and email address in the product or service flow where consumers can find it before buying.
  • Show the trade register and registration number or equivalent identifier when the is registered in such a register.
  • Show the 's self-certification that products or services offered through the marketplace comply with applicable Union law.
  • Do not expose identification documents or payment account details to consumers unless another applicable law requires disclosure.
Citations
Question 3

What should the marketplace do when information is missing or unreliable?

If the marketplace has sufficient indications or reason to believe that Article 30 information is inaccurate, incomplete, or not up to date, it must ask the trader to remedy the problem without delay or within the period set by Union and national law.

If the does not correct or complete the information, the marketplace must swiftly suspend the service for that trader in relation to products or services offered to consumers located in the Union. A refusal or suspension decision also connects to the DSA complaint routes available to the trader.

  • Log the signal that made the data appear inaccurate, incomplete, or stale.
  • Send a remediation request that identifies the exact missing or defective Article 30 field.
  • Pause or prevent EU consumer offers where the required information is not supplied or corrected.
  • Keep evidence of the request, response, suspension decision, and any complaint handling.
Citations
Question 4

How do Article 31 and Article 32 connect to traceability?

traceability should be implemented together with Article 31 marketplace interface controls. The interface must let traders provide required pre-contractual, compliance, and product safety information, including product or service identification, trader signs such as a trademark or logo, and applicable labelling and marking information.

After a is allowed to offer products or services, the marketplace must make reasonable efforts to randomly check official, freely accessible, machine-readable databases or interfaces to see whether offered products or services have been identified as illegal.

If the marketplace becomes aware that a offered an illegal product or service through the service, Article 32 covers consumers who bought it during the preceding six months. Where their contact details are available, the marketplace must inform them of the illegality, the trader's identity, and relevant redress. If it lacks contact details for all affected consumers, it must make the same information public and easily accessible on its interface.

  • Design listing forms so traders can provide product or service identification, economic-operator details, signs, and applicable labelling or marking information.
  • Before listing, make best efforts to assess whether traders have provided the Article 31 information.
  • After listing, make reasonable random checks against official accessible databases or interfaces for illegal products or services.
  • When an illegal product or service is identified, determine the preceding six-month purchaser population and keep evidence of the illegality notice, identity, relevant redress, direct notices sent, and any public interface notice.
Citations
Question 5

What evidence should teams keep?

Keep evidence showing how the marketplace enforced Article 30 in seller onboarding and live seller maintenance. Store the collected data securely, document how reliability and completeness were assessed, and tie each trader status change to the relevant product or service flow.

Article 30 requires secure storage during the contractual relationship and for six months after it ends, followed by deletion. Disclosure to third parties should be limited to cases required by applicable law, including DSA orders and competent-authority or Commission orders.

  • Seller onboarding record with each Article 30 field, collection timestamp, source, verifier, and result.
  • Reliability check evidence, such as official database lookup result, electronic identification check, or supporting document request and response.
  • Consumer-facing disclosure screenshot or rendered-page capture showing the information on the product or service interface.
  • Issue log for incomplete, inaccurate, or outdated information, including remediation request, deadline, suspension, reinstatement, and complaint handling.
  • Retention and deletion record showing secure storage through the relationship and deletion after the six-month post-relationship period.
Citations
Recommended next step

This DSA FAQ helps check marketplace onboarding and disclosure evidence

Sorena can map Article 30 trader fields, Article 31 listing information, consumer-facing disclosures, random checks, and retention evidence into a repeatable marketplace control.

Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Commission overview explains that marketplaces must verify and display seller contact details for consumer transparency.
"whom you’re buying goods or services from"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
An official source DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs
A cited EU Digital Services Act applicability test for classifying intermediary services, hosting services, online platforms, marketplaces, VLOPs and VLOSEs.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and official source evidence.
DSA average monthly active recipients: what platforms must publish
An official source FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.
DSA Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
DSA Enforcement and Penalties in the EU
How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.
DSA illegal content notices: what must be included?
An official source FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.
DSA Marketplace Trader Traceability Guide
EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.
DSA notice and action plus statements of reasons guide
A source-cited Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.
DSA Notice and Action Workflow for Hosting Services and Online Platforms
A source-cited DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
DSA recommender transparency FAQ: Article 27 and VLOP options
What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.
DSA researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher access for VLOPs and VLOSEs under Regulation (EU) 2025/2050: requests, data catalogues, security, deadlines, and records.
DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs
Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.
DSA statement of reasons FAQ
When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.
DSA statement of reasons log workflow for online platforms
Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.
DSA transparency report template fields and cadence
A source-cited template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.
DSA Transparency Reporting Obligations by Provider Tier
A source-cited guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.
DSA VLOP and VLOSE Risk Assessments and Mitigation Guide
A source-cited guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.
DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records
Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.
DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits
What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
DSA vs GDPR: online-platform governance and personal-data obligations
Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.
DSA vs P2B Regulation: EU platform obligations compared
Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.
DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders
Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.
EU Digital Services Act checklist for platforms and hosting services
An official source DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.
EU Digital Services Act Compliance Guide
DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.
EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties
Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.
EU Digital Services Act penalties and fines: caps and enforcement roles
DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.
EU Digital Services Act requirements by service tier
Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.
EU Digital Services Act service types and scope
Classify DSA service scope across mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE threshold duties.
EU DSA deadlines and compliance calendar: application dates, reporting cycles, and VLOP clocks
Calendar view of cited EU Digital Services Act dates: full application, user-number publication, VLOP/VLOSE designation clocks, statements of reasons, and transparency reporting cycles.
EU DSA Transparency Calendar: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.
EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence
Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.