Why do suppliers get invitations for work they do not do?
Published | Updated
For invitation mismatch, the answer to keep in mind is that broad profile codes, family level searches and catalogue mappings that stretched a code too far in UNSPSC, managed by the United Nations Development Programme since 1 January 2025. An invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently. Everything that follows is detail on that one claim about invitation mismatch.
Where invitation mismatch sits on the shelf
On the shelf, invitation mismatch belongs where broad profile codes, family level searches and catalogue mappings that stretched a code too far, and an invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently. The shelf position is not a matter of taste, because the codeset wording for invitation mismatch sets the neighbours it sits beside and the broader shelf it sits under. A reader who can say where invitation mismatch sits can also say where it does not sit, which is often the more useful half of the knowledge. Buyers also cause mismatch by searching one level broader than the tender actually needs.
How the pairs narrow toward invitation mismatch
The digits narrow toward invitation mismatch by the usual UNSPSC logic: each pair refines the pair before it, so broad profile codes, family level searches and catalogue mappings that stretched a code too far becomes more specific at every step. An invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently. The narrowing toward invitation mismatch stops at the level the evidence supports for invitation mismatch, and stopping early is honest while claiming a finer level for invitation mismatch without evidence is not. Buyers also cause mismatch by searching one level broader than the tender actually needs.
Where invitation mismatch is looked at
| What the reader should find | What to watch for |
|---|---|
| Broad view of invitation mismatch | that broad profile codes, family level searches and catalogue mappings that stretched a code too far |
| Close view of invitation mismatch | that an invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently |
| Practical use of invitation mismatch | the claim that broad profile codes, family level searches and catalogue mappings that stretched a code too far |
What trips readers up with invitation mismatch
What trips people up with invitation mismatch is that buyers also cause mismatch by searching one level broader than the tender actually needs, even though broad profile codes, family level searches and catalogue mappings that stretched a code too far. An invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently. The trap is familiar because it looks like carelessness when it is really a wording problem: the titles for invitation mismatch and its neighbours resemble each other closely enough to invite a quick, wrong choice. Slow reading of both wordings for invitation mismatch, side by side, is the unglamorous cure for invitation mismatch.
Before moving on from invitation mismatch, run one last check: does the claim that broad profile codes, family level searches and catalogue mappings that stretched a code too far still hold in the current codeset wording for invitation mismatch? An invitation for the wrong work is a signal to narrow the profile, not a compliment to accept silently. Buyers also cause mismatch by searching one level broader than the tender actually needs.
Leave invitation mismatch with this: broad profile codes, family level searches and catalogue mappings that stretched a code too far is the claim, and the current UNDP codeset is the check. Buyers also cause mismatch by searching one level broader than the tender actually needs. Any tender, catalogue or report about invitation mismatch that carries both the claim and its version can be followed by the next person who picks it up, which is the standard every UNSPSC quotation for invitation mismatch should meet.