This case report is now 0 months old and may not represent current law.
Does a customer’s purchase order create a binding contract? Not on its own, as a purchase order is only an offer, and there’s a contract once you’ve accepted it and the two of you have agreed the things that matter, which usually means what is being bought, how much of it, at what price, when it’s delivered and how it’s paid for. If those are still being discussed, you can have bought the materials and started production and still have no contract.
Most suppliers assume that once a purchase order has arrived and they’ve started work on it, the customer is committed. Shakespeare Monofilament UK Ltd v Eurosaf Srl [2026] EWHC 3011 (Comm) is a good example of why that assumption is risky. It’s a first instance decision of Her Honour Judge Kelly in the Circuit Commercial Court in Leeds, handed down on 20 November 2026, and although it turned on its own documents, the process it describes will look familiar to anyone who sells to trade customers.
What happened
Shakespeare is an English manufacturer of monofilament yarn. Eurosaf, an Italian company, emailed out of the blue in April 2022 looking for a new supplier, partly because its existing suppliers had lead times of a year or more and Shakespeare’s was about seven months. Five months of emails, price lists, technical data sheets, product trials and a meeting in Italy followed, and as the relationship went on, more and more of it moved onto WhatsApp. Shakespeare’s price lists set minimum order quantities (MOQs) for each product, and it kept asking Eurosaf to “respect the MOQs” and to reorder using Shakespeare’s own product codes rather than a competitor’s.
On 22 September 2022 Eurosaf sent three purchase orders. Two (PO132 and PO133) were for delivery in January 2023. The third, PO150, was worth just over €1m and was for staggered deliveries through 2023. Shakespeare’s salesman replied the same day thanking Eurosaf for the orders, saying the payment and delivery terms were on the price list and suggesting a Teams call the following week.
The January orders were renegotiated, acknowledged, paid for and delivered, but PO150 never got that far. Eurosaf sent an amended version in December 2022, Shakespeare replied in January asking whether the original order was still valid and asking Eurosaf to update it with the right codes, and in March 2023 Shakespeare sent eight sales order acknowledgements and pro forma invoices. By then it had bought the raw materials and started making some of the yarn.
Eurosaf’s own production then ran into technical problems. It asked Shakespeare to suspend production in late March and in June 2023 wrote cancelling “all open orders”. Shakespeare sued for the stock it had made and the profit on the rest, a claim which by trial was about €304,000.
Reading the chronology, a lot of the exchanges were short. The salesman’s reply to the purchase orders was four lines long, Eurosaf confirmed its January orders by WhatsApp, and much of the 2023 back and forth about suspending production happened in brief WhatsApp messages (“I’m assuming the orders are only suspended due to qualification”). Brevity is usually a good thing, but a quick reply or a WhatsApp message rarely says exactly what has been agreed, and when the question later is whether there was a contract at all, that’s what you need the documents to show.
Why there was no contract for PO150
The judge accepted that there was a binding contract for PO132 and PO133, although she found it was only made in mid-December 2022, when the quantities had been agreed and the revised acknowledgements sent, and not when the orders arrived in September.
For PO150 she found there was never a contract at all, and she went through each of the dates Shakespeare put forward. PO150 was an offer which Shakespeare was free to accept or reject, but 18 of its 48 product lines were below the MOQ, which the judge treated as a fundamental term for Shakespeare, and five lines had no product code, which meant Shakespeare’s own system couldn’t process them. The covering email asked Shakespeare to send order confirmations “complete with all supply conditions such as delivery dates and payments” and the order itself said payment was still to be agreed. Eurosaf had accepted payment up front, but only “for the first time”, which the judge read as applying to the January orders. Eurosaf had said Shakespeare could pick the delivery dates to suit its production, but the judge didn’t accept that this meant Shakespeare could choose any dates it liked without agreeing them, as Eurosaf had its own production to plan.
The judge didn’t treat the salesman’s September email as an acceptance, and his suggestion of a Teams call showed he expected more negotiation. Both sides also expected the contract to be finalised by Shakespeare sending order confirmations, as it later did for the January orders, so Shakespeare’s own process counted against it.
The March 2023 acknowledgements didn’t help either. Their product lines didn’t match PO150 or the December amendment, seven of the eight pro forma invoices said ex works when Eurosaf had insisted on delivery to its door (DAP), and they attached Shakespeare’s terms and conditions, which Eurosaf had never agreed to. The judge treated them as a counter-offer, and Eurosaf never accepted it.
Even with a contract, the damages would have failed
The judge said that if she was wrong on liability she would still not have awarded what Shakespeare claimed. Shakespeare hadn’t tried to find out whether anyone else would buy the yarn it had made, and simply said it was bespoke, even though competitors had year-long lead times and Eurosaf’s products were modelled on a competitor’s. The lost profit figures came from a sales forecast with nothing behind it to support the costs, and most of the raw materials had since been used for other customers without any evidence about the profit on those orders.
That part of the judgment is obiter (the judge didn’t need to decide it), but a claim like this needs evidence of the loss as well as a contract.
What to do if you sell like this
I’ve written separately about DAZN v Coupang, where a deal done by email and WhatsApp was held to be binding, and about proving which terms and conditions you sold on. This case is the other side of the first one, and the difference is mostly whether the key terms had been pinned down.
If you’re a supplier, it’s worth looking at how an order actually becomes a contract in your business. If your process is that nothing is confirmed until you send an order acknowledgement, the court may well hold you to that, so make sure the acknowledgement matches what the customer asked for (or clearly says what has changed) and that you get the customer to confirm it in writing. If an order is below your minimum quantities, has the wrong codes or leaves delivery dates and payment open, sort that out and confirm it before you treat the order as firm.
Where lead times mean you have to buy materials or start production before everything is agreed, that’s a commercial risk you’re taking, and you can reduce it by getting a deposit, a signed confirmation of quantities and dates, or a simple framework agreement which says what the customer is committed to. Your terms and conditions should also go out at the start, with the quotation, and be accepted then, rather than being attached to the acknowledgement at the end where they can turn it into a counter-offer.
If a customer does cancel, keep records of what you did to sell the stock elsewhere, as saying it was bespoke won’t get you far without some evidence.
I draft terms and conditions and supply agreements for businesses selling to trade customers, here and abroad, and I can look at whether your quotation, order and acknowledgement process actually produces a contract on your terms. Get in touch if you need some help.
Written by Steven Mather, a business solicitor acting on company sales and purchases. This is general information about the law, not legal advice on your situation. Law correct as at .



