If you're manufacturing, importing, or selling medical devices or cosmetics in India, the Central Drugs Standard Control Organisation (CDSCO) is the regulator standing between your product and the Indian market. The process differs sharply depending on your device's risk classification, which is where most first-time applicants get confused.
Device classification comes first
CDSCO classifies medical devices into four risk classes โ A (low risk, e.g. a tongue depressor), B (low-moderate, e.g. a syringe), C (moderate-high, e.g. a ventilator), and D (high risk, e.g. a heart valve). Your classification determines which licence you need, how detailed the technical documentation must be, and which authority (state or central) processes your application.
Manufacturing vs import licences
Domestic manufacturers apply for a manufacturing licence, while anyone bringing a device into India from abroad needs an import licence, which additionally requires appointing an Indian Authorised Agent who takes on regulatory responsibility within the country. Cosmetics follow a parallel but separate registration track under the same authority, with its own document set focused on formulation safety and labelling compliance.
Documentation that actually moves the needle
For medical devices, this typically includes a Device Master File, Plant Master File, free sale certificate from the country of origin (for imports), ISO 13485 certification, and clinical evidence proportional to your risk class. For Class C and D devices, expect a more rigorous review with possible queries on clinical data โ budgeting extra time here saves frustration later.
Realistic timelines
Class A/B devices typically clear in 3โ4 months given clean documentation; Class C/D can run 6โ9 months due to the additional scrutiny. Cosmetics registration is usually faster, in the 6โ10 week range, provided your product formulation and labelling meet Indian cosmetic rules from the start.
State vs central licensing โ why it matters more than people expect
Some device and drug categories are licensed by the State Licensing Authority where your manufacturing unit sits, while others fall under CDSCO centrally โ and applying to the wrong authority is a surprisingly common, entirely avoidable delay. The split isn't always intuitive: it depends on the specific product category and, for some categories, the scale of manufacturing, not simply whether the product 'sounds' like it should be a central matter.
Since state and central authorities run different portals, timelines, and documentation formats, confirming jurisdiction correctly before you start compiling documents saves far more time than any efficiency gained by starting the paperwork early on a guess.
What CDSCO actually scrutinises during review
Beyond the headline documents (Device/Plant Master File, free sale certificate, ISO 13485), reviewers pay particular attention to whether your labelling and instructions-for-use match what was actually tested, whether your quality management system documentation is internally consistent (not just present), and โ for imports โ whether your Indian Authorised Agent's responsibilities are clearly and correctly documented in the appointment agreement. Gaps here, more than the underlying product safety data itself, are what generate the most query cycles in practice.
Key Takeaways
- Your device's risk class (AโD) determines the entire registration pathway and documentation depth.
- Importers must appoint an Indian Authorised Agent โ this isn't optional.
- Confirm whether your product falls under state or central licensing before starting documentation โ this is a common source of delay.
- Class C/D devices take significantly longer due to added clinical scrutiny.
- Cosmetics follow a separate, generally faster registration track under the same authority.
- Labelling/IFU consistency and AIR documentation quality drive more query cycles than raw safety data in practice.
Frequently Asked Questions
How do I know if my product needs state or central CDSCO licensing?+
It depends on the specific device or drug category (and, for some categories, manufacturing scale) rather than a general rule โ we confirm jurisdiction for your exact product before you start compiling documentation, since applying to the wrong authority is a common and avoidable delay.
What's the most common reason a CDSCO application gets stuck in queries?+
Inconsistencies between labelling/instructions-for-use and what was actually tested, or incomplete Indian Authorised Agent documentation for imports, generate more query cycles in practice than the underlying product safety data itself.