Bid Splitting Rules Every Vendor Should Know

The indent was for an agent platform across four regional offices. The financial power of the local head sat just below the number that would have forced a bid. Someone suggested four direct purchases, four identical catalogues, four weeks apart. The vendor's sales lead said yes before legal saw the mail.

That is bid splitting as GFR understands it: dividing a demand into small quantities to avoid the proper method or the higher sanction. It is not a grey productivity hack. It is a named prohibition.

This explainer is for vendors who get asked to play along, and for procurement officers and DDOs who have to write the file when a director wants speed. It is not legal advice. Read the live GFR on doe.gov.in and the live GeM terms on gem.gov.in.

Where the rule lives

GFR 2017, in the GeM chapter, tells buyers that a demand for goods shall not be divided into small quantities to make piecemeal purchases to avoid L1 buying, bidding or reverse auction on GeM, or to avoid the sanction of a higher authority that the total estimated demand would have required. That idea is the same one older GFR language used for ordinary stores. GeM did not invent it. GeM made it clickable.

GeM's General Terms and Conditions repeat the prohibition in marketplace language: splitting demands by creating multiple bids or reverse auctions of the same goods or services, or making repeated procurements of the same item through direct or L1 buying, is strictly prohibited. The terms say splitting loses economies of scale and evades higher sanction. They put responsibility on the buyer, including the primary buyer.

Vendor responsibility is not zero. A seller who designs four catalogue variants so that four under-threshold carts look different is participating in the evasion. Integrity monitoring, incidents and later audit will not be impressed that the buyer clicked first.

Split versus honest structure

Pattern	Looks like	Usually is	Safer alternative
Four identical direct buys in one quarter	Local flexibility	Threshold evasion	One bid against the annual estimate
Pilot now, production next month, same spec, no gate	Agile	Piecemeal of a known demand	Sanction the programme; compete production
New consignee codes for the same directorate	Administrative neatness	Often a split	Multi-consignee bid
Year-1 licence plus a pre-agreed year-2 option	A contract with options	Usually honest if sanctioned	Write the option in the bid
True emergency plus later regularisation	166(ii) then a bid	Can be honest	Record the emergency; do not repeat it

Why AI buys get split

Agent projects arrive as demos. Someone wants a six-week pilot under a direct-purchase limit. Then the same stack is rolled to a second bureau because the first one liked it. Then a third. Nobody writes an annual demand. Everybody thinks they were being modern.

The GFR does not hate pilots. It hates a known demand dressed as a series of surprises. If the department already knows it wants four sites, the estimate is four sites. A genuine pilot has a question, a stop date, an evaluation note, and no presumption that production will be a cart from the same listing.

Three rooms, three files

What vendors should watch in the inbox

• A buyer who asks you to lower the quote so it fits a financial power.
• A request to change the catalogue title so the fourth order looks like a different item.
• A verbal assurance that the next three carts are already decided.
• A wish to avoid reverse auction or a custom bid because those take time.
• A plan to use four MSE-looking invoices to dress a single programme.

Any one of those mails is a reason to move the conversation onto a bid. If the buyer will not, walk. Winning a split pattern is not a logo you want on the wall when the auditor adds.

Objections from people who want the cart today

The other vendor will do it. Then the other vendor owns the integrity risk. That is not a reason for you to share it.

Each office has its own budget. Independent budgets can still be one demand if one programme and one specification sit above them. Ask who wrote the common note.

GFR is only for the Centre. Many CPSEs, autonomous bodies and states adopt GFR or copy the no-splitting idea. GeM terms apply to GeM buyers regardless of that debate. Read the instrument that governs that buyer.

We are below the limit each time, so we are safe. The rule exists precisely for the person who is below the limit each time and above it in sum.

How to write a pilot that is not a split

A genuine pilot has a question the department does not yet know the answer to. Will officers use the agent on live files. Will the air-gap hold under the CISO's test. Will Hindi administrative notes survive retrieval. The estimate names that question, a stop date, a success metric, and a rule that production is a separate sanctioned buy. The value sits wherever the financial power honestly sits. Nobody pretends they do not already want four sites.

A fake pilot has a predetermined rollout and a cart limit. The first PO is called discovery. The second is called phase two. The third is called urgent. The specification never changes. That pattern is what Rule 149's no-splitting sentence was written to catch. Vendors can see it from the inbox. If you can see it, a later monitor can see it.

Optional quantities are the adult middle. Sanction the ceiling. Bid the known first tranche. Write the option so that exercising it does not require a new under-threshold ritual. Finance sees the total. The vendor prices the option. The file has one competent-authority page. That is not evasion. That is how GFR wanted demand to be estimated.

If you are a vendor writing a proposal, do not offer four SKUs that are the same agent with four campus names. Offer one platform SKU and a per-site implementation line. If the buyer then splits the implementation line into four carts, your proposal at least did not design the evasion. Keep that proposal. It is the exhibit that you did not invent the pattern.

Playbook for the next suspicious request

• Day 1: add all related orders in the last twelve months. Same buyer family, same article, same programme.
• Day 2: write a one-page note to the buyer proposing a single bid or a sanctioned option quantity.
• Day 3: if they insist on another under-threshold cart, send a short refusal that cites GFR no-splitting language and GeM GTC, without accusing anyone of crime.
• Day 4: brief your own board that the lost revenue was a control, not a miss.
• Ongoing: keep the addition sheet. It is your exhibit if someone later asks why you sold four times.

Note a DDO can put on the file

Four proposals for substantially the same agent article have been received from the same indenting wing in one financial year. GFR 2017 cautions against dividing a demand to avoid GeM bidding or higher sanction. GeM terms prohibit splitting of demands. The proposals are returned for a single estimate and the procurement method that the total demand requires. Phasing, if needed, may be written as options under that estimate. This is an accounts observation, not a finding of misconduct.

Prcept AI will not design catalogue twins so a programme fits under a cart limit. Ask us for one bid with optional quantities and an on-prem specification. That is slower than four clicks. It is how the file should look.

How a buyer or seller should act on this

Treat “Bid Splitting Rules Every Vendor Should Know” as an operating problem, not a thought piece. A P2 Procurement who searches “bid splitting government rules” 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.

Splitting one demand into many small GeM buys to stay under a threshold is a GFR problem, not a clever hack. Vendors who play along inherit the file. That is why this explainer 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 “Bid Splitting Rules Every Vendor Should Know” 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 P2 Procurement, not “the vendor.”

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