A six-week runway to a rule with a hole in it
On September 1, 2026, every online marketplace operating in Argentina must display a RAMATEL registration number next to every telecom equipment listing — phones, routers, IoT devices, anything requiring type approval. That obligation comes from ENACOM Resolution 57/2026, sanctioned February 24, 2026 and published in the Boletín Oficial two days later, which tore up a homologation framework that had governed the sector since Resolución 729/80 — more than four decades — and replaced it with private, ISO/IEC 17065-accredited certification bodies. Article 10 is explicit: the display duty falls on both direct sellers running their own storefronts and "intermediary portal operators" — marketplaces, in plain language.
What Article 10 doesn't do is say what happens when the number a seller posts is wrong. Article 12 folds violations into the "existing sanctions regime" plus Argentina's commercial-loyalty and consumer-protection statutes (Leyes 22.802 and 24.240), treating sellers and platforms as one undifferentiated category rather than assigning marketplaces a distinct standard of care. As El Diario 24 reported on July 19, "qué responsabilidad les corresponderá a los marketplaces cuando un vendedor informe un registro incorrecto es algo que todavía no está definido" — what liability marketplaces bear when a seller reports an incorrect registration remains undefined, with barely six weeks to go.
Steelmanning ENACOM's sequencing
There's a defensible logic to leading with a disclosure mandate before a liability regime. Regulators frequently sequence reform this way: require the data point first, observe how compliance actually breaks down in the field, then calibrate enforcement to the failure modes that show up rather than the ones a rulemaking process guesses at in advance. Argentina's general consumer-protection framework already establishes joint-and-several liability among "productor, fabricante, importador, distribuidor y proveedor" for defective goods under Ley 24.240 — a body of doctrine ENACOM could plausibly extend to marketplaces through adjudication rather than fresh rulemaking, avoiding the trap of freezing an untested liability standard into a resolution six months before anyone has seen how sellers actually game a registration-number field.
Why the gap still matters
That sequencing argument would carry more weight if ENACOM's own side of the ledger were ready. It isn't. El Diario 24's reporting notes ENACOM still has to build the computer tools needed to cross-check that RAMATEL numbers displayed on marketplaces are genuine, and to coordinate that verification with commerce and industry authorities — meaning the regulator that will eventually judge platform conduct doesn't yet have a system to establish what "false" looks like at scale. Nor is it clear how many private certification agencies will be authorized to issue the underlying approvals, or what they'll charge, per the same reporting. A marketplace the size of Mercado Libre can absorb ambiguity by over-engineering compliance; a smaller regional platform is more likely to either mass-delist telecom listings pending clarity — cutting consumer selection — or do nothing and hope enforcement lags, which is precisely the outcome a liability rule is supposed to prevent.
The uncertainty compounds with a separate legal threat to the resolution itself. COPITEC, Argentina's professional council for telecom engineers, filed an autonomous precautionary measure in May 2026 seeking to suspend Resolution 57/2026 outright, arguing the ENACOM intervention exceeded its authority by restructuring a 45-year-old system and stripping out the licensed technical representative role that anchored it. By July 20, COPITEC had escalated to a full nullity suit. Platforms are now being asked to build compliance infrastructure for a rule that a court could suspend before it ever takes effect.
The fix costs ENACOM little
We think ENACOM's underlying direction — shifting equipment approval to accredited private conformity assessment, a model most OECD telecom regulators already use — is the right call, and a disclosure mandate for registration numbers is a proportionate, low-friction way to make the RAMATEL registry actually mean something to a buyer scrolling a marketplace listing. Neither of those judgments requires leaving platform liability open six weeks out. ENACOM doesn't need a new law to close this gap; a clarifying instructivo before September 1 specifying a notice-and-takedown safe harbor — platforms that promptly remove a listing after being shown a false RAMATEL number face no Article 12 sanction for that listing — would preserve the incentive for marketplaces to build verification tooling without imposing strict liability that only the largest platform in the market could comfortably carry. Absent that, ENACOM is handing itself, and every telecom seller in the country, a compliance deadline with no compliance standard attached to it.