Mapping Roles under the Digital Services Act

A detailed exploration of trader and economic operator obligations in a multi-party marketplace

Key Takeaways

• Trader Identification: The trader named under Article 30 is the party with which the consumer ultimately contracts, which in this arrangement is the merchant‐of‐record handling the transaction.
• Economic Operator Responsibility: The economic operator under Article 31 is the party that “places the product on the market” by controlling the product description, pricing, and other commercial information – typically the original developer/producer.
• Producer Obligations: Despite not having a direct contract with the consumer, the producer must ensure product accuracy, legal compliance, and thorough cooperation in cases of regulatory review or complaints.

Introduction

The Digital Services Act (DSA) introduces complex obligations on online platforms and their participants. In scenarios where multiple entities are involved – such as an original software producer, a marketplace performing vetting, and a merchant‐of‐record arrangement – understanding which party must be named under specific articles is essential. This in-depth analysis will clarify the roles and obligations of the trader under Article 30 and the economic operator under Article 31. Furthermore, it will outline the residual responsibilities that remain with the software producer even when there is no individual contract with the consumer.

Role Definitions under the DSA

The DSA places a strong emphasis on transparency, traceability, and accountability. Two key articles—Article 30 and Article 31—establish the need for clear identification of the relevant parties involved in offering products or services online.

Trader under Article 30

Identifying the Trader

Article 30 of the DSA mandates that providers of online platforms allow consumers to engage only with traders who have provided verified and complete information. The definition provided in the regulatory framework specifies that a trader is any natural or legal person engaged in a professional activity who enters into a contractual relationship with the consumer. In the scenario provided, there exists a multi-layered relationship:

• The original software developer/producer creates the product, sets the product details, pricing, and description, and submits this information to the online marketplace.
• The marketplace provider, in turn, performs vetting checks related to functionality and content compliance.
• The transaction itself, however, is handled by a merchant‐of‐record entity (Fastspring), which processes consumer payments and facilitates the contractual relationship.

The crux of the trader identification lies in determining who is directly entering into a contractual relationship with the consumer. Given that the actual consumer contract is processed through the merchant‐of‐record arrangement with Fastspring, the trader named under DSA Article 30 is effectively Fastspring. It is this entity that finalizes the sale, presents the product pricing, and handles customer‐facing transactions.

Essentially, while the original developer/producer is essential in supplying and dictating the specifics of the product, the legal and commercial interface with the consumer – as defined by contractual evidence – is managed by Fastspring. This interpretation aligns with the notion that trader identification centers on the one who is contractually engaged with the consumer.

Economic Operator under Article 31

Determining the Economic Operator

Article 31 of the DSA focuses on “compliance by design” for online interfaces. The economic operator is defined as the party that exerts control over the product’s commercial presentation. In other words, it is the entity that “places the product on the market” by determining how the product is described, its pricing, and other related information.

In the scenario provided, the original software developer and producer plays a critical role. Despite the fact that they do not have a direct contractual relationship with the consumer, they are responsible for setting the product’s price, description, and other key details. These inputs are presented on the online platform through the marketplace’s interface. By having direct control over these commercial aspects, the producer is positioned as the economic operator under Article 31, responsible for ensuring that the product meets the regulatory and compliance guidelines mandated by the DSA.

The role of the economic operator is to ensure that the product is not only attractive and well-presented but also compliant with all relevant EU legislation regarding product safety, consumer protection, and information accuracy. Thus, the original developer/producer, by virtue of making these decisions and having control over the software, is recognized as the economic operator.

Obligations of the Producer Despite No Direct Consumer Contract

Even though the producer is not signing individual contracts with consumers—since Fastspring and the online marketplace are intermediaries—the producer maintains a series of crucial obligations to ensure full compliance under the DSA. Here are the core obligations that remain with the producer:

Providing Accurate and Updated Product Information

Certification of Compliance

The producer is obliged to furnish detailed and accurate information regarding the product. This includes the product description, pricing, and other commercially relevant details. The data must align precisely with what is provided on the online marketplace. The information serves as a certification by the producer that the product fully complies with applicable regulatory standards and consumer-protection guidelines.

In cases of any discrepancies or if the information is found lacking (for example, if it is misleading or incomplete), the producer must promptly remedy these issues. This obligation ensures that there is transparency and trust in the marketplace environment.

Ensuring Product Safety and Legal Compliance

Adherence to Applicable Laws

One of the producer’s fundamental responsibilities is to ensure that the software complies with all relevant EU laws, including standards related to consumer safety and product quality. This obligation is independent of the contractual arrangement with the consumer, meaning that the producer can never be entirely shielded from these requirements by outsourcing the sales process. They must continuously monitor and verify that their product adheres to both the letter and the spirit of regulatory norms.

In practical terms, this means that if any compliance issues are identified by regulatory authorities or arise due to consumer complaints, the producer must cooperate fully, provide necessary documentation, and take corrective measures as required. This level of accountability remains with the producer because they are the ones who fundamentally design and develop the product.

Maintaining Traceability

Information Provision and Verification

The DSA places a strong emphasis on traceability. The producer must provide comprehensive trader information to the online marketplace, which then verifies and discloses this information to consumers. This includes essential contact details as well as documents that support the identity and legitimacy of the producer. The accurate provision of this information is central to the regulation’s objective of protecting consumer rights and ensuring accountability.

Even though Fastspring, acting as the merchant‐of‐record, is the trader interfacing directly with consumers, the original developer/producer is still required to back the correct and updated listing of data from which the marketplace can verify compliance. If the regulatory bodies or consumer protection agents call for confirmation of provided details, the producer must be able and ready to provide this information.

Cooperation in Case of Regulatory Investigations

Responding to Consumer Complaints and Inquiries

Another essential statutory duty is the producer’s obligation to cooperate with consumer complaints or inquiries that might emerge in relation to product performance or safety. In the event that a complaint is registered or an inquiry is launched by a regulatory authority, the producer is required to supply any relevant information and take remedial steps as necessary. This cooperation cements the producer’s responsibility for any shortcomings in the product, ensuring that they cannot evade accountability simply because a third party is managing the direct consumer contract.

This cooperation includes documentation that supports the compliance claims and testing records that justify the product’s safety and functionality. In this way, the producer’s role as the economic operator under Article 31 ties directly into a continuous compliance and accountability framework.

Comparative Overview with a Detailed Table

The following table summarizes the roles and obligations of each party involved in this intricate scenario:

Analysis and Synthesis

When interpreting the roles defined under the DSA, it is critical to focus on the contractual and commercial interactions between the different participants. The DSA’s clear objective is to ensure that consumers know with whom they are entering into a contract while establishing a framework that holds the instigators of market activities accountable on a continuous basis.

In this scenario:

• The trader identified under Article 30 is required to be the party that concludes the consumer contract. Since Fastspring acts as the merchant‐of‐record handling payment and the transaction process, it qualifies as the trader. Its role as the commercial intermediary means that the consumer interacts with Fastspring for any contractual or transactional disputes.
• Conversely, the economic operator under Article 31 is the party that “places the product on the market,” dictating the product’s commercial attributes. Here, the original developer/producer sets the product’s price, description, and other important details. This grants them the responsibilities tied to product compliance, making them the economic operator.
• Even though the producer does not engage directly with the consumer, regulatory obligations remain intact. Their responsibilities include guaranteeing product safety, providing verifiable and accurate information, and ensuring compliance with EU legal standards. In addition to these, the producer must proactively cooperate in investigations or consumer complaints, which provides a robust level of accountability in the event of any issues.

This multi-party arrangement embodies an advanced layer of transparency and regulatory oversight where each party’s role is clearly delineated not only to shield consumers but also to ensure that all parties remain accountable. While Fastspring is positioned as the trader, the original producer – acting as the economic operator – must closely manage every aspect of the product’s information and compliance.

Conclusion and Final Thoughts

In conclusion, within the described marketplace scenario under the Digital Services Act, the trader to be named under Article 30 is the merchant‐of‐record (Fastspring), as it is the entity that directly engages in the consumer contract through processing payments and completing the transaction process. On the other hand, the economic operator as outlined in Article 31 is the original developer/producer, since they control the product’s market presentation including the product’s pricing, description, and other essential details. Although the producer is not directly contracting with the consumer, they retain significant obligations under the DSA—especially focusing on ensuring that their product information is accurate, that the product complies with all relevant legal requirements, and that they cooperate in any regulatory oversight exercises or consumer complaint processes.

This delineation of roles emphasizes that both the transaction-facilitating party and the underlying product provider carry distinct, yet interdependent responsibilities. The structure supports an ecosystem where transparency, traceability, and accountability are paramount. This model not only protects consumer rights but also ensures that every stakeholder in the marketplace is mitigated for any potential non-compliance.

References

• Are You a 'Trader' Under the DSA? Insights for App Developers - VeraSafe
• Digital Services Act Article 30 - EU Digital Services Act
• Art. 30 DSA - Traceability of Traders - Digital Horizon
• Art. 31 DSA - Compliance by Design - Digital Horizon
• Digital Services Act Article 31 - EU Digital Services Act

More Related Queries

How does the Digital Services Act impact marketplace compliance obligations?

What are the responsibilities of merchants of record under EU consumer law?

How does compliance by design function in multi-party online marketplaces?