Supplier Agreement Clauses

Contracts don’t protect you. Strong clauses do. In procurement, signing a contract is not the finish line it’s the risk management starting point. Over the years, I’ve learned that the organizations that stay protected don’t rely on trust alone. They rely on well-designed assurance clauses. Here are some contract clauses every procurement team should insist on: ✔️ Performance guarantees – protection if delivery fails ✔️ Liquidated damages – clear consequences for delays ✔️ Retention & acceptance clauses – pay only for completed, approved work ✔️ Indemnity & insurance – protection from third-party claims ✔️ Change control – no scope, cost, or timeline changes without approval ✔️ Termination rights – flexibility when performance or priorities change ✔️ Audit rights – transparency, accountability, governance ✔️ IP & confidentiality – protect your data, outputs, and reputation A good contract doesn’t assume everything will go right. It prepares for when things don’t. That’s where procurement adds real value not just buying, but protecting the organization. #Procurement #ContractManagement #RiskManagement #Governance #SupplierManagement #ProcurementLeadership #ProcurementExcellence

When disaster hits your suppliers, will your contract protect you? A weak FM clause = big risk when storms hit. Below infographic shows 10 must-haves in your Force Majeure clause. Procurement Excellence | 04 APR 2026 - Force majeure clauses are Procurement "get-out-of-jail-free" card for supply chain disasters, if they’re written right. Here are 10 Force Majeure key considerations procurement managers need to know: #1. List the "Big Bad Events" ↳Don’t just say "Acts of God" name them! ↳e.g. hurricanes, wars, pandemics, government shutdowns #2. DEMAND proof it’s impossible ↳If Supplier can’t deliver, let them show why. ↳Price spikes don’t count; a flooded factory does. #3. SET notification deadlines ↳Require suppliers to notify you ASAP. ↳Notification shall be within 3 days of the problem. Late notice = no protection. #4. MAKE suppliers find alternatives ↳Suppliers must prove they tried alternatives ↳ e.g. Before claiming find backup suppliers #5. PAUSE deliveries, NOT contracts ↳For delays extend deadlines, don’t cancel orders. ↳Port strike adds 3 weeks to delivery. #6. Add an EXIT clause ↳Don’t get stuck forever if the delay drags on. ↳Either party may cancel after 90 days of delay. #7. Watch Their Suppliers ↳Cover their supplier only for disasters (fire/flood). ↳Sub contractor's bad planning is their problem. #8. Cover Government Surprises ↳Include sudden bans or new laws ↳Unexpected import restrictions e.g. sudden steel tariffs. #9. PAY only for what you get ↳Payment due only for delivered goods. ↳You still pay for what you got! FM pauses future deliveries, not past invoices. #Bonus: Only Unforeseen Events Count ↳Signing a contract during a pandemic? ↳Exclude foreseeable risks e.g. monsoons in rainy season. Your clause is ONLY as strong as its wording. Do This Now: → Review key contracts: Do they cover these 10 points? → Talk to suppliers & align on what FM means upfront! Every contract is different. When in doubt, ask legal! Are there any other considerations that I may have overlooked? ♻️ Repost if to help someone in your network. ➕️ Follow Frederick for more procurement insights. #Procurement #SupplierManagement #ContractManagement #SupplyChainResilience

Don't skip these key clauses in a contract. When it comes to contracts, there are a few non-negotiables that every agreement needs. But, too often, certain clauses get overlooked—until they’re needed the most. 1. Indemnity Clauses One clause I see skimmed over frequently is the indemnity clause. This clause outlines who is responsible for covering certain losses or damages. I remember a case where a small business client didn’t pay attention to indemnity in their vendor agreement. Later, they faced a lawsuit due to a third-party issue and ended up covering legal costs that could have been avoided. A well-written indemnity clause could have saved them thousands! 2. Confidentiality Clause is not a BOILERPLATE Imagine your vendor shares sensitive pricing or client details with a competitor. If confidentiality clauses are not in place, this scenario can quickly become a nightmare. For example, one of my clients was shocked to find that their former partner leaked proprietary data after their contract ended. Had they reinforced confidentiality terms, they’d have had legal ground to seek compensation. 3. Termination Clauses Aren’t Just for Big Businesses The flexibility to end a contract under fair terms should be available for businesses of all sizes. One startup founder I worked with learned this the hard way. They had no exit terms in a long-term contract with a supplier, and when quality started slipping, they were locked in. Adding a simple termination clause with notice period requirements would have made a world of difference. So, what’s the solution? Always review these key clauses carefully before signing. Better yet, get a second set of eyes on it—either from a lawyer or a junior. Which clause do you think gets overlooked the most in contracts? #contracts #legalcontracts #agreements

After drafting and negotiating hundreds of contracts across M&A, finance, and commercial arrangements, I've seen companies make one expensive mistake: repeatedly treating Limitation of Liability and Indemnification clauses independently. They negotiate a strong limitation of liability, then unknowingly destroy it with an indemnification clause that overrides everything. ▪️Where LoL and Indemnity Collide Here's one scenario that captures the problem: Data breach: ·      Liability cap: $1M ·      Indemnity: "Provider shall indemnify Client for all losses arising from failure to maintain security" Breach occurs. Costs: $3M in regulatory penalties and notifications. Even if you negotiated the liability cap for weeks, the indemnity wins. Provider owes $3M, not $1M. ▪️How to Actually Align These Clauses These are strategies, not absolutes. What works varies by deal size, leverage, and industry etc. #1: Make LoL explicitly control indemnification "The limitations of liability in Section [X] apply to all obligations, including indemnification under Section [Y]. No indemnification obligation shall exceed liability caps unless expressly stated." Whether this works depends on many factors – for example – leverage and vendor standards. #2: Use tiered caps Sophisticated contracts tier liability: E.g.- ·      General: $500K ·      IP indemnity: $2M ·      Data breach: $5M ·      Unlimited: confidentiality, fraud, gross negligence Common in high-risk deals, less in low-value SaaS. Scale to contract value and vendor size. #3: Narrow indemnity scope "Provider shall indemnify Client only for third-party claims alleging [specific harms], arising from Provider's breach of [security obligations], subject to caps in Section [X]." Big vendors often resist scope rewrites; smaller vendors may negotiate. #4: Align with insurance "Provider shall maintain cyber liability insurance of not less than $[amount], with Client as additional insured." If risk is $5M but vendor's policy is $1M, you have wishful drafting, not protection. #5: Resolve consequential damages conflict "The exclusion of consequential damages in Section [X] does not apply to indemnification under Section [Y]. Indemnified losses may include business interruption and lost profits, subject to applicable caps." Many vendors treat consequential damage exclusions as sacred, tailor to risk profile. #6: Separate defense from indemnity "Provider shall defend and indemnify Client... Defense costs (including attorneys' fees) are separate from indemnity obligations and shall not erode liability caps." Defense costs often exceed caps before liability is determined. There’s no perfect structure, only alignment. Your LoL and indemnity must work together, or the indemnity overrides the cap and creates a litigation-worthy ambiguity. This post is for general discussion only and isn’t legal advice. #LimitationOfLiability #Indemnification #Contracts

𝐀𝐈 𝐯𝐞𝐧𝐝𝐨𝐫 𝐜𝐨𝐧𝐭𝐫𝐚𝐜𝐭𝐬 𝐚𝐫𝐞 𝐧𝐨 𝐥𝐨𝐧𝐠𝐞𝐫 𝐣𝐮𝐬𝐭 𝐚𝐛𝐨𝐮𝐭 𝐩𝐫𝐢𝐜𝐢𝐧𝐠 𝐚𝐧𝐝 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬. In 2026, they need to clearly define control, ownership, compliance, and exit rights. 𝐁𝐞𝐜𝐚𝐮𝐬𝐞 𝐨𝐧𝐜𝐞 𝐀𝐈 𝐛𝐞𝐜𝐨𝐦𝐞𝐬 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐲𝐨𝐮𝐫 𝐰𝐨𝐫𝐤𝐟𝐥𝐨𝐰𝐬, 𝐭𝐡𝐞 𝐫𝐢𝐬𝐤𝐬 𝐛𝐞𝐜𝐨𝐦𝐞 𝐝𝐞𝐞𝐩𝐞𝐫: Your data may move across regions. The vendor may change the underlying model. Your AI-generated outputs may create ownership confusion. Your workflows may become hard to migrate. Your compliance claims may lack real evidence. That is why every AI vendor contract should include these 5 clauses: 1. Data Residency Define where your data is stored, processed, backed up, and who can access it. 2. Model Swap Rights Get visibility and approval rights before the vendor changes the AI model behind the product. 3. Output IP Clarify who owns AI-generated reports, code, workflows, prompts, and business-critical outputs. 4. Exit & Portability Make sure you can leave without losing your data, workflows, history, or operational continuity. 5. Audit Access Ask for evidence through reports, logs, compliance proof, and incident records. AI tools can create speed. But without the right contract terms, they can also create lock-in, compliance gaps, and ownership risk. Before signing with any AI vendor, don’t just ask: “What can the tool do?” Also ask: “𝐖𝐡𝐚𝐭 𝐡𝐚𝐩𝐩𝐞𝐧𝐬 𝐭𝐨 𝐨𝐮𝐫 𝐝𝐚𝐭𝐚, 𝐨𝐮𝐭𝐩𝐮𝐭𝐬, 𝐚𝐧𝐝 𝐜𝐨𝐧𝐭𝐫𝐨𝐥 𝐨𝐧𝐜𝐞 𝐰𝐞 𝐬𝐭𝐚𝐫𝐭 𝐮𝐬𝐢𝐧𝐠 𝐢𝐭?” ♻️ Repost to help a team understand where they truly fit. ➕ Follow Prem N. for more

The most negotiated clauses in supplier contracts are those you'll never use. Here's 3 that don't matter and 5 that do ... Limitation of liability. Indemnity. Governing law. Teams burn hours on all three, but those clauses only ever bite in one place. A courtroom. And if you're there, it's already in legal's hands. Not yours. Meanwhile the clauses that decide whether you actually get what you paid for? They get a fraction of the attention. So, here's a simple rule for your next supplier conversation. Master these 5: 1. SCOPE/STATEMENT OF WORK What you're actually buying, in black and white. The #1 source of disputes. If it's not written down, assume you're not getting it. 2. PAYMENT & PROICE ADJUSTMENT When you pay, and how prices can move later. Net 30 vs net 60 is real cash. Tie any increase to an agreed index, cap it, make it two-way. 3. ACCEPTANCE, INSPECTION & QUALITY The standard it must hit, how you inspect it, and what happens when it fails. Define "good enough to pay for" on paper or argue it after the invoice lands. 4. SERVICE LEVELS Turns "we'll do our best" into a number. Uptime, response time, defect rate, with credits when they miss and an exit trigger if they keep missing. 5 CONTRACT CHANGES/VARIATIONS The clause that actually gets used, because requirements always shift. This sets HOW a change gets requested, priced, and approved before anyone acts on it. Insist on written approval, no verbal "just get it done," and no work starting until the price is agreed. Notice the pattern? None of these are about surviving a courtroom. They're about making sure you never see one. You can learn these 5 the hard way. One painful dispute at a time. Or you can sit in the room where we teach them. On Saturday, 8 August, we run a live virtual session on Commercial Contract Terms and Conditions. The exact clauses above, plus the more dangerous ones underneath them. AND WE'RE GIVING 3 COMPANIES 2 FREE SEATS EACH. No course fee, but this is not a free trial, neither a discount and nor a sales webinar. It's an invitation. To a real session, part of our CIPP certification, already with people attending who have paid for it and taught by a former CPO. Not an academic reading slides. And it is NOT First Come, First Served. We prequalify every team. We're looking for teams, not individuals, where procurement matters to the business and the people you send are senior enough to act on what they learn. Most teams that sit these sessions go on to bring the rest of their function in through paid training later. If yours doesn't, that's fine by us. So, if you'd like your team come to this for free, DM me: → Company name → Who you're sending, names and job titles → One or two lines on why this matters right now Complete requests get reviewed first. Selected teams complete a short confirmation step to lock the seat.

Procurement contract tip nobody teaches in corporate law: Red flags in vendor contracts can cost your company millions, and most teams spot them too late. I learned this the hard way while reviewing a procurement contract during my previous role. A simple clause caught my eye: “The supplier is not liable for any indirect, consequential, or incidental damages.” On the surface, it seemed standard. But when I dug deeper, I realized it could leave the company unprotected if a major delivery failed, causing huge operational losses. Since then, I follow this checklist for every procurement contract: ✅ Watch for one-sided liability clauses ✅ Check hidden automatic renewals ✅ Flag vague service level obligations ✅ Clarify payment terms and penalties ✅ Ensure clear termination rights Contracts aren’t just paperwork, they are the safety net of your business. If your legal team drafts a contract that leaves you guessing, it’s time to revisit your approach. #legalprofessionals #lawyers #lawstudents #law #contractattorney #contractlaw #businesslaw #businessagreement #contractspecialist #contractmanagement What’s the most overlooked red flag you have seen in a procurement contract ? I spent time jotting down, here’s my list. 👇 💾 Save. 💬 Comment. ♻️ Repost.

Boring technical post today (apologies 🫠). We all know that, ideally, our suppliers will hold adequate insurance, and they should indemnify us (the principal) against any loss, damage, or claim arising from their work. Now, being named on a supplier’s insurance policy, or covered under an indemnity to principal clause, gives us much stronger protection. It helps make sure that liability for incidents caused by the supplier sits with their insurer, and not with us. A common mistake I see is assuming that an indemnity alone guarantees insurance coverage. In reality, unless the principal is specifically named on the policy or included under an indemnity to principal clause, that protection might not apply at all (depending on the wording of your contract). So, if this is how your legal department manages risk in your contracts, you absolutely must ensure that your suppliers insurance policies contain these indemnities, otherwise, your well meaning liability cap agreed during negotiations might be all you have to protect yourself. I have been lucky to have worked with a brilliant team of commercial solicitors over the years, and they drilled into me one piece of important advice. When in doubt, ask.

The Procurement Clause You Can’t Afford to Skip in 2025 In a world of: 📈 Volatile commodity prices 🌍 New geopolitical tariffs 💵 Persistent inflation 🚢 Fragile supply chains …procurement teams are constantly managing supplier price increases. But here’s the real question: When those cost drivers fade, do your suppliers reduce prices? If not—you’ve just absorbed one-way risk. That’s where Clawbacks come in. 🔁 Why Clawbacks Matter Now Clawbacks ensure that temporary surcharges or price hikes are reversible when: - Indexes normalize (LME, ICIS, IHS) - Tariffs are rolled back or exempted - Freight surcharges disappear - Inflation cools With clear baselines and reversal clauses, procurement can: - Protect margins - Reinforce transparency - Share risk across the value chain Example: A supplier raises prices citing aluminum costs (LME at $2,800/MT). You accept—**but only** with a clause: “If LME drops below $2,400 for 60 days, pricing resets.” That’s a clawback. That’s margin protection. Bonus Tip: Tie clawbacks to real indices + timelines. Don’t rely on goodwill—rely on contract language. Closing: I’ve posted a full carousel walking through the why and how of clawbacks. If you’re managing resin, metal, packaging, or freight costs—this is for you. 👇 Swipe through it below. Hashtags: #Procurement #SupplyChain #Sourcing #Inflation #Tariffs #CommodityRisk #StrategicSourcing #CPO #Resins #Metals #LME #CostRecovery #ClawbackClause #RiskSharing #SupplyChainResilience