Mic Telecom Certification Services In Vietnam
Vietnam MIC telecom certification services should be managed as an evidence-to-launch project, not as a single certificate purchase. The former Ministry of Information and Communications (MIC) label remains common in searches; the current governing instruments are issued by Vietnam's Ministry of Science and Technology (MST). For a specific radio or ICT device, the regulatory path depends on the product description, HS classification, applicable QCVN technical regulations and the exact entry in Circular 36/2026/TT-BKHCN.
This page explains how to commission, control and close the work. It does not certify a device without its technical file. On 1 July 2026 Circular 36/2026 replaced Circular 29/2025 and the former sector-specific conformity procedure under Circular 30/2011; Circular 14/2026 governs conformity declarations and assessment methods from 25 May 2026.
Freeze the classification before booking tests
Do not infer the route from a Wi-Fi, Bluetooth or 5G marketing label alone. Compare the product description and HS code with both annexes and footnotes of Circular 36/2026, then map every applicable QCVN and the annex's specific conformity route. An integrated device can require several QCVNs; frequency authorization is a separate check.
Classification cannot rest on an HS code alone: verify the marketed product’s functions, technical characteristics, radio bands and the applicable QCVNs against the annex description. Under Article 5(2) of Circular 36/2026, a product subject to several QCVNs must meet each one, but assessment of the same technical requirement should not be duplicated. Record in the testing plan which existing evidence can be reused and why.
| Finding | Execution route | Evidence or stop condition |
|---|---|---|
| Annex I: high risk | For an Annex I ICT entry, coordinate the entry’s designated-body certification route, conformity declaration and imported-goods quality inspection as applicable. Check the QCVN-specific notes: note (1) can make a particular technical regulation declaration-only. | Confirm the precise QCVNs, approved assessment method and a laboratory whose recognized scope covers each test. |
| Annex II: medium risk | Follow that entry: declaration may rely on eligible certification or self-assessment supported by suitable testing; do not automatically buy designated-body certification. | Record the annex line and permissible evidence basis before selecting a provider. Imported products must meet the applicable pre-market declaration rule. |
| No reliable match or mixed features | Hold the filing decision; obtain a reasoned written classification or competent-authority clarification. | An overseas CE/FCC report or a pre-2026 approval alone does not establish the current Vietnam route. |
Four annex notes that can change the execution route
Before approving a test quote or filing strategy, capture the exact annex row, referenced QCVN and note number. These qualifications apply only where the corresponding entry or QCVN invokes them; they are not blanket exemptions.
| Specific note | Operational effect and limit |
|---|---|
| Note (1): QCVN-specific declaration only | For a QCVN marked (1), conformity certification is not required for that technical regulation, but conformity declaration still applies. Other QCVNs for the same product may follow different routes. |
| Note (3): selected short-range radio exclusions | The specified short-range radio entry excludes receive-only equipment; 2.4 GHz wideband data transmitters and 5 GHz wireless access equipment below 60 mW EIRP; specified standalone wideband/access equipment operating at 5.925–6.425 GHz; and Bluetooth/Zigbee equipment below 60 mW EIRP. The 60 mW threshold must not be silently applied to the separately described 6 GHz category. This excludes only the described entry, not other applicable QCVNs, declarations or radio-frequency rules. |
| Note (12): equipment integrated into medium-risk products | Where ICT goods in Section II of Annex I are integrated into products in Section II of Annex II, the integrated product may follow medium-risk quality-management measures, while satisfying QCVNs for the host and integrated functions. Do not automatically impose the standalone Annex I route. |
| Note (9): restrictions on test evidence | For a QCVN annotated (9), do not rely on an unrecognized/undesignated laboratory or manufacturer results. Verify recognition/designation and each QCVN’s test scope before commissioning. |
Service acceptance check: deliver an exception-by-exception routing note identifying the affected model, applicable note, test basis, certificate/declaration decision and any unresolved authority question.
Seven handoffs from intake to market readiness
The following are coordination gates, not statutory processing deadlines. Each gate produces a document that the next party can actually use.
- 1. Intake and version lock
Manufacturer freezes model IDs, hardware/firmware version, radios, bands, output power, antenna configuration, labels and importer; coordinator opens a controlled SKU register.
- 2. Rules and responsibilities
Compliance lead produces the Annex I/II row-to-QCVN matrix, applicable method, certification/declaration obligations and separate import-check decision; responsible Vietnamese organization is identified and signature authority verified. Identify the party legally responsible for the particular declaration and import activity, verify its signature authority and capacity. Do not assume every overseas manufacturer must appoint the same type of local agent. Confirm who is authorized to declare for this particular product and importer, rather than treating local representation as a uniform precondition.
- 3. Laboratory quotation and samples
Test coordinator validates accreditation/designation/recognition and QCVN scope, confirms report acceptance, sample configuration, sample logistics and retest policy before accepting any quote.
- 4. Testing and discrepancy closure
Laboratory issues traceable results for the frozen version; engineers resolve failures, and a change log records whether partial or full retesting is needed. A passed foreign test is supporting evidence only if acceptance is established.
- 5. Conformity assessment
Where required, the eligible certification body reviews evidence under the permitted method (for example Method 3 or 7 where the annex provides it); otherwise prepare the permitted self-assessment dossier. Do not confuse a lab report with a certificate.
- 6. Declaration and import interface
Responsible signatory registers the declaration under Circular 14/2026, retains the database confirmation and supporting certificate or self-assessment/test results; importer coordinates any separate state inspection under Circular 36/2026 and Decree 37/2026. For an accepted offline filing, obtain and retain the competent authority’s receipt and subsequent registration status; a database screenshot is not the only possible first proof.
- 7. Market-release gate
Release only after the route-specific evidence, declaration, applicable inspection status and conformity-mark/label controls are checked. Deliver the controlled file and a future-change trigger register.
Filing-channel contingency: Article 13 of Circular 14/2026 permits in-person or postal declaration registration with the competent local office if the national database fails or is not ready (or the designated ministry-level body where no local office exists). Under Article 7(4) of Circular 36/2026, import-quality-inspection registration during National Single Window upgrades uses the National Public Service Portal or the inspection authority’s instructions. Keep submission proof; do not equate an upload attempt with a completed registration.
Final marking gate for new conformity declarations from 1 July 2026: use the CR mark model in Annex I to Circular 14/2026, not the former MIC mark model in Annex VI to Circular 30/2011. MST confirms that the conformity mark is not an attachment required to register the declaration; it must be used before market circulation after the declaration is completed. The system-generated QR code does not generally have to be printed on the product or packaging unless a specific technical regulation or sector rule says otherwise. Check this separately from the importer’s ordinary labeling duties.
Intake package: what must be supplied
Ask for these items at kickoff; these are a practical evidence request, not a claim that every attachment is mandatory in every official filing.
- Product inventory: commercial name, all SKUs, manufacturer, origin, intended use and proposed HS code with rationale.
- Radio map: cellular/Wi-Fi/Bluetooth/RFID or other interfaces, exact bands, channel widths, power, antennas and simultaneous transmit modes. State EIRP (not only conducted power), radio variants and whether the radio is a standalone product or integrated into an Annex II host.
- Hardware/firmware and module identifiers, BOM or functional block diagram, revision history and photographs linking sample to commercial model.
- Existing QCVN, ISO/IEC, FCC or CE test reports with issuing laboratory, dates and accreditation scope; never assume automatic recognition.
- Vietnamese importer or responsible operator details, written authority for declaration signatures and destination/import arrangement.
- Labels, CR-mark artwork where applicable, user instructions and packaging versions for the marketed SKU.
- Existing Vietnam certificates, declaration confirmations, pending application IDs and shipment status, especially dossiers received before 1 July 2026.
Deliverable and evidence acceptance matrix
| Milestone | Concrete client deliverable | Acceptance test |
|---|---|---|
| Classification | Dated annex-entry/QCVN/HS route sheet with exclusions and unresolved issues. | Client can see why certificate, declaration and import inspection are or are not in scope. |
| Tests | Lab-scope approval, signed sample log and test report index. | Every applicable QCVN has traceable evidence for the correct model/version. |
| Assessment | Certificate and method where required; or authorized self-assessment file where permitted. | Issuer/method/scope match the applicable annex rather than a generic approval claim. |
| Filing | Signed declaration and national-database confirmation; import-inspection submission/status where applicable. For an accepted offline filing, obtain and retain the competent authority’s receipt and subsequent registration status; a database screenshot is not the only possible first proof. | Receipt IDs, exact model and responsible filer match across records. |
| Release | CR marking/label review, launch decision, retention folder and change register. | No open blocking tests, filing mismatches or unverified import obligations. |
Responsibilities, signatures and filing channels
| Party | Project responsibility | Legal or documentary limit |
|---|---|---|
| Manufacturer | Provide truthful technical data, controlled samples, redesign evidence and production consistency. | Supplier data does not itself discharge the declaring party’s legal duty. |
| Responsible declarant / importer (entity to be verified) | Validate capacity and authority, sign applicable conformity declaration and retain evidence; arrange import-quality checks if required. | An agent can coordinate; the legally responsible organization must be identified in the actual filing. |
| Laboratory / certification body | Issue in-scope test evidence or conformity certification under the applicable method. | Laboratory report ≠ certificate; accreditation ≠ automatically recognized for every QCVN. |
| Service coordinator | Manage scope, handoffs, discrepancies, filing receipts and release checklist. | No implication of government authority, guaranteed approval or fixed statutory timeline. |
Five failure modes that stop a launch
- Using a 2025 product-list screenshot instead of the 2026 annex and its footnotes: reclassify before paying for testing.
- Booking a laboratory merely because it advertises MIC: request its current recognition and exact QCVN test scope.
- Testing an engineering sample while shipping different antennas, RF firmware or chipset: reconcile the version and retest as needed.
- Treating certification, a declaration registration and imported-goods inspection as the same document: track three independent gates where applicable.
- Shipping because the report passed although responsible signatures, declaration confirmation or CR marking are missing: keep market release on hold.
Changes after approval: the rework decision
Circular 14/2026 Article 14 requires a fresh conformity declaration when the QCVN, registered declaration content, or relevant product functions or characteristics change. Screen all changes before distributing affected stock; the table below is a service control, not an automatic finding that every edit requires identical testing.
| Trigger | Operational action |
|---|---|
| RF band, antenna, power, chipset or firmware affecting radio performance | Quarantine affected version; reassess QCVNs, evidence and retesting; update declaration where required. |
| New model name, importer or material filing-field change | Compare recorded models and signatory; determine amendment or fresh declaration before use. |
| Revised QCVN or product-list annex | Re-run legal applicability, effective-date and transition review; verify existing certificate scope. |
| Legacy certificate or pre-July 2026 pending dossier | Check Circular 36/2026 Article 7: existing certificates/declaration acceptances run to stated expiry; applications accepted before 1 July follow the previous rules for their processing. |
Scope of this service and related Vietnam requirements
For customs, non-telecom safety or wider Vietnam product-market obligations, use the Vietnam product compliance and market-access overview. This page owns coordination from MIC/MST intake through test evidence, declaration and launch gate—not every sector's market-access rules.
Official regulatory sources
Frequently asked execution questions
- Do all devices with Bluetooth need a MIC certificate?
- No blanket rule. Check exact radio characteristics and the Annex I/II product descriptions, exceptions and footnotes; the result may be designated certification, another valid evidence route or no match under these entries. In particular, Annex notes exclude some Bluetooth/Zigbee devices below 60 mW EIRP from a specified short-range entry; this is not a universal exemption from other requirements.
- Can our FCC or CE test reports replace Vietnamese QCVN testing?
- Not automatically. Check whether the relevant testing body and report are recognized for the actual QCVN, method, version and scope. A general foreign approval is not Vietnam conformity registration.
- What happens if the shipment was registered for import inspection before 1 July 2026?
- Circular 36/2026 Article 7 preserves processing of imported-goods quality inspection registrations already received before the new circular took effect under the rules at acceptance. Preserve the dated acknowledgment and verify its scope.
- May we file the declaration before getting a certificate?
- Only if the product entry allows an evidence route that does not require that certificate and the supporting assessment is complete. When the entry demands designated certification, a self-declaration does not substitute for it.
- Does a module certificate cover a different finished device?
- Do not assume so. Recheck integrated functions, antennas, RF parameters, product model and QCVNs against the finished product; resolve the conformity route before release. For some products integrating Annex I ICT components into Annex II products, note (12) changes the risk-management route but not the duty to satisfy applicable QCVNs.
- What if the declaration database or import-inspection portal is unavailable?
- Do not skip the filing. Follow the alternative channels specified in Circular 14/2026 Article 13 for the declaration, and Circular 36/2026 Article 7(4) for applicable import inspection; retain acknowledgements and verify the filing status before release.