Quick answer
If you are a government officer or department head, one wrong move during registration can deadlock your procurement pipeline. Here is the full onboarding playbook.
If you are a government officer or department head, "winging it" during registration is not an option. One wrong move on your Aadhaar-linking or email domain, and your procurement pipeline hits a deadlock. Here is the declassified intelligence on setting up a 2026-compliant Buyer Account.
Phase 1: The Reconnaissance (Prerequisites)
Before you initiate the sign-up sequence, verify your "Field Kit" contains these mandatory components:
- Gov Key: Your official email ending in @gov.in or @nic.in. If your department uses private servers, you must apply for a @gembuyer.in alias via the GeM helpdesk before proceeding.
- Identity Link: The Primary User's Aadhaar must be active and linked to their current mobile number, as the OTP is the only way through the firewall.
- Organization Asset: A digital copy of your Departmental PAN and an Authorization Letter signed by the Head of Office.
Phase 2: Deployment (The Registration Flow)
This is the operational sequence for a zero-error setup:
Identity Authentication: Visit the GeM portal and select Sign Up as a Buyer. Once you enter your Aadhaar and mobile, the system pulls your data directly from the UIDAI vault.
Asset Mapping: Select your Organization Type (Central, State, PSU, or Autonomous). Mismatching your Ministry or Department name with the official gazette will lead to an immediate rejection.
Command Credentials: Choose a professional designation-based User ID rather than a personal name for better continuity, as this ID is permanent. Once the Primary User is verified, they must log in to the dashboard to configure the rest of the team.
Phase 3: The Command Structure
Efficiency fails when everyone has the same keys. You must distribute roles based on the Principle of Least Privilege.
| Role | Operational Rights |
|---|---|
| Primary User | Creates the account, manages users, and oversees the entire procurement. Cannot place orders. |
| Secondary User (Buyer) | Browses the catalog, creates comparisons, and initiates the Direct Purchase or L1 Selection. |
| Indentor | A 2026-specialized role. Finds products and "carts" them, then transfers the cart to the Buyer for final approval. |
| Consignee | The boots on the ground. Generates the CRAC (Consignee Receipt and Acceptance Certificate). No CRAC means no payment. |
Ready to win more tenders?
Bid India scans 100+ procurement portals and matches opportunities to your company profile.