A TAREKS application is a conformity declaration submitted before the customs declaration, supported by documents proving the product meets its technical regulation. The quality of the application determines two things: how fast the transaction moves and what the risk analysis decides. Verify the relevant annual communiqué annex through the GTİP code, upload the core evidence of the technical file (declaration of conformity, test reports, certificates and labelling information) so that it matches the actual shipment, and plan the declaration flow around the outcome. If the risk analysis returns no-control-needed, customs formalities continue on that result; if a document review or physical inspection is selected, the goods wait at customs until the assessment completes, and that waiting generates warehouse cost and calendar risk. The application cannot be retrofitted after the shipment arrives; the system is designed to produce an outcome before the declaration.
Every business that wants to import into Türkiye a product covered by the product safety and inspection communiqués passes through the TAREKS gate before the customs declaration. TAREKS is the Ministry of Trade's risk-based product safety inspection system: the importer declares through the system that the product conforms to the applicable technical regulation, uploads the supporting evidence file, and the system runs the application through a risk analysis that decides which route the transaction will follow. The outcome takes one of three shapes: a no-control-needed decision lets the declaration flow continue; a document review puts the file in front of a customs technical unit; or a physical inspection sends a product sample to laboratory analysis. This article walks through how a TAREKS application is built, what quality of evidence each document must carry, how the risk analysis operates, and how the application binds into the shipment timetable. Clinical trial and laboratory product scenarios are used as running examples, but the same discipline applies to every product group in scope.
Who is this for?
This guide is written for anyone importing, or planning to import, products covered by the product safety communiqués. E-commerce and retail companies selling regulated consumer products; sponsors and CROs running clinical trials; distributors supplying laboratory consumables, reagents and equipment; medical device and IVD representatives; customs brokers; and depot and logistics teams coordinating the operation all pass through the same process. Procurement and supply planning teams should read it too, because the route the risk analysis opens directly shapes the delivery timetable and the total landed cost. Quality teams on the manufacturer or exporter side also benefit: the TAREKS evidence set originates from the manufacturer's technical file, and an unprepared manufacturer file leaves the importer exposed at the border. Ultimately the conformity declaration is the importer's responsibility, and this guide explains the operational counterpart of that liability.
Which products does it cover?
The scope is drawn each year by the annexes of the product safety and inspection communiqués published in the Official Gazette, which list controlled products by GTİP code. The families encountered most often in practice are electrical household and office equipment, lighting products, toys and childcare articles, textile and leather goods, personal protective equipment, pressure equipment, construction materials, machinery and spare parts, packaging and food-contact materials, and certain chemical preparations. In a clinical research context, laboratory instruments, measuring equipment and regulated products brought for site use meet the same assessment logic, while medical devices follow a dedicated communiqué and TİTCK registration. Whether a product is in scope is answered not by its commercial name but by the position of its GTİP in the current communiqué annexes. Any product with a plausible scope match must be checked before dispatch; for products outside every annex, an out-of-scope declaration route exists.
When does it apply?
A TAREKS application is made before the declaration, for every free circulation entry of products in scope. Beyond that baseline, several situations make the application more critical than routine. If the product is being imported for the first time and the importer has no history in the system, there is little data to pull the risk score down. If the importer or manufacturer carries a record of previous nonconformity, the probability of inspection rises. If the product sits under a GTİP newly added to a communiqué annex, application practice may not have settled yet. If the same product ships under different GTİP codes, scope must be re-verified for each declaration. If the country of origin changed, the manufacturing site changed, or the technical specification was revised, the evidence set of the previous application loses validity. And in peak-season planning, booking tightly timed transport on the assumption of a no-control result creates serious delay risk if a document review is drawn; timing must carry buffers against every scenario.
Legal framework and authority
The legal backbone of the system combines the law governing the preparation and application of technical legislation on products, the council of ministers decision on technical regulations and standardization in foreign trade, and the product safety and inspection communiqués published annually under that framework. The annual communiqués are issued as a family, published in the Official Gazette in December of the preceding year and entering into force at the start of the new year; each communiqué annex lists the GTİP codes in scope and the technical regulations applicable to the product. The competent authority is the Ministry of Trade; the system runs through the Ministry's product safety portal and outcomes are integrated into customs processing. The Ministry's directorate general for product safety publishes communiqué announcements, guiding documents and current annexes on its pages, while the TAREKS help portal offers screen-by-screen guidance for the application steps. Both sources must be checked in their current form before applying, because annex lists and application practice can be updated during the year.
Step-by-step process
- Confirm the product's GTİP from your classification file; if the position is uncertain, settle classification first, because the TAREKS route opens through the GTİP code.
- Screen the GTİP against the current year's communiqué annexes; note which communiqué covers the product and which technical regulation applies. If several communiqués are candidates, assess each one separately.
- Translate the requirements of the relevant technical regulation onto the product: which safety parameters, which label information and which conformity assessment route apply.
- Collect the evidence set from the manufacturer: declaration of conformity, test and inspection reports, valid certificates, technical file summaries and label samples. Check that documents match the product model, version and production site.
- Create the conformity declaration application in the TAREKS portal; enter product, GTİP, quantity and technical data consistently and upload the documents.
- Track the risk analysis outcome: carry a no-control-needed decision into the declaration flow; prepare for the additional steps a document review or physical inspection requires.
- If control is selected, run communication with the customs technical unit through a single point of contact, respond to document requests quickly and verify the storage conditions of the goods.
- Record the outcome in the shipment file; archive the risk result, evidence set and remaining obligations as the reference for the next application.
- Re-verify the product's scope status at each annual communiqué change and refresh the evidence set.
Document checklist
- GTİP classification note and a copy of the current communiqué annex page.
- Manufacturer's declaration of conformity, signed, matching the product identity and version.
- Safety test reports and inspection records from accredited laboratories.
- Valid certificates, according to the conformity assessment programmes mandated in practice.
- Technical file summary or data sheet, with product, model and version identifiers.
- Label and instruction samples, including the mandatory Turkish-language information.
- Manufacturer and, where applicable, authorised representative identity and address records.
- Purchase documents: proforma or invoice, with a product description consistent with the declaration.
- Shipment details: quantity, carton and marking plan, batch numbers where present.
- Records of previous applications and outcomes, showing the product's history.
Parties and responsibilities
| Party | Responsibility |
|---|---|
| Importer | Primary owner of the conformity declaration; builds the evidence set and tracks the outcome |
| Manufacturer / exporter | Supplies the technical file, test reports and declaration of conformity in versions matching the product |
| Customs broker | Ties the declaration flow to the TAREKS outcome, cross-checks the scope verification |
| Customs technical unit | Runs the document review and physical inspection, requests missing items |
| Sponsor / CRO | Carries study intent and exemption options into the file for research products |
| Quality unit | Manages evidence versions, outcome records and annual updates |
The roles can merge in small organisations, but each responsibility needs a written owner. The conformity declaration is given in the importer's name, and whatever the outcome, responsibility for placing the product on the market stays with the importer. A broker can run the application technically; the authenticity of the evidence and its match with the product are never delegated. Spotting a missing or expired manufacturer document is the importer's checkpoint.
Exceptions and edge cases
Not every product is in TAREKS scope, and not every product in scope follows the same route. Products whose GTİP appears in no current communiqué annex are handled with an out-of-scope declaration, a separate notification type carrying reasoning rather than evidence. Consignments for personal use, without commercial quantity or character, and passenger accompanying goods can fall under exemption; the boundary looks at genuine intended use more than formal labels. Imports for research and development purposes are exempt on the condition that the product is not placed on the market and is used for the stated purpose; breaching that condition produces retrospective sanction. Fair and exhibition goods are assessed with temporary character and acquire an exit obligation at the end of the period. The most frequent edge case is a multi-function product relating to more than one communiqué; there, the most comprehensive technical regulation governs, and where necessary a separate assessment is made under each communiqué. Sample consignments are not automatically exempt either; the commercial value, quantity and recipient of the sample are all open to question.
Common mistakes
The most common mistake is deciding scope from last year's communiqué annex; the annexes are republished every year and the GTİP lists can change. The second is uploading the manufacturer's generic catalogue documents as evidence; the system expects specific documents matching the product model and version. The third is taking the declaration of conformity from an outdated version that no longer matches the product. The fourth is neglecting mandatory Turkish-language information on labels; that deficiency can be a direct nonconformity ground in a document review. The fifth is planning tightly timed transport before the risk outcome arrives; the plan collapses if control is selected. The sixth is reusing the evidence set for every shipment without capturing product revisions. The seventh is leaving application records in email threads instead of binding them to a corporate archive; failing to show the application history weakens the defence in an audit.
Important notice
This article is general information, not legal or customs advice; for the TAREKS scope and application content of a specific product consult a licensed customs broker and verify the current communiqué texts and guiding documents on the Ministry's official pages. GTİP codes and product families mentioned here are illustrative only and do not constitute classification advice; the GTİP examples are not binding. Communiqué annexes are renewed annually and must be verified against the current annexes for every application.
Frequently asked questions
How long does a TAREKS application take to conclude?
The risk analysis is evaluated by the system when the application is complete, and a no-control-needed outcome is generally produced quickly. If a document review or physical inspection is selected, the duration ties to the technical unit's working calendar, the missing-document traffic and the laboratory analysis time. Plan two scenarios therefore: a narrow timetable for the no-control flow, and a buffered timetable with warehouse and analysis allowance for the controlled flow.
Which documents must absolutely be uploaded?
The mandatory set varies with the technical regulation the product falls under, but the core evidence does not: a signed declaration of conformity, safety test reports, valid certificates, a technical file summary and label samples. The guiding documents define, per product group, which document is uploaded to which field. A missing document stalls the application or produces a nonconformity interpretation at the control stage; completing a document afterwards is not always possible.
What happens if the risk outcome is no-control-needed?
The declaration continues through customs formalities on that result and the product completes its free circulation entry. The outcome is not, however, a quality certificate that the product is safe; it means the system saw no control requirement on current risk data. The administration keeps its authority to re-examine the product in later market surveillance or post-clearance controls. That is why the evidence set must be archived fully even for no-control outcomes.
Is a new application required for every shipment of the same product?
Yes. The conformity declaration is transaction-based, and an outcome must be produced before each declaration for the relevant shipment. The evidence set and clean history of a previous application can serve as a reference in a new one and can support the risk score favourably, but they create no automatic exemption. If the product, production site or technical characteristics have changed, the evidence set must be rebuilt from scratch.
Official sources
- TAREKS Product Safety Inspection SystemTicaret Bakanlığı · verified 07 Sep 2026
- TAREKS Help PortalTicaret Bakanlığı · verified 07 Sep 2026
- Product Safety and Inspection Communiqué AnnouncementsTicaret Bakanlığı · verified 07 Sep 2026
Revision history
v1.1 · 07 Sep 2026 — Content import: external full text applied.
v1.0 · 03 Aug 2026 — Initial source-backed publication.