| Scope boundary | Applies to intermediary services with layered duties for hosting services, online platforms, online marketplaces, online search engines, VLOPs, and VLOSEs when the service has a substantial connection to the EU. | Applies to online intermediation services and online search engines that provide services to business users or corporate website users established in the EU and offering goods or services to EU consumers. | Start with two classifications: DSA service role and P2B business-user relationship. A service can be both an online platform under the DSA and an online intermediation service under P2B. |
|---|
| Covered actors | How does the platform handle illegal content, terms enforcement, notices, content restrictions, appeals, ads, recommenders, marketplace trader information, transparency reporting, and systemic risks? | How does the platform treat business users in its terms, restrictions, suspensions, ranking, differentiated treatment, data access, complaints, and mediation options? | Use DSA controls for platform safety and content governance; use P2B controls for commercial fairness and transparency toward business users. |
|---|
| Trigger | Hosting providers must give clear and specific statements of reasons when they remove, disable, demote, restrict visibility, suspend payments, suspend service, or suspend an account because content is illegal or violates terms. | Providers of online intermediation services must give business users reasons for restrictions, suspensions, and terminations, and those reasons should connect to the platform's terms and the affected business relationship. | A single restriction event may need two explanations: a DSA statement for the affected recipient and a P2B business-user reason for the account or commercial restriction. |
|---|
| Core obligations | Online platforms must provide an internal complaint-handling system for covered moderation decisions and inform complainants about reasoned decisions and out-of-court dispute settlement options. | P2B requires internal complaint handling for business users where applicable and requires providers to identify mediators in their terms, with business-user complaint issues centered on commercial platform treatment. | Do not merge queues without labels. DSA complaints concern moderation or notice decisions; P2B complaints concern the business user's relationship with the platform. |
|---|
| Evidence record | Keep DSA service classification, notice/action logs, statement-of-reasons exports, complaint outcomes, out-of-court dispute records, transparency-report inputs, trader files, AMAR data, risk assessments, audits, and ad repository records. | Keep P2B terms, business-user change notices, restriction reasons, ranking disclosures, differentiated-treatment explanations, data-access descriptions, complaint records, mediator information, and policy version history. | The same platform event can appear in both evidence sets, but each record should name the legal basis it supports and the audience it was written for. |
|---|
| Recommender and ranking transparency | The DSA requires online platforms using recommender systems to explain the main parameters in their terms and conditions; VLOPs and VLOSEs also need a non-profiling recommender option and additional advertising transparency duties. | P2B requires online intermediation services and search engines to explain the main parameters determining ranking and the reasons for the relative importance of those parameters for business visibility. | Ranking evidence should say who the audience is: DSA recommender and ad explanations are recipient-facing platform transparency; P2B ranking disclosures are business-user and corporate-website-user transparency. |
|---|
| Enforcement | Digital Services Coordinators supervise DSA compliance at Member State level, while the Commission has direct supervisory and enforcement powers for VLOPs and VLOSEs, including fines for relevant infringements. | P2B relies on Member States to ensure adequate and effective enforcement and allows qualifying organisations, associations, and public bodies to bring actions before competent courts. | Escalate DSA findings through the DSA regulator pathway; escalate P2B findings through business-user dispute, mediation, court, or Member State enforcement pathways. |
|---|
| Overlap and reuse | DSA marketplace rules require platforms that let consumers conclude distance contracts with traders to collect and assess trader identity and registration information, support product information display, and inform consumers about known illegal products or services where required. | P2B focuses on the business user's commercial relationship with the platform, including terms, restrictions, ranking, data access, and complaint mechanisms; it is not a marketplace product-safety or trader-traceability framework. | Trader onboarding files can support DSA marketplace obligations, but P2B evidence should still explain the business user's platform terms, visibility, restrictions, and data access. |
|---|
| Practical decision rule | Use the DSA when the issue is about illegal content handling, notice-and-action, statements of reasons, moderation appeals, marketplace trader traceability, advertising transparency, recommender transparency, AMAR, VLOP/VLOSE duties, or systemic risk controls. | Use P2B when the issue is about business-user terms, ranking, restriction or suspension reasons, termination, access to data, complaint handling, mediation, or fair treatment in the platform relationship. | If the question is about safety, moderation, or recipient-facing transparency, start with the DSA. If the question is about commercial fairness to business users, start with P2B. If a platform change affects both, document both legal bases. |
|---|