Using a CB Report: Which Markets It Saves, and When It Is Wasted

Start with the conclusion: CB is a common base report under the IECEE system, and it means that safety certification in several countries does not have to be tested again from zero. Used well, testing cost and time can be cut by roughly half. But it covers safety only, not radio frequency, and is not market access in itself — take a CB report to customs and it will not be accepted. Pointed in the right direction it saves money; pointed in the wrong direction it is money spent for nothing.

This article does not break down clause text. It answers three questions: which countries can use it, how much each country can save, and when this report does no work at all.

1. What CB actually is: get the identity clear first

CB is a test report and certificate under the IECEE system. It is not positioned as any single country's certification, but as a "base report" that can serve multi-country certification and reduce duplicate testing. Once a product has been through safety testing once, certification bodies in other countries assess it on that basis instead of repeating the same tests.

That is where the industry name "base report" comes from: the base report does not itself create market access; its value lies in how many national certifications it can be connected to. The more it connects to, the lower the per-country cost once spread; if it connects to nothing, it is a pile of data sitting in a folder.

The right-hand column is the source of every "wasted" outcome that follows. In many projects CB was not done wrong; it was treated as something else from the start.

2. What it covers and what it does not

CB covers safety and, for some products, energy efficiency; it does not cover radio frequency. The boundary is clear, yet every year a large number of projects still come to grief on it.

A concrete example. For Bluetooth earphones going overseas, the safety line can run on CB; the RF line has to be done separately — FCC in the United States, CE-RED in the EU, MIC in Japan. However complete the CB is, it replaces none of those three lines. For products with a wireless function, plan on "two lines", not on "one report". For the product-side differences see the Bluetooth earphone certification approach, and for power supplies the power adapter approach.

3. Which countries and regions accept it, and to what degree

The word "accept" has to be unpacked: some accept directly, some accept only part of it, some do not accept it at all. The table below sets out the six situations that come up in real projects.

Read this table across, not down. The same phrase "has a CB" means "the process can move faster" for Saudi Arabia, "fewer test items" for Korea, "lower cost and shorter time" for China CCC, and "differences can be accelerated" for Australia; while for India and Taiwan it means "this piece of paper grants no reduction here". Specific determinations are subject to the current requirements of the authority in the target country, and the position for different product categories within one country may not be fully consistent.

4. How much it saves: country by country

What is saved is not the same thing each time. Sometimes it is time, sometimes test items, sometimes cost; lumping them together as "CB saves 50%" is inaccurate.

Saudi Arabia: what is saved is time. SABER accepts IECEE CB certificates, which can shorten the process to 1-2 weeks. For projects rushing to list or rushing to bid, that time difference is the whole point. For the route see the Saudi SABER knowledge base and the Saudi certification service.

Korea: what is saved is test items. CB plus IEC 62368-1 can waive a large part of safety testing. Note the second half of that sentence: Korean bodies still assess whether the report is sufficient, and will require difference testing if it is not. So what is saved is test items in the lab, not the review step, and not the whole cycle. For detail see the Korea KC knowledge base and the Korea KC service.

China CCC: what is saved is cost and time, about 50%. This is one of the clearer reduction levels. But there is a hard constraint that cannot be routed around: the CCC report must be issued by a China lab designated by CNCA. In other words, what CB saves is "duplicate testing", not permission to use a different lab. Confuse the two and the project stalls at the report acceptance step. For the related rules see the CCC/SRRC knowledge base and the China certification service.

Australia: what is saved is time on difference testing. The safety part of EESS can be accelerated with CB plus AS/NZS differences. The precondition is that the differences are completed; CB itself cannot simply stand in. For the overall RCM structure see the Australia RCM knowledge base.

India: nothing is saved. BIS does not accept CB directly; testing must be at an Indian accredited lab. There is no shortcut on this line, so budget and timeline have to be reserved in full. See the India BIS knowledge base.

Taiwan: nothing is saved either. Mainland reports (including CB) cannot be used directly; a Taiwan locally accredited lab is needed. Many projects come unstuck here because they take "CB issued by a mainland lab" as valid across Chinese-speaking markets by default. See the Taiwan NCC/BSMI knowledge base.

Put the six together and the pattern is clear: CB saves "duplicate safety testing"; it does not save "the local lab" or "the local review". Wherever a market requires a locally issued report, the CB reduction is discounted or falls to zero.

5. When a CB report does no work

The five situations below come up very often in real projects. Hit any one of them and the economic value of that CB shrinks sharply.

1. The product is wireless, and you only did CB. RF is not covered, so the goods still cannot ship. However complete the safety report, it does not fill the RF gap.
2. The target market is one that does not accept CB. India and Taiwan belong to this group. There, CB grants no reduction and counts only as a reference document.
3. The report does not match the product being shipped. CB covers the product that was submitted as a sample at the time. If the model, key construction or key components change, the report no longer describes the goods you intend to sell.
4. Using CB for customs clearance. CB is not a certificate. Customs looks at the target country's market access documents, not at a test report.
5. The standard in the report does not line up with the target country's current requirements. What the target country's authority looks at is not "do you have CB" but "is this CB sufficient, and is it the right version".

There is also a hidden form of waste: the report is made, but nobody uses it. CB does not turn into any country's market access on its own; someone has to take it and connect the next step. File it away when the project ends and start testing again for the next country — that waste is more common than a failed test.

6. How to get full value from CB: sequence matters more than effort

Projects that use CB well have one thing in common, and it is not a well-chosen lab — it is the right sequence. Get the sequence wrong and every later step is patching an earlier hole.

In this flow, the first two steps are the ones people get backwards. Many projects submit for testing first and think about markets afterwards, then discover that the target country does not accept CB, or that the standard version in the report does not match the target country's current requirements — at which point CB is no longer a cost-saving tool but a sunk cost.

Another sequencing issue is the relationship between safety and RF. The two lines should be planned in parallel, not in series: wait for the CB before starting RF and the overall cycle stretches out considerably. The RF line has its own approach in the United States, the EU and Japan; see the USA FCC service, the EU CE/RED service and the Japan MIC service.

If there are several target countries, there is a further judgement to make: whether the report can be transferred to another market. Such transfers have their own rules; run through the report transfer map first, then decide how to schedule the testing.

7. Common pitfalls: four recurring misjudgements

These pitfalls share one feature: none of them is a technical problem, they are perception problems. Finishing the tests is not technically hard; what is hard is knowing in advance in which country this report counts and in which it does not. If you are unsure of a market's position, run it through the certification lookup first, then decide whether to submit for testing.

8. Five checks before you use CB

Before submitting for testing, answer these five questions. If you cannot answer clearly, do not rush to open the case.

To close

CB is worth doing, but its value has preconditions: a clear market list, a matching standard version, an RF line planned separately, and someone to take it into the next country's procedure. Miss any one of the four and CB turns from "saves half" into "one wasted report".

Conversely, as long as the market list includes destinations that accept CB, such as Saudi Arabia, Korea, China and Australia, the spreading effect of this base report is real — especially when one product has to enter several markets at the same time.