Iran TTAC Track-and-Trace System: Labelling, Scanning and Data Reporting in Practice

1. Key takeaways

The Iranian Food and Drug Administration operates a track-and-trace and authenticity verification system (TTAC) that carries the identity, registration code and traceability functions, linked with the Iranian Registration Code (IRC) and the commodity code. GRZAN’s judgment is that TTAC is not an accessory task to be handled after registration is complete; it is a functional component of market authorisation itself. Products whose labelling and data integration are not completed are identified as abnormal in the circulation stage, which in turn affects channel sales and the product’s subsequent regulatory evaluation. The system operates through the portal ttac.ir and touches three concrete, separable actions: placing traceable codes on the packaging, scanning during circulation, and reporting batch and flow data to the system. All three are performed inside Iran by the local importing enterprise, while the manufacturer’s contribution is accurate coding data and packaging design support. Companies that plan packaging and coding late — after artwork is locked and cartons are printed — incur redesign costs and risk circulation interruptions. GRZAN’s recommendation is to reserve space for traceability markings at the label design stage and to contract the data reporting duties explicitly.

• TTAC is the IFDA-level identity, registration code and traceability system, with the portal at ttac.ir.
• TTAC is linked with the IRC and the commodity code, and functions as a practical component of market authorisation.
• Products without completed labelling and data integration are flagged as abnormal in circulation, affecting sales channels and regulatory evaluation.
• Labelling, scanning and data reporting are three separate actions, each of which must be implemented; none can substitute for another.
• All three actions are executed inside Iran by the local importing enterprise; the manufacturer supplies coding data and packaging design support.

2. Legal basis

The requirements described here derive from the TTAC system itself, from the linkage mechanism between the IRC and identification code registration, and from the general authorisation requirement of the 1955 law. The items below state each basis and its verification status.

1. TTAC track-and-trace and authenticity verification system (the health-goods tracking and authenticity system at IFDA level): the identity, registration code and traceability system of the Iranian Food and Drug Administration, with the portal at ttac.ir — see public industry database records of the Iranian pathway; the official Iranian document number has not been released through public channels, so this item is a practical estimate.
2. Linkage mechanism between the IRC and identification code registration — this is a practical estimate.
3. Law on Regulation of Medical, Pharmaceutical and Food and Beverage Affairs, FAOLEX LEX-FAOC227692, dated 20 June 1955, Article 3.

3. Expert insights

Insight 1: the traceability system performs the functions that UDI performs in other markets. Iran has not yet established an independent mandatory UDI regime, and the combination of TTAC with the IRC and the identification code in practice carries the duty of product traceability. Companies planning their packaging should therefore reserve space to carry the traceability markings from the outset. Treating TTAC as an Iran-specific curiosity and designing labels purely to export-market rules leads to redesigns, reprinting and relabelling after launch — costs that are trivially avoidable at the artwork stage and disproportionately expensive afterwards. The earlier the code position is fixed in the layout, the fewer parties have to be consulted when a change is needed, and the lower the chance that a late artwork revision breaks the link between the printed code and the data submitted to the system.

Insight 2: labelling, scanning and data reporting are 3 independent actions. Labelling means embodying the traceable code on the packaging; scanning means recording scans during circulation; data reporting means submitting batch and flow data to the system. The three need to be implemented separately, and none of them can be omitted. A perfectly printed code that is never scanned, or a scan process without data submission, leaves the product appearing abnormal in the system. Companies should therefore verify all three legs end to end rather than assuming that a finished label equals a working traceability chain.

Insight 3: the executing party is the local importing enterprise. All three actions take place inside Iran and are operated by the importer. The manufacturer’s duty is to provide accurate coding data and packaging design support — which means the quality of the traceability chain depends on the quality of the data handover between the two parties. A structured data package, with an agreed format and a change-control process whenever models or batch structures change, is what keeps the system record consistent with what is physically in the market. Where the handover is informal, discrepancies between the printed codes and the reported data appear quietly, and they surface only when the product is flagged as abnormal at a channel checkpoint — by which time the correction costs far more than the data discipline would have.

4. Practical recommendations

• Reserve traceability marking space in the packaging design: plan the code position at the label and outer-carton design stage, to avoid artwork revisions after launch.
• Build a coding data delivery list: hand the local importing enterprise a standard data package mapping models, batches and codes.
• Agree data reporting responsibility and deadlines: state in the agency contract which party reports TTAC data and within what time limits.
• Include TTAC status in monthly self-checks: review it together with the IRC status so that both stay synchronised.

5. Verification checklist

• □ The packaging design reserves space for the traceable code marking
• □ The model–batch–code mapping data package has been delivered to the local importing enterprise
• □ The agency contract states the responsible party and deadline for TTAC data reporting
• □ TTAC status is included in monthly self-checks, reviewed together with IRC status
• □ A flow-record scheme covering the route from factory exit to end use has been designed

Regulatory information verified as of 29 October 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 coordinates local import arrangements, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com