On August 28, 2026, Argentina's telecom regulator ENACOM published Resolution 843/2026, which postpones the new RAMATEL equipment regime from September 1 to December 1, 2026. It also delays the repeal of the old Resolution 729/80 to the same date. The postponement is a chance to fix one gap before it hardens into enforcement practice: the rule puts marketplaces in the compliance chain without telling them what they must check.
What changed, and what did not
Resolution 57/2026, published February 26, 2026, replaces the 1980-era approval system with a modernized one. According to the text on Argentina's official legal database, third-party certification agencies, accredited under Argentina's national accreditation framework, will issue the conformity certificates needed for RAMATEL registration. That moves approval away from direct ENACOM processing.
Resolution 843/2026 does not change that design. According to the summary published by the importers' chamber CIRA, it was issued August 26 and published August 28. Registrations continue under the old regime, with three-year validity, until December 1. ENACOM's stated reason is that the conditions for correct implementation were not in place. The professional body COPITEC reported that the agency had acknowledged it was not ready to implement its own resolution.
The platform provision
The provision that matters for marketplaces is Article 10 of Resolution 57/2026. As reproduced in the Boletín Oficial, telecom materials sold through web portals must state the RAMATEL registration number assigned by ENACOM. The obligation covers both suppliers using their own sites and operators of portals that serve as intermediaries in the consumer relationship.
The strongest case for this rule is a good one. Uncertified radio equipment can interfere with licensed spectrum, and consumers cannot inspect a router or handset for compliance. A visible registration number is cheap, and it lets buyers and inspectors check a listing. Putting some duty on the marketplace makes sense, because the platform, not the regulator, sees every listing.
But the text as we could confirm it says who must display the number, not what a marketplace must do when a seller lists a false one. Article 12 says violations fall under existing sanction regimes, without limiting further penalties under consumer protection laws such as Laws 22.802 and 24.240. That is a general backstop, not a platform standard. The gap between "display the number" and "answer for a false number" is what the reporting on the hook describes as still undefined. We could not confirm that detail on the fetched Resolution 843/2026 page, so treat it as our reading of Resolution 57/2026's silence rather than a stated ENACOM position.
Why the gap matters
The risk is that undefined liability gets settled by enforcement. A marketplace that faces open-ended exposure for any false number has one safe response: verify every telecom listing, or delist. Neither is proportionate for a platform hosting thousands of small sellers. Large platforms can build a registry check. Smaller local marketplaces and cross-border sellers cannot easily do so, and they are the ones most likely to drop categories.
A comparison from India shows how quickly a duty like this can turn into liability. On September 17, 2026, India's Central Consumer Protection Authority fined the platform Xboom Rs 10 lakh for listing restricted drone jammers without required regulatory disclosures. As MediaNama reports, the regulator rejected the argument that the listings were only enquiry-based, and held that the platform remained responsible for ensuring that its listings complied with the law. The facts differ from Argentina's: the products are restricted, and it is a different legal regime. But it shows what happens when a regulator reads general consumer law against a platform's listings. Argentina's Article 12 leaves that door open.
What a proportionate rule looks like
The three-month window is enough time to write a workable standard. Our recommendations follow.
- Define the platform's duty as notice-and-action, not pre-screening. A marketplace should have to remove a listing promptly once it has notice that the number is false, and should not be held liable for every seller assertion in advance.
- Provide a machine-checkable registry. If ENACOM publishes RAMATEL numbers in a queryable form, platforms can run cheap automated checks, and the duty becomes concrete.
- State the safe harbor explicitly. Platforms acting on a good-faith check and removing listings on notice should be protected from sanctions for a seller's false statement.
- Sequence the rollout. The certification agencies must be registered and working before December 1, or the new number will be issued by a system that does not exist yet.
None of this weakens consumer protection. It shifts enforcement toward the seller who made the false claim, where the misconduct actually happened, and it keeps intermediaries from being turned into de facto regulators. That matters for speech and commerce alike: a platform pushed toward over-removal to avoid strict liability suppresses lawful sellers along with unlawful ones.
What to watch
Before December 1, watch whether ENACOM issues implementing guidance that addresses marketplaces directly, whether the certification-agency registry is operating, and whether the deadline holds. A second postponement would be a signal that the regime was designed faster than it could be built. If the deadline holds without a platform standard, sellers and marketplaces should expect the first test of Article 10 to come through consumer-protection enforcement.
The delay is an admission that the system was not ready. It would be worse to use the extra time to fix only the certification logistics and leave the liability question for the first enforcement action to answer.