author
On June 26, 2026, Vietnam’s Ministry of Industry and Trade (MOIT) issued Circular No. 37/2026/TT-BCT, setting a new compliance condition for imported smart locks from October 2026 onward: products must include an offline Vietnamese speech recognition module and pass the VNTA-2026 voice robustness test. For smart lock brands, importers, OEM manufacturers, firmware teams, and certification-related service providers, this is worth close attention because it shifts market access from hardware-only compliance toward localized AI capability and testing readiness.

According to the provided information, the new requirement applies to all imported smart locks. From October 2026, these products must integrate an offline Vietnamese speech recognition module. They must also pass the VNTA-2026 voice robustness test, which includes dialect, noise, and low signal-to-noise ratio scenarios.
The rule was issued by MOIT on June 26, 2026 under Circular No. 37/2026/TT-BCT. The stated policy direction is to strengthen adaptation to Vietnam’s local AI ecosystem. The provided information also indicates that this will significantly increase firmware development and certification costs for Chinese OEM manufacturers.
From an industry perspective, import-focused businesses may be affected first because the rule changes the practical threshold for entering the Vietnamese market. The issue is no longer limited to shipping a connected lock with standard smart functions; imported models will need a built-in offline Vietnamese voice capability and test readiness tied to VNTA-2026. What deserves closer attention is whether current product lines can still be placed into the market without firmware or feature adjustments.
Analysis shows that manufacturing-side pressure will likely concentrate in firmware development, feature integration, and validation. The requirement is specifically tied to offline Vietnamese speech recognition and robustness under dialect, noise, and low-SNR conditions. For OEM manufacturers, that points to additional adaptation work inside the product software stack rather than a simple documentation update. The cost impact mentioned in the provided information also suggests that engineering schedules and certification preparation may need to be reworked.
Observably, service providers involved in testing, certification preparation, and compliance support may see a more central role in project execution. Because the rule links import eligibility to a named robustness test, affected companies will need to pay closer attention to test preparation, required evidence, and the alignment between technical implementation and certification expectations. The business impact here is likely to appear in submission timing, product readiness reviews, and delivery planning.
For procurement teams, distributors, and downstream channel partners, the main concern is not only product specification but also shipment timing and model eligibility. Analysis shows that any product family intended for Vietnam may need a clearer distinction between compliant and non-compliant versions once the October 2026 requirement takes effect. That makes customer communication, order confirmation, and model-level planning more sensitive than before.
The confirmed facts establish the core requirement, but companies should keep watching for any later official clarification around implementation language, testing interpretation, or procedural details. This is especially relevant where compliance depends on how technical functions are assessed in practice rather than only how they are described on paper.
What deserves closer attention is which smart lock models are intended for import into Vietnam after October 2026. Businesses with active or planned shipments should identify the product lines that may require Vietnamese offline voice integration, then compare those requirements against current firmware capability and certification status.
Analysis shows that the policy signal and business readiness are not the same thing. The rule indicates a local AI adaptation direction, but companies still need to determine what is required to make a given model commercially ready for import under the new standard. That means internal teams should avoid treating the headline requirement as complete operational guidance without checking how it affects engineering, testing, and document preparation.
For exporters, OEM suppliers, and import-side partners, the immediate practical issue may be coordination. Businesses should pay close attention to delivery cycles, product version control, supporting compliance materials, and how requirements are communicated to customers and partners. The cost increase mentioned in the provided information also makes it important to review whether existing commercial commitments still match expected development and certification workloads.
Observably, this development can be read as more than a narrow product rule, but it should not yet be overstated beyond the facts provided. It is more appropriate to understand this as a concrete regulatory change with a broader policy signal: Vietnam is tying imported smart lock access to localized offline AI functionality and resilience testing. At the same time, the available information does not by itself establish how quickly different market participants will adapt or how widely the requirement may influence adjacent product categories, so continued observation remains necessary.
In practical terms, this is a short-term compliance change with longer-term strategic meaning. The short-term effect is direct: imported smart locks targeting Vietnam from October 2026 must meet a localized voice requirement and pass a named robustness test. The longer-term signal is that localization and embedded AI suitability may carry more weight in market access decisions. For now, the most reasonable reading is that businesses should treat this as an active operational requirement while continuing to monitor how implementation and enforcement details develop.
This article is based on the user-provided news title, event date, and event summary. For this type of industry update, commonly relevant source categories may include official circulars or notices, company announcements, industry association releases, authoritative media reporting, and standard or testing-related documents.
A specific official source link was not provided in the input, so the underlying document and any later implementation materials still need ongoing verification. Follow-up attention should focus on whether MOIT or related bodies issue further clarification on compliance interpretation, test execution, or supporting documentation expectations.
Protocol_Architect
Dr. Thorne is a leading architect in IoT mesh protocols with 15+ years at NexusHome Intelligence. His research specializes in high-availability systems and sub-GHz propagation modeling.
Related Recommendations
Analyst