| Scope boundary | Creates harmonised ex ante rules for contestable and fair digital markets where gatekeepers are present. | Applies to particular conduct, agreements, dominance questions, and market effects; the DMA recitals describe this enforcement as ex post and case-by-case. | Do not wait for an antitrust infringement theory before implementing DMA duties for a designated gatekeeper service. |
|---|
| Covered actors | Gatekeeper designation for listed core platform services. Article 3 presumptions use turnover or market-value, Member State presence, active end-user, active business-user, and repeated-threshold criteria, with a notification route when the thresholds are met. | A suspected competition issue: agreement or concerted practice, dominance concern, exclusionary or exploitative conduct, merger-related issue, complaint, or authority investigation. | Open the DMA workstream only after confirming gatekeeper and CPS scope; open the competition-law workstream when the market-conduct facts require antitrust analysis. |
|---|
| Trigger | Articles 5, 6, and 7 impose concrete duties on gatekeepers, including data-combination limits, anti-steering rules, user choice, app-store and default-setting obligations, ranking neutrality, interoperability, portability, and business-user data access. | Competition law does not provide the same pre-set product checklist; it tests whether the specific conduct restricts competition or abuses dominance in the relevant circumstances. | Turn DMA duties into engineering, product, data, commercial, and reporting controls; keep competition-law analysis as a separate facts-and-effects assessment. |
|---|
| Core obligations | Designation decision, CPS inventory, Article 5/6/7 matrix, implementation measures, testing, user-flow evidence, request logs, raw data, annual Article 11 report updates, and non-confidential summary. | Market definition, internal strategy and commercial records, contracts, pricing or ranking evidence, economic analysis, complaint or investigation materials, commitments, remedies, and authority or court correspondence. | Evidence can overlap, but label it by legal purpose so Article 11 reporting material is not treated as a full antitrust case file. |
|---|
| Evidence record | Article 11 requires a compliance report and non-confidential summary within six months after designation, then updates at least annually. | No equivalent annual antitrust report is created by the DMA comparison; timing depends on the investigation, merger-control, complaint, commitment, remedy, court, or independent review process. | Calendar Article 11 separately from competition-law matter deadlines and do not let annual DMA reporting become the only antitrust review trigger. |
|---|
| Timing and deadlines | DMA non-compliance can lead to Commission non-compliance decisions, fines up to 10% of total worldwide turnover, up to 20% for repeated same or similar Article 5/6/7 infringements for the same CPS within the specified period, and periodic penalty payments up to 5% of average daily worldwide turnover per day. | Competition-law sanctions and remedies follow the applicable antitrust, merger, authority, court, or settlement route for the specific case and should not be described with DMA caps unless the DMA is actually engaged. | Write separate penalty exposure lines: DMA Article 29-31 exposure for gatekeeper non-compliance, and competition-law exposure for the specific market-conduct matter. |
|---|
| Enforcement | DMA records can share underlying product facts with competition-law files, especially for ranking, access, data, interoperability, steering, and business-user treatment. | Competition-law files can reuse the same product facts, but must still state the market-conduct theory, factual record, effects, defences, procedural posture, and remedy path. | Use one facts repository if helpful, but keep two conclusions: DMA compliance status by obligation and CPS, and competition-law assessment by conduct and market issue. |
|---|
| Overlap and reuse | Shared facts can sit in one evidence repository, but the file should still separate DMA obligations from competition-law theories. | The same product change may be relevant to both regimes, yet each regime needs its own legal test, authority, and record of assessment. | Re-use facts once, then write two legal conclusions so the comparison stays informative instead of repetitive. |
|---|
| Practical decision rule | Start with the designation decision and core platform service list to see whether the DMA applies. | Then test the conduct, agreements, dominance, or effects issue to see whether competition law also applies. | If both tests are satisfied, keep the DMA control plan and the antitrust assessment in separate workstreams and separate records. |
|---|