Recalls and Field Safety Corrective Actions (FSCA) in Iran

1. Key takeaways

Recalls and field safety corrective actions (FSCA) in Iran are executed by the local authorised representative, with the manufacturer providing technical and documentary support. GRZAN’s assessment is that the execution difficulty of a recall lies in the last mile — whether the notification actually reaches every using institution, whether the recalled units are physically retrieved, and whether the disposal is documented. If the first three steps are not done well, even a voluntary recall can be assessed as poorly handled. A recall that looks correct on paper can therefore still fail in practice if the final links of the chain are weak, and this is precisely where the local execution capability matters most, because everything that happens in the last mile happens inside Iran, out of the manufacturer’s direct reach. The last mile is also the part of the process that no remote team can cover: retrieval happens inside hospitals, clinics and distribution channels in Iran, and every unit that cannot be traced back is a gap in the record that the authority will ask about when the action is reviewed. This is why the recommendations below concentrate on preparation and records rather than on the recall itself.

2. Legal basis

1. Obligation to cooperate in recalls and market surveillance: the local entity bears the obligations of recall execution and cooperation with market supervision — see public industry sources; the official Iranian document number has not been published through public channels, and this is a practical estimate. Companies should treat this allocation of duties as settled market practice and fix it in writing with the local party, since it cannot be verified against a publicly citable provision.
2. Law on the Administration of Medical, Pharmaceutical, Food and Beverage Affairs, FAOLEX LEX-FAOC227692, dated 1955-06-20, Article 3 (prohibiting unauthorised changes to composition or labelling) and Article 11 (penalties). These provisions are the statutory foundation on which corrective actions rest: a product that has drifted from its approved composition or labelling is exposed under the same articles that govern the original approval.
3. Traceability system support: the TTAC traceability and authenticity verification system can provide batch and distribution data that supports precisely targeted recalls — this is a practical estimate. Its usefulness in a recall depends on whether the identification and data reporting obligations were fully implemented when the product first entered the market.

3. Expert insights

Insight one: the classification determines the intensity of the corrective action. Class I (may cause serious harm to health or death), Class II (may cause temporary harm to health) and Class III (unlikely to cause harm to health) each carry a different scope of action and a different degree of urgency. The classification decision requires the manufacturer’s technical judgment, and that judgment must be delivered within the shortest possible time, because every downstream step — the scope of notification, the speed of retrieval, the depth of follow-up — depends on it. A delayed or hedged classification does not merely slow the recall; it makes every later step harder to defend, because the authority reads the scope and speed of the action as evidence of how seriously the event was taken.

Insight two: TTAC data makes precisely targeted recalls possible. If identification and data reporting were fully implemented at the time of market entry, a recall can be located batch by batch down to specific distribution channels, instead of being broadcast across the entire market. This is the post-market return on the pre-market investment: the traceability infrastructure built before registration is what converts a blanket recall into a targeted one, and the difference shows up directly in cost, disruption and the confidence the authority places in the action.

Insight three: a closed loop of records is the foundation for exoneration. Records of notification dispatch, quantities retrieved, method of disposal, and follow-up on unretrieved units must all exist in writing. When records are missing, even a voluntary recall can be assessed as improperly handled, because the authority has no way to verify that the action was actually carried out and completed. The record set, not the intention behind the recall, is what the authority reviews, and it is also what protects the company if the effectiveness of the action is later questioned. A template-based record discipline, applied from the first notification onward, keeps the file complete without extra work accumulating at the end.

4. Practical recommendations

1. Prepare a recall plan in advance: fix the classification criteria, the decision chain, the notification templates and the retrieval process before any event occurs, so that execution does not start from zero under time pressure and nobody has to invent a procedure while the clock is running.
2. Use TTAC data to locate batches: implement the recall by batch rather than across the whole market, reducing cost and disruption while improving the traceability of the action and the credibility of its reporting.
3. Build closed-loop record templates: standardise the four categories of records — notification, retrieval, disposal and follow-up — so that every recall automatically produces a complete evidence file without relying on individual diligence.
4. Agree on the executing obligations and timelines of the local party: specify the concrete recall cooperation duties in the contract, so that the last mile is contractually secured rather than left to improvisation when an event actually happens, and so the drill in the checklist below tests the plan rather than the paperwork.

5. Verification checklist

• □ A recall plan has been prepared, containing classification criteria, the decision chain and notification templates
• □ It has been confirmed that TTAC data can be used to locate distribution batch by batch
• □ Record templates for the four categories — notification, retrieval, disposal and follow-up — have been established
• □ The agency contract specifies recall cooperation obligations and timelines
• □ A recall drill has been carried out at least once and documented

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 adverse event reporting and recall coordination with IFDA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com