Do I need to manufacture in India or hit local-content rules to sell hardware or software to the government?
The short answer
Often yes, and it's frequently a hard gate, not a nice-to-have. The Make in India / Public Procurement (Preference to Make in India) order and Class-I/Class-II local supplier rules can decide eligibility before price is even read, and MeitY-style local-content thresholds bite for hardware and some software. Get your local-content declaration and certification sorted early, and for IT products understand the STQC/BIS and data-residency expectations. This is a paperwork moat: painful once, then a durable advantage rivals skip.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
📄 Article
✓ Link checkedIndiaFreeIntermediate
Why we picked it
This is the clearest lawyer-grade walkthrough of the PPP-MII order as it actually bites: it defines Class-I (>=50% local content), Class-II (20 to 50%), and non-local suppliers, and spells out the certification ladder that trips founders up, self-certification upfront with statutory-auditor certification due later and penalties up to 10% if your real local content falls short. It also flags the 2024 change that license fees, royalties, and technical charges paid outside India are stripped out of your local-content number, which is exactly what sinks IP-licensing software vendors.
Class-I supplier (>=50% local content) gets first preference; Class-II (20 to 50%) only qualifies when no Class-I exists, so your local-content number can gate eligibility before price is read
Self-certify local content at bid time, but statutory-auditor certification is due later and understating carries penalties up to 10%, so treat the declaration as a real audit exposure
Royalties, license fees, and technical charges paid outside India are deducted from local content, which quietly disqualifies many overseas-IP software models
Why we picked it
Hardware founders have a clear MeitY component-by-component local-content formula; software founders have almost nothing, and this piece fills that exact gap. It works four real business models (one-time territorial IP assignment, per-product royalty, licensing, and reseller) through the local-content math with a worked example: on a Rs 1,00,000 software license, offshore royalties must stay under Rs 50,000 to hit Class-I. It shows you how to structure IP so you actually clear the bar instead of guessing.
Software local content is measured off offshore royalties as a share of the quoted price, so on a Rs 1,00,000 license, keep offshore royalties under Rs 50,000 for Class-I and under Rs 80,000 for Class-II
A pure reseller model almost always fails to qualify, while a one-time territorial IP assignment can read as 100% local, so your contract structure decides eligibility
MeitY has hardware and cyber-security notifications but no software-specific local-content guidance, so get pre-tender clarification from the buyer and auditor-certify your calculation
Why we picked it
This is the most concrete plain-English explainer of the STQC and BIS gate that most local-content writeups skip, and it maps cleanly onto the reality that government and GeM buyers increasingly want BIS registration on the hardware and STQC certification on the software before you can sell. It names the actual portals (crsbis.in for BIS R-numbers, stqc.gov.in for STQC) and the security bar the tests check (encrypted streams, secure boot, vulnerability-disclosure policy), so you can scope timelines instead of discovering the requirement mid-tender.
Selling IT hardware plus software to government increasingly means two separate certifications: BIS registration on the device and STQC certification on the software, not one
Verify and track certification on the real portals: BIS R-numbers on crsbis.in and STQC on stqc.gov.in, since buyers check these
STQC and BIS test concrete security controls (encrypted streams, secure boot, vulnerability-disclosure), so build the certification runway in early because it is a hard gate for government and GeM procurement
