Artifact GuideEU

DSA marketplace trader traceability

An official source guide for online platforms that let consumers in the EU conclude distance contracts with traders.

Use it to structure seller onboarding, reliability checks, product listing fields, consumer disclosures, retention rules, and workflow evidence under DSA Articles 30-32.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

DSA traceability governs marketplace onboarding and listing controls for covered trader offers. Article 30 applies to providers of online platforms that allow consumers to conclude distance contracts with a trader for products or services offered to consumers located in the Union. The practical test is whether the marketplace can collect the required trader data before access, assess whether it is reliable and complete, display the consumer-facing fields at the point where the product or service appears, store the file securely, and suspend marketplace access when required information is missing or not corrected.

Section 1

Scope the marketplace and the trader relationship

Start with the service model. The DSA marketplace traceability duties sit in the section for providers of online platforms that allow consumers to conclude distance contracts with traders. A marketplace should document which storefronts, apps, booking flows, promoted listings, brand-sponsored offers, and third-party seller journeys let EU consumers contract with a .

Do not treat every platform feature as a -traceability feature. Community posts, search results, advertising services, hosting infrastructure, and content moderation workflows can trigger other DSA duties, but this guide concerns trader onboarding and product or service offers made through an online marketplace.

Document the seller-status test as well as the platform flow. A acts for purposes related to trade, business, craft, or profession, including through a representative; an individual making an occasional private sale is not necessarily a trader. If the facts are borderline, retain the facts and legal basis used for the decision and reassess when the seller's activity changes.

  • Record the consumer journey where the contract is concluded or promoted, including country availability and whether the recipient is located in the Union.
  • Identify whether the counterparty is a and whether the offer is for products, services, or promoted messages about products or services.
  • Separate marketplace traceability from VLOP, advertising, recommender, notice-and-action, and transparency-reporting obligations unless the same product also triggers them.
  • Check whether Article 29 excludes the provider as a qualifying micro or small enterprise. The exclusion can continue for 12 months after loss of that status, but does not apply to a designated very large online platform.
Section 2

Collect the Article 30 trader file before marketplace access

A covered marketplace should not allow a to use the platform to promote messages on products or services, or to offer products or services to EU consumers, until it has obtained the Article 30 trader information where applicable. The onboarding flow should block publication until all required fields are either completed or marked not applicable with a reason.

The transitional collection period for traders already using a marketplace on 17 February 2024 ended on 17 February 2025. A marketplace that still lacks required information for a legacy should not treat that deadline as open: request the missing information and suspend the trader's EU consumer offers if the trader does not fully comply.

The required file is concrete: name, address, telephone number and email; an identity document copy or electronic identification; payment account details; trade-register or equivalent public-register details when the trader is registered; and a trader self-certification to offer only products or services that comply with applicable Union law.

  • Make every required field a structured onboarding control rather than a free-text note in an internal ticket.
  • Store proof of the source used for each field: submission, official register lookup, payment account document, electronic identification (eID) result, or company certificate.
  • Use separate completeness statuses for contact details, identity evidence, payment account details, register information and self-certification so operations can see exactly why a is blocked.
  • For traders already using the marketplace on 17 February 2024, keep an evidence trail of the collection outreach before 17 February 2025, missing items, correction requests, and any suspension for non-response.
Section 3

Assess reliability, completeness, and correction triggers

Article 30 does not make the marketplace a guarantor of every statement. It requires best efforts to assess whether the required trader information is reliable and complete before access, using freely accessible official databases or interfaces made available by a Member State or the Union, or supporting documents from reliable sources requested from the trader.

Build a correction workflow for stale, inconsistent, or suspicious records. When the marketplace has sufficient indications or reason to believe a required item is inaccurate, incomplete, or not up to date, it should ask the to remedy the issue without delay or within the applicable legal period. If the trader does not correct or complete the information, the marketplace should suspend the service for offers to EU consumers until the request is fully complied with.

  • Record which official database, register, VAT or trade-register interface, eID check, payment account document, or company certificate was used.
  • Keep the verification result separate from the raw document so privacy controls can limit access to identification and payment records.
  • Use mismatch reasons such as name mismatch, missing register number, expired document, unreachable contact channel, payment account mismatch, or missing self-certification.
  • Preserve complaint routes when access is refused or suspended, because Article 30 links refusal and suspension decisions to complaint mechanisms.
Section 4

Design listings so traders can provide product and service information

Article 31 turns traceability into product design. A marketplace interface should allow traders to provide pre-contractual information, compliance information, and product safety information required by applicable Union law. It should also let traders identify the product or service clearly, show signs identifying the such as a trademark, symbol or logo, and provide applicable labelling and marking information.

Before allowing the offer, the marketplace should make best efforts to assess whether the has provided the Article 31 information. After publication, it should 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.

  • Add required listing fields for product or service identification, economic-operator contact fields where applicable, marks, and applicable safety or compliance labels.
  • Block publication where required product, service, compliance, or product-safety fields are incomplete.
  • Keep a random-check register showing the sampled listings, official database used, result, reviewer, and follow-up action.
  • Do not describe random checks as a general monitoring duty; Article 31 frames them as reasonable efforts against official machine-readable sources.
Section 5

Display consumer-facing trader information and handle illegal offers

Article 30 requires the marketplace to make selected information available to recipients in a clear, easily accessible, and comprehensible way. At minimum, the product or service interface should expose the trader name and contact details, trade-register information where applicable, and the trader self-certification commitment that only compliant products or services will be offered.

If the marketplace becomes aware that an illegal product or service has been offered to EU consumers through its service, Article 32 adds a consumer information workflow. Where contact details are available, consumers who purchased the illegal product or service in the six months before the marketplace became aware should be told that the product or service is illegal, the identity of the , and relevant means of redress. Where contact details are not available for all affected consumers, the marketplace should make that information publicly available and easily accessible on its interface.

  • Place the consumer-facing fields on or next to the product or service page, not only in a help center or post-purchase email.
  • Maintain a publication check proving that Article 30(1)(a), (d), and (e) fields display clearly for each live listing.
  • Create an illegal-offer incident record with the discovery source, affected listings, affected consumers with contact details, public notice content, redress information, and removal or suspension action.
  • Keep support scripts aligned with the consumer notice so users receive the same identity and redress information across channels.
Section 6

Keep secure records and workflow evidence

traceability records contain identification, contact, payment, register, and self-certification data. Article 30 requires secure storage during the contractual relationship and for six months after it ends, followed by deletion. Disclosure to third parties should occur only where required under applicable law, including DSA information orders or orders from competent authorities or the Commission.

A useful evidence file should prove both the legal duty and the operational control. It should show the 's lifecycle from onboarding through verification, live display, random product or service checks, correction requests, suspension or reinstatement, consumer notices for illegal offers, and deletion after the retention period.

What information must a DSA-covered marketplace collect from traders?

Article 30 requires, where applicable, contact details, identity or eID evidence, payment account details, trade-register details, and a self-certification that the trader will offer only products or services complying with applicable Union law.

Does the marketplace have to guarantee that information is correct?

No. The DSA requires best efforts to assess reliability and completeness using official online databases or reliable supporting documents. Article 30 states that traders remain liable for the accuracy of the information they provide.

How long should Article 30 information be kept?

The DSA requires secure storage for the contractual relationship and six months after it ends, followed by deletion, unless another applicable law requires a different preservation step.

  • Keep a traceability register with status, required fields, verification method, verification date, reviewer, source used, and open defects.
  • Store raw identity and payment evidence with restricted access, audit logging, retention labels, and deletion triggers tied to the contractual end date.
  • Keep screenshots or rendered-page checks proving consumer-facing disclosures were visible on product or service pages.
  • Maintain separate logs for correction requests, complaints, suspensions, random database checks, illegal-offer notices, and retention or deletion actions.
Primary sources

References and citations

eur-lex.europa.eu7 citations
Referenced sections
  • Primary legal source for Articles 29-32 on marketplace scope, trader traceability, compliance by design, random checks, consumer information, secure retention, and deletion.
  • Article 29 defines the marketplace section scope and Article 30 targets online platforms allowing consumers to conclude distance contracts with traders.
  • Article 30(1)-(3) lists the trader information required before marketplace use, set the 12-month legacy-trader collection period that ended on 17 February 2025, and require correction or suspension when required information remains defective.
Show 4 more
  • Article 30(2)-(4) sets best-efforts reliability checks, correction requests, suspension, and complaint rights for refused or suspended traders.
  • Article 31 requires marketplace interface design for trader compliance information and reasonable random checks against official illegal-product or illegal-service sources.
  • Article 30(7) covers consumer-facing trader disclosure and Article 32 covers notices to consumers about illegal products or services.
  • Article 30(5)-(6) sets secure storage, six-month post-relationship retention, deletion, and limited disclosure rules.
"Traceability of traders"
More quoted passages
"Additional provisions applicable to providers of online platforms allowing consumers to conclude distance contracts with traders"
"the name, address, telephone number and email address of the trader"
"make best efforts to assess"
"Compliance by design"
"clear, easily accessible and comprehensible"
"They shall subsequently delete the information."
digital-strategy.ec.europa.eu4 citations
Referenced sections
  • Commission overview explaining marketplace coverage, verified sellers, seller contact display, and random checks in consumer-facing language.
  • Commission overview identifies marketplaces, app stores, travel, and accommodation platforms as DSA-covered online services.
  • Commission overview explains the DSA consumer value of verified sellers and marketplace transparency.
Show 1 more
  • Commission overview states that marketplaces must make reasonable efforts to perform random checks or adopt traceability technologies.
"More transparency on marketplaces"
More quoted passages
"marketplaces, social media networks, app stores, and online travel and accommodation platforms"
"Verified sellers"
"reasonable efforts to perform random checks"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission-hosted Board page confirming that Articles 30-32 are treated as consumer and online marketplace issues with cooperation across consumer protection, customs, market surveillance, and other authorities.
  • Commission-hosted Board page confirms that DSA Articles 30-32 are handled as consumer and online marketplace issues involving consumer protection, customs, market surveillance, and other authorities.
"Consumers and online marketplaces"
More quoted passages
"Articles 30-32 of the DSA"
Show all related guides (35)

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 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 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 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 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: reports, statements of reasons and user counts

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.

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 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 FAQ

Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.

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 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 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.