How to Verify What a Supplier Can Customise Before Choosing OEM, ODM, or Private Label

A supplier may advertise “OEM/ODM available” without explaining what can actually be changed, who provides the design, or what evidence supports the claim. During pre-sourcing research, your task is not to accept or reject the label. It is to translate it into testable requirements.

This guide helps you plan and complete a distinct supplier-customisation verification task. The objective is to document the proposed starting product or technology, requested changes, responsibilities, approval records, and intellectual-property questions before choosing a sourcing path.

The result should be a completed practical verification checklist for every serious option. It can inform later sourcing decisions, but it should not treat marketing language, product pages, or unsupported assurances as proof.

Turn OEM, ODM, and private label labels into testable requirements

Use the labels as working categories, not as evidence

For this verification task, use these operational distinctions:

• Private label: Start with an existing supplier product and verify permitted changes such as branding, packaging, labelling, colour, or other predefined options.
• OEM: Start with buyer-defined requirements and verify whether the supplier can manufacture and document the specified product or modifications.
• ODM: Start with a supplier-originated design or technology and verify what the buyer may adapt, license, brand, or use.

A supplier’s use of any of these labels does not by itself establish:

• Technical capability.
• Ownership of the underlying design or technology.
• Permission to modify or license third-party intellectual property.
• Ownership of newly created modifications.
• The existence of controlled specifications, drawings, samples, or approval records.

WIPO’s supplier-agreement guidance highlights the importance of distinguishing pre-existing IP from newly created IP and defining ownership, permitted use, and confidentiality before collaboration. Its technology-transfer materials similarly frame technology arrangements around the rights and responsibilities being transferred or licensed—not merely the name given to the relationship. See WIPO’s supplier IP guidance and technology-transfer agreement guidance.

Apply one practical rule: convert every sourcing label into a written list of requested changes, party responsibilities, required rights, and supporting information.

Create three separate verification briefs

Do not send only a broad question such as “Do you offer customisation?” Prepare a short brief for each sourcing path that remains under consideration.

Private label brief

Record the changes you want to make to an existing product:

• Brand name, logo, and placement.
• Packaging format and artwork.
• Labels, instructions, and other buyer-supplied content.
• Required product variations.
• Changes that may fall outside the supplier’s standard offer.
• Documents expected before approval, such as a base specification, option list, artwork proof, approved sample record, or written change confirmation.

The brief should make it possible to distinguish routine branding from requests that require product development, new processes, tooling, or technical redesign.

OEM brief

Record what you expect the supplier to manufacture:

• Buyer-supplied specifications, drawings, formulas, software, processes, or other technical information.
• Supplier-requested changes required for manufacturability.
• Responsibility for reviewing and approving revisions.
• Information that must remain confidential.
• Expected records showing approved requirements and later changes.
• Required rights in buyer-provided information and newly created work.

Identify which requirements are fixed, which may be revised, and who has authority to approve each revision.

ODM brief

Record what you expect to use or adapt from the supplier:

• The supplier’s existing design, platform, process, or technology.
• The elements the supplier says it owns or has authority to provide.
• Proposed modifications.
• Intended branding, use, and relevant markets.
• Continuing dependence on supplier-controlled information or technology.
• Rights needed to manufacture, sell, modify, maintain, or transfer the resulting product.
• Treatment of improvements and newly created intellectual property.

Do not assume that possession of a design establishes ownership or authority to license it. Record the supplier’s explanation and identify what must be reviewed later.

Build one comparison matrix before contacting suppliers

Verification question	Private label focus	OEM focus	ODM focus
What already exists?	Supplier’s base product and standard options	Buyer requirements and supplier manufacturing inputs	Supplier’s existing design or technology
What will change?	Branding, packaging, labels, or selected options	Product or process according to buyer-defined requirements	Supplier design, features, appearance, or technology
Who supplies the key information?	Supplier product information plus buyer brand assets	Primarily buyer technical requirements, with supplier production input	Primarily supplier design or technology, with buyer adaptation requirements
What must be documented?	Base product, selected options, artwork, and final configuration	Requirements, revisions, approvals, process information, and results	Design baseline, authorised changes, rights, revisions, and approvals
What IP question comes first?	May the supplier use the buyer’s brand assets for the selected product?	How will buyer-provided IP and newly created work be protected and allocated?	Does the supplier own or control the rights it proposes to provide?
What is not proven by the label?	That every requested variation is available	That every buyer-defined change can be manufactured	That the supplier owns the design or can grant all required rights

Run the practical verification checklist

Set the verification standard

Treat a supplier statement as unverified until it is connected to appropriate documented information. A brochure or email may record what was claimed, but it does not automatically prove ownership, capability, or achieved results.

ISO’s guidance explains that documented information may be maintained to support process operation or retained as evidence of results. It also notes that the appropriate amount of documentation can vary with factors such as organisational size, process complexity, and personnel competence. Accordingly, request information that is relevant to the claim rather than demanding paperwork for volume alone. Do not assume that every useful record must use a particular file type or medium. See the ISO guidance on documented information.

Keep four questions separate throughout the review:

1. What does the supplier claim?
2. What documented information supports that claim?
3. What must be clarified in a later agreement?
4. What remains outside the available evidence?

Practical verification checklist

Copy this table into your working file and complete one version for each serious sourcing-path option.

Check	Question to put to the supplier	Documented information to request or review	Pass condition for pre-sourcing research	Follow-up if unclear
Path definition	What does “private label,” “OEM,” or “ODM” mean for this product?	Written description of the proposed supply model	Actual work and responsibilities are described instead of merely repeating a label	Request a step-by-step division of buyer and supplier inputs
Existing baseline	What product, design, technology, specification, or process exists before customisation?	Baseline specification, drawing, option list, or another controlled description	The starting point is identifiable and distinguishable from proposed changes	Keep the path unverified until the baseline is defined
Customisable elements	Which exact features can be changed?	Written option list or marked specification showing fixed and changeable elements	Every requested change is classified as available, subject to review, or unavailable	Ask who reviews and approves non-standard changes
Change boundaries	Which changes require design, engineering, tooling, new processes, or external rights?	Written change assessment or revision note	Routine configuration is distinguished from development work	Reclassify the request if it crosses into another sourcing path
Responsibility allocation	Who supplies each specification, drawing, design, artwork, process, and approval?	Responsibility matrix or equivalent written allocation	Every material input and approval has an assigned party	Do not accept shared or undefined responsibility
Document control	How are specifications, drawings, artwork, and revisions identified and approved?	Example identifiers, revision history, approval workflow, or equivalent records	The current approved version can be distinguished from obsolete versions	Request a proposed revision and approval method
Evidence of results	What records would show that approved requirements were achieved?	Proposed inspection, review, test, or approval records relevant to the request	Expected evidence is identified before commitment	Record the gap rather than inferring performance
Buyer-provided IP	How will buyer designs, brand assets, know-how, or confidential information be used and protected?	Proposed confidentiality and permitted-use terms	Intended use can be limited and addressed in a later agreement	Escalate for qualified IP or legal review
Supplier background IP	What existing IP is embedded in or required for the proposed product?	Written identification of supplier-controlled technology or other relevant rights	Supplier inputs are separated from buyer inputs and new work	Ask whether third parties own or control relevant rights
Authority to provide rights	On what basis can the supplier manufacture, adapt, or license the design or technology?	Ownership statement, licence explanation, or other relevant rights information	The claimed basis of authority is identified rather than assumed	Treat the ODM or licensed-technology path as unresolved
Newly created IP	Who would own or be licensed to use modifications, improvements, drawings, or other project outputs?	Proposed IP allocation or agreement language	Ownership or licence expectations are raised before development begins	Pause sensitive disclosure or development planning pending review
Scope of permission	What may each party manufacture, use, modify, disclose, or commercialise?	Proposed licence or permitted-use terms	Required uses are explicit enough to support later agreement drafting	Identify missing permissions, restrictions, or dependencies
Confidentiality	Which technical and commercial information must remain confidential?	Proposed confidentiality terms and handling expectations	Protected information and permitted recipients or uses can be defined	Limit disclosure until suitable terms are considered
Third-party involvement	Will subcontractors or other parties receive buyer information or contribute technology?	Written description of relevant third-party roles	Roles and information access are disclosed for later contractual treatment	Ask how obligations and rights would extend to those parties
Improvements	How will later technical improvements be reported, owned, or licensed?	Proposed treatment of improvements	Original technology can be distinguished from later developments	Flag the issue for agreement review
Final configuration	What document will define the exact approved product?	Proposed final specification, requirements list, artwork approval, or equivalent	An authoritative description of the supplied product is planned	Do not approve solely from messages or product-page descriptions
Change after approval	How will post-approval substitutions or modifications be proposed and authorised?	Change-control procedure or written approval method	Changes require defined communication and approval	Add a formal change requirement to later negotiations
Unresolved assumptions	Which answers depend on testing, development, third-party approval, or future contract terms?	Open-issues register	Unverified points are visible and assigned a next action	Do not convert assumptions into capability claims

Record each result consistently

Assign one status to every checklist line:

• Verified for pre-sourcing: Relevant documented information has been reviewed and supports moving to the next research step.
• Conditionally verified: The claim appears supportable but depends on a stated condition, later review, or defined agreement.
• Unverified: The supplier has made a claim without sufficient supporting information.
• Not applicable: The check does not apply to the proposed path; record why.

Add the following fields to your working record:

Record field	Entry
Supplier’s exact statement
Document or record reviewed
Document identifier or revision
Date reviewed
Checklist status
Open question
Responsible follow-up party
Decision impact	Private label / OEM / ODM / no path selected

Recording the exact statement matters. “We can change the packaging” is narrower than “we can alter the product,” while “we own the design” is different from “we are authorised to manufacture it.” Do not silently broaden the supplier’s words.

Interpret the completed checklist

Private label remains plausible when the supplier can identify an existing product baseline, permitted branding or configuration options, controlled artwork or specification approvals, and appropriate handling of buyer brand assets.

OEM remains plausible when buyer requirements can be translated into controlled documents, responsibilities and revisions are defined, evidence of results is planned, and the treatment of buyer-provided and newly created IP can be addressed.

ODM remains plausible when the supplier identifies its existing design or technology, explains its claimed authority to provide the required rights, separates background IP from modifications, and can define the buyer’s intended permissions.

Do not select a path yet when:

• The baseline product, design, or technology is unclear.
• Rights are assumed rather than identified.
• Customisation boundaries are undocumented.
• Material responsibilities remain shared or undefined.
• No method exists for controlling specifications, approvals, and changes.
• Future testing or contract terms are being presented as present capability.

Scope and limits

This guide supports pre-sourcing research and the planning of a supplier-customisation verification task. It does not verify a particular supplier, product, process, design, technology, or intellectual-property claim.

The checklist does not establish that a supplier can satisfy technical, regulatory, quality, delivery, or commercial requirements. A document may support a claim without independently proving ownership, compliance, technical capability, or successful production.

ISO guidance supports decisions about maintaining information for process operation and retaining evidence of results, but it does not prescribe a supplier-specific OEM, ODM, or private label checklist. The terms used here are practical working categories and should always be translated into specific responsibilities, deliverables, rights, and records.

WIPO materials identify issues relevant to supplier IP and technology-transfer arrangements, but this article is not legal advice. It does not replace agreement drafting or review by qualified professionals. The checklist should record both the evidence available and the uncertainty that remains.

Image credit

Workers in an industrial textile manufacturing facility. Photo by EqualStock on Unsplash, used under the Unsplash License.

Sources

• WIPO — IP Agreements with Suppliers: What Ventures Need to Know
  Supplier-agreement considerations involving pre-existing and newly created intellectual property, ownership, permitted use, and confidentiality.

• WIPO — Technology-Transfer Agreements
  Technology-related questions concerning licensing or transfer, scope of rights, responsibilities, and agreement planning.

• ISO — Guidance on the Requirements for Documented Information of ISO 9001:2015
  Guidance on documented information used to support process operation and records retained as evidence of results.

Final next move

Complete a separate checklist for every serious private label, OEM, or ODM option. Then prepare a one-page comparison covering:

• Verified customisable elements.
• Fixed elements.
• Buyer and supplier inputs.
• Required documented information.
• Background and newly created IP questions.
• Conditional or unverified claims.
• Open contractual issues.

Choose the path with the clearest documented fit—not the broadest marketing claim. Carry unresolved confidentiality, ownership, licensing, improvement, and third-party-rights questions into qualified IP or legal review before disclosing sensitive information or committing to development.