DEV Community: Sanjay Kapri

BIS Certification Preparation for IoT Hardware: A Guide for Product Teams

Sanjay Kapri — Wed, 21 Oct 2026 10:20:21 +0000

Building a connected product involves more than writing firmware and connecting a device to the cloud. Hardware teams also need to maintain accurate specifications, document product variants, and prepare information for testing and certification reviews.

For teams planning to supply hardware to the Indian market, certification preparation should be considered alongside engineering milestones.

This article focuses on organising engineering information for a BIS assessment. It is a preparation guide rather than a determination that a particular IoT device requires certification. Requirements should be checked for the specific product and its intended use.

1. Describe the Product Beyond the “IoT” Label

“IoT device” describes connectivity, but it does not fully explain what a product does.

A connected sensor, smart display, gateway, and household controller can differ substantially in function, construction, and power requirements. Start with a product description that explains these characteristics.

Prepare information such as:

Product name and intended use
Manufacturer and manufacturing location
Brand and model identifiers
Input voltage and power specifications
External power supply details, where applicable
Connectivity interfaces
Hardware revision
Firmware version used during testing
Supplied accessories

This information gives the assessment team a clearer starting point. A marketing page may be useful context, but it should not replace the technical specification.

2. Maintain a Product Variant Matrix

Engineering teams frequently develop several variants from one hardware platform. Differences may include power supplies, displays, enclosures, connectors, or component selections.

Document these differences before arranging an assessment.

For example, a hypothetical product family might contain:

Model	Power source	Enclosure	Hardware revision
Gateway A	External adapter	Plastic	Rev A
Gateway B	External adapter	Metal	Rev B
Gateway C	USB power	Plastic	Rev A

This matrix is an engineering record. It does not establish that the models can share an application or test report.

Its purpose is to make differences visible so the laboratory or certification adviser can review the appropriate scope. Do not assume that similar model names mean identical certification treatment.

3. Record the Configuration of Each Sample

A physical sample is easier to track when its configuration is documented.

Record its model, serial number, hardware revision, firmware version, and supplied accessories. Where useful, include photographs of the sample and its labels.

A simple internal record could look like this:

Model: Gateway A
Sample ID: SAMPLE-001
Hardware revision: Rev A
Firmware version: 1.2.0
Power supply: As recorded in the sample register
Configuration date: YYYY-MM-DD

These fields are practical traceability suggestions, not a universal BIS document checklist.

Their value becomes clear when an engineer later asks which board revision was supplied or whether a particular firmware update was present on the sample.

4. Use Version Control for Documentation

Software teams already use version control to track changes. The same discipline can help organise hardware documentation.

Keep specifications, model matrices, release notes, and change logs in an accessible system. Store sensitive manufacturing information in a private repository or another appropriately controlled location.

An example structure is:

product-records/
  specifications/
  model-matrix/
  hardware-revisions/
  firmware-releases/
  sample-register/
  change-log/

Large reports and restricted files can remain in a controlled document system, with references maintained in the project records.

The goal is to identify the current version and understand what changed. Avoid circulating multiple files with names such as “final,” “final-new,” and “final-latest.”

5. Review Changes Before Replacing Components

During development, teams may replace a power supply, PCB component, enclosure material, or connector. These changes should be recorded and reviewed.

Create an internal change record that explains:

What changed
Why it changed
Which models are affected
Whether sample configurations are affected
Who must review the change

The review should determine whether further technical or certification advice is needed. An engineering team should not assume that a component substitution is automatically covered by an existing assessment.

Firmware changes also deserve documentation, particularly when they affect how the device operates during evaluation. Record the change and ask the relevant technical reviewer whether it affects the assessment.

6. Assign Clear Owners

Certification preparation can involve engineering, quality, operations, and management teams. Without clear ownership, requests may remain unanswered.

Assign a project coordinator and identify technical contacts for hardware and firmware questions.

A practical division of responsibilities is:

Activity	Suggested internal owner
Product specifications	Engineering
Model and revision records	Product or engineering
Manufacturing information	Operations
Quality records	Quality team
Document tracking	Project coordinator
Commercial quotation review	Procurement or management

Adapt this arrangement to your organisation. The important point is that every requested item has an owner.

7. Separate Preparation From Approval

An organised documentation system can make preparation easier, but it does not establish product conformity or guarantee certification.

The applicable requirements, testing arrangements, application scope, and assessment activities must be checked for the specific product.

Ask for a clear explanation of the proposed certification route. Also request a breakdown of consultancy charges, testing expenses, official fees, and other applicable costs.

Treat timelines as estimates that depend on document readiness, testing, queries, and assessment activities.

8. Where Consultancy Support Can Help

Disclosure: I am associated with Brand Liaison.

Brand Liaison supports Indian and overseas manufacturers with BIS CRS registration, ISI certification, and FMCS projects. Its assistance includes documentation preparation, testing coordination, and application-related communication, according to the agreed scope.

Teams looking for a BIS Certification Consultant in India can discuss their product specifications and manufacturing arrangements to identify the support required.

Engineering teams remain responsible for supplying accurate technical information. Consultancy support helps organise preparation and coordination; final certification decisions remain with BIS.

A Practical Starting Checklist

Before your initial assessment discussion, prepare:

A clear product description
Current technical specifications
A model and variant matrix
Hardware revision records
Sample configuration details
Relevant firmware release information
An internal contact list
A checklist of missing documents

You do not need a complicated system to begin. A maintained spreadsheet, controlled document folder, and clear ownership can provide a useful starting point.

For hardware teams, traceable information makes technical discussions more productive. It helps everyone understand which product is being reviewed, which configuration was supplied, and which questions still need answers.

How does your team track hardware revisions and sample configurations across product variants?

TEC Certification in India: A Technical Compliance Guide for Telecom Products

Sanjay Kapri — Wed, 26 Aug 2026 07:49:23 +0000

Telecom and networking devices connect with public and private communication infrastructure. A poorly tested device can create security, interoperability, safety, or network-performance problems.

For this reason, notified telecommunication equipment may require certification from the Telecommunication Engineering Centre before being manufactured, imported, or sold in India.

This guide explains TEC certification, the products it covers, technical documents, testing requirements, and the complete application process.

What Is TEC Certification?

TEC stands for the Telecommunication Engineering Centre, which operates under India’s Department of Telecommunications.

TEC certification is implemented through the Mandatory Testing and Certification of Telecommunication Equipment (MTCTE) framework. It verifies whether notified telecom equipment meets its applicable Essential Requirements.

Depending on the product, these requirements may cover:

Electrical safety
Electromagnetic compatibility
Technical performance
Network integrity
User protection
Radio-frequency requirements
Other product-specific parameters

Manufacturers should always check the latest product notification and Essential Requirements before starting testing.

Which Products May Require TEC Certification?

TEC certification does not apply automatically to every electronic product. It applies to telecom equipment notified under MTCTE.

Common examples may include:

Routers
Modems
Ethernet switches
Optical Network Terminals
GPON equipment
IP phones
Media gateways
Tracking devices
Wi-Fi access points
IoT gateways
Telecom transmission equipment
Repeaters
Base stations The product’s communication functionality, intended use, specifications, and notified category must be reviewed before deciding its certification route.

Manufacturers uncertain about product applicability can consult a TEC Certification Consultant in India for an initial assessment.

Who Should Apply?

TEC certification is generally obtained by the manufacturer of the notified telecom equipment.

Eligible applicants may include:

Indian manufacturers
Foreign manufacturers exporting telecom products to India
Original Equipment Manufacturers
Manufacturers selling products under different brand names

A foreign manufacturer generally needs to appoint an Authorized Indian Representative, commonly called an AIR, to coordinate the Indian application.

Importers and traders should coordinate with the product manufacturer. They should verify that the equipment has the required certification before arranging imports.

Technical Documents Required

The exact checklist depends on the product category and certification scheme. Common documents may include:

Company registration documents
Manufacturing-facility address proof
Trademark or brand details
Product datasheet
Technical specifications
User manual
Circuit diagram, where applicable
Bill of Materials, where required
Model and series information
Eligible laboratory test reports
Authorisation documents
AIR appointment documents
Required declaration s and undertakings

The product name, brand, model number, manufacturer name, and factory address should remain consistent across the application and supporting documents.

Even a minor difference in the model number can result in a regulatory query.

Understanding Essential Requirements

Each notified product category is linked to applicable Essential Requirements, often called ERs.

These requirements define the technical and testing parameters that a product must satisfy. Manufacturers should identify the correct ER before sending samples for testing.

Using an outdated or incorrect Essential Requirement can lead to:

Incomplete testing
Additional laboratory expenses
Application objections
Re-testing requirements
Certification delays

Manufacturers should also check whether product variants can be included as a model series or require separate testing.

TEC Certification Process

*1. Product Applicability Assessment
*
Review the product’s specifications and functionality to determine whether it is covered under MTCTE.

2. Essential Requirement Identification

Identify the correct Essential Requirements and technical standards applicable to the product category.

3. Certification Scheme Selection

Determine the appropriate certification scheme based on current TEC requirements and the notified product category.

4. Document Preparation

Prepare the company, factory, brand, product, technical, and authorisation documents.

5. Product Testing

Get the product tested according to the applicable Essential Requirements through an eligible testing laboratory.

6. Online Application

Submit the application, supporting documents, test reports, and prescribed fees through the applicable TEC portal.

7. Application Review

TEC officials review the application and verify the submitted technical information.

8. Query Resolution

If an observation is raised, submit the required clarification, corrected document, or additional information.

9. Grant of TEC Certificate

After satisfactory review, the TEC certificate may be issued for the approved product and models.

A detailed explanation of the registration journey is available in this TEC certificate registration guide.

Common Reasons for Application Delays

TEC applications may face delays because of:

Incorrect product classification
Selection of an incorrect Essential Requirement
Incomplete technical documents
Unacceptable laboratory reports
Differences in brand or model information
Missing authorisation documents
Incorrect AIR information
Delayed responses to authority queries
Changes in applicable regulatory requirements

A document and testing review before submission can reduce many of these issues.

Is TEC the Same as WPC Approval?

No. TEC certification and WPC approval serve different regulatory purposes.

TEC certification primarily evaluates notified telecom equipment against applicable technical and safety requirements.

WPC Equipment Type Approval is generally associated with products using wireless or radio-frequency technologies operating in de-licensed frequency bands.

A product may require:

Only TEC certification
Only WPC approval
Both TEC and WPC approvals
Additional certifications depending on its features

Manufacturers should assess the complete product instead of assuming that one approval covers every regulatory requirement.

How Can a TEC Consultant Help?

An experienced TEC Consultant may assist with:

Product applicability assessment
Product-category identification
Essential Requirement review
Technical-document verification
Testing coordination
Model-series assessment
Online application support
AIR guidance for foreign manufacturers
Regulatory-query management
Amendment and renewal support

A consultant cannot guarantee approval because the authority makes the final decision. However, professional support can reduce avoidable testing, classification, and documentation mistakes.

Final Thoughts

TEC certification helps ensure that notified telecommunication equipment meets India’s technical requirements before entering the market.

Manufacturers should begin with a proper applicability assessment, identify the correct Essential Requirements, prepare consistent technical documents, and complete testing through an eligible laboratory.

Since product lists and regulatory requirements may be updated, businesses should verify the latest TEC and MTCTE requirements before submitting an application.