CERT – Centre d'Expertise et de Régulation des Télécommunications – is the body responsible for type approval of wireless, telecom, and ICT equipment in Tunisia. Phones, routers, Bluetooth products, IoT terminals – any product with RF functionality – needs type approval for market circulation.

CERT and vehicle CETV‑VN whole‑vehicle certification are two separate systems. Whole vehicles follow the VN system – in‑vehicle Bluetooth and other wireless components fall under CERT – they cannot be exempted simply because the vehicle has a certificate. Understanding this boundary is essential for realistic timeline planning.

1. Tunisia CERT Certification – Stage‑by‑Stage Timeline

Stage 1: Document preparation and local submission

Typical duration: 1–2 weeks. CERT requires applications to be filed by a Tunisian locally registered entity – overseas companies must use a local agent or importer.

Required documents:

·Product specifications, user manual, circuit diagrams, PCB layout, BOM.

·Internal/external photos, Declaration of Conformity (DoC).

·RF, EMC, and safety test reports.

·Cellular products: GSMA TAC letter – TAC letters have validity periods – cannot be reused indefinitely.

Missing parameters cause direct rejection and supplementary submissions – extending the timeline.

Stage 2: Samples and reports

CERT does not mandate local testing for all products – ordinary wireless ICT devices can use test reports from overseas accredited labs. Only special categories require local testing in Tunisia.

If samples are needed, temporary import is possible – not necessarily high customs duties – but allow 2 weeks for customs clearance. Tunisia prohibits 2.4 GHz Channel 14 – most chips disable it by default – but confirm channel configuration at development stage – avoiding rejection.

Stage 3: CERT testing and assessment

If local testing is required: 4–6 weeks – including lab scheduling and sample debugging.

Accepted overseas reports allow fast‑track approval – this is an official CERT path – not a secret agent "green channel." Many projects do pre‑testing – identifying RF and EMC issues early. Pre‑testing is a commercial value‑added service – not mandatory – but significantly reduces formal‑test failure rework.

Stage 4: Review and certification

After testing/assessment: CERT internal review and issuance – ~2 weeks. Certificates have no fixed expiry – but when local standards are updated, old certificates may restrict new batches.

Hardware or RF firmware changes: the original certificate is invalid – must re‑apply – cannot be amended. Mass‑production samples must match the tested version – avoiding market‑surveillance discrepancies.

  2. Total Timeline and Variables

·New first‑time certification: typically 6–8 weeks.

·Fast‑track with accepted overseas reports: can be compressed to ~10–15 days – not for first‑time new products.

Most delays are not from official review efficiency – but document errors and test failures. Complete document checks and sample pre‑reviews help you hit estimated timelines.

  3. Key Documentation Points

·User manual: clearly state RF parameters.

·Spec sheet: accurate bands and transmit power.

·Circuit diagrams, PCB, and component list: all must align.

·DoC: must be signed by a Tunisian locally registered entity – overseas manufacturer signatures are not accepted – you cannot directly reuse EU CE DoC documents.

Non‑compliant documents = application rejected.

  4. Retesting Impact on Timeline

If formal testing fails: generally full retesting after remediation – adding 2–4 weeks. Freeze firmware versions during testing – no OTA changes – avoid version inconsistencies.

  5. Difference from Vehicle VN Certification

VN (Vehicle Notification) is a CETV‑issued whole‑vehicle announcement – valid for 1 year – covering the complete vehicle.

In‑vehicle wireless components still require separate CERT – the vehicle certificate does not cover them. Run the two projects in parallel.

  6. Practical Implementation Advice

·Work with an agent with a Tunisian locally registered entity.

·Confirm RF channel configuration upfront.

·Pre‑check all documents.

·Allow 8–10 weeks for project scheduling – including buffer for revisions.

  7. Certificate Changes and Transfer Rules

·Changing product model, manufacturer, or hardware → new application.

·Certificate is tied to the applicant – changing importers: certificate cannot be transferred – re‑apply.

  8. North African Multi‑Country Project Reference

·Morocco ANRT, Egypt NTRA – similarly require local agents – accept overseas reports.

·For North African market coverage, unify core documents – enabling reuse across countries – reducing duplicate work.

  9. Choosing the Certificate Holder

·Importer‑held certificate: smooth shipping – but tied to that importer.

·Agent‑held certificate: more flexible – each shipment needs association.

Choose based on your local sales model.

  10. Certificate Verification and Mass‑Production Reminder

·CERT certificates can be verified on the official system.

·Even without a fixed expiry – product changes invalidate the old certificate – check system status before shipping.

·Mass‑production samples must match the tested version – avoiding market‑surveillance risks.

  11. What a Service Provider Can Offer

·Liaison with Tunisian local‑agent resources.

·Document pre‑review, sample pre‑checks, progress tracking.

·For first‑time projects, most issues come from documentation gaps – upfront review reduces rework.

For Tunisia CERT certification timelines, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.