Guide for device owners · Outsourcing production
Contract manufacturing agreement: the clauses to agree before you outsource device production
A contract manufacturing agreement sets out who owns the design, what the factory builds and tests, how quality is accepted, how changes, components and prices are handled, and how the relationship ends. For electronic devices such as network equipment, most disputes start in five places: acceptance testing, ownership of the design and firmware, tooling and test fixtures, component supply, and exit. This page lists the clauses to cover. It is a checklist, not a legal template: have your lawyer draft and review the final agreement.
The documents in a manufacturing relationship
A contract manufacturing agreement rarely stands alone. Each document below does a different job, and keeping them separate makes each easier to update.
| Document | What it settles | When it is signed |
|---|---|---|
| Non-disclosure agreement | What each side may do with the other's confidential information | Before design files and specifications are shared |
| Contract manufacturing agreement | Scope, ownership, pricing mechanics, supply, liability, term and exit | Before the first production order |
| Quality or technical agreement | Specification, test plan, acceptance criteria, first-article approval, change control | With the main agreement, updated as the product changes |
| Forecasts and purchase orders | Quantities, delivery dates and prices for each order | During production |
An "OEM agreement" is often the same thing under another name: the factory builds a product that the owner sells under its own brand.
Clause checklist for a device contract manufacturing agreement
| Clause | What it should settle | Questions to ask |
|---|---|---|
| Parties and scope | Which products, which stages of manufacture, which sites | Is the scope final assembly only, or board assembly too? Can work move to another site? |
| Specifications and documents | Which version of the specification, drawings and bill of materials governs | What happens when documents conflict? |
| Ownership of design, firmware and IP | Who owns the design, the firmware and any improvements made during production | Does anything developed on the line belong to the factory? |
| Confidentiality | Use and protection of design files, firmware and test data | Does it survive the end of the agreement? |
| Tooling, fixtures and test equipment | Who pays for them, who owns them, where they are kept, who maintains them | Can you take them to another factory? |
| Components and approved alternates | Who buys components, which alternates are approved, who carries the risk of shortages | Who decides on a substitute when a part is short? |
| Forecasts, orders and capacity | How forecasts become firm orders, and how much capacity is reserved | What happens if you order above or below forecast? |
| Buffer stock | Whether stock of components or finished units is held, and who pays for it | Who owns excess stock if the programme slows? |
| Testing and acceptance | Which tests run on every unit and which on a sample, the acceptance criteria, first-article approval | Who signs off the first build, and against which document? |
| Certification and type approval | Who holds approvals for the finished device in each market | Does a change of build site or component trigger re-qualification? |
| Change control | How design, component or firmware changes are proposed, approved, priced and re-validated | Can either side make a change without written approval? |
| Pricing and price review | Price basis, currency, and how component cost changes are passed on | How often can prices be reviewed, and on what evidence? |
| Delivery, packaging and labelling | Delivery terms, packaging and labels, and when risk passes | Who meets the labelling rules of the target market? |
| Defects, warranty and field support | How defects are reported, analysed and remedied, and for how long | What counts as a manufacturing defect, as opposed to a design defect? |
| Liability and insurance | Limits of liability and the insurance each side holds | Are some losses excluded? |
| Local content records | Which data each side provides when a buyer or authority asks about local content | Who prepares and keeps the records? |
| Term, termination and exit | Notice periods, and what happens to tooling, fixtures, stock and open orders | Can you place a last order before the agreement ends? |
| Governing law and disputes | Which law applies and how disputes are resolved | Is there a step for escalation or mediation before formal proceedings? |
Clauses that matter more for network devices
- Firmware version control. Name the firmware build that is loaded on each production lot, who supplies it, and who approves a new version before it reaches the line.
- Per-unit tests. For ONT devices, decide what is tested optically on every unit; for 5G CPE, which RF tests run on every unit rather than on a sample. Write the split into the test plan.
- Type approval for the locally built model. Agree who holds the approval and what re-qualification is needed when the build site or a component changes. Settle it before volumes are committed.
- Kits and labelling. For devices sold as kits, such as Mesh Wi-Fi nodes, define what is in each box and how units are labelled and paired.
- Local content records. If your buyers ask about local content, agree which records the factory keeps. Local content is assessed by the authority for a specific product, not declared by either party.
Gaps to check before signing
- The test plan is "to be agreed" with no date or owner.
- Fixtures are paid for by you but not named as yours.
- There is no clause on what happens to stock and fixtures at exit.
- Component substitutions are allowed "as needed" without your approval.
- Price review has no stated trigger or evidence.
- The agreement is silent on who holds type approval for the locally built model.
Questions about contract manufacturing agreements
Is there a template I can download?
This page is a clause checklist, not a template. Agreements differ by product, volume and jurisdiction, so use the checklist to brief your lawyer, who can draft the agreement for your situation.
What is the difference between an OEM agreement and a contract manufacturing agreement?
Usually only the name. Both cover a factory building a product to the owner's design for the owner to sell under its brand. An ODM arrangement is different: the factory's own design becomes the product.
Who should own the test fixtures?
Whoever the agreement says. If you pay for fixtures and want the option to move production, the agreement should name them as yours and say how they are returned.
Should the quality agreement be a separate document?
It is common, because the test plan and acceptance criteria change more often than the commercial terms.
Which law governs the agreement?
The parties choose it in the agreement. Take legal advice in the jurisdiction where the agreement will be enforced.
Planning to outsource production of a network device?
IK Semiconductor (Interkey Semiconductor) assembles network devices in Riyadh under OEM contracts: ONT, 5G CPE and Mesh Wi-Fi, with a 5G MiFi line planned. The work today is at the SKD stage, and board-level assembly (CKD) is planned for 2028. If you are preparing to outsource assembly, we can go through these points for your device. Terms are agreed for each programme.
info@interkey-sc.com.sa · +966-11-2180999 · +966-55-3475469 · Riyadh, Saudi Arabia