10 Fundamentals in Offers, Acceptance, and Battle of the Forms: Practice Points

Start every analysis with the three questions that actually matter. Laura built her whole approach around whether a binding contract exists, when it became binding, and what it said in that moment. Until you know a contract exists, you are managing a relationship with no contract, which is a completely different risk picture and a completely different conversation with the business. Once you know when it became binding, you know which document set the terms. Answer them in that order and the rest of the analysis follows.

Treat purchase orders as offers and train the people who send them. A purchase order is the customer's offer, and depending on the facts it can also work as an acceptance of something the vendor sent earlier. Laura called the frontline buyer one of the most critical parts of a company's contracting process, because that person sends out offers all day long and fields whatever comes back. Buyers manage detail for a living and they respond to understanding the gravity of the situation far better than to a rule telling them to handle replies. Give them the reasoning and they will protect the company.

Remember that a rejected offer is dead and cannot come back. Once the other side rejects an offer, it cannot be accepted later, and that rule gave Laura real leverage when she counseled procurement teams. It means you can permanently kill an offer you no longer want by getting a clear rejection on the record. It also means you control your own offers and can cancel them any time before acceptance, absent a firm offer you promised to hold open or reasonable detrimental reliance. Knowing an offer is gone is often more valuable than arguing about what it said.

Read a counteroffer as two moves happening at once. A counteroffer rejects the offer on the table and makes a brand new one, so the original cannot be revived and the roles flip. The vendor becomes the offeror and your company becomes the party deciding whether to accept, reject, or say nothing. That matters enormously with purchase orders, because your PO was built to be the offer that controls. Counteroffers usually change only a few terms and carry the rest forward, which makes it easy to miss that you are now looking at the vendor's offer.

Reply to every vendor response to a purchase order. This was one of Laura's top rules for the supply chain teams she trained. Silence after a vendor writes back with a change is exactly where the facts go fuzzy and nobody can say what the terms are. Every email that comes in from a vendor who received a purchase order needs an answer, and usually that answer rejects the counteroffer rather than agreeing to it. She estimated these vendor responses were mishandled a quarter of the time over her career, which made it one of the biggest unmanaged risks she saw.

Handle post-PO changes by canceling and reissuing rather than agreeing by email. Purchase orders live in the ERP system, and finance reads them for spend while logistics and operations read them for what arrives and when. A side agreement in an email never reaches that system, so the whole company runs on terms that do not match the deal. Laura's practice was killing the purchase order, settling the terms in conversation, and issuing a new one on the terms you actually want. Never amend a purchase order or any contract through a side email.

Know the rules that turn no answer into acceptance. Master agreements and purchase order terms often carry deemed acceptance language, where a purchase order not rejected within a couple of days becomes binding on the seller. Under the UCC, two merchants can also end up bound when a counteroffer does not materially change the offer and nobody objects within ten days. Laura saw sellers send fast replies with small changes, and she assumed most of them knew exactly what they were doing. The clock on those emails is running whether or not anyone is watching it.

Put safe harbor language in your offer and still manage the communications. Laura pointed to UCC safe harbor language saying the offer can be accepted only exactly as offered and any counteroffer is rejected, and she noted that many states apply similar principles to services and digital deals. She was clear that the language reduces your risk rather than eliminating it, because you never know the full course of dealing or everything the parties said along the way. Keep the language in your terms and keep replying to vendors anyway. Both together are what actually protect the deal.

Never incorporate a sales quote into your purchase order. Laura called this one of her cardinal rules, and she had watched it go wrong all the time. Attaching a vendor's sales quote, or writing that the PO confirms it, hands a court an offer that swallows the vendor's warranty, indemnity, and liability terms, which is the opposite of what your purchase order was built to do. When the team needs the commercial details, copy the pricing, scope, and technical terms into an attachment and leave the legal terms behind. Acknowledging that a quote arrived is fine, and accepting it is not.

Watch the quiet documents that create obligations. Credit applications hide fine print agreeing to legal terms in a vendor sales quote you have never read, and Laura wanted those reviewed unless the credit team had someone sophisticated looking at them. Award letters hand vendors an argument that the deal was theirs before you awarded it, and she avoided them as a general practice because no good deed goes unpunished. Emails and texts create binding obligations too, which is why she made offers only through purchase orders or real negotiated contracts. Put your terms where your system can see them.