Iran Registration Code (IRC) Explained: Identification, Foreign Exchange and Customs

1. Key takeaways

The Iran Registration Code (IRC) is the sole identity marker through which Iran manages medical devices. It is granted on the combination of “product plus manufacturer” and is designed as a common primary key running through four stages: registration, identification, foreign exchange and customs clearance. GRZAN must flag one point with particular emphasis: obtaining an IRC does not mean the product can be imported. Imported devices must additionally complete identification code registration through an Iranian importer, and until that step is done, the IRC is in a suspended state, hidden from the imed.ir site, and removed from the foreign-exchange allocation list reported to the Central Bank of Iran. This is the most distinctive institutional design separating Iran from other Middle East markets. It means the code functions less like a trophy at the end of a process and more like a switch that subsequent actions must actually turn on. Companies that plan only to the point of code issuance routinely discover that their goods wait at port and their payment flows stall, not because anything failed at the registration stage, but because the two downstream steps were never assigned, scheduled or verified. Treating identification registration and foreign-exchange linkage as formal project milestones, with owners and deadlines, closes that gap. For budgeting purposes this means the IRC should be costed as the beginning of a sequence rather than as its end, with the two follow-on actions planned, owned and tracked like any other project deliverable.

2. Legal basis

1. The IRC and identification code registration system: administered by the IFDA General Directorate of Medical Equipment and Supplies (IMED) through the imed.ir portal; for items whose identification code registration is not completed, the IRC is suspended, the item is hidden on the site, and the item is removed from the foreign-exchange allocation list reported to the Central Bank. This mechanism is recorded in public industry databases covering the Iranian pathway; no official Iranian document number has been published through open channels, so this is a practical estimate. Public industry records are, in this area, the only systematic source available to foreign applicants, and they should be preserved with their retrieval dates.
2. The TTAC tracing and authenticity verification system carries the identity, registration code and traceability functions and is linked with the IRC/GTIN.
3. The Law Concerning the Regulations on Medical, Pharmaceutical and Food and Beverage Affairs, FAOLEX LEX-FAOC227692, 1955-06-20, Article 3 (the prior-approval principle).

3. Expert insights

Insight one: the IRC is a “switch”, not a “certificate”. In Iran, the force of an IRC is actually switched on by 2 subsequent actions: identification code registration and foreign-exchange allocation. If a company obtains the IRC but does not push the local importer to complete identification code registration, the result is a triple standstill — “the code is in hand, the goods cannot enter, and the foreign exchange cannot be drawn”. Each of the three failures feeds the others, and none of them is visible from outside the country, which is why they tend to persist until someone actively checks the status of the item on the official systems. The lesson is organisational rather than technical: the actions after issuance must be contracted, scheduled and verified with the same rigour as the submission itself. The three failures also share one root cause — the handover between the foreign applicant and the local importer — so contract design is the cheapest point of prevention.

Insight two: the foreign-exchange stage is the most easily overlooked link in this chain. Iranian imports depend on the foreign-exchange allocation of the Central Bank, and the allocation list is drawn directly from the list of identified items. This means compliance actions and the availability of funds are hard-bound to each other: any interruption anywhere in the chain transmits into a commercial loss. A delay of a few weeks in identification registration can therefore cost far more than the entire compliance budget of the project, because it stalls payment for goods that may already be manufactured or shipped. Because the allocation list is compiled from identified items, the company’s own diligence on identification is, in effect, a contribution to its own cash flow.

Insight three: suspension of an IRC is immediate and public. Once an IRC is suspended, the item is hidden from the public imed.ir site. This is a visible, self-checkable signal for companies — GRZAN recommends making “whether our items can be retrieved on imed.ir” a standing monthly self-check. A monthly check converts a silent failure mode into a managed one: anomalies surface within weeks rather than at the moment a shipment is blocked, and the company retains time to remedy the position before commercial damage accumulates. A standing check also produces a dated record of visibility, which is useful evidence if a later dispute arises about when an item became unavailable.

4. Practical recommendations

1. Write identification code registration into the agency contract: state expressly that the Iranian importer is responsible for completing identification code registration, and agree a completion deadline together with liability for breach, so the obligation is enforceable rather than aspirational.
2. Institute a monthly IRC status self-check: every month, search the visibility of all company items on imed.ir and handle any anomaly immediately, while the remedy window is still open.
3. Schedule foreign exchange and compliance as one linked plan: tie the preparation point of the foreign-exchange application materials to the completion point of identification code registration, so funds are never left idle waiting on a compliance step.
4. Manage the IRC ledger on the basis of 1 code per model within change control: a new model means a new IRC, which means a new round of identification and foreign-exchange actions — schedule these in advance rather than discovering them at shipment time.

5. Verification checklist

• □ It has been confirmed that each model to be marketed corresponds to one independent IRC, recorded in the ledger
• □ The agency contract states the responsible party and the deadline for identification code registration
• □ Retrieval on imed.ir has confirmed that the company’s items are in a visible state
• □ Confirmation of the foreign-exchange allocation list linkage has been completed (handled by the local importer)
• □ A monthly IRC status self-check mechanism has been established with a named responsible person

Regulatory information verified as of October 29, 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Iranian market. Our team manages IFDA (Iran FDA) registration procedures, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com