Template
Vendor rejection letter: 12 templates and what to say
A vendor rejection letter tells a supplier, in writing, that their bid or proposal was not selected. A good one states the decision in the first line, thanks them for specific work, gives a reason they can use, and says whether the door stays open. Below are 12 copy-ready letters and emails, from an RFP that was not shortlisted to a formal public sector notice, plus rules for feedback, timing, and the "can we lower the price?" reply.
Updated November 17, 2026 ยท 16 min read
Key takeaways
- Decision first, reason second, next step third. Never bury the "no" under three paragraphs of thanks.
- Do not reject the runner-up until the winner has signed. Losing your first choice with no fallback is the costliest timing mistake.
- Share the vendor's own scores and gaps. Never share competitors' prices, line items or proposal content.
- Call finalists, then confirm in writing. Email is fine for bidders who did not make the shortlist.
- Once the decision is made, do not reopen it for a lower price. It is unfair to the bidders who priced honestly the first time.
- Public bodies have legal notice duties, such as standstill periods and assessment summaries. Check the rules that apply to you.
Quick template: the standard vendor rejection email
If you need one letter right now, use this. It works for most private sector bids and takes two minutes to personalize.
What every vendor rejection letter must include
- The project and reference. Vendors bid on many things at once. Name the RFP, tender number or project.
- The decision, in the first or second sentence. "We have decided not to move forward" is clearer than "we have chosen to explore other directions".
- One real reason. Price, scope, experience, timeline, compliance. A vague reason makes vendors guess, and they will guess "politics".
- Specific thanks. Mention one thing from their proposal. It proves someone read it.
- Whether the decision is final. If it is, say so. If you are keeping them as a backup, say that instead (see template 7).
- The next step. Feedback call offer, future opportunities, or nothing. Do not invite feedback you will not give.
If you are still deciding how to choose between bidders, our guides to vendor evaluation criteria and the vendor selection process come first. A rejection letter is only as clear as the scoring behind it.
Rejection reasons vs what to say
The reason you write should be true, specific and useful to the vendor, without handing them ammunition to argue or information that belongs to someone else.
| Real reason | What to say | What not to say |
|---|---|---|
| Price too high | "Your price was above both our budget and the most competitive bids." | "Vendor B came in at $42,000." (competitor price) |
| Weaker on a key criterion | "You scored lower on [criterion], which carried 30 percent of the weighting." | "The team just liked the other one better." |
| Scope mismatch | "Your proposal covered [X] but not [Y], which was a core requirement." | "You did not understand the brief." |
| Not enough relevant experience | "We prioritized vendors with recent projects in [industry or platform]." | "You are too small for us." |
| Timeline | "Your earliest start date of [date] did not meet our launch date of [date]." | Nothing. Timeline is easy to state. |
| Failed a mandatory requirement | "The submission did not include [certificate or document], which was mandatory." | "We had concerns." (too vague to fix) |
| Poor presentation or chemistry | "Another team showed a more detailed plan for [phase]." | Comments about individuals. |
| Project cancelled or postponed | "The project has been cancelled, and no vendor has been selected." | Internal budget fights or reorganization details. |
| Went with the incumbent | "We decided the switching cost outweighed the benefits this cycle." | "We used your bid to negotiate with our current vendor." (even if true) |
| Financial or risk concern | "The bid did not meet our [insurance / financial standing] threshold." | Speculation about their solvency. |
12 vendor rejection letter templates
Each template below is written for a specific stage and reason. Replace the bracketed parts and delete any sentence that is not true for your situation.
1. RFP or RFI response not shortlisted
Early-stage rejections can be shorter, because the vendor invested less. Send them within a week of the shortlist decision so they can stop holding capacity for you. Not sure which document you sent? See RFI vs RFP vs RFQ.
2. Lost after the final round
Finalists have usually spent days or weeks on presentations, workshops and revised pricing. Call them first, then send this letter the same day as written confirmation.
3. Price too high
Be honest that price was the reason, but describe your position relative to the field, not individual competitor numbers. If the decision is final, say so, or the next email will be a discount.
4. Scope mismatch
5. Project cancelled or postponed
When nobody wins, tell every bidder at once and make clear the decision is not about them. If the project may restart, say whether you will re-run the process or come back to existing bidders.
6. Keep them on the bench for future work
Use this for a strong vendor who lost on one factor, and only if you mean it. Name a concrete next step, otherwise "we will keep you in mind" reads as a form letter.
"Pre-qualified" should mean something real, such as a place on your approved vendor list, so the promise survives when the person who wrote the letter moves on.
7. Runner-up: on hold until the contract is signed
If your first-choice vendor has not signed yet, do not reject the runner-up. Tell them the truth: they are not the preferred bidder, and you will confirm the final outcome by a date.
8. Bid did not meet a mandatory requirement
9. Incumbent vendor not renewed
The hardest letter, because the vendor has people, revenue and a relationship tied to you. Call first, give the transition timeline, and keep the tone generous: you will need their cooperation during the handover.
10. Public sector style formal letter (unsuccessful bid notice)
Public bodies usually have to tell each bidder how its tender scored, who won, and when the contract can be signed. The format below follows that pattern. Adapt it to your own procurement rules: it is a starting point, not legal advice.
Public procurement rules (summary, not legal advice). In the UK, the Procurement Act 2023 requires contracting authorities to give each supplier that submitted an assessed tender an assessment summary, and sets a standstill period of at least eight working days before most contracts can be entered into. In the EU, Directive 2014/24/EU (Article 55) requires contracting authorities to tell unsuccessful tenderers, on request, the reasons for rejection, and tenderers with admissible bids the characteristics and relative advantages of the winning tender and the winner's name. It also allows authorities to withhold information that would harm a company's legitimate commercial interests or fair competition. In US federal contracting, the debriefing rules in FAR Part 15 bar point-by-point comparisons with other offerors' proposals and the release of their confidential commercial information.
11. Reply to "can we lower the price?"
The most common response to a rejection is a better offer. Reopening a decision for a lower price has three costs: it is unfair to bidders who priced their best the first time, it teaches every vendor to pad their first bid with you, and it breaks the process you told everyone you would follow. In public procurement, negotiating after the award decision is generally not permitted outside the procedure that was published. The exception is a process that announced a best and final offer (BAFO) round you have not yet run; then the round is part of the process, not a reopening.
12. Reply to a feedback or debrief request
How to give useful feedback to a rejected vendor
Most vendors ask for feedback, and few get anything usable. Good feedback is specific to their submission, tied to your criteria, and short. It also has firm limits: it must never leak another bidder's information.
| Share | Never share |
|---|---|
| Their own scores per criterion, and the weightings | Competitors' prices, rates, discounts or line items |
| Their overall position (rank, or a band like "top three") | Content from other proposals: methods, staffing plans, technology choices |
| The specific gaps: missing requirements, weak sections, timeline | Individual evaluators' names or personal scores |
| What would have changed the outcome, in general terms ("on-site support") | Internal politics, budget disputes or who argued for whom |
| Strengths you would want to see again | Anything covered by an NDA or marked confidential by another bidder |
| Whether price was a deciding factor | "If you had come in at $X, you would have won" (it invites a rebid and reveals the winning price) |
| The winner's name, if it is public or you are comfortable sharing it | Personal comments about the vendor's staff |
Public bodies often publish the winner's name and contract value. That is different from handing a losing bidder a breakdown of the winning price, which can harm the winner's commercial interests and, in a private process, breach the confidentiality you promised all bidders.
Three rules for feedback calls
- Prepare from the score sheet, not memory. Read from the evaluation notes so what you say matches what is on file.
- Do not debate the scores. Explain them. If the vendor points out a factual error in the evaluation, take it away and check it; do not rescore on the call.
- Keep it to 15 to 20 minutes and follow up with a short email summary, so both sides have the same record.
When to send a vendor rejection letter
| Vendor | When | How |
|---|---|---|
| Not shortlisted | Within a week of the shortlist decision | Email (template 1) |
| Non-compliant bid | As soon as compliance checks are done | Email or letter (template 8) |
| Finalists, not the runner-up | Within two working days of the decision | Call, then email (template 2) |
| Runner-up | After the winner has signed | Status note first (template 7), then call and email |
| Incumbent not renewed | As early as the contract notice period allows, never at the last minute | Meeting or call, then letter (template 9) |
| All bidders, project cancelled | As soon as the cancellation is approved | Same email to all, at the same time (template 5) |
| Public sector tender | To all bidders together, with the award decision, before the standstill period starts | Formal notice (template 10) |
The worst timing is silence. A vendor who hears nothing for weeks keeps capacity reserved for you and assumes the worst about your process. If the decision is delayed, send a one-line update with a new date.
Keep the losing proposals: they are your next benchmark
A rejected proposal is still a priced, dated offer for a service you buy. The next time the need comes up, those numbers tell you what the market charged, which vendors were close, and who to invite without starting from zero. Store each one with the vendor, service, price, date and the reason it lost, so whoever runs the next process can compare vendor quotes against real history.
If offers reach your company through many inboxes, PitchBin can hold them in one shared catalog: forward a proposal email to save@pitchbin.com and it is filed with company, service and price, where you can mark it declined and add a note on why. A submitted pitch is an immutable snapshot, so the quoted price stays on record even if the vendor later sends a different number.
Common mistakes in vendor rejection letters
- The same paragraph for every bidder. Fine for a first-round cut, not for finalists, and often not enough to meet public procurement duties to explain the decision.
- A reason that is not the real reason. If you say "scope" when it was price, the vendor will fix the wrong thing and lose again.
- Promising future work you will not offer. "We will definitely keep you in mind" from a buyer who never calls back damages your name with suppliers.
- Rejecting the runner-up too early. If the winner's contract falls through, you are back at square one.
- Leaking competitor information, usually by accident, in a "you were only 8 percent off" comment.
- Letting the vendor find out from LinkedIn that someone else won. Tell bidders before any announcement.
Turning down an unsolicited sales pitch is a different job with a lighter touch. For that, see how to politely decline a sales pitch.
Frequently asked questions
How do you write a vendor rejection letter?
Name the project, state the decision in the first two sentences, give one specific reason, thank the vendor for one concrete part of their proposal, and say whether the decision is final and whether you will invite them again. Keep it under 200 words for most private sector bids.
How do you reject a vendor proposal politely?
Be prompt and specific. Politeness in procurement means a clear answer quickly, a real reason, and an offer of feedback, not soft language that leaves the vendor guessing whether they are still in the running.
Should I tell a vendor who won the contract?
In a private process it is your choice, and many buyers share the winner's name once the contract is signed. In public procurement, the winner is typically named in the award notice. Never share the winner's pricing or proposal details.
Can I tell a vendor a competitor's price?
No. It breaks the confidentiality bidders expect, can harm the winner's commercial interests, and invites a rebid. Say where their price sat relative to the field ("above budget and above other compliant bids") instead.
What is an unsuccessful bid letter?
It is the formal notice, mostly used in tenders and public procurement, telling a bidder their tender was not selected. It usually includes the bidder's scores, the reasons, the successful bidder, and the standstill period before the contract is signed.
What should I do if a rejected vendor offers a lower price?
If the decision is made, decline the revised offer and explain that all bidders were assessed on the prices submitted by the deadline. Suggest they use the lower price as their starting point next time.
Should a vendor rejection be by email or phone?
Email for bidders who did not make the shortlist. For finalists and incumbents, call first and confirm in writing the same day, so the decision is on record.
Keep reading
Every proposal you turn down is a price you will want later.
Keep won and lost offers in one shared, searchable catalog, with the quoted price on record and a note on why. Free for companies receiving offers.