A rule that arrived before its machinery
On 28 August 2026, ENACOM published Resolution 843/2026 in the Boletín Oficial. It moves the start of the new RAMATEL regulation, the registry through which telecom equipment is homologated for sale in Argentina, from 1 September to 1 December 2026. The resolution is dated 26 August and signed by the agency's intervenor, Juan Martín Ozores. Its stated reason is blunt. A technical report from the national directorate for spectrum engineering found that the conditions needed to meet the original deadline were not in place (Boletín Oficial, Res. 843/2026).
The case for the underlying reform is real, and it deserves a fair statement. Argentina's old framework dates to Resolution 729/80, and a modernization is overdue. Third-party certification against international standards is how many mature markets work. It can shorten approvals and put real market surveillance behind the paperwork. A regulator that tries to modernize should not be punished for it.
But the delay shows something else. The rule was written and published before the capacity to run it existed.
What Resolution 57/2026 actually does
Resolution 57/2026 was dated 24 February and published on 26 February 2026. It approved three regulations: one for RAMATEL, one for a certifiers registry and one for a testing-laboratories registry. It also created a new Registro de Agencias de Certificación de Materiales de Telecomunicaciones. These agencies issue the Certificates of Conformity needed for registration and carry out post-approval market surveillance. They must be accredited by the Organismo Argentino de Acreditación. Bodies already accredited under ISO/IEC 17065 for other schemes can get one year of provisional recognition (Boletín Oficial, Res. 57/2026).
The resolution also reaches into commerce. Article 8 restricts commercialization to materials registered in RAMATEL, and Article 10 requires online listings to show the RAMATEL number. This is where the topic touches platform liability. Marketplaces and sellers who list a router or phone without a valid number become the enforcement surface for a registry that, as of today, is not yet in force.
That is a heavy obligation to attach to intermediaries before the certifier ecosystem exists. A marketplace cannot check a number against a system that has not launched. Under the earlier timetable, sellers and platforms would have faced compliance duties from 1 September with certifiers still being stood up.
The delay is the lesser problem
The postponement itself is sensible. Three more months is better than a launch that stalls applicants. Resolution 843/2026 keeps the current system running meanwhile. Registrations continue under Resolution 729/80 and last three years. After that they must be brought into the new regime or be automatically cancelled. The repeal of the older rules also moves to 1 December (DPL News).
The deeper problem is process. COPITEC, the telecom engineering professional council, has filed a contentious-administrative nullity action with a request for a precautionary measure. It argues the resolution eliminates the technical representative, which it calls the system's central axis for more than four decades. It also argues the resolution hands public functions to private bodies without equivalent professional oversight, and that it raises costs and complexity. COPITEC says ENACOM granted no hearing or dialogue and rejected its claim only after the administrative route was exhausted (DPL News, COPITEC filing).
The account that prompted this article adds that ENACOM's lawyers told the federal courts about four days earlier that the system would start on 1 September, before the agency itself postponed it. That exchange is reported by deradios.com, which does not name the court, and we found no court ruling on the injunction. Readers should treat the report of the court exchange as lightly sourced.
What proportionate design looks like
The defensible core of COPITEC's complaint does not need a court to be right. Whether professionals should remain in the loop is a genuine policy question. A better answer to it is a published draft, a comment period and a regulatory impact assessment. Those steps would have exposed the readiness gap before February, not after August.
There is also a proportionality point for the open internet. Putting RAMATEL numbers on every online listing makes intermediaries a compliance checkpoint. That can be reasonable for safety-critical radio equipment. It is far less defensible if the registry is unavailable, or if a platform is penalized for a seller's invalid number it had no practical means to verify. Liability should follow a working verification mechanism, not precede it.
We would suggest three things for the period up to 1 December:
- Publish the readiness criteria that the spectrum directorate's report found unmet, so applicants and platforms can see what must change.
- Open a short consultation on the technical-representative question and the certifier-accreditation pipeline.
- Confirm in writing that platforms will not face liability for listings until a public lookup of RAMATEL numbers exists.
The risk of getting this wrong is practical. Importers face a regime they cannot yet navigate, small sellers face uncertainty, and consumers face delays on new devices. Regulators also lose credibility when a rule's own preamble concedes it was not ready.
Bottom line
ENACOM was right to delay and right to modernize. It should now do the work that should have come first: consult, assess impact and build the verification infrastructure. Doing that would reduce the litigation risk and keep a safety regime from becoming an access barrier.