GeM Category Creation: How to Petition

The closest GeM category wanted a licence metric the product did not have and a hosting field that assumed a URL. The founder mapped on-prem to hosted to get past validation. Six weeks later a buyer raised a catalogue incident. The listing was accurate only in the founder's head.

Category creation is the grown-up path. GeM knows categories lag products. Buyer FAQs tell buyers to use Request Management. Sellers have a request path of their own. Startup India even advertises less restrictive treatment for innovative products. None of that is a same-day SKU. It is still better than a bent printer.

This is a petition guide. Confirm the live labels on gem.gov.in. This is not legal advice.

When to petition rather than map

• The mandatory specifications assume a hosted URL and you sell an air-gapped install.
• The unit of measure is seats or boxes and you sell an environment plus support.
• The category forbids a training-ban or data-residency attribute you need buyers to filter on.
• Two honest products are being forced into one SKU, so comparability is already dead.
• A PAC conversation has started only because the category cannot express the constraint.

Who should ask

A seller-only request looks like a marketing wish. A buyer request looks like demand. The strongest pack is both: a department that wants to buy under Rule 149 without leaving GeM, and a seller who can describe the article. If you have a friendly indentor, ask them to raise the buyer-side request and give them the specification draft. Do not write their PAC. Do write their category fields.

What to put in the request, and what to leave out

Include	Leave out
Plain-language article definition a joint secretary can repeat	Sovereign, revolutionary, first-in-India
Mandatory specs that are tests: on-prem, no training, log export	Brand names and model numbers
Unit of measure that matches delivery	A unit you will later argue about in CRAC
How buyers will search for it	A demand for exclusive listing
Similar existing categories and why they fail	Abuse of those categories as a threat

The petition text

Request type: new category / specification change, as the form then labels it.

Proposed name: On-premises / air-gapped software agent platform (or whatever GeM's taxonomy can swallow).

Definition: software that plans and calls tools to complete an official workflow, with inference and logs inside the buyer's perimeter, without training on the buyer's data unless the contract says otherwise.

Why existing categories fail: [name two], because they require [URL / seat metric / OEM brand] and cannot express [air-gap / training ban / deletion certificate].

Suggested mandatory specifications: deployment mode; training on customer data (yes/no); log export format; exit and deletion certificate; environment count.

Buyer interest: [organisation], indent in draft / bid planned in [month]. We will list only what we ship.

Two petitions

Startup Runway, if you use it, is a parallel discovery door, not a substitute for a production category. A buyer who finds you on Runway still needs a bid path that can carry on-prem tests. Tell them that in the first call. Otherwise they will try to cart a showcase listing and you will both be sorry.

While you wait

1. Use custom bid or a service bid that can carry your ATC.
2. Look at Startup Runway if you are DPIIT recognised and the product is genuinely new.
3. Do not clone three near-miss listings.
4. Keep the request id in the bid folder so a committee can see you tried.
5. If GeM asks for clarification, answer in five calendar days as if it were an incident clock.

Objections

Competitors will use the category we created. Good. That is how PAC pressure falls and reasonableness becomes possible.

GeM never replies. Then keep the custom-bid path and the dated request. Silence is not permission to tinker.

We will just put the real spec in the product description. Hidden specs do not flow into comparison. They flow into incidents.

A spec tree GeM can actually build

Category teams do not need your brand story. They need fields with values. Deployment: on-premises, air-gapped, or hosted. Training on customer data: prohibited, permitted with written order, or unspecified. Log export: supported format list. Human approval before outward correspondence: required or not. Environment count: one, many. Support: business hours in named cities, or remote only. Each field should have values a comparison table can sort.

If you cannot express a constraint as a field, you cannot expect GeM to police it. Putting the constraint only in a product description is how two unlike articles look comparable and then fight in an RA. The petition is your chance to make unlike articles look unlike.

Bring a buyer who has a draft indent. GeM evaluates demand as well as neatness. A category with no likely bid is a taxonomy hobby. A category that unblocks a Rule 149 purchase this quarter is work. Give the buyer a paragraph they can paste into their request so they do not have to invent your product in official language at midnight.

If GeM instead maps you to an existing category and adds a specification, take the win. Pride in a new name is not the goal. The goal is a mandatory field that can fail a hosted copilot when the department asked for an air-gap. That field is worth more than a heading.

Fifteen-day petition playbook

• Days 1–3: screenshot the failed category fields.
• Days 4–6: draft definition and mandatory tests. Strip adjectives.
• Days 7–8: ask one real buyer to raise or endorse.
• Day 9: submit. Save the id.
• Days 10–15: decide the interim bid path. Brief sales not to invent a mapping.

Note for the listing folder

Existing GeM categories [names] cannot express [constraints]. Request [id] filed on [date] via Request Management. Interim selling path: [custom bid / service / Startup Runway]. No stretched catalogue will be created. Buyer endorsement: [yes/no].

Prcept AI would rather wait for a category that can say on-prem and no training than win a cart on a lie. If you are writing the buyer request, use the test list, not our brand.

How a buyer or seller should act on this

Treat “GeM Category Creation: How to Petition” as an operating problem, not a thought piece. A P5 Founder who searches “new GeM category request” 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.

If the category cannot describe on-prem inference and a training ban, do not bend a nearby SKU. Petition through GeM Request Management and bring a buyer with you. That is why this guide 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 Category Creation: How to Petition” 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 P5 Founder, not “the vendor.”

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

What the next noting must contain

“GeM Category Creation: How to Petition” belongs in a file, not only in a search result. A P5 Founder should be able to point at one artefact that proves “new GeM category request”: a packet capture, a processing schedule, a scored evaluation row, a dated notice, or a refusal rule. If the only evidence is a slide, you have a heading.

If the category cannot describe on-prem inference and a training ban, do not bend a nearby SKU. Petition through GeM Request Management and bring a buyer with you. DPDP 2023 does not define sovereign AI and does not write a blanket localisation rule for every model hop. CERT-In’s 28 April 2022 directions still set specified incident clocks and 180-day log retention in India for in-scope events. The November 2025 AI governance text is guidance, not a statute. A Proprietary Article Certificate, when it is lawful, lives in GFR Rule 166 — not Rule 161.

Write three dated sentences under C3 GeM & Procurement: what was decided, which designation owns it after the next posting order, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the designation that owns “new GeM category request”, plus a deputy.
• Attach one artefact a stranger can open next year.
• Name the instrument you are actually using — Act, direction, GFR clause, GeM term, or guideline paragraph.
• Leave unsourced percentages, GMV slides and house forecasts out of the noting.
• Revisit when the model, the SI, the notice, the region or the posting changes.