Statute of Limitations for UCC / Sale of Goods in Connecticut

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Connecticut, the statute of limitations (SOL) for many Uniform Commercial Code (UCC) / sale-of-goods contract claims is 3 years under Conn. Gen. Stat. § 52-577a. This default rule generally applies to common sale-of-goods scenarios (for example, disputes over late performance, nonconforming goods, or nonpayment) unless a different, claim-specific statute or a legally recognized accrual/tolling variation applies.

SOL deadlines depend on the type of claim and the facts—especially the date the claim accrued. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found, so this page uses the general/default 3-year period as the baseline. If your facts clearly fit a different statutory category or a recognized modification, you’d need to adjust accordingly.

Note: SOL timelines are procedural deadlines. Missing a deadline can bar a claim even if the underlying business dispute has merit.

Limitation period

Connecticut’s general/default SOL period is 3 years, typically measured from the date the cause of action accrues. Under Conn. Gen. Stat. § 52-577a, the “accrual” concept matters: courts often examine when the plaintiff’s claim became actionable based on the dispute mechanics and, in some contexts, when the plaintiff knew or reasonably should have known the relevant facts.

Practical checklist: identify the likely accrual dates

Before you run a calculation in DocketMath (the statute-of-limitations tool), gather the dates tied to your timeline:

  • Invoice / delivery date (often relevant in sale-of-goods disputes)
  • Date of breach alleged (e.g., late delivery, nonconforming goods, failure to pay)
  • Tender / rejection timing (if acceptance vs. rejection is part of the story)
  • Notice dates (when the dispute became concrete enough to bring a claim)
  • Last payment or performance date (sometimes relevant to accrual arguments)

How the SOL output changes when inputs change

The SOL “deadline” you get from DocketMath will move based on the start/accrual date you select:

  • Earlier accrual dateearlier SOL deadline
  • Later accrual datelater SOL deadline
  • Different accrual theory (e.g., delivery vs. notice vs. refusal) → different SOL endpoint

That’s why it’s useful to run multiple scenarios rather than betting everything on a single accrual narrative.

Quick example (illustrative)

  • If a buyer claims a sale-of-goods breach tied to nonconforming delivery on January 15, 2023, the 3-year baseline points toward an SOL deadline around January 15, 2026 (subject to how accrual is determined and any tolling/accrual modifications).
  • If instead the buyer’s accrual theory anchors to March 1, 2023, the deadline shifts to around March 1, 2026.

Key exceptions

The 3-year default under Conn. Gen. Stat. § 52-577a is the baseline, but real outcomes can change based on legally recognized concepts. Even if this page doesn’t list every possible exception, here are the most common categories to check in UCC / sale-of-goods disputes.

1) Tolling and “pause” scenarios

Some events can affect whether and when the SOL countdown runs. Depending on the facts, this can include issues like:

  • Fraudulent concealment (impacting when a claim reasonably should have been discovered)
  • Defendant absence or other circumstances affecting when suit could be brought
  • Agreements that impact timing, settlement posture, or practical accrual arguments

Warning: Tolling is highly fact-specific. Two disputes with similar-looking dates can produce different SOL results depending on notice, concealment, disability, or other legal circumstances.

2) Accrual disputes (often the biggest practical driver)

Even when there’s no formal tolling, parties frequently fight about when the cause of action accrued. In sale-of-goods/UCC-style disagreements, accrual can be argued from different milestones, such as:

  • Delivery date
  • Rejection date
  • Notice of breach
  • Payment refusal / nonpayment trigger
  • Discovery of nonconformity (in certain factual patterns)

Because the accrual date drives the deadline calculation, be deliberate about why your chosen accrual date makes sense for your particular claim theory.

3) Contract timing provisions (use care)

Some contracts include notice-and-procedure clauses or internal time limits. Those clauses may affect how the dispute is handled, but they do not always automatically override statutory SOL rules.

For safe use of DocketMath, treat contract-based “notice” or “dispute step” deadlines as possible date inputs you may need for an accrual/timeline argument—but don’t assume they automatically change the statutory SOL without analyzing how the statute and the specific contract interact.

Statute citation

The general/default SOL period used for Connecticut UCC / sale-of-goods contexts in this guide is:

This page uses 3 years because the provided jurisdiction data does not identify a claim-type-specific sub-rule. In other words: assume the general rule unless your facts clearly place you within a different statutory category or a recognized accrual/tolling modification.

This is general information, not legal advice. If the SOL is mission-critical for your situation, consider speaking with a qualified Connecticut attorney.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you generate an actionable SOL deadline by using your relevant dates and the Connecticut (US-CT) 3-year baseline.

How to run it

CTA link: /tools/statute-of-limitations

When you use /tools/statute-of-limitations, you’ll typically want to:

  • Enter your Start/Accrual date (the date you believe the claim accrued)
  • Select **Jurisdiction: Connecticut (US-CT)
  • Use the selection that matches the general/default 3-year SOL baseline for UCC/sale-of-goods analysis consistent with Conn. Gen. Stat. § 52-577a

How to test different scenarios (“what if”)

Because accrual can be contested, run multiple calculations:

  • Scenario A: accrual at delivery
  • Scenario B: accrual at notice of breach
  • Scenario C: accrual at refusal to pay / repudiation
  • Scenario D: accrual tied to a rejection-related milestone (if supported by your facts)

Then compare the resulting deadlines to see which accrual argument creates the tighter (riskier) timeline.

What to check in the output

After you calculate, review:

  • The computed SOL deadline date
  • Whether the deadline is explicitly based on the 3-year rule from your selected accrual date
  • Any displayed adjustments (if the tool offers optional inputs for scenario adjustments)

Note: Even when a calculator returns a deadline date, you should verify the underlying accrual facts (delivery, notice, breach timing) because choosing the wrong start date can shift the result materially.

Related reading