GATE 01
REVIEW POINTBrief and design direction
Evidence to examine
Requirements, intended use, proposed solution and unresolved assumptions.
Customer decision
Confirm priorities, scope and the direction to develop.
BUILDING A NEW PRODUCT
New Product Development
New product development creates a new product from requirements through concept, engineering, prototypes and mass-production release.
Xinyinhai’s ODM product development route starts with the problem, intended user and functions you need. We review feasibility, develop the agreed plastic and electronic design, and use samples and stage reviews to prepare it for tooling and manufacturing.
DEFINE THE PRODUCT
A useful brief explains the experience the product must deliver
Technical choices follow the purpose, users and conditions of use.
Intended userWho handles the product?
Use conditionsWhere and how is it used?
Core functionsWhat must it do?
Describe what the user should be able to do, how the product will be handled and where it will be used. Identify essential functions, size or handling constraints, appearance expectations and packaging needs. Separate confirmed requirements from ideas that need investigation.
For an electronic product, explain the expected interaction and power arrangement as far as they are known. Sound, light, buttons, movement or sensing each introduce design and test considerations. More complex connectivity or software needs a separately defined scope and responsibility.
Feasibility review identifies practical constraints, information gaps and the next evidence needed. If an existing design already meets the core need, Product Adaptation may provide a more suitable starting point.
PLAN THE PROGRESSION
New Product Development Stages
The scope determines which stages apply and what evidence is needed to move forward.
THE DEVELOPMENT ROUTE AT A GLANCE
- 01
Idea
- 02
Requirements
- 03
Concept
- 04
Engineering
- 05
Prototype
- 06
Tooling
- 07
Validation
- 08
Pilot run
- 09
Mass production
STAGE REVIEWSWork to completeDecision before progressing
- 01
Requirements and feasibility
Define users, use conditions, essential functions and acceptance needs. Assess the proposed approach, key parts, risks and open questions.
Review decisionAgree the brief and the work needed to resolve uncertainty.
- 02
Concept and engineering
Develop the selected direction into mechanical and applicable electronic design. Review interfaces, materials, assembly and the information needed for a sample.
Review decisionReview the concept and drawings before the next build.
- 03
Prototype and DFM
Use prototypes to examine form, fit and function. Review design for manufacture and assembly, including molded features, joining, inspection access and production testing.
Review decisionConfirm corrections and the design proposed for tooling.
- 04
Tooling and trial builds
Prepare the agreed tools and components. Evaluate tool-made samples for dimensions, appearance, assembly and function, then review corrections and repeat trials where needed.
Review decisionApprove the trial results and design-release information.
- 05
Pilot production (PP)
Run the planned production process with the applicable materials, instructions, fixtures and checks. Review defects, process readiness, packaging and unresolved trial issues.
Review decisionClose release issues and confirm readiness for volume production.
- 06
Mass production (MP)
Release production against the approved specification and sample. Apply the agreed incoming, process and finished-product controls, with shipment review and issue feedback.
Review decisionConfirm the required release evidence and delivery arrangements.
Development is iterative. Prototype results can change the design, and tooling trials can lead to further corrections. The number of builds and approval points is agreed around the product's risks and remaining questions.
MAKE THE NEXT DECISION
Reviews connect design evidence with customer approval
Each gate should make the current revision and outstanding actions clear.
GATE 02
REVIEW POINTPrototype and tooling decision
Evidence to examine
Sample findings, revised drawings, DFM recommendations and testing needs.
Customer decision
Approve the design basis and authorized tooling work.
GATE 03
REVIEW POINTDesign and pilot review
Evidence to examine
Trial results, approved materials, key dimensions, process checks and open issues.
Customer decision
Agree the production baseline and release conditions.
A review record identifies the version, findings, action owners and decision. Consolidated feedback helps engineering resolve the same requirement consistently across appearance, mechanics, electronics and packaging.
After design approval, changes are assessed against that baseline. We confirm effects on samples, tooling, validation, cost and timing before carrying the revision into the next stage.
Document the evidence behind the decision
Xinyinhai’s documented design procedure connects the product specification, stage reviews, sample tests and pilot findings. The project plan identifies which records apply to the agreed development scope.
A prototype demonstrates the characteristics it was built to evaluate. A generic check sheet describes a method; project-specific findings and recorded decisions establish what was reviewed and accepted.
PREPARE FOR MANUFACTURING
Production Readiness & Engineering Handover
An approved prototype is one part of the evidence for production readiness.
PRODUCTION RELEASE REVIEW
Safety and reliability requirements depend on the product, users and intended markets. The project plan identifies the applicable checks and any external testing or specialist work needed. The release decision uses those agreed requirements.
See the tooling and injection molding process for preparation, trials and repeat-production controls.
The release package uses controlled versions of the bill of materials (BOM), technical drawings (DWG), operating instructions (SOP) and inspection instructions (SIP), as applicable. Document control distributes approved revisions and withdraws obsolete internal copies. See Xinyinhai’s quality management system for the controls connecting engineering records with production.
PROJECT OUTPUTS
What you receive
Agree the applicable deliverables, their revision and approval owner in the project scope. The output must support the next decision.
Confirm the scope and acceptance criteria before authorizing the next stage.
An agreed brief, feasibility findings and development scope with review points.
Concept and engineering information appropriate to the authorized stage.
Prototype or sample findings, issue records and the agreed validation evidence.
Approved design and production information for tooling, pilot work and manufacturing handover.
BUYER QUESTIONS
Common questions about new development
Start with your current product information and the decision you need to make.
Can I start with an idea rather than a drawing?
Yes. Explain the intended user, problem, use scenario and essential functions. References or sketches help. The first task is to clarify requirements and feasibility so the proposed development scope has a useful starting point.
What does a prototype prove?
That depends on how it is made and what it is intended to test. A form model, functional prototype and tool-made sample answer different questions. We agree the purpose of each sample and record differences from the planned production version.
When is the design ready for tooling?
The relevant design, prototype findings, manufacturing considerations and product requirements must be reviewed. Open risks and required corrections are identified, and the customer confirms the applicable design and tooling scope before tool work is authorized.
Can development include electronic functions?
The review can include mechanical and electronic integration, power, controls and production testing. Connected features, displays, apps or complex software require individual assessment. Any specialist development and responsibility for it must be agreed in the project scope.
How are development timing and cost established?
They depend on design maturity, technical uncertainty, sample iterations, tooling, testing and the production plan. The proposal defines stages and assumptions. A changed requirement is assessed for its effect on the remaining work, cost and schedule.
Which technical files do I receive?
The agreement identifies the deliverables, file formats, revision status, usage rights and ownership arrangements. Relevant outputs may include drawings, BOM information, sample findings and production documentation. Confirm native design files or software deliverables explicitly when they are required.
How are document revisions controlled during development?
Xinyinhai’s documented procedure requires review and approval of applicable engineering documents before controlled distribution. The release package can include the BOM, technical drawings, operating instructions and inspection instructions. Changes are recorded and assessed, updated information reaches the relevant teams, and obsolete internal copies are withdrawn. The project scope identifies the records and customer approvals required at each stage.
YOUR NEXT STEP
Discuss a New Product Idea
Share the idea and the decision you need help making. Early information can be incomplete; identify assumptions and essential requirements so we can define the next useful development step.
Use the inquiry form to prepare your brief, or share it through your existing project contact. Agree a confidential exchange before sending restricted drawings, code or customer information. Downloading a brief does not submit a project.
What we need from you
- The product purpose, intended users and use scenario.
- Essential functions, appearance references, sketches or available samples.
- Intended markets, use conditions and known safety or test requirements.
- Expected quantities, budget expectations and launch priorities.
- Available brand or design assets, rights to use them and desired deliverables.