- A delisted model can no longer be treated as ALMM-compliant for projects that require ALMM.
- There is no guaranteed procurement-date grandfathering — DISCOM acceptance is discretionary.
- First: confirm the delisting on the live MNRE list by exact model number, then pull the invoice and serials.
- Pause pending installs of that model; ask the DISCOM in writing how it treats your stock.
- For new supply, source a currently enlisted equivalent and re-verify its live status.
Few things rattle a project like opening the ALMM list and finding your module gone. The good news: a delisting is not always a disaster, and there are clear steps to protect the job. The honest news: there is no cast-iron protection, so move fast and document everything.
What delisting actually means
When a module is delisted from ALMM mid-project, the model can no longer be treated as ALMM-compliant for projects that require ALMM. Work already done may be argued on the procurement date, but new use of the model is blocked. Confirm the delisting on the live MNRE list and ask your DISCOM how it treats stock bought while the model was listed.
Delisting is not the same as the module being unsafe or fake. The panel can still work fine; it has simply lost its place on the approved list for government-linked work. That distinction matters, because it shapes your options — the module may be perfectly usable on a non-ALMM job.
Why a model gets delisted
A solar module gets delisted from ALMM when the maker is removed, the BIS registration or licence lapses, the enlisted capacity is exhausted, or the model fails a re-check. Delisting can happen without much notice. Check the live ALMM list by exact model number rather than the brand, because one model can be removed while others from the same maker stay.
The common triggers
- BIS lapse — ALMM leans on a valid BIS registration; if the BIS licence lapses, the model can drop.
- Capacity exhausted — an enlisted model has a capacity ceiling; once used up, supply against it can stop.
- Maker removed — the whole maker can be taken off the list, removing all their models.
- Failed re-check — a periodic verification or audit can remove a model.
Is there procurement-date protection?
There is no guaranteed grandfathering by procurement date. Some EPCs argue that modules bought when the model was on ALMM should be accepted, and a DISCOM may agree, but acceptance is discretionary and varies. Do not assume protection. Verify whether any formal MNRE transition rule applies before you treat delisted stock as safe to install.
This is the single most important point on this page, so we will be blunt: do not tell a client the job is safe just because you bought the modules while they were listed. A DISCOM may accept that argument, but it is not a settled right. Get the position confirmed before you commit. Our grandfathering check guide walks the timing in more detail.
Your first 48 hours
When a module is delisted, move in order. First confirm it on the live MNRE ALMM list by the exact model number, then gather the procurement invoice, dispatch date and module serials. Pause any pending installation of that model, and ask your DISCOM in writing how it treats stock bought while the model was listed before you proceed.
Do not skip the written DISCOM step
A phone call with a DISCOM officer is not protection. Ask the question in writing and keep the reply. If the DISCOM later challenges the module at net metering, that written position is your best evidence. Build the habit of getting compliance answers on paper.
Symptom, cause and fix
Delisting shows up in a few different ways depending on how far the job has gone. Find your symptom in the table, then follow the matching action. Treat every DISCOM-acceptance line as discretionary, not a promise.
Source: MNRE ALMM practice as understood on 20 Jun 2026. DISCOM acceptance is discretionary — verify the live list and your DISCOM position before acting.
Net metering and the DISCOM check
The delisting usually surfaces at net metering, because the DISCOM checks ALMM when it approves the connection. If the model is no longer on the list at that point, the DISCOM can flag it. This is where the procurement date and your written records do the heavy lifting. See our ALMM and net-metering guide for how the check runs.
Different DISCOMs handle this differently, which is exactly why the rule feels uneven across states. One DISCOM may accept stock bought while the model was listed; another may insist on a currently enlisted model. Do not generalise from one state to another — ask yours directly.
If the panels are already up
Already-installed delisted modules may still be accepted, but it is not guaranteed. Document the install date, serials and procurement invoice, then press the procurement-date argument with your DISCOM, which decides at its discretion. For projects requiring ALMM, treat acceptance as uncertain and get the DISCOM position in writing before you rely on it.
If a DISCOM refuses, your options narrow to negotiation, escalation, or in the worst case re-supply. None are cheap, which is why prevention beats cure. Keep your client informed early — a delisting handled openly damages trust far less than a surprise rejection at net metering.
How to stop this happening again
The fix for next time is a live link between what you buy and the ALMM list. Re-verify a model on the live MNRE list at order and again before dispatch, keep the procurement date and serials on record, and watch for BIS-lapse signals on the makers you use. A model that is close to its capacity ceiling is a risk worth flagging early.
- Verify at two points — at order and before dispatch, by exact model number.
- Record the procurement date — it is your main argument if a model drops later.
- Keep serials linked to the site — you cannot argue grandfathering without them.
- Diversify makers — do not put a whole pipeline on one model near its capacity limit.
How SuryaHub helps you handle delisting fast
When a model drops off ALMM, the question is always the same: which of my live jobs are exposed, and where is the proof? SuryaHub can hold each model ALMM status, procurement date, invoice and serials against the project in procurement and inventory, so you can see which jobs are hit and pull the evidence in minutes, not days. It links the same records to the net-metering workflow so the DISCOM file is ready. SuryaHub is pre-revenue; the only real pilots are Suryantra Energy and RGESPL, and ALMM statuses change, so always verify on the MNRE portal.
Know which jobs are exposed
See how SuryaHub links ALMM status to every project and BOM.
Related guides
Frequently asked questions
What happens if a module is delisted from ALMM mid-project?+
If a module is delisted from ALMM mid-project, the model can no longer be treated as ALMM-compliant for projects that require ALMM. Work already done may be argued on the procurement date, but new use of the model is blocked. Confirm the delisting on the live MNRE list and ask your DISCOM how it treats stock bought while the model was listed.
Is there grandfathering protection by procurement date?+
There is no guaranteed grandfathering by procurement date. Some EPCs argue that modules bought when the model was on ALMM should be accepted, and a DISCOM may agree, but acceptance is discretionary and varies. Do not assume protection. Verify whether any formal MNRE transition rule applies before you treat delisted stock as safe to install.
Why does a solar module get delisted from ALMM?+
A solar module gets delisted from ALMM when the maker is removed, the BIS registration or licence lapses, the enlisted capacity is exhausted, or the model fails a re-check. Delisting can happen without much notice. Check the live ALMM list by exact model number rather than the brand, because one model can be removed while others from the same maker stay.
Can I still use already-installed delisted modules?+
Already-installed delisted modules may still be accepted, but it is not guaranteed. Document the install date, serials and procurement invoice, then press the procurement-date argument with your DISCOM, which decides at its discretion. For projects requiring ALMM, treat acceptance as uncertain and get the DISCOM position in writing before you rely on it.
What should I do first when a module is delisted?+
When a module is delisted, first confirm it on the live MNRE ALMM list by the exact model number, then gather the procurement invoice, dispatch date and module serials. Pause any pending installation of that model, and ask your DISCOM in writing how it treats stock bought while the model was listed before you proceed.
How does SuryaHub help when a module is delisted?+
SuryaHub can hold each model ALMM status, procurement date, invoice and serials against the project, so when a model is delisted you can see which jobs are exposed and pull the proof fast. SuryaHub is pre-revenue; the only real pilots are Suryantra Energy and RGESPL, and ALMM statuses change, so verify on the MNRE portal.
Sources & references
Delisting, enlistment and any transition rules come from MNRE; BIS lapse is a common trigger. ALMM statuses and any grandfathering treatment change and are applied at DISCOM discretion — verify on the MNRE portal and confirm your DISCOM position in writing.
- Ministry of New & Renewable Energy (MNRE) ↗
The ALMM orders, enlistment and delisting, and any transition rules.
- Bureau of Indian Standards (BIS) ↗
BIS registration, whose lapse can trigger a delisting.
- NISE DCR portal ↗
DCR certificate context where domestic content is required.
Written by the SuryaHub team · reviewed against MNRE & BIS sources · updated 20 June 2026.
Method: Delisting behaviour and the DISCOM response are taken from MNRE rules and field practice and re-checked regularly. There is no confirmed formal MNRE procurement-date guarantee, and DISCOM acceptance is discretionary — verify on the MNRE portal. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 20 Jun 2026 — first published.