Minnesota Gave Product Manufacturers a Defense Instead of a Repose Statute. The Difference Is the Whole Case.

The letter shows up early in almost every product case I handle, and it always reads like a deadline. The machine was twenty-two years old. Its published service life was fifteen years. Under Minn. Stat. § 604.03, the claim is barred.

That sentence has a real statute in it and the wrong conclusion. Section 604.03 bars nothing. It isn’t a statute of limitations. It isn’t a statute of repose. It gives you no date certain, and it doesn’t tell a court to dismiss anything. It creates a defense, and that defense has to be pleaded, tried, and proved on a six-factor look at what users of similar products actually experience. The manufacturer’s own brochure is factor number five.

I’ve watched lawyers make both of the mistakes this section invites. A plaintiff’s lawyer who doesn’t know the statute cold concedes a case that was never barred. A plaintiff’s lawyer who assumes the defense has no teeth gets an unpleasant education at trial. You can avoid both, and it starts with reading the text.

Section 604.03 is a defense. It isn’t a deadline.

Subdivision 1 says exactly what it is:

In any action for the recovery of damages for personal injury, death or property damage arising out of the manufacture, sale, use or consumption of a product, it is a defense to a claim against a designer, manufacturer, distributor or seller of the product or a part thereof, that the injury was sustained following the expiration of the ordinary useful life of the product.

Every word of the operative clause describes a defense. None of it is a time bar. It doesn’t say the action may not be commenced. It doesn’t say the cause of action doesn’t accrue. It doesn’t run from sale, delivery, manufacture, or substantial completion. It runs from nothing at all. There’s no triggering date in the section, because there’s no fixed period. The subdivision’s own catchline is “Expiration as defense.”

Here’s what a real Minnesota repose provision looks like. Minn. Stat. § 541.051, subd. 1(a) provides that in an action arising out of the defective and unsafe condition of an improvement to real property, “nor in any event shall such a cause of action accrue more than ten years after substantial completion of the construction.” That’s a date certain, measured from an event you can point to, and it works on accrual rather than on filing. I take that distinction apart in Minnesota’s construction repose statute does not bar your lawsuit.

Now read the sentence at the end of that same subdivision:

The limitations prescribed in this section do not apply to the manufacturer or supplier of any equipment or machinery installed upon real property.

I read that exclusion narrowly, because it’s narrow. It lifts the repose only for the manufacturer or supplier of equipment or machinery installed upon real property. It doesn’t lift it for everybody who makes a product. Subdivision 1(a) reaches, in its own words, any person “performing or furnishing the design, planning, supervision, materials, or observation of construction or construction of the improvement” — so a company that supplied materials incorporated into a building is inside the ten-year repose, not outside it.

The Uniform Commercial Code points the same way. Section 336.2-725’s penultimate paragraph provides that its own limitations “do not apply to actions for the breach of any contract for sale of a grain storage structure or other goods that are incorporated into an improvement to real property, except equipment and machinery,” and that “[t]hese actions are subject only to the statute of limitations set forth in section 541.051.” A warranty claim on goods built into an improvement goes to the repose statute, not to the four-year UCC clock.

So the real rule is narrower than the one the demand letters state. Where the product is equipment or machinery installed on real property, or a product that never becomes part of an improvement to real property at all — the ordinary consumer-goods case — no repose statute supplies an outer date, and § 604.03 is the only thing in the books that speaks to age. It’s a jury question. Where the product was incorporated into an improvement as materials, § 541.051 may well supply a date certain, and a defendant should check that before conceding there isn’t one.

That’s the trade the 1978 Legislature made, and in the cases § 604.03 actually governs, it cuts both ways. A plaintiff injured by a forty-year-old machine has no repose statute to get past. A defendant sued over a forty-year-old machine has a defense no calendar can beat.

The statute’s “useful life” isn’t how long the machine lasts

Subdivision 2 defines the term, and the first thing it does is throw out the obvious definition:

The useful life of a product is not necessarily the life inherent in the product, but is the period during which with reasonable safety the product should be useful to the user. This period shall be determined by reference to the experience of users of similar products, taking into account present conditions and past developments, including but not limited to (1) wear and tear or deterioration from natural causes, (2) the progress of the art, economic changes, inventions and developments within the industry, (3) the climatic and other local conditions peculiar to the user, (4) the policy of the user and similar users as to repairs, renewals and replacements, (5) the useful life as stated by the designer, manufacturer, distributor, or seller of the product in brochures or pamphlets furnished with the product or in a notice attached to the product, and (6) any modification of the product by the user.

Three phrases do the heavy lifting, and I push all three in discovery.

“Is not necessarily the life inherent in the product.” Useful life isn’t how long the thing physically lasts. A press that still runs isn’t necessarily within its useful life, and a machine that’s been junked isn’t necessarily outside it.

“With reasonable safety.” The measure is safety, not whether the thing still works. The question the statute asks is the period during which the product should be useful to the user with reasonable safety. That folds the safety question into the definition instead of treating age as a stand-in for it.

“By reference to the experience of users of similar products.” The benchmark is empirical, and it comes from outside the company. It isn’t what the manufacturer intended, it isn’t the warranty period, and it isn’t the depreciation schedule. It’s what users of similar products actually experience. That’s discoverable, and it’s a subject a plaintiff can put on proof about.

The manufacturer’s brochure is one factor of six

The stated service life doesn’t control. For a plaintiff, that’s the single most useful thing in the section.

The manufacturer’s own statement of useful life shows up in the statute exactly once, as factor (5) of six, in a list the statute introduces with “including but not limited to.” It sits next to five other considerations, and three of them have nothing to do with the manufacturer at all:

A defendant who raises the defense on the strength of a service-life statement in an owner’s manual is raising one factor of six, on a list that isn’t exclusive. The statute doesn’t make that statement presumptive, controlling, or even weighted. And look at the limit the Legislature built into factor (5) itself: it reaches the useful life “as stated … in brochures or pamphlets furnished with the product or in a notice attached to the product.” A number produced for litigation, or pulled from an internal engineering document that never went to a customer, isn’t what factor (5) describes.

Two of the factors actively help a plaintiff in the ordinary industrial case. Factor (4) — “the policy of the user and similar users as to repairs, renewals and replacements” — invites proof that comparable operators keep, maintain, and rely on the same equipment for the same period. Factor (1) invites proof about this machine’s condition, which is often better than its age would suggest.

Factor (6) cuts the other way, and I want to know about it before the defendant does. Any modification by the user is expressly relevant to shortening useful life.

Who has to prove it?

The statute calls it a defense and stops there. It doesn’t allocate a burden of production, a burden of persuasion, or a standard of proof, and this article doesn’t supply one. That allocation is governed by authority I’m not citing here.

What the text does support is a pleading obligation. Minn. R. Civ. P. 8.03 requires a party pleading to a preceding pleading to “set forth affirmatively” an enumerated list of defenses “and any other matter constituting an avoidance or affirmative defense.” A statutory provision whose own catchline is “Expiration as defense,” and whose operative words are “it is a defense to a claim,” is hard to call anything else. A defendant who doesn’t plead it, and who raises it for the first time in a dispositive motion or at trial, has a problem. I press that problem.

It’s also not a basis to dismiss a complaint. Nothing in § 604.03 conditions the existence of the claim on the useful life question. The defense assumes there’s a claim and answers it.

Three clocks run in a product case. None of them is useful life.

Strict liability: four years. Minn. Stat. § 541.05, subd. 2: “Unless otherwise provided by law, any action based on the strict liability of the defendant and arising from the manufacture, sale, use or consumption of a product shall be commenced within four years.”

Negligence: six years. Section 541.05, subd. 1(5) covers actions “for criminal conversation, or for any other injury to the person or rights of another, not arising on contract, and not hereinafter enumerated.” My survey of Minnesota civil limitations periods lays these out side by side.

Warranty: four years from tender of delivery. This is the one that surprises people, because it doesn’t run from the injury at all. Minn. Stat. § 336.2-725(1) requires an action for breach of any contract for sale to be commenced “within four years after the cause of action has accrued,” and subsection (2) fixes accrual: “A breach of warranty occurs when tender of delivery is made, except that where a warranty explicitly extends to future performance of the goods and discovery of the breach must await the time of such performance the cause of action accrues when the breach is or should have been discovered.”

Put that next to § 604.03 and the picture flips. On a fifteen-year-old machine, the UCC warranty claim expired eleven years ago no matter when the injury happened, unless the warranty explicitly extended to future performance. The tort claims are alive if suit is brought within four or six years of accrual. And useful life isn’t a deadline at all. It’s an argument the defendant makes to the jury. Three clocks and a defense, and only the defense cares how old the product is.

One more wrinkle in § 336.2-725 is worth knowing, because it’s nonuniform Minnesota text. The section’s final paragraph provides: “This section does not apply to claims against sellers of goods for damages to property caused by the goods where the property that is damaged is not the goods and the sale is not a sale between parties who are each merchants in goods of the kind.” A consumer’s claim for damage the product did to other property falls outside the UCC limitations section by its own terms. For warranty law generally — creation, disclaimer, notice, and remedy limitation — see the UCC gives buyers warranties, then hands sellers three ways to take them back.

Useful life isn’t misuse

They’re different tools with different consequences, and mixing them up costs a plaintiff twice.

Useful life (§ 604.03) is a complete defense if the finder of fact accepts it. The injury was sustained after the ordinary useful life expired, and the claim fails.

Misuse and modification are comparative fault. Minn. Stat. § 604.01, subd. 1a defines “fault” to include “breach of warranty, unreasonable assumption of risk not constituting an express consent or primary assumption of risk, misuse of a product and unreasonable failure to avoid an injury or to mitigate damages, and the defense of complicity under section 340A.801.” Fault reduces the recovery in proportion. It doesn’t wipe it out unless the plaintiff’s share is greater than the defendant’s under subdivision 1.

The overlap is factor (6). A user modification is evidence on useful life and potentially fault, and a defendant will want it pulling double duty. Which special verdict question it belongs in is worth a fight before the instructions conference, not after.

The notice almost nobody sends

Section 604.03 came out of the same 1978 act as a provision most Minnesota lawyers have never used, and this one’s aimed at the plaintiff’s attorney personally. Minn. Stat. § 604.04, subd. 1:

The attorney for a person who intends to claim damage for or on account of personal injury, death or property damage arising out of the manufacture, sale, use or consumption of a product shall cause to be presented a notice of possible claim stating the time, place and circumstances of events giving rise to the claim and an estimate of compensation or other relief to be sought. This notice shall be given within six months of the date of entering into an attorney-client relation with the claimant in regard to the claim. Notice shall be given to all persons against whom the claim is likely to be made.

Four things about § 604.04 matter when you’re working a file.

The clock runs from retention, not from the injury. Six months from the date of entering into the attorney-client relation. I calendar it the day the engagement letter is signed.

It buys the plaintiff something. The same subdivision provides that “[a]ny person in the chain of manufacture and distribution shall promptly furnish to the claimant’s attorney the names and addresses of all persons the person knows to be in the chain of manufacture and distribution if requested to do so by the attorney at the time the notice is given.” That’s a pre-suit identification obligation, enforceable by the subdivision 3 remedy, and it pairs directly with the certification procedure a nonmanufacturer seller uses to get out of the case under Minn. Stat. § 544.41 — see the retailer’s escape hatch.

Actual notice suffices. “Actual notice of sufficient facts to reasonably put a person against whom the claim is to be made or the person’s insurer on notice of a possible claim satisfies the notice requirements of this section.”

And failing to send it doesn’t kill the claim. Subdivision 3 creates a damages remedy against a violator — “may recover damages, costs and reasonable attorney fees from a person who violated this section” — and then closes with the sentence that matters most: “but failure to give notice does not affect the validity of a claim against a party who did not receive notice.” The sanction lands on the lawyer, not on the client’s case.

How I work the file

When the useful-life letter arrives:

1. Don’t treat it as a limitations argument. Ask which affirmative defense was pleaded, and whether it was pleaded at all.
2. Get the source of the stated service life. Factor (5) reaches statements made “in brochures or pamphlets furnished with the product or in a notice attached to the product.” Find out whether the number the defendant is quoting was ever furnished to anyone.

In discovery:

3. Build factor (4). What do comparable operators do with this equipment — repair, rebuild, replace, and at what intervals? That’s the statute’s own benchmark: “the experience of users of similar products.”
4. Build factor (1) on the specific unit. Maintenance records, rebuild history, inspection logs, hour meters.
5. Find factor (6) first. Every modification, guard removal, aftermarket part, and retrofit — and decide whether it’s a useful-life fact, a comparative fault fact, or both.
6. Check factor (2) against the defendant’s own conduct. “The progress of the art, economic changes, inventions and developments within the industry” cuts both ways. A manufacturer arguing that the industry has moved past a design is making an argument that comes back to bite elsewhere in the case.

On intake:

7. Calendar the § 604.04 six-month notice from the retention date, send it to everyone in the likely chain, and use it to demand the chain-of-distribution identification the statute requires.
8. Compute all three clocks — four years strict liability, six years negligence, four years from tender of delivery on warranty — and confirm which claims are actually available before deciding what the case is.

Most states that wanted to protect manufacturers from stale claims wrote a repose statute: a fixed number of years from sale, after which the claim can’t exist. Minnesota went a different way in 1978. It wrote a definition and a list of factors, and it handed the question to whoever decides the facts.

What you get is a defense that’s unusually hard to win on paper and unusually hard to kill at trial. There’s no date to point at in a motion. But there’s also no age at which a Minnesota product claim becomes automatically safe, and a jury asked whether a machine had outlived the period during which it “should be useful to the user” with reasonable safety may find that a natural question to answer against the plaintiff. That’s why I work the six factors in discovery, on both sides of the question, long before anyone frames the special verdict.

I handle Minnesota product liability matters at Madgett Law, LLC — design and manufacturing defect, failure to warn, and breach of warranty — including the useful-life defense under Minn. Stat. § 604.03, the seller certification procedure under § 544.41, and the pre-suit notice obligation under § 604.04. If a product injured you or someone in your family, the age of the product isn’t the end of the conversation. Send us a message or call 612-470-6529.

Sources: Minn. Stat. § 604.03 (useful life of product) — subd. 1, quoted in full (the defense, its scope as to designers, manufacturers, distributors and sellers, and the “expiration of the ordinary useful life” condition); subd. 2, quoted in full (the definition, the “experience of users of similar products” benchmark, and factors (1) through (6) on an “including but not limited to” list). Minn. Stat. § 604.04 (notice of possible claim) — subd. 1 (the attorney’s notice obligation, the six-month period running from entering into the attorney-client relation, notice to all persons against whom the claim is likely to be made, the chain-of-manufacture-and-distribution identification obligation, and the actual-notice provision); subd. 2 (unreasonable delay in retaining counsel); subd. 3 (damages, costs and reasonable attorney fees, and the proviso that “failure to give notice does not affect the validity of a claim against a party who did not receive notice”). Minn. Stat. § 604.01, subd. 1a (definition of “fault,” including misuse of a product) and subd. 1 (proportionate diminution; the “not greater than” bar). Minn. Stat. § 541.05, subd. 1(5) (six-year period) and subd. 2 (four-year strict product liability period, quoted in full). Minn. Stat. § 541.051, subd. 1(a) (two years from accrual and the ten-year accrual cutoff for improvements to real property) and subd. 1(e), quoted in full (the limitations in that section “do not apply to the manufacturer or supplier of any equipment or machinery installed upon real property”). Minn. Stat. § 336.2-725(1) and (2) (four years, and accrual of a breach of warranty at tender of delivery subject to the future-performance exception), and the section’s final unnumbered paragraph, quoted in full (claims against sellers for damage to property other than the goods where the sale is not between merchants in goods of the kind). Minn. Stat. § 544.41 is referenced by subject only, for the seller certification procedure. All statutory text from the Minnesota Office of the Revisor of Statutes, 2025 Minnesota Statutes; the history line for § 604.03 shows a single entry, Laws 1978, ch. 738, § 9, and no section cited was amended in the 2026 Regular Session. Minn. R. Civ. P. 8.03 (affirmative defenses; the requirement to set forth affirmatively “any other matter constituting an avoidance or affirmative defense”) (Minnesota Court Rules, as published by the Office of the Revisor of Statutes). No case law is cited in this article. The allocation of the burden of proof on the § 604.03 defense, and the standard of proof applied to it, are governed by authority not cited here. This article is general legal information about Minnesota law, not legal advice, and reading it does not create an attorney–client relationship. Every product case depends on its own facts, its own product, and its own record. No outcome is promised or implied.