How to Prove an Implied Warranty of Merchantability Claim

Start with the complete sales record

Gather the documents identifying the transaction and legal seller.

• Receipt
• Invoice
• Order confirmation
• Sales contract
• Financing documents
• Delivery record
• Product listing
• Seller profile

These records help establish who sold the goods, when delivery occurred, what condition was represented, and which terms formed part of the transaction.

Prove that the seller was a merchant

Merchantability generally requires a seller that deals in goods of the relevant kind.

Evidence may include:

• Store or website inventory
• Business descriptions
• Seller listings
• Advertisements
• Invoices showing repeated commercial sales
• Specialized product knowledge represented by the seller

A private individual making a one-time sale may not satisfy the same requirement.

Identify the contract description

Preserve the description under which the goods were sold.

Relevant information may include:

• New, used, or refurbished condition
• Model and version
• Material
• Capacity
• Grade
• Compatibility
• Quantity
• Disclosed defects

Screenshots should be saved before online listings are edited or removed.

Define the product's ordinary purpose

Explain the normal function associated with goods of that kind.

The ordinary purpose may be supported by:

• Product instructions
• Manufacturer specifications
• Product-category descriptions
• Industry standards
• Expert evidence
• Seller advertising

Avoid defining ordinary purpose through a highly specialized use that was never disclosed to the seller.

Identify the merchantability standard that failed

A claim should identify more than a generalized defect.

State whether the goods failed because they:

• Could not perform their ordinary purpose
• Did not conform to the contract description
• Were below fair average quality
• Were materially inconsistent within a lot
• Were inadequately contained or packaged
• Were inadequately labeled
• Did not conform to factual label promises

Photograph and record the condition

Photographs should show both detail and context.

Capture:

• The complete product
• The failed area
• Model and serial numbers
• Packaging and labels
• Measurements
• Surrounding damage
• Conditions of ordinary use

Keep original image files and avoid editing the only copy.

Use video for operational problems

Video can document:

• Failure to start
• Unexpected shutdown
• Leaks
• Intermittent operation
• Unusual sound or vibration
• Safety events
• Error messages

Record the date, operating settings, environment, connected equipment, and relevant use conditions.

Preserve the product and failed parts

The product itself may be the most important evidence.

Preserve when safe and practical:

• The complete product
• Removed parts
• Packaging
• Labels
• Lot or batch codes
• Fluids, samples, or residues where appropriate

Do not discard important evidence before the seller, manufacturer, insurer, laboratory, or expert has a reasonable inspection opportunity.

Document ordinary use

The seller may argue that misuse, overloading, poor maintenance, or unsuitable conditions caused the failure.

Preserve evidence showing:

• How the product was used
• Frequency of use
• Operating settings
• Environmental conditions
• Compliance with instructions
• Maintenance performed
• Accessories and connected equipment

Document installation and setup

Installation errors can produce symptoms similar to product defects.

Gather:

• Installer identity
• Installation invoice
• Photographs
• Startup or commissioning records
• Manufacturer installation instructions
• Electrical, plumbing, ventilation, or network information

Separate defective goods from defective workmanship when possible.

Create a product-failure timeline

A clear chronology should include:

• Purchase date
• Delivery date
• Installation date
• First use
• First symptom
• Failure date
• Notice date
• Inspection dates
• Repair attempts
• Continuing damage

A timeline helps evaluate whether the condition likely existed when supplied and whether notice and filing deadlines were met.

Obtain diagnostic and repair records

Diagnostic records can help distinguish a product defect from external or user-caused problems.

Request:

• Error-code reports
• Technician notes
• Test results
• Repair invoices
• Parts replaced
• Cause stated by the technician
• Whether the condition existed before repair

Ask that removed parts be preserved when they may be important.

When expert evidence may be needed

An independent expert may be useful when:

• The cause is disputed.
• The defect is concealed.
• Installation and product failure overlap.
• The product was substantially damaged.
• The seller blames misuse or maintenance.
• Technical testing is required.

The appropriate expert may be an engineer, technician, laboratory, mechanic, inspector, trade specialist, or manufacturer representative.

What a useful expert report should address

A useful report may identify:

• The expert's qualifications
• The product inspected
• Documents reviewed
• Testing performed
• The observed condition
• The probable cause
• Whether the condition likely existed at sale
• Whether ordinary use contributed
• The recommended correction

Preserve disclaimer and warranty documents

Gather every document affecting coverage.

• Sales agreement
• As-is language
• Merchantability disclaimer
• Manufacturer warranty
• Dealer warranty
• Service contract
• Return policy
• Remedy limitations

Preserve the version in effect at the time of purchase.

Prove notice to the seller

Written notice evidence may include:

• Email
• Certified mail receipt
• Support ticket
• Chat transcript
• Claim number
• Delivery confirmation
• Seller response

The notice should identify the transaction, product, problem, and requested response.

Document damages and expenses

Preserve records showing the financial effect of the breach.

• Purchase price
• Repair estimates
• Inspection costs
• Transportation and storage costs
• Replacement-product costs
• Damage to other property
• Other claimed incidental or consequential loss

Keep losses reasonable and document efforts to avoid unnecessary additional damage.

Common proof weaknesses

A merchantability claim may be harder to prove when:

• The legal seller cannot be identified.
• The product was discarded.
• The failure was not documented.
• Another party altered the product.
• Maintenance records are missing.
• The ordinary purpose is not defined.
• The expert report does not explain cause.
• Notice was delayed.
• Damages are estimated without records.

Merchantability evidence checklist

• Receipt and invoice
• Seller and merchant-status evidence
• Product description
• Model, serial, lot, or batch information
• Photographs and video
• Installation and maintenance records
• Diagnostic and expert reports
• Product and removed components
• Disclaimer and warranty documents
• Written notice and delivery proof
• Expense and damage records
• Complete timeline

How to prove a merchantability claim: key takeaway

Strong proof connects a merchant seller, covered goods, an applicable merchantability standard, the product's condition, ordinary use, cause, notice, and loss.

Preserve the product and original records before repairs or disposal, and obtain an independent technical assessment when the seller disputes the cause.

Related merchantability guides

Frequently asked questions