Thank You for Evaluation Product, Product Unacceptable Template

Free Word download β€’ Edit online β€’ Save & share with Drive β€’ Export to PDF

1 pageβ€’20–30 min to fillβ€’Difficulty: Standardβ€’Signature requiredβ€’Legal review recommended
Learn more ↓
FreeThank You for Evaluation Product, Product Unacceptable Template

At a glance

What it is
A Thank You For Evaluation β€” Product Unacceptable letter is a formal written notice a buyer sends to a vendor or supplier after evaluating a submitted product sample or trial unit and determining it does not meet the required specifications, quality standards, or contractual criteria. This free Word download gives you a structured, professionally worded rejection letter you can edit online and export as PDF to send to any supplier or vendor contact.
When you need it
Use this letter whenever a product submitted for evaluation fails to meet your stated requirements β€” whether due to quality defects, specification mismatches, performance failures, or regulatory non-compliance β€” and you need to formally close the evaluation, document the rejection, and specify return or disposal instructions for the sample.
What's inside
Buyer and vendor identification, evaluation reference and sample details, a courteous acknowledgment of the submission, a clear statement of unacceptability with documented reasons, return or disposal instructions, any applicable confidentiality reminder, and a professional closing with signature block.

What is a Thank You For Evaluation β€” Product Unacceptable Letter?

A Thank You For Evaluation β€” Product Unacceptable Letter is a formal written notice a buyer sends to a vendor or supplier after reviewing a submitted product sample and concluding that it does not meet the required specifications, quality standards, or acceptance criteria established for the evaluation. It combines professional courtesy β€” acknowledging the vendor's effort β€” with a clear, documented rejection that identifies the specific grounds for the decision, references the applicable criteria, and instructs the vendor on the return or disposal of the submitted sample. Unlike an informal verbal decline, this letter creates a binding written record that is enforceable under applicable sale-of-goods law and protects both parties in the event of a later dispute about whether and when formal rejection was communicated.

Why You Need This Document

Declining a vendor product without a formal written notice exposes your business to significant legal and operational risk. Under the UCC in the United States, the Sale of Goods Act in Canada and the UK, and equivalent commercial codes across the EU, a buyer who retains non-conforming goods beyond a reasonable period without issuing written rejection may be deemed to have accepted them β€” triggering a payment obligation regardless of the product's condition. Without documented grounds for rejection, a vendor can claim the refusal was arbitrary, subjective, or in breach of the evaluation agreement, turning a routine procurement decision into a costly dispute. This template closes the evaluation cleanly: it states the rejection in unambiguous language, cites objective specification failures, directs sample return, and reminds the vendor of continuing confidentiality obligations β€” creating the paper trail your procurement and legal teams need to defend the decision if challenged.

Which variant fits your situation?

If your situation is…Use this template
Product fails technical specifications onlyThank You For Evaluation β€” Product Unacceptable (Spec Failure)
Product meets specs but fails internal budget or pricing reviewVendor Proposal Rejection Letter
Product evaluation is ongoing and a decision is deferredProduct Evaluation Acknowledgment Letter
Vendor relationship is being terminated entirely after rejectionVendor Termination Letter
Product was acceptable and the buyer wishes to proceedThank You For Evaluation β€” Product Acceptable Letter
Product requires re-submission with corrected specificationsRequest for Revised Product Sample Letter
Rejection follows a formal RFP or tender processBid Rejection Letter

Common mistakes to avoid

❌ Vague rejection grounds

Why it matters: Stating only that 'the product did not meet our standards' gives the vendor grounds to dispute the rejection as subjective or arbitrary, especially if a supply agreement requires objective acceptance criteria.

Fix: Cite each specific non-conformance by specification reference number or clause β€” e.g., 'tensile strength of 340 MPa versus the required minimum of 450 MPa per Section 4.2 of the specification sheet.'

❌ Omitting sample return instructions

Why it matters: Without written instructions, the buyer may become liable for storage fees, damage, or loss of the vendor's sample β€” and the vendor may claim the buyer accepted the goods by retaining them without objection.

Fix: Include a specific return or disposal directive with a deadline in every rejection letter, regardless of sample value.

❌ Signing the letter below the required authority level

Why it matters: If the rejection is later disputed and the letter was signed by an administrative assistant rather than an authorized buyer, the vendor may argue the notice was not a valid contractual rejection under the governing supply agreement.

Fix: Confirm who has signing authority for procurement decisions in your organization before issuing the letter, and use that person's name and title in the signature block.

❌ Using ambiguous future-opportunity language

Why it matters: Phrases like 'we encourage you to resubmit' or 'we remain open to future products' create a reasonable expectation that the vendor will be reconsidered β€” and can expose the buyer to a claim if the door is later closed without process.

Fix: Include a future-opportunity clause only if you genuinely intend to accept a revised submission, and specify what changes are required to trigger a new evaluation.

❌ Failing to reference the NDA or confidentiality agreement

Why it matters: Vendors who receive a rejection without a confidentiality reminder may assume their obligations end with the evaluation β€” leading to inadvertent or intentional disclosure of the buyer's proprietary specifications.

Fix: Add a single sentence referencing the NDA by date and title every time a rejection letter closes an evaluation that involved the exchange of confidential technical data.

❌ Sending the rejection verbally or by informal message before the letter is issued

Why it matters: An informal verbal or chat-based rejection without a follow-up letter leaves the buyer without a documented notice date β€” which matters if a supply contract requires formal written rejection within a specific timeframe.

Fix: Issue the formal letter first, or immediately after any verbal communication, and confirm the written notice date is the one relied upon for any contractual timing obligations.

The 9 key clauses, explained

Parties and evaluation reference

In plain language: Identifies the buyer's organization and the vendor by legal name, and references the specific evaluation request, purchase order, or submission date that prompted the product review.

Sample language
This letter is addressed to [VENDOR LEGAL NAME] ('Vendor') regarding the product sample submitted on [SUBMISSION DATE] in response to Evaluation Request No. [EVALUATION REFERENCE NUMBER] issued by [BUYER LEGAL NAME] ('Buyer').

Common mistake: Referencing only the vendor's trade name instead of their registered legal name β€” this creates ambiguity in the event of a supply dispute or formal claim arising from the evaluation.

Acknowledgment and appreciation

In plain language: Opens with a professional thank-you to the vendor for participating in the evaluation process, maintaining goodwill regardless of the outcome.

Sample language
We appreciate the time and effort [VENDOR LEGAL NAME] invested in preparing and submitting [PRODUCT NAME / DESCRIPTION] for evaluation, and we thank you for your participation in this process.

Common mistake: Skipping the acknowledgment entirely and leading with the rejection. Omitting a courteous opening can damage vendor relationships and invite a more adversarial response to the notice.

Statement of unacceptability

In plain language: Clearly and unambiguously states that the evaluated product does not meet the buyer's requirements and will not be accepted, purchased, or approved for use.

Sample language
After completing our evaluation, we regret to inform you that [PRODUCT NAME] does not meet [BUYER LEGAL NAME]'s acceptance criteria and cannot be approved for [purchase / use / listing] at this time.

Common mistake: Using hedging language such as 'we are not moving forward at this stage,' which implies the decision may be revisited and creates vendor expectations the buyer does not intend to fulfill.

Grounds for rejection

In plain language: Specifies the documented reasons the product failed evaluation β€” referencing the applicable specification, standard, or criterion that was not met.

Sample language
Specifically, the product was found to be unacceptable for the following reasons: (a) [SPECIFIC DEFECT OR NON-CONFORMANCE], which fails to meet Specification Section [X]; (b) [SECOND REASON, if applicable]; (c) [THIRD REASON, if applicable].

Common mistake: Providing vague grounds such as 'the product did not meet our standards' without citing specific criteria β€” this weakens the buyer's position if the vendor disputes the rejection or claims wrongful refusal.

Reference to evaluation criteria or specification document

In plain language: Attaches or references the specification sheet, evaluation criteria document, or contractual standards against which the product was measured, establishing the objective basis for the rejection.

Sample language
The evaluation was conducted against the specifications set out in [SPECIFICATION DOCUMENT TITLE], dated [DATE], a copy of which was provided to Vendor prior to submission and is attached hereto as Exhibit A.

Common mistake: Failing to attach or formally reference the specification document β€” without it, the vendor may contest the rejection criteria used and allege the buyer applied undisclosed or shifting standards.

Sample return or disposal instructions

In plain language: Directs the vendor on what to do with the submitted product sample β€” whether to arrange pickup, accept a return shipment at their cost, authorize disposal, or make other arrangements within a defined timeframe.

Sample language
Please arrange for the return or disposal of the submitted sample within [NUMBER] business days of the date of this letter. [BUYER LEGAL NAME] will [return the sample at Vendor's expense / hold the sample for pickup / dispose of the sample] unless otherwise instructed in writing.

Common mistake: Leaving return or disposal instructions out of the rejection letter β€” the buyer may then be held liable for storage costs, loss, or damage to the vendor's sample if no instructions were given.

Confidentiality reminder

In plain language: Reminds the vendor that any proprietary, technical, or commercial information exchanged during the evaluation remains subject to the terms of any existing non-disclosure or confidentiality agreement.

Sample language
Any proprietary information, specifications, or data shared by [BUYER LEGAL NAME] during the evaluation process remains subject to the Non-Disclosure Agreement dated [DATE] and must not be disclosed or used for any purpose other than this evaluation.

Common mistake: Omitting the confidentiality reminder when a prior NDA exists β€” the reminder reinforces the vendor's continuing obligations and reduces the risk of proprietary specifications being shared with the buyer's competitors.

Future opportunity or alternative supplier note (optional)

In plain language: Optionally invites the vendor to resubmit a revised product in the future or acknowledges that the buyer may consider other products from the vendor, preserving the commercial relationship.

Sample language
While we are unable to accept [PRODUCT NAME] at this time, we welcome the opportunity to evaluate revised submissions that address the deficiencies noted above, subject to a new evaluation request from [BUYER LEGAL NAME].

Common mistake: Including an open-ended future opportunity invitation when the buyer has no intention of re-engaging β€” this creates a reasonable expectation in the vendor that another submission will be considered and can lead to disputes.

Signature and authority block

In plain language: Closes the letter with the authorized signatory's name, title, and contact information, confirming the decision was made by a person with authority to bind the buyer on evaluation outcomes.

Sample language
Sincerely, [AUTHORIZED SIGNATORY NAME] | [TITLE] | [BUYER LEGAL NAME] | [ADDRESS] | [EMAIL] | [PHONE] | Date: [DATE]

Common mistake: Having the letter signed by an administrative contact rather than the procurement manager or authorized decision-maker β€” this can allow the vendor to dispute whether the rejection constitutes a binding notice under the governing supply agreement.

How to fill it out

  1. 1

    Enter the buyer's and vendor's legal names

    Use each party's full registered legal entity name β€” not trade names or abbreviations. Reference the original evaluation request number or submission reference so both parties can trace the correspondence.

    πŸ’‘ Confirm the vendor's registered name from their original quotation, submission cover letter, or company registry before drafting β€” mismatches delay dispute resolution.

  2. 2

    Reference the specific product and submission date

    Identify the product by its name, model number, SKU, or other unique identifier used in the submission, and state the date the sample was received for evaluation.

    πŸ’‘ If the vendor submitted multiple samples or product variants, identify each one separately to avoid any ambiguity about which item is being rejected.

  3. 3

    Draft the statement of unacceptability

    State clearly that the product has not met your acceptance criteria and will not be approved. Use definitive language β€” avoid qualifiers that suggest the decision might change.

    πŸ’‘ One sentence is sufficient: 'After evaluation, [PRODUCT NAME] does not meet [BUYER NAME]'s acceptance criteria and is not approved for purchase.' Brevity reduces misinterpretation.

  4. 4

    Document specific grounds for rejection

    List each failure with a reference to the applicable specification clause, standard, or criterion. Number the grounds separately if there are multiple failures.

    πŸ’‘ Pull the grounds directly from your evaluation report or QA inspection form β€” this ensures the letter and the internal record are consistent.

  5. 5

    Attach or reference the specification document

    Attach the specification sheet, evaluation criteria document, or relevant contract section as an exhibit, and reference it in the body of the letter.

    πŸ’‘ Label the attachment 'Exhibit A' and confirm it is the same version the vendor received before submission β€” version-date mismatches are a common dispute trigger.

  6. 6

    Specify sample return or disposal instructions

    State clearly whether the vendor should arrange pickup, accept a return shipment at their cost, or authorize you to dispose of the sample, and set a deadline for the vendor to respond or act.

    πŸ’‘ Set the deadline at 10–15 business days β€” long enough for the vendor to arrange logistics, short enough to resolve your storage obligation.

  7. 7

    Include the confidentiality reminder if an NDA is in place

    If an NDA or evaluation agreement was signed before the process began, add a one-sentence reminder that all shared information remains confidential and must not be reused.

    πŸ’‘ Reference the NDA by its date and title so the vendor cannot later claim ignorance of the continuing obligation.

  8. 8

    Have the letter signed by an authorized signatory

    Obtain the signature of the procurement manager, purchasing director, or other person with authority to issue binding rejection notices on behalf of the buyer.

    πŸ’‘ Send by email with a PDF attachment and request a read receipt or delivery confirmation β€” this creates a timestamped record of when the vendor received formal notice.

Frequently asked questions

What is a thank you for evaluation β€” product unacceptable letter?

A thank you for evaluation β€” product unacceptable letter is a formal written notice a buyer sends to a vendor after evaluating a submitted product sample and finding that it does not meet the buyer's acceptance criteria, specifications, or quality standards. It combines professional courtesy with a clear, documented rejection, specifying the grounds for the decision and instructions for the return or disposal of the sample. It serves as the official close of the evaluation process and protects both parties by creating a written record of the outcome.

Why does a product rejection need to be in writing?

A written rejection letter creates a timestamped record of the decision, the grounds cited, and the date formal notice was given to the vendor. Many supply agreements and purchase order terms require rejection to be communicated in writing within a defined period β€” typically 10 to 30 days after delivery β€” or the buyer may be deemed to have accepted the goods. A verbal rejection without a written follow-up leaves the buyer without documentary evidence if the vendor later disputes the refusal or claims the goods were accepted by conduct.

What grounds should I include when rejecting a product?

Cite each specific failure by reference to the applicable specification clause, quality standard, or acceptance criterion β€” for example, dimensional tolerance, material composition, performance test result, or regulatory certification. Avoid generic language like 'did not meet our standards.' The more specific the grounds, the harder it is for the vendor to dispute the rejection or argue that the buyer applied undisclosed or shifting criteria. Attach the specification document as an exhibit to anchor the rejection to objective criteria.

Who should sign a product rejection letter?

The letter should be signed by the person with authority to issue binding procurement decisions on behalf of the buyer β€” typically the procurement manager, purchasing director, or VP of operations. Signing authority matters because some supply agreements require rejection notices to be issued by an authorized representative to be contractually effective. Check your internal signing authority policy and the terms of any existing vendor agreement before selecting a signatory.

Does the vendor have to return the sample at their own cost?

Cost responsibility for sample return depends on the terms of the evaluation agreement, purchase order, or supply contract in place. In the absence of a specific agreement, buyers typically specify in the rejection letter whether they will ship the sample back at the vendor's expense, hold it for vendor pickup, or dispose of it after a reasonable waiting period. Stating your position clearly in the letter avoids disputes over storage costs and liability for the sample while it remains on your premises.

Can a vendor dispute a product rejection notice?

Yes β€” a vendor can dispute a rejection if they believe the buyer applied undisclosed criteria, evaluated the product incorrectly, or failed to follow the rejection procedure required by the supply agreement. A well-drafted rejection letter with specific grounds referenced to an attached specification document significantly reduces the likelihood of a successful dispute. If the vendor escalates, the written record becomes the primary evidence in mediation, arbitration, or litigation.

Should the rejection letter reference a prior NDA?

Yes, whenever an NDA or confidentiality agreement was signed before or during the evaluation. The rejection letter's confidentiality reminder reinforces the vendor's ongoing obligation not to disclose or reuse the buyer's proprietary specifications, evaluation data, or technical information. Reference the NDA by its exact title and date so the vendor cannot later argue they were unaware their obligations continued after the evaluation ended.

What happens if I reject a product but the vendor claims I accepted it?

Acceptance by conduct is a real legal risk in most jurisdictions β€” if a buyer retains goods beyond the rejection period without issuing formal written notice, courts may find implied acceptance. A dated, written rejection letter sent within any contractually specified notice period is the primary defense against such a claim. Keep a copy of the letter and any delivery confirmation as evidence of the date formal notice was given to the vendor.

Is this letter appropriate for rejecting a digital product or SaaS trial?

The core structure applies to any product evaluation β€” physical goods, software, or SaaS tools β€” but the specific grounds and return instructions will differ. For digital products, replace sample return instructions with account deactivation or data deletion directions, and reference any applicable software evaluation agreement or free trial terms in the specification section. The letter still provides a formal close to the evaluation and documents the rejection for your records.

How this compares to alternatives

vs Thank you for evaluation β€” product acceptable letter

The product acceptable letter confirms approval of a submitted sample and typically initiates the next step in the procurement process β€” purchase order issuance or contract execution. The unacceptable letter formally closes the evaluation with rejection grounds and return instructions. Use the acceptable version when the product meets your criteria; use this template when it does not.

vs Vendor termination letter

A vendor termination letter ends an existing supply relationship β€” terminating an active contract or ongoing purchasing arrangement. A product rejection letter closes a single evaluation without necessarily ending the vendor relationship. Use a termination letter when you are exiting a contract; use this template when you are declining a specific product submission.

vs Bid rejection letter

A bid rejection letter declines a formal proposal or tender response from a supplier competing for a contract award. A product rejection letter declines a physical sample or product submission evaluated against technical specifications. Use the bid rejection when declining a commercial proposal; use this template when declining a product after hands-on evaluation.

vs Non-conformance report

A non-conformance report is an internal quality document that records a product failure in the buyer's quality management system β€” it is not typically sent to the vendor as formal correspondence. This rejection letter is the external-facing notice derived from that internal finding. Both documents should reference the same specification criteria and failure details for consistency.

Industry-specific considerations

Manufacturing and industrial supply

Material composition, dimensional tolerance, and performance test failures are the most common rejection grounds, with specification sheets attached as exhibits and third-party lab reports cited.

Retail and consumer goods

Rejections frequently cite packaging non-conformance, safety certification gaps, or failure to meet private-label specification standards required for shelf approval.

Healthcare and medical devices

Regulatory compliance failures β€” missing FDA 510(k) clearance, CE marking, or ISO 13485 certification β€” are documented as rejection grounds, and the letter must be retained in the quality management system.

Food and beverage

Rejections address microbiological test failures, ingredient specification deviations, or labeling non-compliance under FDA or EFSA standards, with inspection reports attached.

Jurisdictional notes

United States

Under the UCC (Article 2), a buyer must reject non-conforming goods within a reasonable time after delivery and give the seller seasonable notification β€” typically interpreted as within 30 days for commercial buyers. Written rejection is critical to preserve the right to reject and to avoid acceptance by conduct. Rejection grounds must be stated with particularity if the seller could have cured the defect.

Canada

Canadian provinces apply Sale of Goods Act provisions (federal model with provincial variants) that require timely written notice of rejection for non-conforming goods. In Quebec, the Civil Code of Quebec governs sales contracts and requires the buyer to notify the vendor promptly of any defect or non-conformance to preserve warranty and rejection rights. Written documentation is essential for any cross-provincial dispute.

United Kingdom

The Sale of Goods Act 1979 and the Consumer Rights Act 2015 (for B2C transactions) require buyers to reject goods that do not conform to contract within a reasonable period β€” typically 30 days for a short-term right to reject under the CRA. For B2B transactions, the right to reject can be lost by acceptance, including by retaining goods beyond a reasonable time without objection. A dated written rejection notice is the primary evidence of timely rejection.

European Union

The EU Sale of Goods Directive (2019/771) and national implementing legislation require timely notification of non-conformance β€” generally within 2 months of discovering the defect for consumer transactions. For B2B transactions, the applicable commercial code of the member state governs rejection procedures; German, French, and Dutch commercial law each impose different notice timelines and formality requirements. GDPR applies if any personal data was shared with the vendor during the evaluation process.

Template vs lawyer β€” what fits your deal?

PathBest forCostTime
Use the templateStandard domestic supplier rejections for routine product evaluations with no active contract disputeFree15–30 minutes
Template + legal reviewRejections where an existing supply agreement, framework contract, or NDA governs the evaluation process$150–$400 for a brief legal review1–2 business days
Custom draftedHigh-value rejections with litigation risk, cross-border supply disputes, or regulated-industry procurement (medical devices, aerospace, food safety)$500–$2,000+3–7 business days

Glossary

Product Evaluation
A structured process in which a buyer tests or inspects a vendor's product sample against predefined specifications, standards, or acceptance criteria.
Acceptance Criteria
The documented set of requirements β€” technical, qualitative, regulatory, or commercial β€” that a product must satisfy before a buyer will accept it.
Non-Conformance
A finding that a product or sample deviates from the agreed or stated specifications, triggering formal rejection or corrective action.
Sample Return Instructions
The buyer's direction to the vendor specifying whether a rejected sample should be returned at the vendor's cost, destroyed, or held pending further instruction.
Rejection Notice
A formal written communication from a buyer to a seller stating that submitted goods do not meet acceptance criteria and will not be purchased.
Specification Sheet
A document β€” often attached or referenced β€” that details the technical, dimensional, material, or performance requirements the product was evaluated against.
Vendor Scorecard
An internal evaluation tool rating a supplier's product across multiple criteria such as quality, price, delivery, and compliance β€” often the basis for a rejection decision.
Confidentiality Reminder
A clause in the rejection letter reminding the vendor that any proprietary information shared during the evaluation process remains subject to any existing NDA or confidentiality agreement.
Evaluation Period
The defined timeframe during which the buyer tests the product sample, typically specified in a prior evaluation agreement or purchase order.
Commercial Terms
Pricing, payment, delivery, and warranty conditions associated with a product submission β€” separate from technical specifications and often evaluated independently.

Part of your Business Operating System

This document is one of 3,000+ business & legal templates included in Business in a Box.

  • Fill-in-the-blanks β€” ready in minutes
  • 100% customizable Word document
  • Compatible with all office suites
  • Export to PDF and share electronically

Create your document in 3 simple steps.

From template to signed document β€” all inside one Business Operating System.
1
Download or open template

Access over 3,000+ business and legal templates for any business task, project or initiative.

2
Edit and fill in the blanks with AI

Customize your ready-made business document template and save it in the cloud.

3
Save, Share, Send, Sign

Share your files and folders with your team. Create a space of seamless collaboration.

Save time, save money, and create top-quality documents.

β˜…β˜…β˜…β˜…β˜…

"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."

Managing Director Β· Mall Farm
Robert Whalley
Managing Director, Mall Farm Proprietary Limited
β˜…β˜…β˜…β˜…β˜…

"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."

Business Owner Β· 4+ years
Dr Michael John Freestone
Business Owner
β˜…β˜…β˜…β˜…β˜…

"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."

Owner Β· Upstate Web
David G. Moore Jr.
Owner, Upstate Web

Run your business with a system β€” not scattered tools

Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.

Start freeΒ Β·Β No credit card required