Background
Versata Software held patents covering a computer-implemented method for pricing products by efficiently combining hierarchical customer groups and product groups. Before Versata’s invention, calculating a price that depended on multiple factors — customer type, product type, and order volume — required multiple sequential database queries. Versata’s patents described a more efficient approach: identify all the groups to which a customer belongs, gather all applicable price adjustments in one pass, and compute the final price. Versata marketed this as a product called “Pricer” and licensed the technology widely.
SAP America, the dominant enterprise software company, incorporated similar pricing technology into its enterprise resource planning (ERP) software used by thousands of major corporations worldwide. Versata sued SAP in the Eastern District of Texas in 2007. After two jury trials — the first verdict was set aside by the trial judge — the second jury awarded Versata $260 million in lost profits and $85 million in reasonable royalties, totaling $345 million, which with prejudgment interest came to approximately $391 million. SAP appealed, challenging the patent’s validity, the infringement findings, and the massive damages award.
The Court’s Holding
Chief Judge Rader, writing for the Federal Circuit, affirmed the liability and damages verdict in all material respects. The court rejected SAP’s challenges to the validity of Versata’s patents, finding the claims both novel and non-obvious in light of the prior art. On infringement, the court upheld the jury’s finding that SAP’s pricing module directly infringed Versata’s claimed methods.
The most significant aspect of the appeal was the $391 million damages award. The Federal Circuit affirmed the lost-profits calculation, finding that Versata had adequately established that it lost specific sales of its Pricer product to SAP’s infringing software — the classic lost-profits framework established in Panduit Corp. v. Stahlin Bros. The court also upheld the reasonable royalty portion of the award.
The court did vacate the permanent injunction entered by the district court, finding it overbroad. The injunction had been written to cover SAP products beyond those actually adjudicated to infringe, and the Federal Circuit remanded for tailoring of the injunctive relief to the specific infringing products and features.
Key Takeaways
- The $391 million verdict was the largest patent damages award ever affirmed by the Federal Circuit in a software case at that time — a milestone in the era of large patent judgments against enterprise software vendors.
- Versata established that lost-profits damages remain available in software patent cases when the patentee can show a direct market substitution between its licensed product and the infringer’s competing product.
- The court’s vacatur of the injunction reinforced that permanent injunctions must be tightly scoped to the specific infringing features or products found at trial, not drafted to cover a defendant’s entire product line.
- The case contributed to growing industry pressure for patent reform and was a driver of debates about software patent scope during the period leading to Alice.
Why It Matters
Versata v. SAP stands as a landmark in the history of software patent litigation — a reminder that before the Alice era made § 101 the primary battlefield, patent battles were fought and won (or lost) on massive damages. The case demonstrated that software companies could be exposed to existential patent liability: SAP, one of the world’s largest software companies, was ordered to pay nearly $400 million to a smaller competitor over what was fundamentally a data-retrieval efficiency improvement.
The case also shaped litigation strategy: Versata’s success in demonstrating lost profits — rather than relying solely on a reasonable royalty — showed patent plaintiffs a path to larger damages when they could prove a competitive head-to-head market. SAP subsequently challenged the patents through covered business method (CBM) review at the PTAB, leading to another round of litigation over whether the PTAB had jurisdiction — a dispute that reached the Federal Circuit again in 2015.