Supplier-blind sourcing means no supplier can learn who else was invited to an RFx: no shared recipient lists, and no participant names or counts on any page, email, file name, export or error message a supplier can see. "By construction" means the software makes that leak impossible to cause by accident, so nobody has to remember to prevent it.
Most procurement teams already try to keep bidders apart. The difference is between trying and being unable to fail. This post explains why that difference matters, and what it takes to build it in.
How do suppliers find out who else is bidding?
Rarely through bad intent. Almost always through an ordinary slip in a tool built for sharing:
- A CC instead of a BCC. One invitation, eight supplier addresses, all visible to every recipient.
- A forwarded chain. A clarification is forwarded with the earlier thread below it, and the earlier thread names another bidder.
- A shared file name. "Comparison_SupplierA_vs_SupplierB.xlsx" goes back to a supplier as an attachment by mistake.
- A reply-all to a clarification. One supplier's question, and the buyer's answer, reach everyone, with the asker's name attached.
- A number on a portal. "5 suppliers invited" or "3 responses received" tells a bidder exactly how crowded the room is.
- An error message. "This supplier has already submitted" can say more than it should.
- An auction console. A leaderboard with company names instead of ranks.
Each of these is one click away in email and spreadsheets. A careful team avoids most of them most of the time. Over a year of events, "most of the time" is not a control.
Why does it matter so much?
Because once a supplier knows the field, the event changes.
- Pricing changes. A supplier who knows the incumbent is bidding prices against the incumbent, not against your requirement. A supplier who knows only two others were invited may bid higher.
- Fairness is gone. Bidders are no longer competing on the same information. In a regulated or public tender that is a legal problem, not just a commercial one.
- Confidentiality breaks. Some suppliers do not want it known that they bid for your business, and some buyers do not want competitors to learn which suppliers they are talking to.
- The audit trail cannot fix it. An auditor can see that a mistake happened. Nobody can undo what the supplier learned.
Why isn't a careful team enough?
Because the default of every general tool is to share. Email puts recipients in a visible list unless someone remembers not to. A spreadsheet carries its file name wherever it goes. A portal shows counts because counts are useful to the buyer.
A policy that says "always use BCC" relies on every person getting it right on every message, including the engineer who joined the event last week. Controls that rely on memory fail at the rate of human memory.
What does "by construction" look like?
It means the product has no path by which the leak can happen. In iProcure, supplier blindness is one of the ten rules we build by. It is enforced by the product, not left to a setting or to anyone's memory:
- Every supplier hears from you alone. No shared recipient lists, and no way to create one by mistake.
- No names or counts anywhere a supplier looks. Whatever a supplier can open, read or download says nothing about the rest of the field.
- Ranks, never names, in auctions. A bidder sees where they stand, never who they are up against.
- A supplier's-eye view before anything goes out. A buyer can check exactly what a supplier will see before publishing.
That is what "by construction" means in practice: a new feature cannot quietly add a participant count to a supplier page, because the product does not allow it. The 10-minute demo shows it from both sides.
How is this different from blind evaluation?
They protect different people. Supplier-blind sourcing stops suppliers from seeing each other. Blind evaluation stops your evaluators from seeing supplier names while they score the technical response, so a familiar brand does not lift a weak answer.
Two related controls often travel with them. Two-envelope evaluation seals prices until the technical scoring is signed off. An NDA gate keeps confidential documents locked until a new supplier has accepted an NDA. Together they make an event fair on the way in and defensible on the way out.
What is live in iProcure today?
We are pre-launch, and we label status honestly.
- Live: supplier blindness enforced across the eRFx module, a supplier's-eye view before publishing, and restricted events hidden even from admins.
- Demo on sample data: the auction console that shows ranks, never names, and the evaluator workspace with sealed prices.
- Roadmap: anonymised clarifications, the NDA gate, and a password-free supplier portal.
How do you check your own process?
Look at your last three events and ask: could any supplier have learned who else was invited, from any email, file or page? If you are not sure, that is the answer. The RFx Health Check covers this and ten other signs. Or see a supplier-blind RFx live in 10 minutes.