Starting September 1, 2026, Argentina will stop having its telecommunications regulator personally sign off on every cellphone, router, and IoT gadget sold in the country. Resolución 57/2026, published in the Boletín Oficial on February 26, 2026, replaces a state homologation regime that traces back to Resolución 729/80 with a system of privately accredited certifying agencies operating under ENACOM's new RAMATEL framework. It is, on paper, exactly the kind of deregulatory modernization this publication tends to favor. It is also missing a load-bearing piece: nobody has said who is on the hook when a marketplace listing displays a registration number that is fake, expired, or lifted from a different model.
The reform, and its real case
The case for privatizing homologation is genuine, not manufactured. ENACOM's own justification — that the change will "strengthen sector competitiveness, reduce costs, encourage investment, and promote technological innovation" — reflects a real bottleneck: a single state agency personally certifying every Wi-Fi access point, smartwatch, and Bluetooth speaker entering a market of 46 million people was never going to scale, and vendors have spent years absorbing the delay as a cost of doing business in Argentina. Letting accredited private labs handle conformity testing, while the state retains registry and market-surveillance authority, mirrors a direction plenty of mature telecom-equipment regimes have already taken. Faster approvals mean faster device launches and, eventually, more competitive prices for Argentine consumers — that's a real win worth banking.
Where the resolution stops short
Resolución 57/2026 does extend obligations to e-commerce: platforms and marketplaces — both their own storefronts and third-party sellers operating through them — must display the RAMATEL registration number assigned to each listed device. That's a sound instinct: force the paperwork into the open where a regulator, a competitor, or a customer can check it. The problem is what happens next. As Argentine outlet El Diario 24 reported on July 19, 2026, "the responsibility that will correspond to marketplaces when a seller reports an incorrect registration is something that has not yet been defined" — including cases where a listed number is simply borrowed from an unrelated, already-approved model. ENACOM, per that reporting, still has to build the IT tooling and coordinate with the Secretariat of Industry and Commerce just to verify that published numbers are real in the first place.
That is a genuine regulatory gap, not a hypothetical one. A private certifier can validate that a specific device model meets emissions and spectrum standards. It cannot stop a third-party seller on a marketplace from typing a plausible-looking string into a listing field. Under the old regime, that risk existed too, but a single state registry made spot-checking comparatively simple. Under a distributed system of private certifying agencies, with a mandated but unverifiable display field, mislabeling gets structurally easier at the exact moment enforcement gets structurally harder.
Two ways this goes wrong
Regulators overseas are wrestling with the mirror-image failure mode. The EU's Court of Justice issued a July 2026 platform-liability ruling that, per the Electronic Frontier Foundation's analysis, risks pushing platforms toward defensive over-removal and proactive monitoring obligations that chill legitimate speech and commerce alike. That's the caution Argentina should heed on the other side: strict, retroactive liability that makes a marketplace guarantee the truth of every third-party seller's registration claim would push smaller Argentine e-commerce platforms — the ones without the legal and compliance headcount of MercadoLibre — toward blanket over-caution, delisting borderline sellers, or exiting device categories entirely.
The fix is neither silence nor strict liability. It's a conditional safe harbor tied to a verifiable registry: ENACOM should ship a public, machine-readable RAMATEL lookup — an API or searchable database — so a marketplace's "display the number" obligation can be paired with a "verify the number against the registry" capability. Liability should attach only when a platform ignores a specific, substantiated notice that a listed number is fraudulent, not to the platform for a seller's initial fraud. That's the same architecture — notice, verify, act — that underlies most functioning e-commerce product-safety regimes, and it avoids both the CJEU's proactive-monitoring trap and ENACOM's current vacuum.
The other fight, and why it's separate
The reform faces its own legal test. Copitec, the Professional Council of Telecommunications, Electronics and Computing Engineering, filed a contentious-administrative nullity action with a precautionary measure on May 18, 2026, seeking to suspend Resolución 57/2026 before it takes effect. Copitec's case, as its own July 20 update confirms, centers on the elimination of the mandatory "representante técnico" role that anchored homologation filings for over four decades, and on the claim that ENACOM improperly delegated indelegable public functions to private certifiers. As of that filing, no court has suspended the resolution, and September 1 remains the operative date.
That dispute is worth watching, but it's a professional-gatekeeping fight, not a consumer-protection one — restoring a mandatory engineer-of-record requirement wouldn't close the marketplace-liability gap this piece is about. ENACOM can lose the Copitec case, win it, or settle it, and the fake-registration-number problem persists regardless. The agency has four weeks before implementation to publish the piece its own reform is missing: a public verification tool and a notice-based liability standard for the platforms it just handed a new, unenforceable obligation.