🎉 Your free trial plan has started. Plan will expire in 0 days

GeM Incident Management: How Sellers Can Handle Order Disputes, Buyer Complaints and Service Issues

GeM Incident Management: How Sellers Can Handle Order Disputes, Buyer Complaints and Service Issues
Pragati Tiwari
November 18th, 2026

For many GeM sellers, learning to use the Incident Management System comes with a stressful experience. A notification arrives. A buyer has submitted a complaint about an order. A response deadline is nearing. Unfortunately, sellers often lack clarity regarding the consequences of missing the deadline.

In the context of GeM, the term "incident management" denotes a formal process that is used to manage buyer-seller conflicts. It should not be used as an alternate channel to channel complaints and customer support requests. There are a defined number of stages and steps that govern the incident management process, and each stage has its own timeline and consequences. The incident management process, if left unaddressed, has the potential to result in negative ratings and suspensions.

Buyers and sellers who understand the incident management system protect themselves and handle conflicts efficiently. On the other hand, those who are uninformed about the process lose by default.

The intention of this blog post is to clarify how to make the best use of the incident management system. It explains the actions sellers need to take at each stage and, additionally, how to handle cases where the issue originates with the buyer.

Note: There are a few nuances with regard to the policy of GeM concerning the Incident Management System. Please ensure you go through the policy document and FAQs to make yourself aware of the latest updates.

What Incident Management on GeM Is

GeM (Government e-Marketplace) has a deviation policy that spells out what counts as a breach of the terms and conditions users agree to. It lists the situations GeM treats as “deviations”: non-delivery, wrong or substandard delivery, refusing to accept an order, failing to supply after accepting one, and misrepresenting a product in a listing. A seller can also be in violation when payment is delayed or when goods are rejected unfairly.

Deviations can happen before an order is placed (pre-order) or after it (post-order). GeM’s policy is also separate from the contractual terms between each buyer and seller, so a deviation doesn’t release anyone from their contractual duties.

This article looks at GeM Incident Management for post-order disputes, since those affect sellers the most. The incident management policy covers both buyers and sellers of goods and services on GeM. It gives users a way to report deviations from the terms agreed when a product was listed or a sale was made on the portal.

Users should also know that reporting a deviation through Incident Management is separate from any legal or contractual remedy a buyer or seller may have. GeM only facilitates the reporting of incidents. It takes no liability for any proceedings or remedies the parties pursue.

Post-order incidents can be reported at any time and in any form. They cover a range of problems, from disputes over the quality of delivered goods to non-delivery and late delivery.

The Basic Process Flow

The exact flow depends on the type of incident and the policy version in force, but the general sequence stays the same.

  1. Reported. The buyer, the seller or GeM raises the incident on the dashboard and states the category of deviation and the reason for it.

  2. Mutual resolution window. The parties are expected to try to settle the matter between themselves first. GeM’s materials describe a seven-day window for buyer and seller to resolve the issue before it escalates.

  3. Escalation. If the matter stays unresolved, the party who raised it can escalate it to GeM. According to the FAQs, when an incident is against a seller, the buyer can escalate after the seller’s first comment or after seven days from creation, whichever comes first. When it is against a buyer, the seller can escalate after seven days. GeM Admin can escalate sooner. For post-contract incidents raised by GeM Admin, the policy says they escalate automatically after 48 hours.

  4. Show cause notice and response. Once an incident is escalated, the system sends a show cause notice to the party at fault and asks it to explain. If a buyer is taking action against a seller, the policy requires the buyer to get internal approval from the competent authority on the disputed issue before raising and escalating the incident. The competent authority’s decision is then uploaded as the reply to the seller’s comments on the notice.

  5. Evaluation and decision. GeM reviews the incident and the responses, then issues a decision. Depending on the deviation and the policy, this can include a penalty, an impact on the seller’s rating or other action.

  6. Closure. The incident is closed once the issue is resolved or the decision has been carried out. The incident history stays on record.

What Happens If the Seller Wants to Fix the Problem

A lot of incidents involve problems that can still be fixed, such as a late delivery that can yet be completed or a gap in the paperwork. For these, the policy offers a rectification route.

As the process is described, a seller who has already corrected the deviation can say so on the incident dashboard. If the buyer is willing to allow rectification, the buyer has to give consent on the dashboard within five days of the seller’s request. After the fix is made, both buyer and seller update the status and attach valid documentation. If the seller then fails to do what it promised, the buyer can re-escalate the matter to GeM after ten calendar days.

The practical takeaway is that a credible rectification request, made early and supported by dates and documents, is often the cheapest way out of an incident. A promise with no date and no evidence behind it rarely convinces anyone.

Mutual Resolution After Action Is Taken

Sellers who have already had action taken against them still have a route open. On the incident detail page, the Mutual Resolution tab lets them submit a request for mutual resolution, as the FAQs describe. In practice it is a formal way of asking GeM to reconsider, either because the original problem has since been fixed or because the circumstances call for a different result.

It’s worth putting real effort into this request. A short, general plea rarely works. A request that comes with proof of delivery, the buyer’s acceptance, corrected documents or a written explanation of why the delay happened is far more likely to succeed.

Why Incidents Matter Beyond the Single Order

An incident doesn’t stay tied to a single order. GeM’s FAQs say that deviations feed into the overall seller and buyer rating, and that both the rating and the incident history can be seen on the GeM portal.

For sellers, that has three consequences:

  • Buyers can see your record. When a buyer is weighing you up, a pattern of incidents counts against you, whether it’s a competitive bid or a direct purchase.

  • Repeat or serious deviations bring tougher action. The policy allows escalating consequences, including penalties and restrictions on selling.

  • Some actions fall outside the standard GeM appeal route. Steps taken by a ministry, department or competent authority, such as debarment, may not go through GeM’s own appeal process. The FAQs indicate that in those cases the seller may take up an appeal with the buyer organisation offline.

Ignoring an incident costs more than that one order. It can change how every future buyer sees you.

Common Causes of Incidents Against Sellers

Most incidents come down to a handful of problems that keep repeating.

  • Delivery delay. This is the most common cause. The seller misses the date, never asks for an extension and then goes quiet.

  • Non-supply after acceptance. A seller accepts an order and then doesn’t deliver, often because the price or availability has changed since. The platform treats this as a serious deviation.

  • Wrong or substandard supply. The goods arrive in a different make or model, with accessories missing, with quality failures, or without meeting the specification.

  • Documentation and compliance gaps. Certificates are missing, invoices don’t match, registrations have expired, or statutory proof is absent in service contracts.

  • Service level failures. On service orders, this means poor attendance, slow response, or wages and statutory dues left unpaid.

  • Listing misrepresentation. The product details, specifications or prices in the listing don’t match what was actually supplied.

Once you know which category an incident belongs to, you know what evidence to put together.

How to Respond When an Incident Is Raised Against You

How fast you respond and how good your response is matter more than how polished it sounds.

  1. Open the incident right away and read all of it. Note the incident ID, the order number, the deviation category, who raised it, the reason given and every deadline on the screen.

  2. Don’t ignore it, and don’t argue over the phone. Bring the discussion onto the dashboard. A phone call leaves no record, and the incident record is what the decision makers will read.

  3. Check the facts against your own records. Look at order dates, dispatch records, transport receipts, delivery challans, consignee acknowledgements, inspection reports, correspondence and payment status. Work out what actually happened.

  4. Be honest about your position. The buyer is either right, partly right or wrong. A response built on the true picture is stronger than one built on a story your own documents contradict.

  5. If the buyer is right, offer to put it right. State the corrective action, the completion date and the plan behind it. Ask for the buyer’s consent on the dashboard, then keep to the date.

  6. If the buyer is partly or wholly wrong, answer with evidence. Upload proof of delivery, proof of acceptance, and anything showing delays or access problems on the buyer’s or consignee’s side, change instructions or an extension you were granted. Point to the specific clause in the order or terms that backs you up.

  7. Keep comments factual and short. Dates, documents and references persuade people. Complaints about unfairness and vague assurances don’t.

  8. Reply within the window. If you miss the response period, the process can move ahead on the buyer’s version of events.

  9. Update the dashboard once it’s resolved. Make sure the status shows the rectification, with documents attached, so the record is accurate.

How to Respond to a Show Cause Notice

A show cause notice is the formal step that comes right before a decision, so treat it as the most important document in the whole incident.

  • Read exactly what is alleged. Note which clause it falls under and what action is being proposed.

  • Check the dates. Pay particular attention to the response deadline.

  • Answer point by point. A general narrative is much easier to dismiss than a reply that takes each allegation in turn.

  • Attach organised evidence. Label each document and refer to it by name in your reply.

  • Admit genuine errors. Say what you have done to correct them. Credibility counts for a lot here.

  • Show buyer or consignee delays with records. If the delay or failure was caused on their side, back it up with dates and documents.

  • Ask for a hearing or reconsideration. Do this wherever the process allows it.

  • Keep a copy of everything you submit.

The buyer’s decision on the matter comes from a competent authority. A clear, well-documented response gives that authority a solid basis for reaching a fair outcome.

When the Seller Needs to Raise an Incident Against a Buyer

Sellers have rights too, and knowing how to use them is part of running a GeM business. The usual reasons for a seller to raise an incident are delayed payment after acceptance, unreasonable rejection of goods that conform, delayed or refused acceptance, unauthorised changes to the terms, and a buyer’s refusal to give the consignee access or confirmations the seller needs in order to deliver.

For delayed payment, guides written by sellers suggest a sequence. Write to the consignee first, then raise a GeM incident, then file a grievance on CPGRAMS, then use RTI with the buyer department, and, if you hold Udyam registration, file on the MSME dispute resolution portal. These are third-party recommendations and not official GeM procedure, so check the current requirements of each channel before you rely on them. The underlying approach still makes sense: begin with documented written follow-up, use the platform’s own mechanism, and move to formal channels only when you have to.

When you raise an incident against a buyer:

  • Quote the order number and specific dates. Include the delivery date, acceptance date, invoice date and the date payment fell due.

  • Attach your evidence. Add delivery proof, acceptance records, invoices and earlier correspondence.

  • State the remedy you want. Say clearly whether it’s payment, acceptance or reinstatement of the order.

  • Stay factual and professional. Your tone is part of your credibility with the officer evaluating the case.

  • Note the escalation timing. Sellers can escalate once the window has passed if the buyer hasn’t responded.

Raising an incident can feel like picking a fight with a customer. But a documented incident is often what finally gets a stuck file moving in a government department.

Evidence Sellers Should Collect on Every Order

Nearly every incident is settled by documents. Make a habit of collecting them on every order, not just the ones that go wrong.

  • The full order. Keep it together with all additional terms and conditions.

  • Key dates. Record when the order was placed, accepted, dispatched, delivered and installed, and when the consignee accepted it.

  • Dispatch and delivery papers. Hold on to dispatch documents, transport receipts and delivery challans signed by the consignee with a date and stamp.

  • Photos or video. Where it’s practical, capture the delivery and the installation.

  • Inspection reports and test certificates.

  • Extension requests in writing. Keep every request along with any reply or approval.

  • All correspondence. This covers emails and platform messages with the buyer or consignee.

  • Invoices and payment records. Add reconciliation statements as well.

  • Service order records. For services, keep attendance records, proof of wage and statutory payments, and service reports.

An incident is decided on the record, and the seller with the better record usually comes out ahead.

Preventing Incidents in the First Place

Incident management is there as a safety net. The best protection is making sure the incident never happens.

  • Accept only what you can deliver. Check your capacity, lead time and landed cost before you click accept.

  • Read the buyer’s additional terms. Most unpleasant surprises come from conditions the seller never bothered to read.

  • Keep your listings accurate. Specifications, lead times and prices should match what you can really offer.

  • Speak up early. If a delay is coming, tell the buyer in writing and ask for a formal extension before the date passes.

  • Follow up on acceptance. Delivery isn’t complete until the consignee records acceptance.

  • Keep statutory compliance current on service orders. Wages, provident fund, insurance and registrations should all be in order before you raise a bill.

  • Check the dashboard regularly. Missing a notification is the easiest way to lose a dispute, and it’s entirely avoidable.

  • Give someone ownership. One person in your organisation should be responsible for checking incidents and responding to them promptly.

Mistakes That Make Incidents Worse

  1. Silence. Not responding gets read as an admission, or as plain indifference.

  2. Verbal assurances. A promise made by phone to a consignee leaves no evidence, and people often forget it later.

  3. Over-claiming. An exaggerated or inaccurate reply loses credibility the moment your own documents contradict it.

  4. Late responses. Once the window closes, you lose the chance to influence the decision.

  5. Ignoring the rating effect. One incident is never really isolated, because the record is visible to every buyer.

  6. Escalating emotionally. A hostile tone toward buyers or officers rarely helps and often does damage.

  7. Not updating the status after resolution. An incident left open after the problem is solved can keep affecting your record.

Final Thought

Incident management is the point where GeM’s promise of a fast, open marketplace runs into the fact that government contracts are still contracts. Orders are binding, performance is recorded, and disputes are settled on documents and process.

Sellers who make the incident system part of their everyday operations tend to come through disputes without lasting harm. They check the dashboard, collect evidence on every order, communicate early, and answer notices with facts and proof. Sellers who see it as an annoyance to be ignored find that the process carries on without them.

A clean incident record is among the most valuable assets a GeM seller can build, and it gets built one order at a time: through reliable delivery, good documentation and professional conduct when something goes wrong.


Frequently Asked Questions