GeM Order Cancellation: Grounds and Recourse

The purchase order had been accepted on a Thursday. On Monday the deputy secretary returned from leave and said the department had 'changed its mind' about an on-prem agent. The buyer clicked toward cancellation. The founder, who had already blocked two engineers and ordered a disk for media transfer, opened GeM’s incident pages for the first time.

Cancellation is a cluster of different acts: a bid withdrawn before award, an order cancelled before acceptance, a contract cancelled after acceptance, a consignee refusal, a mutual closure, or an admin decision after a show-cause. People use one word for all of them. The portal does not.

This guide is for the founder who just had an order yanked, and for the DDO who is being told to yank it. It is not a restatement of GeM’s incident policy and not legal advice. Policies are updated on gem.gov.in. Open those pages for the instrument you used, then use the map below to decide what fact you actually have.

Name the act before you name the outrage

If the bid is still open, withdrawal and amendment follow bid rules, not contract rules. If an order has been generated but not accepted, the duties differ from a contract the seller already accepted. After acceptance, cancellation is a contract event and often an incident event.

Buyer-side incident pages have long treated cancellation after the seller has accepted as a buyer deviation unless a recognised ground exists. Seller-side pages treat refusal to supply after acceptance as a seller deviation. Both can be true in the same week if each side tells a different story about why the work stopped.

Read the live incident FAQs before you file. Some tickets cannot be closed by the parties after GeM admin has issued a show-cause. Mutual-closure options, where they exist, are limited to certain incident types — commonly described on the FAQ pages as available for some bid/contract incidents and not for catalogue incidents. Confirm the current text. Do not promise a close the policy does not give.

Grounds that usually exist — and stories that do not

Recognised grounds live in the contract, the ATC, and the current GeM terms: delay beyond the allowed period, specification failure at inspection or acceptance, force majeure as defined, a sanctioned termination clause, or a documented buyer default such as site not ready. 'We found a cheaper deck' is not a ground. 'The secretary is no longer excited' is not a ground.

For software, specification failure has to be tied to a written requirement. An agent that boots but fails the gold set you put in the ATC is a different fact from an officer who dislikes the tone of a draft. Write the fact.

If the department never provisioned the VLAN, identity or test data, a seller delay may be a buyer-caused delay. Cancelling for that delay and then rating the seller is how you lose the incident you thought you were opening.

If the middle column has no answer, do not click cancellation to 'sort it later'. Later is the incident.

Story in the WhatsApp group	Question the portal will ask	Paper that should already exist
Changed our mind	Is there a termination-for-convenience clause you actually signed?	The contract / ATC termination clause, competent-authority approval, payment for work done if required
Seller is late	Was the site, identity and data ready on the start date?	Delivery schedule, delay notices, buyer-readiness emails
Software does not work	Against which numbered specification or gold-set case?	Acceptance test record, defect notice, cure period
Budget frozen	Does the contract treat this as termination, and who pays sunk cost?	Finance note, competent authority, communication to seller before the click
Wrong SKU ordered	Is this buyer error or seller mis-catalogue?	The indent versus the PO; whether cancellation is the honest path versus amendment
Mutual — both want out	Does this incident type allow mutual closure, and who must confirm?	A written scope of what is being unwound, including data deletion

Seller recourse without theatre

First, freeze facts: order number, acceptance timestamp, what you have already delivered, what the buyer has not provided, and every written instruction to stop work. Do not keep shipping into a cancellation fight hoping it proves goodwill. It can also prove you ignored a stop.

Second, use the portal path: respond to the incident with documents, not adjectives. Attach the ATC, the acceptance, the readiness mails, the defect notices. GeM admin, if they enter, will not watch your explainer video.

Third, know the limits. Portal remedies are portal remedies — ratings, suspension recommendations, administrative findings. They are not a decree for your engineering sunk cost. If the rupees matter, the contract’s dispute clause and ordinary civil routes exist; this article will not choose them for you. Speak to counsel before you threaten them in a GeM comment box.

• Export the contract PDF and the incident thread the day it starts.
• Stop informal voice notes to the consignee; put facts on the ticket.
• Offer a structured unwind: data deletion, media return, invoice for accepted milestones if any.
• Do not retaliate by withholding admin passwords the contract says you must hand over.
• If you are in the wrong — you cannot perform a yes you ticked — propose a cure or a clean exit before admin does it for you.

Buyer recourse without wishful clicks

If the seller cannot perform, issue a defect or delay notice that quotes the clause, give the cure window the contract gives, then terminate on that paper. A sudden cancel the day after a minister’s meeting looks like convenience even when the defect is real.

If the department is the problem, say so internally and take competent-authority approval for a convenience termination if the contract allows it. Paying a documented sunk-cost invoice can be cheaper than an incident that freezes the cell’s GeM reputation.

Do not refuse a conforming delivery at the gate to force a cancellation. Consignee refusal is its own deviation on the buyer incident pages.

Software-specific unwinds the printer policy never mentioned

An agent leaves residue: accounts, embeddings, prompt logs, a fine-tune, a jump-host user, a copy on a vendor laptop used during install. Cancellation without a deletion and access-removal schedule is not an unwind. It is an abandoned processing activity.

Write that schedule even in a fight. Both sides look better if the citizen data left the seller on a dated certificate. DPDP duties do not pause because GeM is angry.

Licence keys and offline entitlements should be listed. A cancelled on-prem install that still phones a licence host you forgot to revoke is a security note waiting for the CISO.

Sentences that make cancellations sloppier

If you hear these, open the contract before anyone opens the portal menu.

It is only a click. We can re-issue later to the same seller.

Clicks create incident history, rating effects and a paper trail of indecision. Re-issuing to the same seller after a convenience cancel can also look like a split or a favour. Use amendment if the contract allows a scope change.

GeM admin will decide who is right, so we need not write notices.

Admin decides on the documents you already created. If you created none, you have given them adjectives. Write the defect notice first.

We will settle on a phone call and leave the portal as is.

The portal state is the state a later auditor will see. If you have unwound, make the ticket and the contract state match the unwind, including data deletion.

Startups should absorb a cancel; that is the cost of government work.

No. A lawful cancel may still have commercial consequences the contract named. An unlawful convenience cancel is not a teaching moment. It is a buyer deviation.

Seven days after the cancel threat

Whether you are the seller or the DDO, the first week is for facts, not for social media.

1. Day 1: export PO, acceptance, ATC, messages, and name the act — pre-acceptance, post-acceptance, bid cancel, mutual.
2. Day 2: list obligations already performed and buyer-readiness gaps. Stop or continue work only on a written instruction.
3. Day 3: issue or answer a clause-quoted notice. Offer a structured unwind including data and keys.
4. Day 4: file or respond on the incident with exhibits, not narrative essays.
5. Day 5: competent-authority brief on rupees, reputation and service impact.
6. Day 6: if mutual exit is allowed for this incident type, write the deletion certificate into it.
7. Day 7: decide counsel, wait, or cure. Do not add a new threat every afternoon.

What goes in the file the day the order wobbles

Put the contract, the acceptance timestamp, every stop-work or defect notice, the incident ID, the deletion/access-removal plan, and the competent-authority decision in one folder. If money changed hands, add the invoice and the payment advice.

The folder should answer three questions without you: what act occurred, which clause allowed it, and what happened to the data. If it cannot, you are not finished.

GeM incident management and cancellation terms are portal-controlled and change. This guide is not legal advice and not a restatement of gem.gov.in. Read the current buyer and seller incident pages and your signed contract before you act.