The mandatory national standard is still in draft, and Guangdong is the first to collect a round of evidence of 'adaptation in progress'

Guangdong Industry and Information Technology Consumer Goods Letter [2026] No. 129 requires submission to the local city by November 20; what is assessed is not the certificate, but what the model can connect to.

On the afternoon of November 11, a customer in Foshan who makes smart door locks sent over a screenshot of Document No. 129 and asked: We don't have an interoperability certification certificate, so does that mean we don't need to report it?

This question hits the nail on the head. Because over the past few years, the threshold for this kind of call for submissions was usually written as “has passed XX certification.” If you had the certificate, you applied; if not, you waited for the next round—the judgment was straightforward. This time, it’s not.

The three “or”s changed the threshold from certificates to process

In the "Notice of the Department of Industry and Information Technology of Guangdong Province on Soliciting Smart Home Interoperability Products and Demonstration Application Scenario Cases (First Batch)" (Yue Gong Xin Xiao Fei Han [2026] No. 129, dated November 10), Article 3 under "Product Requirements" states the following sentence:

The product has complied with or been adapted to relevant national standards and industry standards, or is undergoing adaptation in accordance with the draft national mandatory standard for smart home interconnection and interoperability, or has participated in technical verification related to the national mandatory standard.

Three “ors,” three states—any one counts as passing. Already compliant, currently adapting, has participated in verification—the last one doesn’t even require that you can connect right now, only that you’ve actually tried.

This isn't loosening; it's having no choice. The mandatory national standard for smart home interoperability is still at the draft stage, and the official text has not been released, so no company can possibly produce a certificate of 'having passed the mandatory national standard.' If policy sets thresholds based on certificates, the first batch will be zero.

So what is really being tested this round has changed: it is not whether you have a certificate, but whether you can clearly explain “what I did and how far I got.”

There’s a pitfall here: the document doesn’t spell it out clearly. The word “relevant” in “already complies with or is adapted to relevant national standards and industry standards” is very broad. Companies making door locks mostly have GB 4706 series electrical safety reports—does that count as “adaptation to relevant national standards”? In my understanding, no—this item tests interoperability capability, not electrical safety. But the document indeed does not rule it out; whether it will be accepted during the prefecture/city preliminary review depends on the specific case handler’s interpretation. We asked in one of the cities, and the reply was, “The adaptation test records provided by the enterprise shall prevail.” This is an oral reply, not a document; don’t use it as a basis.

What is submitted is the product; what is tested is whether the master data can clearly state “what it can connect to”

The second item of the product requirements lists seven capabilities: device discovery, network provisioning access, access authentication, device control, status subscription and notification, device collaboration, and scene linkage. Having more than one is sufficient.

Here's the question: where do these seven capabilities exist in your system?

For most companies, the answer is “in the spec sheet PDF.” Spec sheets are made by the marketing department, one per model, versions are distinguished by file name, and changes are not announced. By the time they need to report to the province, they discover that no one can clearly say which items this version in production in 2026 actually supports.

We once did an implementation for a client that makes smart lighting. The approach wasn't complicated: add two groups of fields to Odoo's product master data—one group for seven capabilities as multi-select, and one group for a protocol list (Wi-Fi, BLE, Zigbee, Thread, Matter, multi-select), plus a "standard or draft version" and an "adaptation verification record number." Four fields can be added in half a day. The hard part isn't adding the fields; it's filling them in correctly, one by one, for the more than forty models in production.

During the filling process, a real problem was exposed, and it is also the part most likely to cause errors in this round: how to count a model as one.

The same hardware platform ships with three communication modules: a Wi-Fi version, a Zigbee version, and a Matter version. In Odoo, build them as variants (using the color and size attribute setup); the three modules are three variants attached to the same product template. But what the provincial authorities want is “products,” and the test reports list model numbers. If the three modules each have their own separate report, then in the reviewers’ eyes they are three products; if one report covers all three modules, then it is one product.

The criterion is not in your system; it is on the cover of the test report. So the order should be reversed: first look through the report to see how the report classifies the model, then decide whether to create variants in the system or create three independent finished products. We have seen people do it the other way around: create them as variants in the system, but report them as one product; as a result, the model on the report does not match, and it is sent back and must be reported again.

Data models follow the evidence, not habits. This statement holds especially true in this round.

There is another point that is easy to overlook: during the draft stage, the standard will change versions. What is adapted today is one draft version, and after formal release the clauses may change. Therefore, the 'standard version' field must be able to retain history and must not be overwritten. Three years later, proving 'which version was adapted at the time' will depend on exactly this record.

The case column is where people most easily get tripped up by “no address”

Among the four requirements for scenario cases, the toughest is the second one: the content must be authentic, with a clear implementation location that can be verified on site, and have value for demonstration and promotion.

The phrase “can be verified on site” shuts many cases written by the marketing department out the door. We reviewed a document: the case title was “a certain smart community whole-home smart linkage project,” the implementation location was given only as the park name, with no building number and no property contact, and the launch time was written as “2025.” If reviewers want to go see it, where would they look?

Clients who do solid work take a different approach. In 2025, they completed 120 households in one residential community in Guangzhou, with four brands—door locks, lighting, curtains, and air conditioning—integrated; addresses were precise down to the building, property management had a point of contact, and each household’s go-live time had an installation work order in the system. These were not added retroactively for the application; they were kept as part of the project from the start.

The difference is that the former treats cases as copywriting, while the latter treats cases as project records.

In Odoo, this information is spread across three places: customers and addresses are in the contact master data, installation and commissioning are in project tasks and work orders, and the go-live time is in the work order completion time. When reporting a case, if you pull it from these three places, you can put one together in twenty minutes; if you rely on memory to fill it in, even two weeks won't be enough to get it accurate.

By the way, there is no funding subsidy in this round. The benefits of being selected are promotion on the provincial department's portal and in mainstream media, plus display slots at “Cantonese Goods Travel the World” and “Guangdong Intelligence Empowers Ten Thousand Enterprises”, as well as encouragement to participate in mandatory national standard compliance verification. Those in it for the money can skip it; those in it for prestige and a say when the standard is officially released later are worth applying.

Three things you can do this week

First, categorize yourself first. If the product is already in mass production and on sale, report the product directly; if it is not yet in mass production but has completed pilot testing, report the product and attach the pilot test report; if neither applies, do not report in this round—don't force it. The document states clearly: if it is not in mass production and has no pilot testing foundation, it will be returned even if reported.

Second, go through the test reports and classify models according to the report cover. The same hardware platform has several communication module versions; whether the reports are combined or listed separately directly determines whether to create variants or independent finished products in the system. If this step is set wrong, shipping, warranty, and report traceability will all be wrong afterward. Reports to prefecture-level cities are due by November 20; counting backward, only one week is left, so do this step first.

Third, choose a case that can be taken to visit in person. The criteria are simple: whether you can provide an address precise to the building, an on-site contact whose phone can be reached, and an operating record of more than three months. If all three are available, report it; if one is missing, switch to another project. The deadline for prefecture-level cities to summarize and report to the province is December 4. Guangzhou, Shenzhen, Foshan, and Dongguan must recommend no fewer than 20. Quotas are not lacking; what is lacking is verifiable ones.

关于我们

​我们致力于帮助中小企业实现数字化转型,我们的团队由一群充满激情和创新思维的专业人士组成,他们具备丰富的行业经验和技术专长。

扫一扫获取顾问以及手册

Sign in to leave a comment
Both the 62 and the 280 have gone into storage; the money still has to wait for the budget to have its say.
Follow-up|Dongguan and Foshan both issued public notices on November 10, with both public notice periods running until November 16