GeM incident management policy: incidents, suspension and appeals
The GeM incident management policy is how GeM deals with sellers and buyers who break its rules. A complaint on the portal is called an incident. If it is not fixed, GeM issues a show cause notice and can place the account under a temporary moratorium or suspension, during which the seller cannot bid or list products.
The version in force is the Incident Management Policy V14.10, applicable from 9 June 2026. It supersedes all earlier incident policies and circulars. For decisions on an incident or appeal, GeM uses the version in force on the date the incident was created, with one exception: non-payment of transaction charges or the Annual Milestone Charge is always dealt with under the current policy.
What counts as a deviation
The policy starts from the idea that GeM is a trust-based system built on self-declaration. Any act, omission, deficiency or non-compliance, deliberate or not, that goes against the policy, GeM's General Terms and Conditions, the forward auction terms, the Revenue Policy, applicable law or government procurement rules is a "deviation". An incident is a deviation that has been reported or detected and taken up for action.
Examples from the policy's list of incident reasons include:
- non-delivery or incomplete delivery
- supplying goods of inferior or substandard quality
- delivering fake, counterfeit or refurbished products
- not honouring warranty obligations
- unsatisfactory performance on a service contract
- delaying wages, PF or ESI for staff deployed at the buyer's site
- submitting fake documents or false statements
- wrong country of origin
- incorrect shipment details that trigger an automatic CRAC
- anti-competitive behaviour or cartels
- non-payment of transaction charges or the Annual Milestone Charge
Buyers can face incidents too, for example over delayed payment.
Who can raise an incident
Clause 1.4 lists five sources:
- a buyer
- a seller or service provider
- GeM Admin, on an offline request or on noticing a deviation
- the GeM system itself, which can raise incidents automatically
- the verifying agency or any other agency appointed by GeM
Incidents against a product or catalogue are pre-contract incidents. Incidents against a seller ID, order or bid are post-contract incidents.
| Incident against | Can be raised |
|---|---|
| A bid | Up to 180 days from the end of technical evaluation or the bid validity date, whichever is later |
| A contract | Up to 6 months after the delivery period or service end date, or an approved extension |
| A buyer, for seller dues | From the CRAC or SDAC until payment shows as Completed |
Four severity levels
| Level | Meaning in the policy |
|---|---|
| Mild | Deviations that affect the functioning of other stakeholders |
| Serious | Deviations with the potential to harm the market ecosystem |
| Severe | Deviations that harm the procurement process, or breaches of contract |
| Grave | Deviations that harm GeM's reputation or credibility and could significantly affect its market |
Annexure 1 of the policy assigns a level to each incident reason. For deviations not listed, GeM Admin decides the level.
Step by step: incident, 7 days, escalation, SCN
For a post-contract incident:
- Incident raised. The party it is raised against gets 7 calendar days to fix the problem and report the corrective action in the incident module. If it is fixed, the person who raised it can close it.
- Escalation. If it is not fixed, the reporter escalates to GeM Admin after receiving a reply or after the 7 days, whichever is earlier. Incidents created by GeM Admin escalate after 48 hours.
- Show cause notice (SCN). GeM sends an SCN on escalation, on the dashboard and by email.
- Reply within 5 calendar days. Respond on the incident dashboard. If you do not, the system warns you, and if there is still no response 10 days after the SCN, the system acts automatically. Automatic action is disabled for grave incidents, buyer debarment cases and "Other" incidents, which GeM Admin decides itself.
- Further clarification. GeM Admin can ask any party for more information, to be given within 5 calendar days.
- Decision. If there was no deviation, the incident is closed. If it was raised under the wrong reason, it is rejected. If the explanation is unsatisfactory, a moratorium or suspension follows.
All responses must be given on the incident dashboard, not by email. The policy also asks parties to avoid revealing identifying details there, such as names or phone numbers.
Pre-contract incidents differ: GeM Admin asks both sides for justification, then rejects or escalates, and no changes to the catalogue in question are allowed while the incident is open.
Suspension vs temporary moratorium: what you lose
| Effect | Temporary moratorium | Suspension |
|---|---|---|
| Used for | Mild, serious and severe incidents, and unpaid charges | Grave incidents and other cases needing stronger action |
| New bids and reverse auctions | Not allowed | Not allowed |
| Catalogues | Removed | Removed |
| New or updated offers | Not allowed | Not allowed |
| Dashboard and brand (OEMs) | Removed | Removed |
| Ongoing contracts | Can be completed and paid | Can be completed and paid |
| Public visibility | Shown in the suspended sellers list, with rating impact | Shown with rating impact and incident history |
Bids you had already entered before the action are processed under the policy's clause on ongoing bids. A seller suspended at bid opening is disqualified in technical evaluation; one suspended when the buyer creates the demand is disqualified and L2 is treated as L1.
Suspension periods by level
| Level | First and second deviation | Third and later deviations |
|---|---|---|
| Mild, within 90 days | 30 days | 45 days |
| Serious, within 120 days | 45 days | 60 days |
| Severe, within 180 days | 60 days | 90 days |
| Grave | 365 days | 365 days |
The periods apply to deviations within the window shown for each level. A grave suspension can be extended up to 2 years with the approval of GeM's Chief Marketplace Officer. A fifth established deviation under certain post-contract reasons leads to a 365-day suspension and removal of the seller's catalogues. For OEMs, repeated deviations under specified reasons can also lead to removal of the brand, dashboard and all catalogues.
Reductions for good history and buyer dues
For post-contract deviations, the period can be reduced on two grounds.
Good fulfilment history. If you had at least 20 contracts on GeM in the year before the incident, and not more than two incidents for the same reason in the last 30 days, your fulfilment rate counts. Fulfilled contracts are those with all CRACs or SDACs generated; contracts still within their delivery period are left out.
| Fulfilment rate in the last year | Period reduced to |
|---|---|
| 98% or more | 30% of the normal period |
| 95% or more but under 98% | 40% of the normal period |
| Over 90% but under 95% | 50% of the normal period |
Buyer dues. If the buyer that raised the incident has more than two of your contracts with CRAC or SDAC generated but payment overdue, the policy says the period "would be reduced to 30% of what otherwise is Applicable".
After reductions, minimum periods still apply: 10 days for mild, 15 days for serious and 20 days for severe deviations. Neither reduction applies to grave incidents or to buyer-specific debarment orders.
Appeal: once, within 10 days, new evidence only
- You can appeal after a moratorium or suspension is imposed.
- Appeal only if you have information or documents that were not available when GeM decided.
- File within 10 calendar days of the order, not counting the day it was issued.
- Only one appeal is allowed per incident.
- GeM can ask any party for clarification, with 5 calendar days to answer at each stage.
- The appellate authority can increase or decrease the period.
- The moratorium or suspension continues while the appeal is pending, whatever the outcome.
Appeals against buyer-specific debarment are made to the buyer organisation outside GeM.
Mutual closure
If the problem is fixed after escalation, you can ask for mutual closure. Before action is taken, the buyer can accept it. After action, the request goes to the buyer's primary user (HoD); if approved, the incident closes and all its effects are removed. You can make a mutual closure request once to the buyer and once to the HoD. It is not available for pre-contract incidents or incidents raised by GeM Admin or the system.
There is also a route to fix a problem after escalation: within 5 calendar days of the SCN, tell the buyer on the dashboard that you will rectify the deviation. The buyer has 5 calendar days to consent; silence counts as no consent. If you then fail to fix it, the buyer can re-escalate after 10 calendar days. Liquidated damages remain the buyer's right under the contract.
Unpaid transaction charges
Non-payment of transaction charges or the Annual Milestone Charge within the Revenue Policy deadlines is raised automatically by the system and treated as a temporary moratorium. The policy's annexure says the moratorium lasts for 2 years or until the seller pays, and the incident closes automatically and the account is restored within 24 hours of payment. The charges fall due by the earliest of 15 days from award, the first invoice or the first delivery due date.
How to avoid incidents
- Keep stock and prices accurate, because direct and L1 orders count as accepted.
- Deliver within the delivery period, or agree an extension on the portal.
- Enter correct shipment details.
- Answer every incident within 7 days and every SCN within 5 days.
- Pay GeM charges by the deadline.
- Keep certificates, licences and vendor assessment valid.
- Never list in the wrong category or declare the wrong country of origin.
Frequently asked questions
How long is a GeM suspension?
For a first or second mild deviation, 30 days; serious, 45 days; severe, 60 days; grave, 365 days. Later deviations and good history change the period.
Can I bid while under temporary moratorium?
No. You cannot join new bids or reverse auctions, and your catalogues are removed, but you can finish and get paid for existing contracts.
How do I respond to a GeM show cause notice?
On the incident dashboard, within 5 calendar days. After 10 days without a response, the system can act automatically.
Can I appeal a GeM suspension?
Yes, once per incident, within 10 calendar days, and only with new information.
Where is the list of suspended sellers?
The suspended, moratorium and buyer-debarred sellers list is displayed on the GeM portal.
What if I do not pay transaction charges?
The system places the account under temporary moratorium until you pay, and restores it within 24 hours of payment.