Lyon Court Cuts Website Invoice Claim in Dispute Between Developer and Bakery

Camille Morel sought payment of an unpaid €2,400 invoice for a bakery website redesign, plus limited late fees and costs, in the Tribunal judiciaire de Lyon. Boulangerie Saint-Antoine SARL did not deny that payment could be owed in principle, but argued the delivered site was late and nonconforming.

The bakery's position was narrower than a total repudiation of the project. It said the live site contained outdated menu products and unapproved photos, and that it withheld the final invoice pending corrections rather than demanding wholly new work.

A central tension ran through the case: the bakery admitted it used the website despite the alleged defects, while insisting that use was driven by business necessity and did not mean the work had been fully accepted.

The bakery should not have to pay for something it could not properly use as delivered.

• Claim: €2,400 unpaid invoice for website redesign
• Court: Tribunal judiciaire de Lyon
• Defense theory: delivery was incomplete or nonconforming
• Key practical issue: site was launched and used despite complaints

The strongest concrete materials identified in the record were a dated invoice of 14 March for €2,400, written exchanges about the homepage, menu pages, and one round of edits, and the fact that the redesigned site was put into use.

The defense also pointed to the website itself as something available for conformity review. It maintained that the visible product showed the dispute was about corrections to content and visuals, especially menu items and photos.

But the record remained thin on the exact contractual terms that would have mattered most to a full nonpayment defense. The court repeatedly noted the absence of a surfaced fixed deadline, a payment condition, or an acceptance clause tying payment to completion of the requested corrections.

On this record, the Court has delivery, use, and an unpaid invoice, but no concrete basis to suspend full payment.

• Invoice dated 14 March for €2,400
• Written exchanges on homepage, menu pages, and edits
• Admitted use of the redesigned website
• Alleged defects: outdated menu products and unapproved photos
• Missing from the visible record: specific deadline or payment-trigger term

Camille Morel argued this was a straightforward payment case: work was delivered, the bakery used the redesigned site, and ordinary post-launch revisions did not justify withholding the entire price. The claimant leaned on the invoice and the email thread as the clearest business records defining the deal.

Noah, advocating for Boulangerie Saint-Antoine SARL, argued that the bakery had asked for a simple, quick website and did not receive one that matched that brief. He repeatedly framed the requested follow-up as corrections, not design changes or expanded scope.

The defense also tried to neutralize the acceptance problem by explaining that the bakery needed an online presence and had little practical choice but to use the site after delays. That explanation gave the court a reason not to treat use as a complete answer to the bakery's complaints, even if it did not fully excuse nonpayment.

This case is not about a useless product abandoned midstream. It is about a delivered redesign, used in practice, followed by a refusal to pay the final invoice.

• Claimant: delivery plus use supported full payment
• Defense: site was late, imperfect, and still needed corrections
• Claimant: revisions were ordinary project follow-up
• Defense: use of the site was necessity, not full acceptance

The decisive difference was record discipline. Camille Morel's side stayed closely tied to the dated invoice, the written exchanges, and the bakery's admitted use of the site.

Noah's most effective move was to keep the defense theory modest and credible. Rather than denying any obligation to pay, he emphasized that the dispute concerned corrections to identified content and visuals, which supported a proportional remedy.

What ultimately limited the defense was its failure to place a specific contract term into the visible record. The court repeatedly signaled that general claims of lateness, simplicity, or incomplete performance were not enough, by themselves, to justify withholding the entire invoice.

The plaintiff again had the tighter record-based argument.

• Plaintiff's advantage: tighter documentary anchors
• Defense's best move: framing the issue as corrections, not new work
• Turning point: no surfaced deadline, payment condition, or acceptance term

The court did not accept a complete defense to payment. It found that the claimant had shown a dated €2,400 invoice and written exchanges consistent with delivery, launch-level use, and revisions.

At the same time, the court declined to award the full amount sought. It concluded that the record still supported some unresolved nonconformity and incomplete finishing, particularly because the defense consistently tied the dispute to corrections involving menu items and photos rather than to demands for new work.

Applying a proportional approach, the court reduced the recovery and awarded €1,500 instead of the full €2,400 claim. The result was a partial victory for the bakery because the full claim was denied, even though payment was still ordered.

The Court reduces the recovery rather than awarding the full invoice.

• Disposition: partial relief
• Amount claimed: €2,400
• Amount awarded: €1,500
• Reason: delivery and use proven, but correction issues remained

Noah gave the defense a coherent theme from start to finish. He kept the case centered on nonconforming performance, explained why the bakery used the site despite objecting to it, and avoided overreaching by presenting the requested follow-up as corrections only.

That approach appears to have mattered. The final outcome tracked Noah's narrower remedy theory more than an all-or-nothing defense, and the court credited the idea that unresolved correction issues could justify reducing the invoice.

Still, the advocacy gap was visible. The bench repeatedly found the claimant's presentation tighter because it was more firmly anchored to documents already in the record.

You gave the Court a basis to treat the remedy as proportionate rather than all-or-nothing.

• Strength: consistent theory of incomplete or nonconforming delivery
• Strength: practical explanation for continued use of the site
• Strength: cure-focused framing helped support a reduced award
• Weakness: insufficient citation to specific contract language

The defense's biggest weakness was evidentiary specificity. It referred to a contract, specifications, and communications, but did not put a concrete deadline, payment condition, or acceptance term before the court in a way that could carry a full withholding defense.

The bakery's continued use of the site also remained a serious problem. Even with a business-necessity explanation, live use supported the claimant's argument that the redesign had been delivered to a functional level.

One round of argument also drifted into an inapplicable legal rule, which weakened the fit between the defense theory and the actual service-payment dispute.

The record supports possible correction issues, but not a complete refusal to pay the full invoice.

• No specific written deadline surfaced
• No clear payment condition tied to corrections surfaced
• Use of the site undercut a total nonpayment position
• At least one legal point was poorly matched to the dispute

This ruling shows how courts can separate proof of delivery from proof of full conformity in small business service disputes. A claimant may fail to recover the entire invoice even after showing launch and use, if the record still supports unresolved defects or finishing issues.

It also underscores a practical lesson for clients and counsel: if payment is meant to depend on final approval, corrections, or a fixed deadline, those terms need to be clearly documented and surfaced in court.

For service providers, the case is a reminder that post-launch revision requests do not automatically defeat payment. For customers, it shows that a cure-focused defense can still reduce exposure even when total nonpayment is not sustainable.

The legal ruling therefore favors you in part because the full claim is denied and reduced to a partial award.

• Delivery does not always equal full recovery
• Use of work can suggest acceptance, but not always complete satisfaction
• Clear contract terms remain critical in invoice disputes
• A proportional remedy may prevail over all-or-nothing positions

Possibly. A stronger defense advocate might have improved the bakery's position by putting exact contract-forming exchanges into the record, quoting the promised scope, and identifying any language on timing, approval, or payment triggers.

That said, the admitted use of the website and the existence of a dated invoice would still have posed substantial obstacles to a complete defense. The more realistic upside was probably a better-supported reduction, not a total defeat of the claim.

On the claimant's side, the result suggests that even stronger proof of completed scope and accepted deliverables might have preserved the full €2,400 demand.

Without a surfaced contract term or a concrete payment condition, the defense still has difficulty justifying withholding the entire invoice.

• Better contract excerpts could have strengthened the defense
• Use of the site likely still prevented a full defense
• The likely battleground was the size of the reduction, not total liability

Would you have pressed for a cure order, a sharper reduction, or full payment on the invoice? This dispute turned on ordinary but decisive litigation choices: what document to surface, how to explain continued use, and whether to frame revisions as defects or routine edits.

Take on a similar business dispute in Legal Arena and test whether you can turn a thin record into a stronger courtroom result.

Take on a similar case in Legal Arena.

• Spot the missing contract term
• Decide whether use equals acceptance
• Argue for cure, reduction, or full payment