REFERENCE GUIDE

GeM Buyer Registration: The Process, HOD & User Roles Explained

By Chandan Kumar
Updated July 2026
11 min read
GeM buyer registration is restricted exclusively to authorized government entities leveraging official credentials. A designated primary user (typically the Head of Department or office head) acts as the organizational anchor, provisioning secondary users who execute day-to-day procurement under strictly compartmentalized role structures. Private commercial enterprises are structurally barred from registering as buyers — businesses operate strictly on the supply side; seller registration is available here.
GeM Buyer
ACCOUNT STRUCTURE

Serving as an authoritative reference manual, this documentation approaches GeM architecture through a specialized seller-side consultancy lens. Developing granular literacy around internal buyer operations empowers commercial vendors to execute precision maneuvers across everything from interpreting complex purchase orders to systematically tracking Consignee Receipt and Acceptance Certificates (CRACs). For government procurement officials utilizing this portal, this structural map delivers the core orientation often omitted during standard administrative onboarding.

Who can register as a buyer?

GeM buyer registration is strictly authorized for government and government-adjacent institutions, encompassing central ministries and departments, state-level administrative departments, Public Sector Undertakings (PSUs), statutory autonomous bodies, and local municipal authorities.

The fundamental security gatekeeper is verifiable institutional identity: system onboarding operates entirely on official domain credentials (specifically gov.in-family email infrastructure) rather than individual or commercial email accounts. Commercial enterprises cannot register as buyers under any statutory provision. Inquiries such as "can my business buy on GeM" terminate here with a definitive negative; commercial vendors belong exclusively on the fulfillment side, managed via GeM seller onboarding protocols.

Primary user (HOD): the account anchor

The primary user — functioning routinely as the office's Head of Department (HOD) or an authorized senior administrative officer — initializes the organizational profile by registering core entity metadata, executing official email validation, and mapping internal administrative hierarchies.

Beyond account creation, the primary user’s core mandate centers on structural governance: provisioning and supervising secondary users, defining precise transactional permissions, and accepting full administrative accountability for the entity's platform conduct.

Frequent personnel transfers, postings, and retirements generate recurring lifecycle administration queries across system logs:

  • Changing/transferring HOD: Administrative succession requires formal primary-user transfer workflows. This transition must be executed during active operational handovers rather than months post-transfer when legacy email addresses become defunct; orphaned accounts represent a major administrative vulnerability.
  • Deactivating a primary user: Executed in direct conjunction with succession protocols. Comprehensive step-by-step procedures are detailed in the dedicated user management guide.

Secondary users: where procurement actually happens

Operating downstream from the primary account anchor, secondary users execute day-to-day procurement operations — generating demands, evaluating catalog parameters, issuing formal supply orders, and recording physical fulfillment. User permissions map directly to established public procurement functions:

Role Operational Function
Buyer Role
Initiates internal demands, conducts exhaustive technical/financial comparisons, administers competitive bids and Reverse Auctions (RAs), and formally issues purchase orders.
Consignee
Performs physical receipt inspection, verifies technical compliance, and generates Provisional Receipt Certificates (PRC) and CRAC documentation (critical for vendors, as processing payment clocks hinge entirely on this desk).
Payment Chain (DDO/PAO)
Disbursing Officer (DDO) and Pay and Accounts Office (PAO) frameworks bridging finalized order settlements with national Public Financial Management System (PFMS) disbursement channels.

Effectively managed public offices enforce strict structural separation across these roles, adhering precisely to standard separation-of-duties audit controls mandated throughout public finance regulations.

How buying works, once registered

Once registered, the buyer's operational toolkit aligns systematically with defined monetary purchase slabs: direct procurement within baseline thresholds, mandatory L1 price evaluation across mid-tier brackets, and comprehensive bidding or Reverse Auctions for high-value acquisitions — complemented by special procurement mechanisms including Proprietary Article Certificates (PAC) for specialized requirements and Non-Availability Certificates (NAC) for authorized off-GeM exemptions.

Procurement workflows remain bound by rigorous compliance overlays, including mandatory MSE preference quotas, Make in India (MII) domestic value-addition mandates, and automated conduct monitoring systems — notably red and orange buyer penalty flags — designed to penalize procedural violations such as malicious purchase-splitting.

Why sellers should care about any of this

Mastering the underlying mechanics of buyer administration yields four distinct strategic advantages for commercial vendors:

Chase the right desk

CRAC bottlenecks reside exclusively with the consignee; payment processing files rest within the DDO/PAO hierarchy. Utilizing the specialized chase playbook succeeds because follow-up communications target the exact accountable desk.

Read order behavior

Analyzing order sizes clustering immediately below statutory slab limits, quarter-end budgetary expenditure spikes, and shifting direct-versus-bid patterns offers high-value intelligence into buyer constraints and inventory forecasting.

Spot trouble early

Identifying incoming orders originating from flagged procurement profiles or transactions indicative of purchase splitting allows vendors to recognize and price or mitigate compliance risks proactively.

Serve better

Vendors who optimize administrative friction for the buyer — providing immaculate documentation, inspection-ready consignment packing, and robust CRAC-ready verification evidence — position themselves as preferred suppliers within governing regulatory frameworks.

FAQs

Who can register as a buyer on GeM?
Authorized government entities and their designated officials operating via official domain credentials. Private commercial enterprises are strictly ineligible to register as buyers.
What is HOD in GeM?
Head of Department — designated as the primary user who initializes and anchors the organization's institutional buyer account while overseeing user governance.
What is the difference between primary and secondary users?
The primary user holds administrative ownership and governance over the corporate entity account, whereas secondary users execute transactional tasks under assigned role constraints (demands, ordering, receiving).
How do I change the HOD/primary user in GeM?
Through the official primary-user administrative transfer workflow (step-by-step protocols outlined here), optimally executed during official staff handover intervals.
Can one person hold multiple roles?
While technically permissible within smaller administrative units, strictly separating operational roles across distinct personnel represents the required audit-safe standard.
How does a government buyer create an account?
Initiated via official email authentication, followed by institutional entity profiling, primary-user profile establishment, and subsequent provisioning of secondary users with granular role mapping.

Lost a bid and never learned why?

Bring it to us — ATC autopsies are usually five-minute diagnoses.

Bid & Tender Support

Let our experts handle document compliance and checklist audits.