Short answer: Before production, agree in writing which product revision is being made, which requirements and markets apply, who owns each quality decision, how acceptance is determined, how defects and changes are handled, and which records must be retained. A useful OEM/ODM quality agreement connects the approved product baseline to the people, evidence and decisions that govern production.
This guide is for brand owners, importers and product teams moving from supplier selection into product development or repeat production. It answers a different question from a supplier scorecard: once the parties decide to work together, how will they make, inspect, release and change the agreed product? The agreement may be a separate document or a controlled section of a broader contract, provided the documents are consistent and traceable.
Start with a shared product baseline
Identify exact products and approved variants. Reference model numbers, drawings, bills of materials, critical component requirements, software or control versions where relevant, packaging artwork and revision dates. State which files are authoritative and how superseded files are marked. For a product family, define which requirements are common and which are model-specific.
Name the destination markets and the party responsible for identifying, obtaining, reviewing and keeping current applicable technical and market evidence. Avoid generic statements such as “all certificates included.” Tie each required report, declaration, label or test record to the model, configuration and market it actually covers.
Make ownership and acceptance measurable
| Agreement area | What to define | Buyer question |
|---|---|---|
| Quality responsibilities | Named roles for supplier controls, buyer approvals, document review and shipment release. | Who can approve a deviation or stop a shipment? |
| Inspection and testing | Product characteristics, method, sample selection, frequency, pass/fail rules and who pays for agreed checks. | Can both sides reproduce the acceptance decision from the same record? |
| Evidence package | Required test reports, inspection results, traceability details and file formats for each product or order. | Which evidence is needed before production, shipment or market release? |
| Nonconformance | Containment, notification, investigation, corrective action, disposition and approval authority. | What happens when a lot, component or document does not meet the agreed requirement? |
| Change control | How requests are submitted, impact is assessed, files are updated and written approval is recorded. | Which changes must be approved before use or shipment? |
| Records and traceability | Lot or batch links, revision history, retention period, access rights and record retrieval contact. | Can a delivered unit be traced to its approved configuration? |
Acceptance criteria should be specific to the product and intended use. If a sampling plan, defect classification, test method or independent inspection is agreed, identify the exact version and how disputed results are resolved. Do not rely on an undefined phrase such as “industry standard quality.”
Define the change and escalation route
Require a written request for proposed changes to components, materials, production location, process, software, packaging, markings or test methods when they could affect the agreed product. Ask for the reason, affected models and lots, risk or performance impact, market-document impact, proposed validation and effective date. State which authorized buyer representative must approve before implementation.
For a nonconformance, define the notification timing, how potentially affected inventory is identified, who decides rework or other disposition, what root-cause evidence is expected, and how corrective actions are verified. Use escalation levels and timeframes the actual teams can meet.
Keep the agreement usable across a programme
- Assign an owner on each side for the agreement and controlled product records.
- Link model, revision, market, test evidence and order in a document index.
- Review the agreement when product scope, supplier process or market changes.
- Record exceptions with an expiry or closure date instead of leaving them as informal email decisions.
- Make the order, specification, quality agreement and approved artwork refer to one baseline.
ISO’s public guidance describes defining and controlling processes according to intended outcomes and context; its documented-information guidance also recognizes that documentation needs vary. Tailor controls to the actual product and programme instead of copying a generic agreement unchanged. See ISO’s quality-management overview and have legal and technical teams review contractual wording for the relevant jurisdictions.
For supplier selection, read the OEM/ODM partner evaluation guide. For governance after the first order, see the quarterly programme review framework. To discuss a manufacturing brief, visit Partnerships.
Frequently asked questions
What should an OEM/ODM quality agreement include?
Define the product and approved revision, market scope, quality responsibilities, inspection and release criteria, nonconformance handling, change approvals, traceability and record control.
Is a purchase order enough to control product quality?
A purchase order may cover price, quantity and delivery but not the product baseline, evidence ownership, inspection method or change process. Link the documents and make their precedence clear.
Does ISO 9001 require a separate supplier quality agreement?
Do not assume a separate document is universally required. ISO describes process-based quality management and documented information determined by an organization’s needs. Agree controls and records appropriate to the product, risk and contract.
Who approves a product or component change?
Name authorized buyer and supplier roles, required impact information and the point at which written approval is needed before implementation or shipment.
This article is an operational checklist, not legal advice, a certification claim or a guarantee of product conformity. Confirm contractual terms, applicable regulations and product-specific acceptance criteria with qualified legal, engineering and compliance teams.