Saya & Associates
EU marketplace seller onboarding under the Digital Services Act
1. Does the special marketplace section apply to your platform?
First ask whether the service is an online platform allowing consumers to conclude distance contracts with traders. A marketplace that only advertises businesses and redirects consumers elsewhere may need a different analysis from one that enables the transaction through its own interface. The DSA can apply to intermediary services offered to recipients in the EU even when the provider is established outside the EU. An India-based company should not dismiss it simply because its corporate entity is in India.
Then test the provider's size against Article 29 of the DSA. That provision excludes qualifying micro and small providers from the section containing Articles 30 and 31, with special rules for loss of that status and very large online platforms. The exemption concerns this section; it is not an all-purpose statement that a small marketplace has no EU obligations.
Record the classification and the evidence supporting it. Revisit it as the business grows, changes its transaction flow, or acquires another entity.
2. What does trader traceability involve when Article 30 applies?
Article 30 requires a covered provider to obtain specified information before allowing a trader to use the platform to offer products or services to EU consumers. It includes the trader's name, address, telephone number and email address; an identity document or recognised electronic identification; payment-account details; trade-register details where applicable; and a self-certification about offering only products or services compliant with applicable EU law.
The provider must make best efforts to assess whether the information is reliable and complete, using official databases or trustworthy supporting documents where appropriate. When it has sufficient indications that information is inaccurate, incomplete or outdated, it must seek correction. Continued failure to correct can lead to suspension under the procedure in Article 30. This is a defined process, not a licence to delete a seller account without considering the trader's procedural rights.
The same article also addresses secure retention and disclosure. In general, the collected information is kept for six months after the end of the trader relationship and then deleted, subject to applicable law. Certain trader identity and registration information must be made available to consumers where the product or service is presented. Not every document collected during onboarding is meant to be displayed publicly.
3. Seller onboarding and product listings are different controls
Verifying a seller once does not prove that each listing contains the information required by product-specific or consumer law. Article 31 addresses compliance by design: where it applies, the interface must enable traders to provide the information needed to meet obligations concerning pre-contractual information, product compliance and product-safety information.
For a marketplace team, that suggests two separate gates:
- Trader gate: has the seller supplied the required identity and business information, and has the required reliability check been completed?
- Listing gate: can the seller supply the required product, economic-operator and safety information for the particular category and destination market before publication?
The second gate may vary by product. Clothing, toys, cosmetics and electrical equipment do not share one universal evidence pack. The DSA does not replace the EU General Product Safety Regulation, sector-specific product rules, consumer rights, tax, customs or GDPR requirements.
4. Where marketplaces lose the thread
In practice, the most expensive failures are often allocation failures. The onboarding form asks for a company name, while the seller agreement promises compliance in general terms. The listing page omits information the product team never made into a required field. Support cannot identify who must respond when a product is challenged. Operations can approve a seller without seeing whether an identity check is incomplete.
Before launch, walk through one real seller and one real order. Identify who owns each step: registration, verification, listing review, consumer disclosure, complaint handling, suspension, records and deletion. Then compare those answers with the interface, seller contract, customer terms and support workflow.
If they disagree, fix the operating flow before adding another policy paragraph.
5. A practical implementation sequence
Start with a short legal and product map:
- Scope: classify the service and document whether Article 29's micro/small exception applies.
- Seller record: specify which fields, documents and checks are required before an in-scope trader is enabled.
- Listing schema: map mandatory information by product category and destination market.
- Consumer view: verify which trader details appear at the point the offer is presented.
- Exceptions: define correction, suspension, appeal and reinstatement steps.
- Evidence: keep a dated record of the information received, the check performed and the decision made.
- Lifecycle: define review triggers, retention, deletion and ownership when the seller relationship ends.
For an early-stage marketplace, this can begin with a single transaction flow and one product category. The point is to make each legal responsibility executable by a named team member or product control.
Frequently asked questions
Does an India-based marketplace have to consider the DSA?
Yes, if it offers an intermediary service to recipients in the EU. The exact duties depend on the service, its EU-facing activity and whether the relevant provisions apply. Incorporation outside the EU does not itself answer the question.
Must every small marketplace perform Article 30 trader checks?
No blanket answer is safe. Article 29 provides a micro/small-enterprise exception for the DSA's special marketplace section, subject to its conditions and exceptions. The provider's size and classification must be assessed, and other applicable laws may still require seller or product information.
Is a seller's promise to obey the law enough?
No. Where Article 30 applies, it specifies information collection and best-efforts reliability checks in addition to a trader self-certification. Where Article 31 applies, the interface must support the required disclosures. The contract and the product flow need to work together.
Does trader verification solve product-safety compliance?
No. It identifies and documents the trader. Product-safety obligations depend on the actual goods, supply chain, economic-operator roles and destination market. A verified seller can still publish a non-compliant listing.
The takeaway
For an EU-facing marketplace, the useful question is not simply, "Do we have seller terms?" It is, "What prevents a seller or listing from going live before the information we need exists?" Answer the DSA scope and size questions first. Then make the answer visible in onboarding, listing design, contracts and operational records.
For broader India-to-EU launch issues, see our cross-border ecommerce checklist. To discuss a specific marketplace structure, contact Saya & Associates.
This article is general information, not legal advice. Application of the DSA and related laws depends on the platform's functionality, size, products, traders, markets and current law.