Procurement · GeM

An OEM on GeM since 2018 — eight categories

Registered on GeM as an OEM since 2018, across eight categories from servers to mini PCs. What that changes for a buyer, how a custom bid differs from a catalogue purchase, and what evidence a specification can ask for.

The status

An OEM on GeM since 2018, not a reseller with a catalogue

GeM distinguishes between sellers who make a product and sellers who resell one, and the distinction carries obligations rather than badges. We have been registered as an OEM since 2018, across eight categories, which means the machines on our listings are machines we build.

For a buyer comparing two identical-looking listings, that is the difference that does not appear on the screen. An OEM can answer a specification question about the product rather than relay it, can commit to a configuration for a repeat order, and remains the party responsible when something has to be fixed in year four.

It also changes what a custom bid can be. A reseller quotes what the catalogue holds. We can quote what the workload needs, because the configuration is ours to decide.

Eight categories

All eight are machines we manufacture ourselves

Eight categories on GeM, and every one of them is something we manufacture rather than resell.

Buying modes

Five routes, and what each one suits

The mode is chosen before the specification is written, and it constrains what the specification can ask for.

Seller types

Who you are actually buying from

GeM records the distinction. A listing does not make it obvious, and it decides who answers when something is wrong.

In practice

The three routes that account for most orders

Direct purchase, for small requirements, where a listing is bought as it stands. Our listings carry the configuration as built, so what arrives is what the page described.

Bid and reverse auction, where a specification goes out and sellers respond. We quote against the specification as written, and where the specification and the workload look to us like they have diverged, we say so in the response rather than after the award.

Custom bid, where the requirement does not match anything listed. This is the route where being the manufacturer changes the outcome rather than the paperwork: the configuration can be built to the requirement, and we can commit to supplying it again.

Local content

Make in India, as GeM actually asks it

Public procurement preference for domestic suppliers runs on declared local content, not on where a company is headquartered. A supplier declares a class, the declaration is auditable, and above a threshold it has to be certified rather than asserted. An Indian invoice, an Indian brand or assembly in India do not by themselves settle the question.

For a buyer, the practical consequence is that the local-content claim on a listing is a declaration with consequences behind it, and it is reasonable to ask what supports it. For a seller, it means the bill of materials has to be knowable — which is straightforward when components are nameable and impossible when they are not.

We write our declarations per configuration, because the figure depends on what is in the machine. Our blog has the long version of what these tenders actually ask of a server vendor, written from the notified rules rather than from a summary of them.

Before you order

What our listings state, without being asked

Every line below is answerable about our own listings. It is here so that a buyer comparing them does not have to send an email to find out.

Verification

What a buyer has to confirm, and what confirms it

The right-hand column is what we hold, not what we would obtain.

Read further

The rest of the procurement record

On this site

Where the eight categories live

The same machines, described properly.