GeM Custom Bid vs Direct Purchase for Software

Direct purchase on GeM feels like competence: a listing, a comparison price, a cart, a consignee. Custom bid feels like delay: specifications, ATCs, a waiting room of clarifications. That emotional difference is why air-gapped platforms keep getting bought as if they were toner. The listing was easy. The isolation was not on the listing. The file now holds the wrong tenant.

This comparison is for procurement officers deciding the GeM tool, not whether to leave GeM. Rule 149 still sits on availability. Both tools can be through GeM. Only one of them can carry an annexure that an evaluator can fail.

Value thresholds for direct purchase versus mandatory bidding change. Read the current Rule, OMs and the portal's own limits. This article will not reprint a rupee line that will be wrong next financial year. Use the logic; look up the cut-off the morning you file.

What direct purchase can honestly carry

A versioned on-prem licence whose specification parameters already include the deployment mode, the support years, and anything else you would have written as mandatory. A GPU workstation that is actually in stock. A training pack with a clear seat count. Objects the catalogue already knows how to describe. Direct purchase cannot honestly carry a no-outbound drill, a six-site media protocol, a DPDP processor schedule, or a QCBS-like quality story unless those are somehow fully expressed in the listing you are comparing. They almost never are. Comparing L1 among three similar listings is not the same as evaluating an isolation annexure. If your technical committee needs to mark rows, you are in a bid.

If the committee must mark, do not cart. If the listing is the object, do not write a novel.

Situation	Direct purchase if rules allow	Custom (or ordinary) bid
Catalogue SKU is the object	Yes, within live value limits	Optional if you still want more competition
SKU exists but cannot express isolation	No — you would be buying a different object	Yes, with annexure / ATC
Multiple sites, one architecture	Risky; quantity hides complexity	Yes, consignees and drills in the packet
You need startup/MSE preference applied a certain way	Confirm live tool behaviour	Often clearer in a bid if the portal evaluates it there
Thin market, one serious on-prem vendor	A cart will look like a nomination	A bid records who was invited and who declined
POC licence, tiny value, no personal data	Often yes	Overkill if the object is truly the listing

What custom bid is for

Custom bid is GeM's way of admitting that not every object fits a frozen specification template. You describe the requirement, attach ATCs, and let registered sellers respond. It is still through GeM. It is still a competition if you run it as one. It is the natural home of the air-gap annexure in this batch. It is also easy to abuse: a custom bid so brand-specific that only one startup can answer, or so vague that every SI will tick yes. The annexure article is the antidote to vagueness. Legal is the antidote to brand locks. Custom bid is not an exemption from reasonableness, MSE/MII fields, or your manual's publicity norms. Do not treat the word custom as private.

A decision test in five lines

One: is there a live listing that is the same object, including mandatory isolation and support mode? Two: does my current threshold even allow direct? Three: does a committee need to mark rows the listing cannot hold? Four: would a cart look like a nomination in a thin market? Five: can I write this choice in a paragraph an auditor will accept? If one is no, or three is yes, or four is yes, you are in a bid. If one and two are yes and three and four are no, stop writing theatre and buy the listing.

1. Write the object and the mandatory rows.
2. Search listings; file whether any listing is the object.
3. Look up today's direct-purchase limit; do not remember it.
4. Choose cart or custom/ordinary bid.
5. If bid, paste the annexure and the payment hook.
6. If cart, paste the screenshot that proves the listing held the rows.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Custom bid takes too long for the secretary's date.

Then shrink the object to something a listing can carry — a lab licence, a CPU POC — or move the date. Do not cart a different object to protect a calendar.

We will direct-purchase and add an MoU for isolation.

An MoU after a cart is how terms fight. If isolation is mandatory, it belongs in the competition. Post-hoc paper is how both sides win until an incident.

Custom bid reduces MSE participation.

Not if you write rows that artefacts can meet and you keep eligibility relaxations available as current policy allows. A vague goods cart that only three SIs understand is not pro-MSE. Confirm live preference rules either way. GeM FAQs typically describe MSE purchase preference as an L1+15% price-match window, and a buyer can involve more than one MSE — confirm live portal terms.

Choose the tool before you choose the vendor

1. Hour 1: object and rows.
2. Hour 2: listing search and threshold lookup.
3. Hour 3: five-line test in the note.
4. Same week: either cart with screenshots or issue the custom bid.
5. Never start a vendor demo series before the tool is chosen — demos will pick the cart for you.

How this shows up in the file

The five-line test is the file. Attach screenshots. If you chose custom bid, attach why no listing was the object. If you chose direct, attach why the listing held the rows. A later officer should not have to infer your tool from the invoice type.

How to write a custom bid that is still a market

Invite widely enough that a rival can appear. Use functional rows, not a product name. Publish the isolation annexure. Give time for a pre-bid. Publish a query table. This is slower than a cart and faster than a court. A custom bid that names a single startup's SKU in the title is a nomination with extra clicks. If only one seller can isolate today, you may still run the bid so the emptiness of the market is on paper. Then your single-source or limited path, if you take it, has evidence.

Direct purchase checklists that keep you honest

Before you click buy: screenshot the listing's deployment mode and support mode; confirm they match the note; confirm value versus today's limit; confirm you are not splitting last month's work order; certify reasonableness; confirm MSE/MII fields if the portal shows them. If any screenshot would embarrass you in a PAC, do not click.

The politics of the easy cart

Secretaries like carts because they look like action. Give them a one-week custom-bid calendar instead of a no. A short bid with a frozen annexure is still action. A cart of the wrong object is action that will be undone. If political time cannot stand a week, shrink to a listing that truly is a POC object — no personal data, CPU, one site — and write that production will be a bid. Do not let the POC cart become production by inertia.

This article is informational field guidance, not legal or procurement advice. Confirm against the current Gazette, GFR, live GeM terms on gem.gov.in and your counsel before you file it.

How a buyer or seller should act on this

Treat “GeM Custom Bid vs Direct Purchase for Software” as an operating problem, not a thought piece. A P2 Procurement who searches “GeM custom bid software” is usually one bid, one CRAC, or one rejection away from a cash event. The file that wins is the one with dates, document names and a named officer — not a paragraph that restates GeM’s homepage.

Direct purchase is for a listing that already is the object. Custom bid is for the object your annexure has to create. Most on-prem agents are the second. That is why this comparison ends in artefacts: screenshots of the live portal term, the clause you invoked, and the date you last checked it. GeM, GFR notes and state portals move. A citation without a date is folklore.

Confirm the live GeM FAQ, the current revenue policy and the bid text before you copy any number from a blog — including this one. If the portal and this article disagree, the portal wins. Put the printout in the file.

• Write the purpose of the buy in one sentence a DDO will sign.
• Name the route: catalogue, custom bid, bid, RA, CPPP, or state portal.
• Attach the exemption or preference documents you will actually upload (Udyam, DPIIT, MII, OEM).
• Record who can accept the consignee receipt and who raises the bill.
• Do not invent a category, a PAC, or a price-reasonableness story after L1 is public.

Close this loop before the next CAB

Put “GeM Custom Bid vs Direct Purchase for Software” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P2 Procurement, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “GeM custom bid software” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.