Before committing to a JDM eyewear project, put four things side by side: what you are paying for, which files or assets you will receive, how each party may use them, and what any exclusivity covers. A development quotation needs to address each of those questions separately.
At Quick Wonder, each party retains its pre-existing intellectual property. Rights relating to newly developed designs, tooling, process applications and exclusivity are agreed for the individual project. JDM itself does not include automatic exclusivity over our core technology, general structures or process platforms.
For a U.S. eyewear brand, these questions are best reviewed by the product and sourcing teams before development begins. List the concept drawings, engineering files, physical tooling and any requested exclusivity separately, then confirm the deliverables and rights associated with each. This guide outlines the commercial points to discuss; it does not provide legal advice. Ownership, usage rights and exclusivity should be confirmed in your written project agreement.
Start With the Assets Each Party Brings
The first question is what already exists when the project starts.
Our OEM, ODM and JDM capabilities begin from different inputs. OEM starts with the customer's complete design and technical specification. ODM starts from an existing Quick Wonder design or product concept. JDM begins with a jointly defined brief and can involve trend research, design, process development, engineering and prototype iteration.
Those starting points help identify three groups of assets:
For example, a brand may want a distinctive frame front developed around an existing construction platform. The discussion should identify the new front design and the existing platform separately, then define the rights requested for each. This is an illustrative project situation, not a completed Quick Wonder case.
If your team is still choosing its development route, our design-to-production manufacturer guide explains the different starting points. For a JDM agreement, the next task is to identify the assets within that route.
Define the Deliverables Beyond “Design Service”
Quick Wonder's JDM scope may include trend direction, a project brief, concept drawings, color/material/finish direction, structural proposals, process research, cost and feasibility assessment, engineering drawings and a bill of materials, prototypes, approval samples and production standards. The deliverables vary by contract. For JDM programs with stable demand, defined quality standards and an ongoing purchasing plan, Quick Wonder may also evaluate a dedicated production line or reserved-capacity arrangement. This is an optional scale-up arrangement. Investment responsibilities, minimum purchase commitments, capacity allocation and idle-capacity risk must be agreed separately in writing.
Turn the agreed scope into a deliverable list. For each item, specify:
If editable CAD files matter to your sourcing strategy, request them explicitly. Ask which files and formats can be included, when they would be delivered, and whether your intended use includes modification or disclosure to another manufacturer. These are points to negotiate for the project, rather than a standard file-release promise.
A production-approved drawing can establish the manufacturing version, as discussed in our guide to evaluating development, sampling and production controls. Separately, the commercial documents need to state the agreed ownership and usage rights for that drawing. Keeping both records clear helps the product team approve the frame while the sourcing team confirms its future options.
Match Each Fee to Its Scope and Deliverables
Quick Wonder quotes JDM work according to the design, R&D and exclusivity scope. Sample quantities, fees, tooling, revisions and possible order credits are project-specific.
When reviewing a quotation, ask for the scope behind each charge:
Record the rights alongside the corresponding fee. A line labeled “development” or “tooling” should be accompanied by the agreed deliverables and rights, so the buyer does not have to infer them from the invoice description.
If your team requests a design buyout, broader territory or additional file access, include that request in the initial scope review. It needs to be evaluated and documented with the rest of the project requirements.
Give Tooling Its Own Set of Decisions
“Who owns the mold?” is a useful starting question. A workable tooling discussion also addresses who holds it, who may use it and what happens when the program changes.
Identify the proposed tool by the relevant product or component and drawing version. Then ask the parties to agree on:
These are discussion fields for your agreement, not a statement of Quick Wonder's standard storage, maintenance or transfer policy. Specific tooling arrangements are agreed per project.
Keep the physical tool and the associated design or engineering files as separate entries. If your business plan depends on moving production later, discuss both the requested tooling arrangements and the file-use permissions needed for that plan before committing to development.
Define What “Exclusive” Protects
When discussing exclusivity for a JDM project with Quick Wonder, points to consider may include the product or design covered, territory, sales channels, duration, purchasing commitments, confidentiality, and what happens when the arrangement ends. The scope and conditions are subject to written agreement for the individual project.
Use the following questions to prepare for that discussion:
The tradeoff should be visible to both teams: how much product and market protection the brand requests, and what purchasing commitment it is prepared to discuss. A forecast can inform that conversation; the agreement needs to identify the commitment actually accepted. For the wider purchasing context, our guide to supplier selection for growing DTC eyewear brands covers SKU expansion, repeat orders and total project cost.
If the practical question is “Can the same design be sold to another customer?”, put that question against the exact design, territory, channel and period in the proposed agreement. The JDM label alone does not answer it.
Use One Rights-Confirmation Matrix
Use the following worksheet to prepare a project discussion. Its questions are proposed review fields, not pre-agreed rights or contract clauses. Split a row whenever two assets require different treatment.
Asset or output | Deliverable or record to identify | Fee or cost scope to clarify | Ownership, use or exclusivity to agree |
Customer-supplied design and brand assets | Supplied files, versions and authorized references | Any agreed adaptation work | Customer's existing rights; permitted project use and handling of supplied materials |
Existing Quick Wonder platform | Selected design, structure or process platform | Customization and engineering scope | Background assets retained by Quick Wonder; scope available to the project |
New design and engineering outputs | Named drawings, BOM, versions and agreed file formats | Design, engineering and revision work | Ownership, delivery, modification, reuse and any requested third-party access |
Project tooling | Tool or mold identity and related component/version | Manufacture, modification and any agreed upkeep or transfer costs | Physical ownership, custody, authorized use and agreed end-of-program handling |
Samples and production standard | Sample purpose, approval record and governing specifications | Sample rounds, revisions and any agreed credits | Items supplied or retained; agreed use of the associated documentation |
Exclusive product or design | Exact protected scope and a record of agreed conditions | Exclusivity scope and purchase commitment | Product, territory, channel, term, confidentiality, renewal and lapse/termination conditions |
For your working copy, add a status, decision owner and document reference to each row. Mark unresolved items as open. That gives both sides a specific issue to resolve instead of a general request to “confirm IP.”
Recheck the Matrix When the Project Changes
At Quick Wonder, customers confirm the ownership of their inputs and the rights they require. Our responsibility is to identify pre-existing Quick Wonder assets and document the agreed rights for new outputs, tooling and exclusivity.
Customers submit post-approval changes in writing. We assess their effects on cost, MOQ, quality, samples, materials and timing. Where a change introduces a new component, drawing or tool, add that item to the rights discussion as well.
For example, if a later collection adds a revised temple to the original frame, identify the new drawing and tooling, then confirm whether the existing commercial terms cover them. This is an illustrative review step, not a claim about an actual project or an automatic extension of exclusivity.
Before a program ends, revisit any open file-delivery, tooling, continuing-use and confidentiality questions. Quick Wonder's allocation of purchased materials, completed work, tooling and non-cancellable external charges follows the project contract; there is no universal cancellation arrangement to insert in place of those terms.
Bring Your Intended Use to the Project Review
For a focused discussion with Quick Wonder, prepare your product brief, current design files or authorized references, target market and channels, expected purchasing plan, and a list of the deliverables and rights your business needs.
Be specific about future use. If you need editable engineering files, protection for a defined market, or the option to discuss a later tooling transfer, raise those requirements at the start. They belong in the scope, quotation and written project discussion.
Request a JDM project review from Quick Wonder with your brief and completed rights-confirmation worksheet, so the development work, deliverables and requested commercial conditions can be reviewed together.