GeM vs CPPP vs Direct: Routes for Software

Software buyers in Indian public institutions inherit three habits. The GeM habit: if it is on the marketplace, buy it there. The CPPP habit: publish a full RFP on eprocure.gov.in the way the last large SI project was published. The direct habit: call the firm that did the POC and write a work order because the secretary saw a demo. Each habit is sometimes lawful. Each is sometimes a later paragraph in an audit.

This comparison is for procurement officers choosing a route for an on-prem agent platform, a hosted complement, or the implementation around either. It is not a declaration that one portal is modern and the others are obsolete. It is a map of which questions each route answers well.

Always overlay your own body's rules. A state that has notified its own e-procurement portal may treat CPPP as a cousin, not a home. A PSU manual may still prefer advertised tenders above a threshold even when GeM custom bid exists. This article uses the Union GFR + GeM + CPPP triangle as the common language.

What each route is actually for

GeM is a marketplace plus a set of bid tools. It shines when the object is catalogue-shaped or can be made evaluable in a GeM bid / custom bid: licences, AMC, standard services, many goods. It also carries policy machinery — MSE preference, Make in India filters, seller KYC — that you would otherwise reinvent. Rule 149 points many buyers here when the object is available.

CPPP (eprocure.gov.in) is an e-publishing and e-bidding home for tenders that look like documents: long RFPs, QCBS, complex evaluation, multi-lot SI projects. Many software programmes still live here because the evaluation is a booklet, not a parameter grid. CPPP does not by itself answer Rule 149 if the same service is available on GeM. Using CPPP because we always have needs a written reason. Direct purchase — on GeM within portal limits, or off-portal where your rules still allow small-value buying — is for objects that are clear, low enough in value, and not being split to evade a bid. Limited tenders, PAC / single source, and nomination exist in GFR for stated grounds. AI novelty is not automatically a PAC ground.

Choose the route that can carry your mandatory rows and your lawful channel duty.

Question	GeM	CPPP / e-procure	Direct / limited
Rule 149 when object is available	Default channel	Needs a written reason if you skip GeM	Only if the portal tool for that value is direct, or a lawful exception
Long QCBS booklet	Possible but often awkward; custom bid helps	Natural home	Unsuitable
Catalogue licence / AMC	Natural home	Heavy	If value and rules allow
Isolation ATCs	Put in bid / custom bid / ATC	Easy to attach as annexure	Easy to forget; do not
MSE / MII machinery	Built into many flows — confirm live	You must write it	Easy to skip unlawfully
Public discoverability	Sellers watch categories	Sellers watch tender titles	Only the people you called
Audit story	Search note + cart / bid id	NIT + corrigenda	Must be tighter, not looser

Software-specific traps on each route

On GeM, the trap is the almost-right listing: SaaS instead of on-prem, subscription instead of licence, a category that cannot hold isolation. Direct-purchasing that listing is the trap's mouth. On CPPP, the trap is a 90-page RFP copied from an SI mega-project, with eligibility that only three global firms can meet, while a GeM-available service sits ignored. The other trap is publishing on CPPP and GeM with different texts. On direct, the trap is the POC vendor becoming the production vendor without a documented market check. Another trap is splitting implementation into many small work orders to stay under a threshold. Auditors can add.

A decision order you can defend

Ask Rule 149 first, not last. If GeM availability holds, start on GeM and pick the portal tool that matches value and complexity. If you need a booklet evaluation, see whether a GeM custom bid can carry the booklet. If your manual still forces an advertised tender on CPPP, write the coexistence. Do not run two live competitions for the same object. If GeM availability does not hold, write the search note and then choose CPPP, the state portal, or another GFR-compliant path. Direct remains a function of value and urgency, not of embarrassment about portals. Whatever you choose, carry the same air-gap and DPDP rows. The portal will not remember them for you.

1. Object and mandatory technical rows first.
2. Dated GeM availability note.
3. If available: GeM tool (direct / bid / custom / RA) per current limits.
4. If not: CPPP or other lawful advertised path, with the same rows.
5. Direct or limited only with the GFR ground written.
6. One competition, one text.

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.

GeM cannot do QCBS.

Check the live portal and current buyer documentation before you repeat this. Some quality-cum-cost patterns exist or can be approximated in custom bids. If your QCBS is genuinely a booklet the portal cannot hold, write that. Do not assume 2018's GeM is 2026's GeM.

CPPP is more transparent.

Both can be transparent if you publish and both can be opaque if you hide corrigenda. Transparency is the text and the log, not the hostname.

Direct is fine; it is only software.

Software is easy to copy and easy to lock into. Direct needs the same hygiene as a chair: value, reasonableness, no splitting, right object.

Pick a route in one sitting

1. Write the object and the rows.
2. Do the GeM search note.
3. Read your manual's threshold and portal clauses.
4. Choose one home for the competition.
5. Put Rule 149, MSE/MII and isolation in that home.
6. Brief the committee on why the other homes were not used.

How this shows up in the file

A route note of ten lines prevents a six-month complaint. Portal, why, what was not chosen, where the rows live, who certified reasonableness. If your state portal is the real CPPP, name it. Do not pretend eprocure.gov.in is the only e-procure.

QCBS and the booklet problem

Quality-cum-cost evaluation is why many software programmes cling to CPPP. They have a 30-page marking scheme and a committee that knows how to sit with it. GeM has grown tools; it may still feel awkward for a 30-page scheme. Before you flee to CPPP, try to express the quality that actually matters — isolation artefacts, language eval, exit — as pass/fail gates plus a short score. Many AI buys do not need a 30-page scheme. They need five gates that can fail a phone-home runtime. If you truly need the booklet, write why GeM could not hold it this month, and still do the availability search.

Corrigenda are a route risk

Whatever portal you pick, corrigenda that change isolation rows after bidders have priced are how you buy complaints. Freeze the air-gap annexure before you publish. If a pre-bid meeting forces a change, extend time and say what changed in one table. Two portals with two corrigenda is chaos. One portal with a dated table is adult.

Direct without becoming casual

Direct is lawful in its lane. Write the object, the limit, the reasonableness, the screenshot. Do not use direct because a founder is in the building. Do not use direct because the POC went well. Those are reasons to write a fair bid the POC vendor can win, not reasons to skip the field. If your body still allows off-GeM small-value buying, prefer the GeM direct tool when the listing is the object, so you stay in the channel and the KYC.

This article is informational field guidance, not legal or procurement advice. Confirm against the current General Financial Rules, Department of Expenditure OMs, 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 vs CPPP vs Direct: Routes for Software” as an operating problem, not a thought piece. A P2 Procurement who searches “GeM vs CPPP procurement” 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.

Portals are not religions. GeM is the default channel when the Rule says so. CPPP is still where many large RFPs live. Direct is a value-and-urgency tool, not a personality type. 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 vs CPPP vs Direct: Routes 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 vs CPPP procurement” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.