Statute of Limitations for UCC / Sale of Goods in Turkey

Overview

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

Turkey’s commercial claims involving the sale of goods often turn on when the right to sue becomes enforceable and how long that right can be pursued afterward. In many sale-of-goods contract disputes, the “headline” time limit you’ll see in practice is commonly 4 years—but the exact deadline depends on the claim’s trigger date (for example, delivery, payment due date, demand, or refusal).

For readers familiar with UCC-style workflows: Turkey is not governed by the U.S. Uniform Commercial Code (UCC). The practical approach is still similar in spirit: identify the key event date that starts the clock, then map that to the applicable limitation rule (including any special exceptions or suspension/tolling events). DocketMath’s “statute-of-limitations” tool is designed to help you estimate the deadline quickly from those key dates and see how the end date changes when you adjust inputs.

Limitation period

Default rule (common starting point)

A frequent baseline for many contractual claims tied to the sale of goods is a 4-year limitation period. Courts and litigants typically focus on two things:

1. whether the dispute is contractual in nature (i.e., enforcing an obligation arising out of the sale), and
2. what fact pattern determines when the claim became actionable/enforceable.

“From when?”—the most important part

In limitation analysis, the question is not only “how long?” but “from when?”. For goods-related contractual claims in Turkey, the start date is often linked to the moment the creditor can realistically bring the claim, such as:

• Delivery or tender date (often relevant where the buyer’s nonconformity assessment and breach theory begins)
• Due date for payment (often relevant for nonpayment or payment-default theories)
• Date of refusal/demand (often relevant when performance is rejected, or when payment/delivery is formally demanded)

How this affects the DocketMath output

DocketMath’s statute-of-limitations calculator typically changes the estimated end date based on the inputs you provide, especially:

• Claim type (to align the general rule with your scenario)
• Key event date (delivery vs. due date vs. demand/refusal)
• Any suspension/tolling markers you include (only when you have a factual basis)

In other words, if you enter a different “clock-start” event, the computed deadline can shift materially—sometimes by the same magnitude as the difference between the two dates.

Quick timeline example (conceptual)

Suppose a contractual claim is tied to goods delivered on 2026-01-15.

• If your analysis treats the limitation start as the enforceable breach date (often aligned with delivery/tender for nonconformity-type issues), a 4-year period conceptually points to an end date around 2030-01-15.
• If instead your case turns on nonpayment, and your invoice due date is 2026-02-15, using the payment due date as the anchor would shift the end date to align with that later starting point.

Because exact “start” triggers can be fact-sensitive, use the calculator to estimate and then confirm the correct trigger for your specific claim theory.

Key exceptions

Turkey’s limitation framework includes exceptions and special rules that can shorten, extend, or otherwise affect how the limitation period is computed. For goods-sale disputes, the most practical exceptions to consider are:

1) Characterization matters (contract vs. something else)

Even if a dispute “looks” like a sale-of-goods problem, how the claim is legally characterized can change the applicable limitation rule. If the claim is treated as something other than a straightforward contractual enforcement action, the standard 4-year anchor may not apply in the same way.

• Practical takeaway: if your pleading is clearly contract-based (payment due, delivery obligation, damages for breach), you’re more likely in the “contractual goods claim” bucket.
• If your theory relies on a different cause of action, reassess the limitation rule rather than assuming the same 4-year period.

2) Suspension / tolling / enforceability-related shifts

Some events can affect the clock—either by changing when the claim becomes enforceable or by suspending how time runs. Examples in practice include:

• events tied to when an obligation becomes enforceable (e.g., certain notice/demand structures), and
• later clarifications, refusals, or definitive demands that change the effective enforceability point.

Even if the total duration is the same, altering the starting point (or entering a suspension marker when supported by facts) can change the computed deadline.

3) Consumer vs. commercial context

If the underlying transaction is treated as consumer-related rather than purely commercial/B2B, limitation rules and triggers may differ. A mismatch here can lead to incorrect deadline estimates.

• Pitfall: applying a commercial-style approach when the transaction is legally treated as consumer-related.

A practical approach is to model both scenarios in DocketMath if the consumer/commercial characterization is uncertain, and then validate which scenario matches the transaction facts.

4) Contractual provisions vs. statutory limitation rules

Parties sometimes add notice windows or claim-presentation steps in contracts. These provisions can affect how disputes are raised, but they typically operate alongside the statutory limitation framework. Where contract language conflicts with mandatory rules, statutory limitations will generally govern.

In DocketMath, you can still reflect the practical effect of contract timelines by using relevant notice/demand dates as your key event date, but you should avoid assuming the contract can override statutory limitation periods.

Statute citation

Turkish Code of Obligations (Türk Borçlar Kanunu, T.B.K.) Article 146(1) is commonly cited for the 4-year limitation period for many contractual claims where no shorter specific period is prescribed.

Caution (gentle disclaimer): limitation outcomes are highly dependent on how the claim is characterized and what factual event triggers enforceability (delivery, payment due date, demand/refusal, etc.). Article 146(1) should be treated as a starting reference, not an automatic result for every sale-related dispute.

Use the calculator

Use DocketMath’s statute-of-limitations tool at: /tools/statute-of-limitations

Inputs to enter (practical checklist)

• Jurisdiction: Turkey (TR)
• Claim type: contractual sale-of-goods claim (e.g., nonpayment, damages for breach, enforcement of an obligation)
• Key event date (choose the one that best matches your enforceability theory):

  • delivery/tender date, or
  • payment due date, or
  • demand/refusal date (if enforceability is tied to that event)
• Tolling / suspension markers: only if you have a solid factual basis to support them
• Target date (optional): the date you plan to file (or the date you’re evaluating against)

How outputs change when you adjust inputs

To stress-test your estimate, run “what-if” scenarios:

• Move the key event date by ~30 days

  • Expected effect: the computed end date generally shifts roughly in parallel, because the limitation start moves.
• Switch the anchor from delivery to payment due date

  • Expected effect: the deadline may move forward or backward depending on the invoice/payment terms.
• Add a demand/refusal date as the trigger (when relevant to enforceability)

  • Expected effect: the starting point may shift later, potentially extending the estimated deadline.

Primary workflow idea (recommended)

1. Run the calculator using your most likely trigger (delivery vs. due date vs. demand/refusal).
2. Re-run using alternative plausible triggers.
3. Compare results and keep a simple record of assumptions for internal review.

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison