China Contract Dispute Case Law: A Dataset Walkthrough for Cross-Border Counsel

Every commercial relationship a foreign company has in China rests on a contract—a supply agreement, a construction contract, a distribution deal, a loan, a lease, a services engagement. So when something goes wrong, the dispute that follows is, overwhelmingly, a contract dispute. It is the largest single category of commercial litigation in China by volume, and the body of judgments it generates is the best available record of how a breach, a penalty clause, or a termination right actually resolves in a Chinese court—far more reliable than any treatise on what the Civil Code says in the abstract. The problem, as always with Chinese case law, is getting at it in a form you can actually use.

This piece is a walkthrough of China's contract dispute case law as a data problem: how the Civil Code frames it, why the category splinters in ways that make precedent hard to assemble, and what it takes to make breach, liquidated-damages, and performance precedent searchable—for cross-border commercial counsel and for legal AI teams building China coverage. It is informational; it is not legal advice.

The substantive frame: one Code, many sub-causes

Since January 1, 2021, contract matters in China have been governed by the Contract Part of the Civil Code, which absorbed and replaced the former standalone Contract Law and its judicial interpretations. The Code sets the recurring battlegrounds of any commercial dispute:

But "contract law" is too coarse to research with. In the courts, contract disputes are filed and decided under specific sub-causes of action—sale of goods, construction and engineering, loan and financing, leasing, transport, services, supply—and each sub-cause has its own patterns, its own typical breaches, and its own way of handling damages. A construction-payment dispute and a sale-of-goods quality dispute are both "contract" cases, but the precedent that predicts one tells you almost nothing about the other. The unit of useful precedent isn't "Chinese contract law"; it's judgments in the right sub-cause, in the right window, on the right issue.

Two regimes, split by a date

There is a second structural feature Western teams routinely miss: the controlling authority shifts in the middle of the dataset. Judgments dated before 2021 apply the old Contract Law and its judicial interpretations; judgments from 2021 onward apply the Civil Code. Much of the substance carried over, but not all of it, and the citations, article numbers, and some rules changed.

This is why contract precedent has to be sliced by year, not just by sub-cause. Comparing a 2018 liquidated-damages adjustment with a 2024 one without noting the regime shift can quietly mislead. The trajectory of the law—what survived the Code, what changed—is itself part of the answer, and you only see it if the corpus lets you filter by date and read the two periods side by side.

Why this case law is genuinely hard to assemble

Contract disputes are, paradoxically, both the easiest category to find some case in and one of the hardest to assemble well. The volume that makes precedent plentiful is the same thing that makes it unwieldy. Several difficulties compound:

So a question that sounds simple—"how have courts in this province adjusted excessive liquidated-damages clauses in sale-of-goods cases since the Civil Code took effect?"—turns into a manual slog. Answering it well is less a contract-law problem than a data-structure problem.

Turning it into a tractable dataset

Reframed as data, the requirement is concrete. To research China contract precedent reliably, you need a corpus where you can do four things a document dump won't let you do:

1. Isolate the right matters. Filter to the specific sub-cause—sale of goods, construction, loan, lease, service—by cause of action and case-number conventions, rather than wading through everything that mentions "contract" or "breach."
2. Slice by the dimensions that decide the outcome. Narrow by sub-cause, region, court level, year, and outcome—because in contract work the governing regime and the local court's tendencies are part of the holding, not metadata.
3. Cross the language gap. Query in English and read English summaries, while the underlying authority stays the original Chinese judgment.
4. Verify against the source. Every result carries a cited link back to the original document, because no commercial opinion—or AI answer—should rest on an unverifiable summary.

Those four capabilities are what a structured case law corpus provides and an unstructured one does not. Stable fields—case number, court, date, cause of action, parties, outcome—are what let you filter to, say, construction-payment judgments in a given province and window instead of keyword-guessing. We've described how those fields are modeled in our walkthrough of the case law API and document structure; contract litigation is one of the practice areas where that structure pays off most, precisely because the category splinters into sub-causes and the controlling regime turns on a date.

What this looks like for two kinds of teams

For commercial and cross-border counsel

The research workflow becomes tractable. Scope the question—say, how courts in a given region have treated termination for fundamental breach in supply contracts, or how often a particular kind of liquidated-damages clause gets adjusted down—retrieve the matching matters filtered by sub-cause, region, and year, read English summaries to triage, then open the cited Chinese originals for the matters that bear on the deal. For a multinational negotiating a China supply agreement, pricing the exposure on a contested construction claim, or deciding whether to enforce or settle, the value is reasoning from the current local pattern under the right regime rather than from a generic memo.

For legal AI vendors building China coverage

Contract disputes are high-volume, high-frequency, and commercially central—exactly the kind of use case that drives adoption of a legal AI product, and exactly the kind that punishes hallucination. An invented holding on penalty-clause adjustment, or a confident answer that cites the old Contract Law for a 2024 matter, is worse than no answer. That makes it a textbook case for retrieval-grounded generation over a structured corpus: the model answers from retrieved, cited judgments—filtered to the right sub-cause, region, and regime—rather than from parametric memory. If you're building this, the data layer is the whole game; see building China coverage into your legal AI for the stack view, and license vs scrape for why a maintained, freshly synced corpus beats a homegrown scrape in a category this large and this regime-sensitive.

The bottom line

China contract disputes are the litigation almost every multinational eventually touches, and the case law is correspondingly vast—the largest commercial category there is. But that volume cuts both ways: the precedent that predicts a breach or a penalty-clause outcome is plentiful and almost impossible to use without structure, because it splinters into many sub-causes, splits across the Contract Law and Civil Code by date, hides the decisive figures in prose, and lives in Chinese in browse-first databases. Whether you're commercial counsel pricing exposure on a contested claim or a legal AI vendor supporting the question, the constraint is the same: you need the case law to be findable, by sub-cause, region, and year, with citations back to the source. That is a data-structure problem before it is a contract-law one, and it is solvable with the right corpus.

That corpus is what SinoVerdict provides. We license a structured body of more than 170 million Chinese court judgments with stable fields, English queries and summaries, and cited links back to original judgments—delivered via bulk dataset, REST API, and MCP server, with daily updates that matter especially in a category where the governing regime shifted mid-decade. Our clients include LexisNexis and China's leading legal databases. For contract work, that's the difference between guessing how a penalty clause will fare and seeing how courts in the relevant region, under the current Code, have actually treated it.