THE BOTTOM LINE
- The burden of proof is on the customer: If you claim new software is underperforming, you must prove the issue is an inherent defect in the product itself, not a problem with your own IT environment.
- Vague complaints are not enough: Simply stating that a system is “too slow” is insufficient grounds to legally terminate a contract for cause.
- A failed termination can become a standard cancellation: If a customer’s attempt to terminate for breach of contract fails, a court may reinterpret their notice as a simple cancellation of ongoing services, obligating them to pay for the core product and all services used up to that point.
THE DETAILS
This case involved a dispute between a software supplier, Agro IT, and its customer. After Agro IT installed a new software system, the customer refused to pay the outstanding invoices, arguing the system was unacceptably slow compared to their previous one. Believing this poor performance constituted a breach of contract, the customer attempted to terminate the agreement and demanded a refund of payments already made. Agro IT disagreed and sued for the outstanding amount, forcing the court to decide a question familiar to many businesses: when performance disappoints, who is legally at fault?
The court’s decision provides a critical lesson for any company buying or selling technology. It ruled that the burden of proof lay squarely with the customer. While the supplier did not contest that the system was slower, the customer failed to provide concrete evidence that this was due to a flaw in the software itself. The court emphasized that performance issues can arise from numerous factors within a client’s own ecosystem, such as server configurations, network traffic, or hardware limitations. Without a technical analysis that could definitively isolate the cause of the slowness to the supplier’s product, the customer’s claim of a contractual breach failed.
Ultimately, the court’s ruling created a pragmatic, albeit expensive, outcome for the customer. Because no breach was proven, the customer’s attempt to terminate the contract “for cause” was invalid, meaning they were still liable for the full price of the software package. However, the judge did not disregard their communications entirely. The customer’s letters asserting termination were reinterpreted as a standard cancellation of the ongoing maintenance and support contracts. This meant the customer had to pay for all services rendered up until the date the supplier verifiably received the cancellation notice, plus a pro-rata amount for the final service period. The case underscores that clear proof is paramount and highlights the financial risk of withholding payment without it.
SOURCE
Source: Rechtbank Zeeland-West-Brabant
