Supplier agreement – what should a B2B Supplier Agreement contain?
Guide to B2B supplier agreements: orders, forecasts, price, delivery, quality, GPSR, subcontractors, continuity, liability, insurance, and exit.
A supplier agreement should do more than state what is to be purchased and at what price. For an ongoing B2B partnership, the agreement needs to create a clear model for forecasts, orders, delivery, quality, changes, complaints, product requirements, information security, liability, and what happens when the partnership ends.
For editable documents to support this work, see our procurement, supplier and service templates.
12 questions a supplier agreement should answer
- Which products or components are covered?
- How are orders placed and accepted?
- Are forecasts binding or merely planning documents?
- What prices, currencies, and price adjustment mechanisms apply?
- When and where does delivery and transfer of risk take place?
- What quality and documentation requirements apply?
- How are deviations, warranty, RMA, and recalls handled?
- Is the supplier allowed to engage subcontractors?
- What requirements apply to continuity and capacity?
- How is confidential information, data, and IP protected?
- How is liability limited and what insurance is required?
- How is the partnership terminated and handed over?
The Sale of Goods Act and freedom of contract between companies
When purchasing personal property between companies, the Sale of Goods Act (Köplagen) is often an important background rule. The Sale of Goods Act is dispositive, meaning that its provisions do not apply to the extent that otherwise follows from the agreement, established practice between the parties, or binding trade usage. This makes the supplier agreement particularly significant: unclear or missing clauses may mean that the act's standard rules carry more weight than the parties intended.
Framework agreements, orders, and forecasts
A common setup is for the supplier agreement to act as a framework agreement, while individual purchases arise through orders. The agreement should then describe when an order becomes binding, how quickly the supplier must confirm it, which documents take precedence in the event of a conflict, and whether forecasts imply purchase commitments or are used solely for capacity planning.
| Area | Examples of contractual issues |
|---|---|
| Price | Fixed price, index, raw material surcharges, currency, renegotiation, and invoicing. |
| Delivery | Lead time, place of delivery, Incoterms if used, delivery precision, and delay. |
| Quality | Specification, testing, approval, traceability, and deviation management. |
| Capacity | Forecasts, reserved capacity, safety stock, and escalation. |
| Changes | Change control for product, process, material, subcontractor, or manufacturing site. |
| Exit | Final order, stock, tools, data, documentation, and transition support. |
Quality, warranty, and deviation management
The agreement should state how it is determined whether a delivery is contractually compliant. For technical products, this may require drawings, specifications, inspection plans, certificates, or testing requirements. Also regulate the complaints process, root cause analysis, corrective actions, replacement delivery, sorting, and cost liability.
If the parties use RMA processes or special quality portals, the agreement should explain how they relate to the legal rights and what documentation is required.
Product compliance and GPSR
For products covered by the EU's General Product Safety Regulation, GPSR (EU) 2023/988, the supplier agreement may need to allocate responsibility for, for example, product information, traceability, documentation, safety-related incidents, and recalls. GPSR has been applied since December 13, 2024. The exact obligations that apply depend on the product, the role in the supply chain, and any special legislation.
Subcontractors and change control
A supplier may be dependent on a long chain of subcontractors. Therefore, the buyer should take a position on whether certain subcontractors or production locations must be approved in advance and which changes must be notified. This applies in particular to changes that may affect quality, certification, delivery time, or regulatory compliance.
Continuity and supply-chain risk
A modern supplier agreement should describe what happens in the event of capacity shortages, component shortages, cyber incidents, fire, transport disruption, or other events that affect delivery. For critical supplies, it may be relevant to have a continuity plan, alternative production routes, safety stock, recovery times, and an obligation to escalate disruptions early.
Information security, GDPR, and confidentiality
If the supplier is given access to personal data or sensitive business information, the agreement needs to be supplemented with appropriate data protection and security terms. If the supplier processes personal data on behalf of the customer, a separate data processing agreement under the GDPR is normally required. Cybersecurity requirements should be adapted according to risk, system access, and the nature of the parties' operations.
Liability and insurance
Limitation of liability should be designed in conjunction with the actual risks. A general liability cap may need to be supplemented with exceptions or specific rules for, for example, breach of confidentiality, intellectual property infringement, product liability, or costs associated with recalls. The agreement should also state which insurance policies the supplier must maintain and whether proof of insurance can be requested.
Common mistakes in supplier agreements
- Forecasts are unclear. The parties do not know what constitutes a binding purchase volume.
- Price adjustment lacks mechanics. "Price may be renegotiated" does not say when, how, or on what grounds.
- No change control. Critical material or process changes are made without the customer's knowledge.
- The liability clause does not match the risk profile. The limitation may become too broad or create unexpected gaps.
- Exit is forgotten. Stock, tools, data, and documentation only become points of conflict when the agreement ends.
Frequently asked questions about supplier agreements
Is a supplier agreement the same as an individual purchase agreement?
Not necessarily. A supplier agreement often serves as a framework for many future orders and therefore also regulates processes, quality, and the ongoing management of the relationship.
Must forecasts be binding?
No. The parties can agree that forecasts are binding, partially binding, or merely planning documents. The important thing is that the agreement states which.
Should Incoterms be specified?
If the parties wish to use Incoterms, the chosen rule, the version, and the relevant location should be stated clearly so that the allocation of delivery, costs, and risk becomes understandable.
Is a separate data processing agreement needed?
If the supplier processes personal data on behalf of the customer, such an agreement is normally required in addition to the commercial terms of delivery.
Does GPSR apply to all products?
No. The regulation has a broad scope of application but contains exceptions and interacts with product-specific EU legislation. Check which rules apply to the product in question.
Template for Supplier Agreement
The Mallbutiken agreement template is intended for ongoing B2B deliveries and is available in Swedish and English versions with a structure for commercial, operational, and legal terms.
Read also
- NIS2 and supplier agreements – what cybersecurity requirements should be agreed upon?
- Continuity plan – what should it contain and how is it developed?
- Data processing agreement – when is it needed and what should be included?
Sources
- Sale of Goods Act (1990:931) – The Swedish Parliament
- Regulation (EU) 2023/988 on general product safety – EUR-Lex
Last updated: October 4, 2026. The article provides general information and does not replace individual legal advice.
Templates in this article
Explore the topic
Business guides – contracts, HR, AI & complianceNIS2 and supplier agreements – which cybersecurity requirements should be agreed upon?
How NIS2-affected organizations can agree on supplier security: incidents, subcontractors, access, vulnerabilities, continuity, monitoring, and exit.
Business guides – contracts, HR, AI & complianceContinuity plan – what should it contain and how is it developed?
A business continuity plan describes how critical operations should continue or be restored in the event of disruptions. See what the plan should i...
Business guides – contracts, HR, AI & complianceData Processing Agreement – when is it needed and what should it include?
Determine whether a supplier is a data processor and what the data processing agreement needs to regulate. Practical examples, appendices, and chec...



