What changed
On 28 August 2026 Argentina's Boletín Oficial published ENACOM Resolution 843/2026, signed two days earlier. It moves the start of the new RAMATEL regulation, approved by Resolution 57/2026, from 1 September to 1 December 2026. Article 1 replaces Article 13 of Resolution 57/26. Until 1 December, registrations continue under the older Resolution 729/80 and each runs for three years. After that, holders must comply with the new rules or be removed automatically. Article 2 moves the repeal of the legacy rules (including 763/78, 729/80 and 5424/19) to the same date, according to the text reproduced by the CIRA.
The stated reason is short. A technical report from ENACOM's spectrum engineering directorate (IF-2026-81958565) found that the conditions needed to meet the original deadline were not in place, and it identified pending tasks. Marval quotes the regulator as saying the "indispensable conditions for correct implementation" were not given.
The case for the regime
The strongest argument for RAMATEL is consumer safety and spectrum hygiene. Uncertified radios, chargers and routers can interfere with licensed services and can be unsafe. Online marketplaces are now where most of that gear reaches buyers. A registry that regulators cannot enforce at the point of sale is easy to evade. Making listings show a registration number gives customs, consumer-protection offices and buyers a simple check.
That is what Resolution 57/2026 does. According to a Beccar Varela analysis, equipment sold online must show its RAMATEL registration number in each listing. The duty falls both on suppliers selling through their own sites and on owners of portals that act as intermediaries in the consumer relationship.
Where the proportionality problem sits
A listing-display duty is manageable. It is a field in a template, and a marketplace can validate the number format automatically. The risk is the open question behind it: what happens when a seller posts a false number, or none?
The sources I could reach describe the display duty. They do not describe a liability standard for marketplaces, and I found no ENACOM guidance on one. A fiberbroadband.org regulatory bulletin reports that e-commerce intermediaries have questioned the extension of their responsibilities in the equipment registry. The postponement does not answer that question. It only delays it.
There are three broad ways to settle it, and they differ sharply in cost:
- Notice-and-action. The platform removes a listing once ENACOM or a rights-holder flags it as unregistered. This is predictable, and platforms can build for it.
- Verification at onboarding. The platform checks registration numbers against the RAMATEL database before a listing goes live. That is workable only if ENACOM provides a reliable, queryable registry, and the delay suggests the infrastructure is not finished.
- Strict liability for seller violations. The platform answers for every uncertified item sold. For a marketplace with millions of third-party listings this amounts to a general monitoring duty. Large incumbents can absorb it, while smaller local marketplaces and cross-border sellers cannot.
The third path is the one a pro-innovation reading should resist. Argentina's open-market tradition depends on small sellers reaching buyers cheaply. Strict liability pushes platforms to over-remove, and the people hurt are legitimate importers whose paperwork lags the database.
EFF makes a related point about Brazil's new platform regime, urging regulators to keep prevention duties from becoming general monitoring and to treat smaller services differently from dominant ones. That reasoning applies by analogy to equipment compliance. The subject is hardware rather than speech, but the mechanism is the same: broad intermediary duties produce blunt, error-prone enforcement.
What ENACOM should do with the three months
The delay is the right call. Launching a registry the regulator itself judged unready would have created legal exposure for platforms and sellers alike. Three months is useful only if it is spent on specific work:
- Publish a liability standard. ENACOM should state in writing that marketplaces are responsible for displaying and format-checking numbers, and for acting on notice, not for guaranteeing every seller's compliance.
- Ship a public lookup. Platforms cannot verify numbers against a database that is not open to them, via API or bulk file.
- Set a grace period for enforcement. Sanctions should start only after the lookup tool has been running for a defined period.
- Consult. Resolution 843 cites an internal technical report and a legal review. A public comment round with platforms, importers and consumer groups would be cheap and would surface implementation problems before December.
The resolution itself does not commit ENACOM to any of this. I found nothing newer on platform liability in the sources available, so the question stays open as of 25 October 2026.
The bottom line
Registering telecom equipment is a legitimate aim, and putting marketplaces in the compliance chain is defensible. But the regulator has delayed the date without clarifying the burden. If 1 December arrives with a vague intermediary duty and no usable verification tool, platforms will protect themselves by delisting borderline products and sellers. A narrow, notice-based standard would achieve the safety goal at much lower cost to Argentine online commerce.