Statute of Limitations for Breach of Warranty in Minnesota

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Minnesota, a claim for breach of warranty is generally governed by the state’s three-year statute of limitations. That means the clock typically starts running from the relevant event tied to the warranty—most commonly when the breach occurs or when the buyer discovers (or should have discovered) the problem, depending on the legal theory being used.

DocketMath’s Statute of Limitations Calculator helps you convert this general rule into a concrete deadline by using your key dates (for example, the date of delivery, the date the breach was discovered, or another date you’re using as the trigger for the claim).

Note: Your situation may involve timelines that differ from the general rule depending on contract wording, warranty type, and the specific legal theory pleaded. This page describes the general/default period Minnesota uses for breach-of-warranty claims, not a claim-by-claim breakdown.

Limitation period

General/default SOL in Minnesota for breach of warranty: 3 years.

  • Default period: 3 years
  • Governing statute: Minnesota Statutes § 628.26
  • Rule status: No claim-type-specific sub-rule was found for breach of warranty in the provided jurisdiction data—so this page uses the general/default period.

How to think about the “start date”

The biggest factor in calculating a deadline is usually the start date—not the three-year length. Even when the length is constant, the deadline changes a lot based on what date the claim is treated as accruing.

Common start-date candidates people use in practice include:

  • Delivery date (often relevant in goods warranty disputes)
  • Tender/rejection or attempted cure date
  • Discovery date (when the issue is detected or should have been detected)
  • Date of refusal to repair/replace (when warranty performance breaks down)

DocketMath can help you test different start dates so you can see how the outcome changes.

What the three-year period means operationally

A three-year SOL typically results in a deadline like:

  • Start date: March 22, 2023
  • Period: 3 years
  • Likely deadline: March 22, 2026 (adjusting for how the specific calendar date is treated)

Because the exact accrual trigger can vary, it’s smart to run the calculator using the date most aligned with your facts and your intended theory—then double-check whether there’s a stronger argument for a different accrual date.

Quick checklist for using the calculator

Before you calculate, gather:

Key exceptions

Even with a general three-year limitations period, real-world timing can shift due to recognized legal doctrines. This section flags the kinds of exceptions that commonly affect deadlines in Minnesota practice, so you can look for them in your documents and timeline.

1) Accrual timing differences (the “trigger” can move)

Because the default is three years, the most frequent “exception-like” change is not the length—it’s when the limitations period begins.

If warranty issues weren’t apparent at delivery, a plaintiff may argue for a later accrual based on discovery or when the breach was effectively made known. The practical takeaway: run the calculator using multiple plausible start dates and document why each one fits your timeline.

2) Contractual warranty terms that affect when the breach becomes actionable

Warranty language sometimes sets a performance period—such as repair/replace obligations lasting for a defined time. Depending on how the warranty is structured, a breach may not be treated as complete until the warrantor fails to perform during the agreed window.

Action step:

3) Tolling or other deadline-modifying doctrines

Certain circumstances can pause (toll) or otherwise modify the SOL. Examples in civil litigation settings can include procedural issues or statutory tolling scenarios.

Warning: The existence of an exception can turn a deadline from “missed” to “still open,” or vice versa. Don’t assume a three-year period runs cleanly from your first selected date—verify whether any tolling or special accrual doctrine plausibly applies to your facts.

4) If your timeline is close, treat it as urgent

SOL disputes often become high-stakes quickly. If you’re within weeks (not months), you generally want to:

Statute citation

Minnesota’s general statute of limitations provision referenced for breach-of-warranty claims in the provided jurisdiction data is:

  • Minnesota Statutes § 628.263-year general limitations period

Based on the jurisdiction data provided, this page applies the general/default period of three (3) years and does not apply a separate, claim-type-specific sub-rule for breach of warranty.

For quick reference:

ItemMinnesota rule (general/default)
SOL length3 years
StatuteMinn. Stat. § 628.26
Claim-type-specific rule found in provided data?No (general rule used)

Use the calculator

DocketMath’s statute-of-limitations calculator turns the three-year rule into a specific deadline date based on your selected start date.

Use this primary CTA to get started:

If you want to understand how to structure your inputs, you can also use DocketMath’s guidance tools—start with the calculator itself: /tools/statute-of-limitations.

What inputs to use (and how outputs change)

You’ll typically supply:

  • Start date (the date the claim is treated as accruing)
  • Optionally, you may compare alternative start dates

Because the rule length is fixed at 3 years, the output changes mainly when you change the start date:

  • If you move the start date later, the deadline moves later by roughly the same amount.
  • If you move the start date earlier, the deadline moves earlier accordingly.

Example scenario (timing comparison)

Suppose your timeline is:

  • Delivery: January 10, 2022
  • Discovery of defect: September 1, 2022

Run two calculations:

  • Start date = January 10, 2022 → deadline = January 10, 2025
  • Start date = September 1, 2022 → deadline = September 1, 2025

Same length (3 years), different deadline—exactly why selecting the right start date matters.

Practical output interpretation

When the calculator outputs a deadline date, treat it as your timing checkpoint for civil filing risk under the general/default rule.

Pitfall: Relying on the earliest plausible date can make the deadline look “already expired.” Conversely, relying on the latest plausible date can backfire if the legal theory requires an earlier accrual. The safest approach is to calculate using the start date you can best justify with your warranty and timeline records.

Sources and references

Start with the primary authority for Minnesota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading