A GeM seller profile should identify the same enterprise across PAN, bank, Udyam or GST records, and product information. Product claims and catalogue entries need their own evidence; business registration alone does not establish the specification, price, or ability to supply an item.
Decide what the enterprise can truthfully offer
Before building a GeM seller profile, define the enterprise that will sell and the products or services it can actually supply. Reconcile the legal or proprietor name, PAN, bank account, Udyam or GST records where applicable, address, and authorised contact. Then describe the proposed catalogue item from its real specification, source, capacity, price basis, and delivery ability. Registration facts identify the seller; they do not establish every claim made about an item.
Choose catalogue entries that can be supported and fulfilled. A manufacturer, reseller, or service provider may need different evidence for a particular offering, but the profile should reflect the enterprise's actual role. Do not copy a competitor's description, claim a certification that the seller does not hold, or list supply capacity that cannot be explained. Resolve material differences between source registrations before they appear across bids, invoices, and bank records.
Separate enterprise records from catalogue claims
The issuing authorities own PAN, Udyam, GST, and other source registrations. The bank owns the account record. The seller owns the accuracy of its profile, catalogue, bid, price, and fulfilment statements, while GeM and the buyer control their respective platform and procurement actions. If the enterprise name is wrong at its source, correct it there before changing the seller profile. If an item specification or price entry is wrong, correct the catalogue or bid record rather than altering business registration evidence.
Keep proof behind each material product or service statement, including specifications, authorisations, certifications, or supply records where genuinely relevant. Preserve the submitted catalogue version and any platform or buyer query. A registration certificate should not be used to answer a technical-product question, and a catalogue listing should not be treated as proof that a buyer accepted or ordered the item. These boundaries make disputes easier to direct.
Follow listing, bid, order, and fulfilment independently
Create a chronology for each significant opportunity. Record profile completion, catalogue submission or update, bid version, buyer query, response, order or contract, delivery, acceptance, invoice, and payment communication. If the seller corrects a specification or enterprise field, note the effective date and the transactions affected. Do not overwrite the version relied on for an earlier bid or order.
When a problem arises, identify the stage and owner. A rejected catalogue item, a bid clarification, a delivery dispute, and a delayed payment are separate matters even when they concern the same product. Preserve formal platform and buyer references, and answer only the disputed fact with supporting evidence. The final trail should show what the enterprise offered, what the buyer requested, and what was delivered, without presenting registration as proof of technical compliance or procurement success.
Before reusing a catalogue entry in a later bid, compare its specification, price basis, and fulfilment assumptions with the new requirement. Record any revision and the evidence behind it. This prevents an accurate statement made for one order from becoming a misleading claim in another, and it gives the seller a clear reason for every material catalogue change.
GeM Seller: source pages and next actions
Read Government e-Marketplace official portal for the current instruction affecting business identity, bank, tax registration, product catalogue, and compliance records. Keep that GeM Seller page and its check date with the application record, and route an error in the underlying source to the issuer or programme channel that owns the disputed fact.