Fair competition depends on each supplier bidding against the market, not against named rivals. When a supplier learns who else is in an event, behaviour changes: an incumbent that knows it faces only weak competitors prices higher, and suppliers who know each other may coordinate. Even a count of participants is useful information to a bidder. Supplier-blind sourcing removes that signal, so each supplier's best response is simply its best offer.
Most leaks are accidental. A buyer puts every supplier in the CC line instead of BCC. A clarification answer is forwarded with the original thread attached. A shared file name or a document property reveals another company's name. A supplier portal shows a participant list or a count of responses. An auction console displays competitor names beside their bids. Each of these is a process failure, and each is hard to prevent by policy and training alone.
That is why blindness works best as a system rule rather than a habit. Messages go to each supplier separately, supplier-facing pages and exports never list other participants, and auctions show a rank or signal instead of names. The idea is related to, but different from, blind evaluation, where evaluators score responses with supplier identities hidden to reduce bias. One protects the competition between suppliers; the other protects the judgement of the evaluation team.
How iProcure handles supplier-blind sourcing
Supplier blindness is a platform rule in iProcure, enforced by the product and live today: no supplier-facing page, email or export shows who else was invited or how many. Buyers can check any event from the supplier's point of view before it goes out. In auctions, shown on sample data today, bidders see their rank, never a competitor's name. Hiding supplier names from evaluators is also shown on sample data.