Start with the category, then verify the bulb
H11, H8, H16 and HB4 appear in the current R.E.5 Group 5 LED replacement category list. TF S/R material records H11 as established and reports H8, H16 and HB4 in force from March 2026. A buyer may therefore describe these as in-force category specifications when citing the current documents. That wording does not approve every LED bulb carrying one of those base names. A supplier must still show approval evidence for the exact product type, the correct marking, the intended lamp application and the markets where the route is recognized.
What "in force" means here
R.E.5 organizes technical specifications for light-source categories. Group 5 lists LED replacement light sources intended for use in lamps approved with filament light sources of the same category designation. When a category sheet is in force, manufacturers have a defined technical basis for seeking product type approval. Authorities and technical services can assess a submitted product against that basis.
The category sheet is not a blanket market authorization. It does not tell a buyer whether a certificate shown by a supplier is authentic, whether the supplied SKU matches the approved type, whether production remains consistent or whether a destination country applies the relevant regulation. Those questions sit after category status. Good product copy therefore names the category and the product evidence separately.
The phrase "approved category" is common in sales discussions, but "in-force category specification" is clearer. It avoids suggesting that the resolution has already approved every product. The product claim should only move to "UN R37 type approved" when the exact product and approval communication support that wording.
Why these four categories are discussed together
H11 provided a working model for later road-illumination LED replacement work. The 2024 amendment added Configuration-2 detail to the H11 LEDr sheets. The H8, H16 and HB4 proposals then used established equivalence ideas from H11, with changes for each category. The package included a bi-directional configuration approach and category-specific features such as the HB4 light-emitting-area description.
The H8/H16/HB4 project was developed around front-fog applications. This explains the labels used in task-force agendas and many industry summaries. The history should not be stretched into a claim that any bulb with one of these bases is a legal fog lamp replacement, or that no approved use could exist outside the simplified description. The category sheet, product approval and installation instructions control the precise claim.
How the four categories differ
| Category | Status reading | Buyer focus |
|---|---|---|
| H11 LEDr | Established Group 5 category; Configuration-2 detail adopted in 2024 | Check whether the product uses the applicable configuration, cap/keying and approval marking. |
| H8 LEDr | Added through the 2026 amendment package | Confirm the lower-output counterpart category, application and exact product evidence. |
| H16 LEDr | Added through the 2026 amendment package | Pay close attention to compact geometry, electrical behavior and intended lamp use. |
| HB4 LEDr | Added through the 2026 amendment package | Check the category-specific emitting-area approach and avoid inferring use from the base name. |
The comparison is deliberately about evidence, not advertised brightness. R37 approval work covers the light source as a regulated product. A raw lumen figure, color temperature, fan speed or wall photo cannot replace the required electrical, photometric, thermal, mechanical and geometrical assessment.
Category designation is not the whole installation
Group 5 wording connects an LED replacement category to lamps approved with a filament light source of the same category designation. That is a stronger relationship than generic socket compatibility. The cap, keying, reference geometry and controlled light distribution are part of the regulated concept. A product that can be forced into several related sockets may create misuse risk even when its packaging looks convincing.
Buyers should ask the supplier to name the lamp function covered by its product documentation. The answer should come from the category and approval file, not from an ecommerce fitment database. Installation instructions should identify orientation, electrical connections and any prohibited substitutions. If the product has a high-efficiency variant or uses additional electronics, the supplier should explain how those parts relate to the approved type.
Country scope is another independent check. The safest international wording is tied to countries where UN R37 is recognized or applied. "ECE member country" is too broad because countries choose which UN regulations they apply, and national implementation still matters.
What an importer should expect in the product file
- A complete approval communication that identifies the approval holder and exact light-source type.
- Product and packaging markings that match the approval communication.
- The applicable LEDr category and configuration, including any high-efficiency or additional-electronics provisions.
- Installation instructions that define orientation, application and required components.
- Production-consistency controls linking shipped units to the approved sample.
- A market statement that names where the approval route is recognized instead of using "legal everywhere."
An importer should compare these records with a physical sample. Check the cap keying, labels, connector arrangement and supplied accessories. TF S/R has discussed products that appeared to carry H11 R37 approval but raised concerns because the physical keying did not meet the expected requirement. This is why a certificate image should never be reviewed in isolation.
A safer way to source these categories
Begin with one category and one market. Ask the supplier for the approval communication before agreeing on packaging claims. Confirm the SKU and marking against a sample. Then review the intended lamp use and destination-country position. Only after those checks should the buyer compare price, output, cooling design and commercial terms.
Keep the evidence attached to the SKU in the purchasing system. A general supplier folder is easy to misuse when several bulbs share a housing or brand. Record the approval number, holder, category, configuration, instructions, accessories and markets in structured fields. Packaging and product-page copy should be generated from those fields rather than from a sales summary.
Recheck the file when the supplier changes LEDs, drivers, caps, fans or external electronics. A change that looks small commercially can affect the approved type or production consistency. Ask the approval holder to confirm whether the change is covered by the existing approval, an extension or a new application.
Write the catalogue claim from the evidence file
A product page should identify the approval object before it uses the word "approved." For an H11, H8, H16 or HB4 product, the page can name the LEDr category, the exact product reference and the regulation shown in the approval communication. It should also state the intended use supported by that file. If market recognition has not been checked, the page should ask the buyer to verify local requirements instead of promising road legality everywhere.
Keep R10 language in a separate field. A product may have electromagnetic-compatibility evidence as well as R37 light-source approval, but the two documents answer different questions. Showing only the R10 E-mark beside a "street legal" heading is likely to mislead a buyer even when the R10 certificate itself is valid. The same rule applies to a lamp assembly approval under R112 or R149. It does not automatically approve a replacement bulb.
Packaging has less room than a technical page, so use a traceable short claim. Name the category and approval route, then direct the buyer to the full documentation and installation instructions through a stable page or code. Avoid vague badges such as "ECE LED approved." They are difficult to audit and easy to copy onto unrelated products. A narrow claim backed by a complete file is more useful to an importer than a broad badge that cannot survive a document check.
Translations must keep the same scope. Terms such as legal, approved, certified and homologated do not always carry identical meanings in every language or market. Give translators the approved English claim, the regulation number, the object being approved and a list of prohibited expansions. Review the final packaging in each sales language before printing.
Questions buyers ask about the four categories
Are H11, H8, H16 and HB4 LEDr categories in force?
Yes, based on the R.E.5 and TF S/R materials checked on 10 July 2026. The exact product still needs matching type-approval evidence.
Are H8, H16 and HB4 only for front fog lamps?
The package was developed around front-fog applications. Use the category sheet and exact approval documentation to describe the approved use. Do not rely on the project label alone.
Can any LED bulb with the same base use the LEDr claim?
No. Base compatibility does not establish compliance with the category sheet or approval of the manufactured type.
Is an R10 certificate enough?
No. R10 concerns electromagnetic compatibility. It does not replace R37 light-source approval or establish installed road-use permission.
A category sheet and a product approval answer different questions
A category sheet defines the technical route for a named LED replacement category. It does not identify which commercial products have passed type approval. For a product claim, the evidence must connect the marketed type to an approval number, approval holder, authority and applicable category sheet. This distinction is especially important for H8, H16 and HB4 because the formal UNECE proposal describes the category specifications and their equivalence basis; it should not be presented as a blanket approval for products carrying those base designations.
Official sources
- UNECE Consolidated Resolution R.E.5 register
- ECE/TRANS/WP.29/2024/156
- ECE/TRANS/WP.29/GRE/2025/17
- ECE/TRANS/WP.29/2026/41
- TF S/R report of the 28th meeting
This article explains source documents for purchasing and editorial use. It is not a substitute for market-specific legal advice.