Breach of Contract

Occurs when one party fails to fulfill their contractual obligations, either express (explicitly written) or implied (understood from contract's nature or law)

- Warranties - Software must correspond with its specifications and be free from defects

- Fitness for Purpose - Whether Safemix software is fit for the agreed purpose

• Frameguard purchased Safemix to control paint mixing quality
• The malfunction during the first production run indicates failure to meet warranted purpose
• Whether or not compatibility was an issue, software should not malfunction during its intended use.

Installation and Instructions

• Implied Obligation: Sharp was obligated to ensure clear and effective instructions for installation

• Frameguard followed the written instructions provided by Sharp
• Despite following instructions, software failed to perform its intended function
• Suggests a failure in instructions or product

Implied Terms under the Supply of Goods and Services Act 1982 (SGSA)

Section 14 – Fitness for Purpose:

• Goods must be fit for the specific purpose made known to the supplier.

• Application:
• Frameguard explicitly communicated their need for quality control in paint mixing.
• Sharp provided Safemix as a solution for that purpose.
• The malfunction indicates non-compliance with this implied term.

Section 13 – Reasonable Care and Skill:

• Services must be carried out with reasonable care and skill.
• Application:
• If Sharp's team failed to ensure compatibility or proper installation support, they might have breached this obligation.

Establishing the Breach

a. Was the Software Fit for Purpose?

Issue: The Safemix software failed during production despite being installed per Sharp's instructions.

Argument: Sharp breached the fitness for purpose warranty by supplying defective software.

b. Did Sharp Adequately Communicate Compatibility Requirements?

Issue: The email from Steph Mann to Monique Shaw placed responsibility on Frameguard to check compatibility but lacked clarity.

Argument:

A reasonable supplier would have ensured clear and unambiguous communication of essential compatibility requirements.

If the software was incompatible regardless of system upgrades, then Sharp failed in their primary obligation.

c. Was Reasonable Care and Skill Exercised?

Issue: Sharp might argue that Monique had the responsibility to verify compatibility.

Argument:

Even if Monique overlooked compatibility, Sharp had a duty to confirm that Safemix was compatible or to refuse the sale if concerns remained.

Sharp's reliance on an ambiguous email could constitute negligence in exercising reasonable care and skill.

Remedies for Breach of Contract

a. Damages

Frameguard can claim monetary compensation to put them in the position they would have been in if the contract had been performed properly.

Direct Losses:

£18,000 (cost of Safemix software).

£6,000 (wasted materials).

Indirect Losses: While Frameguard managed to recover lost time, any financial implications of delays might be considered.

b. Rescission of the Contract

Frameguard could argue that Sharp’s breach was so significant that it undermines the entire purpose of the contract.

Rescission would involve undoing the contract entirely and returning the purchase price (£18,000).

c. Specific Performance

Frameguard could demand that Sharp rectify the issue or provide a working version of the software.

However, this remedy is rarely granted for defective software contracts.

Legal Precedents Supporting Breach of Contract Claim

The Moorcock (1889)

Principle: Implied terms must ensure the product/service serves its intended purpose.

Application: Sharp failed to ensure Safemix performed adequately for Frameguard's stated needs.

Young & Marten Ltd v McManus Childs Ltd (1969)

Principle: Goods must be fit for the specific purpose communicated to the seller.

Application: Frameguard communicated their needs explicitly, and Sharp failed to meet those.

St Albans City and District Council v International Computers Ltd (1996)

Principle: Limitation clauses may be invalid if they fail the test of reasonableness under UCTA.

Application: Frameguard might argue the liability cap of £18,000 is unreasonable given the scope of Sharp’s breach.

Recommended Strategy for Frameguard

Focus on Breach of Contract:

Emphasize failure to meet express and implied warranties regarding fitness for purpose and reasonable care.

Challenge the Limitation Clause:

Argue it is unreasonable under UCTA 1977 given the nature and impact of the breach.

Pursue ADR (Alternative Dispute Resolution):

Suggest mediation to negotiate a refund and avoid prolonged litigation.

Document Evidence Clearly:

Highlight communication gaps, failed functionality, and financial impact.

Misrepresentation

• Email from Steph Mann to Monique Shaw (21st August '24)
• Steph Mentioned system requirements and said Monique would look into compatibility
• the wording is ambiguous and does not guarantee compatibility

Frameguard Argument

• Software not fit for purpose, even with existing system
• Sharp did not adequately clarify or ensure Frameguard understood the system requirements
• Monique relied on impression from Steph software would work

Sharp Counter- Argument

• They made compatibility requirements clear in email
• Monique acknowledged she would check those requirements
• Any failure to confirm compatibility lies with Frameguard

Types of Misrepresentation and Application

a. Fraudulent Misrepresentation:

Definition: A knowingly false statement made with the intent to deceive.

Application:

No evidence suggests Steph intentionally lied.

Therefore, fraudulent misrepresentation is unlikely to succeed.

b. Negligent Misrepresentation (Misrepresentation Act 1967, Section 2(1)):

Definition: A false statement made carelessly, where the maker had no reasonable grounds to believe it was true.

Application:

Steph’s statement was vague and left compatibility confirmation to Monique.

However, Sharp might argue they did their duty by mentioning system requirements.

Frameguard will struggle to prove negligence here.

c. Innocent Misrepresentation:

Definition: A false statement made honestly and without negligence.

Application:

If Steph’s email was honest but misleading in its vagueness, it could fall under innocent misrepresentation.

The court may order rescission (cancellation of the contract) or damages in lieu of rescission.

Challenges to Misrepresentation Claim

The email placed responsibility on Frameguard (Monique Shaw) to verify compatibility.

The contract contains a warranty clause stating the software would be fit for purpose, which could supersede earlier discussions.

Sharp’s defense will rely heavily on arguing that Frameguard failed to carry out reasonable checks before purchase.

Conclusion: Will Misrepresentation Hold Up?

Fraudulent Misrepresentation: Very unlikely.

Negligent Misrepresentation: Unlikely—Frameguard would struggle to prove negligence on Sharp’s part.

Innocent Misrepresentation: Possible, but not guaranteed.

Best Strategy for Frameguard:

Frameguard should focus on breach of contract rather than misrepresentation.

Use the misrepresentation argument as a supporting claim to strengthen their negotiation position.

Seek Alternative Dispute Resolution (ADR) for a practical resolution.

Limitation of Liability

Clause stating there is a Limitation of Liability

Meaning-

• Liability Cap: Sharp's max liability for any breach, negligence or other claim is limited to £18k.
• No Additional Damages: Frameguard cannot claim beyond £18k regardless of indirect losses, ie lost profits, reputation damage.
• Scope of Coverage: Applies whether the claim arises from contract law, tort (negligence), or any other legal basis.

Is This Clause Legally Enforceable?

Under UK contract law, limitation clauses are generally enforceable if:

Reasonable and Fair: The clause must be fair under the Unfair Contract Terms Act 1977 (UCTA).

Clearly Drafted: The wording must be unambiguous and brought to the attention of the parties during negotiation.

Not Excluding Fundamental Obligations: A party cannot exclude liability for fundamental breaches (e.g., if the software was entirely unfit for purpose).

In this case:

The clause was included in the written agreement signed by both parties.

It is clearly worded and sets a specific cap.

It is likely enforceable, but it may be challenged if Frameguard can argue:

The clause is unreasonable under UCTA.

Sharp failed in their fundamental obligations (e.g., delivering fundamentally defective software).

How Should Frameguard Proceed?

Challenge the Clause: Argue that the clause is unreasonable under UCTA due to the fundamental failure of the software.

Negotiate a Settlement: Suggest an ADR process (e.g., mediation) to avoid costly litigation.

Focus on Evidence: Highlight the software’s failure and the resulting financial loss of £6,000 in materials and overall disruption.