Define, prioritize and approve
Requirements · authorized inputs · consolidated feedback · acceptance decisions
ODM & OEM / INPUTS, REVIEWS & SHARED DECISIONS
Project Reviews & Production Approvals
Project reviews connect agreed inputs, reviewable deliverables and recorded approvals at each relevant development or production stage.
The starting point determines the work. Branding a base product needs different reviews from creating a new product or transferring a finished design into manufacturing. Both sides agree the scope, acceptance criteria and decisions that authorize the next stage.
01 / CHOOSE THE RIGHT START
Begin with what you already have
The first review identifies the work that is necessary and the evidence needed to make the next decision.
Base productCustomizationExisting designProduct adaptationNew requirementProduct developmentReleased designOEM manufacturing
| Your starting point | What to bring | First decision |
|---|---|---|
| A current product to brand | The base product reference, authorized artwork and required colors, finishes or packaging. | Is the base suitable, available for authorized customization and compatible with the proposed changes? |
| An existing product to improve | Current drawings or samples, known problems and a clear list of requested changes. | Which changes need engineering, tooling revisions and renewed verification? |
| A new product idea | The user, use case, essential functions, market and commercial constraints. | Can a feasible product requirement and development scope be defined? |
| A production-ready design | Released drawings, BOM, specifications, samples and tooling information. | Is the package complete and suitable for manufacturing transfer? |
On smaller screens, scroll the table to see every column.
The written scope identifies included work, deliverables, acceptance criteria and dependencies. Prototype, tooling, testing and production requirements are made explicit when applicable. Commercial terms and any specialist work are confirmed for the project.
02 / STAGE INPUTS & OUTPUTS
Project Review Gates & Stage Approvals
Your project plan identifies the drawing, prototype, trial, pilot and production reviews that apply. Each review establishes the evidence and decisions needed for the next stage.
- 01
Inquiry
Share your starting point.
- 02
Requirement review
Clarify use, scope and rights.
- 03
Feasibility
Review risks and dependencies.
- 04
Quotation
Agree scope and commercial terms.
- 05
Sample / prototype
Evaluate the relevant product revision.
- 06
Confirmation
Record the approved baseline.
- 07
Tooling / preparation
Prepare tools, materials and instructions.
- 08
Pilot run / PP
Check the intended production process.
- 09
Mass production / MP
Work to the authorized release package.
- 10
QC & delivery
Record final checks and shipment release.
The route is agreed for your project. The review gates below define what each decision needs.
| Review | What is evaluated | Output needed to move forward |
|---|---|---|
| Brief and feasibility | Requirements, intended use, risks, key components, cost assumptions and schedule dependencies. | An agreed scope and proposed route, with unresolved feasibility questions identified. |
| Drawings and prototype | Mechanical and electronic fit, safe use, functionality, assembly and manufacturability. | Reviewed drawings and sample findings; corrections and customer confirmation for the next commitment. |
| Specification and tooling authorization | Product specification, test plan, materials, packaging and the proposed tooling design. | Approved baseline and explicit tooling instruction; agreed control points for trials. |
| Tool trials and design completion | Trial samples, fit and critical dimensions, function, reliability and corrections from earlier trials. | Resolved trial findings and the current BOM, controlled drawings and core-material approvals. |
| PP / pre-production pilot | Production materials, assembly methods, fixtures, SOPs, test results, packaging and line feasibility. | Pilot findings closed or otherwise resolved under agreed acceptance conditions; required customer approval. |
| MP / mass production | Pre-production meeting, incoming status, first articles and in-process quality against the release package. | Authorized production under controlled instructions, with abnormal results investigated. |
| Shipment and follow-up | Final inspection, packing, shipment confirmation and subsequent product feedback. | A recorded release decision; feedback and corrective actions carried into future work. |
On smaller screens, scroll the table to see every column.
03 / BOTH SIDES HAVE A ROLE
Who provides what, and who decides?
Xinyinhai’s factory review connects development, quality, production engineering, manufacturing and purchasing. Customer decisions remain part of the same controlled workflow.
Review, execute and document
Feasibility · agreed engineering work · production controls · review evidence
| Topic | Customer contribution | Project-team contribution |
|---|---|---|
| Requirements and rights | Define intended use and target markets; provide authorized designs, branding and content. | Review feasibility, identify risks and request missing evidence or clarification. |
| Engineering and samples | Confirm priorities and give consolidated feedback on the identified revision. | Prepare the agreed engineering work and samples; report findings and proposed actions. |
| Acceptance and validation | Agree acceptance criteria and provide customer-specific standards and available reports. | Define applicable checks and records; clarify any external verification or specialist support needed. |
| Production readiness | Approve the agreed sample, packaging and production commitment. | Review materials, work instructions, fixtures, pilot findings and production controls. |
| Changes and follow-up | Authorize changes and supply product-use or field feedback with supporting information. | Evaluate impact, update controlled information and investigate relevant product or process issues. |
On smaller screens, scroll the table to see every column.
Each issue needs an owner and a next decision. The agreement defines responsibility for customer-supplied design, software, content, compliance evidence and manufacturing execution. It should not leave either side responsible for an undefined activity it cannot control.
04 / FREEZE & SAMPLE APPROVAL
Design Freeze & Sample Approval
An approval should identify the exact files or sample, the characteristics accepted and any remaining conditions.
DESIGN FREEZE
A controlled reference for the next commitment
Record the approved drawing, BOM and specification revisions. Identify the sample and relevant artwork, packaging and material references. Confirm the scope of approval before tooling or production preparation relies on it.
What an approval record should resolve
- Which revision and sample were reviewed?
- Which functional, dimensional, appearance and packaging criteria were accepted?
- Which open issues still require action or verification?
- Who approved the decision, and which stage may now proceed?
- Do the relevant teams hold the same current information?
Appearance should be evaluated using suitable physical references where color, texture or finish matters. The sample and written criteria work together. See appearance inspection for how defined viewing conditions and defect criteria support consistent decisions.
| Information | Purpose | Revision control |
|---|---|---|
| Product definition: BOM and DWG | Identify the bill of materials, component specifications and technical drawings used for the approved product. | Review and approve changes, then distribute current versions to the departments using them. |
| Production and inspection: SOP and SIP | Connect operating instructions and inspection instructions to the relevant process steps. | Issue approved instructions and withdraw obsolete internal copies when the requirements change. |
| Customer inputs and references | Identify the supplied drawings, artwork, color references and written product requirements. | Register and distribute the accepted inputs; replace or mark superseded material so the approved reference is clear. |
On smaller screens, scroll the table to see every column.
A blank form or general check sheet defines what to record. A completed review record identifies the actual revision, findings and decision. Agree which project records can be shared and any confidentiality restrictions as part of the quality review.
05 / CONTROL CHANGES
Engineering Change Review & Approval
A requested improvement can affect more than the drawing: materials, molds, validation, existing parts and the production plan may all depend on the current revision.
- 01
Identify the requested change
Reference the affected revision, describe the reason and define the intended result. Distinguish a correction to the agreed scope from an added function or new direction.
- 02
Review consequences and obtain written confirmation
Assess engineering work, tooling, procurement, testing, cost and schedule. Resolve responsibility for affected work and materials before implementation is authorized.
- 03
Update, communicate and verify
Issue the changed files and instructions to the relevant teams. Identify any affected samples or stock and repeat the required checks. Close the change only with a clear record of the result.
For broader engineering changes, review Product Adaptation. For unresolved rights, safety or responsibility questions, use the project fit and working principles to establish what must be clarified before the affected work continues.
Order changes affecting agreed quantities, specifications or delivery are recorded, reviewed by the relevant teams and confirmed with the customer. Where a product is subject to certification, assess any additional certification approval separately from the general engineering-change decision.
06 / FEEDBACK & CORRECTIVE ACTION
Turn a reported problem into a reviewed action
Xinyinhai’s documented service procedure records customer feedback and brings quality, engineering and production into the investigation when needed. Agree the communication and evidence needed for the specific issue.
- 01
Record the issue
Identify the product revision, order or batch, affected quantity and use conditions. Photos, test results or a returned sample help establish what happened.
- 02
Review and agree handling
Review available inspection and shipment records, investigate the cause and agree the relevant containment, return or other handling with the customer.
- 03
Verify the corrective action
Assign the responsible team, track the action and review its effectiveness before closing it. Carry confirmed permanent changes into controlled documents.
For a field issue that needs recovery of affected products, the scope and handling plan are reviewed with the customer using the available batch and shipment evidence. Response timing and service arrangements are agreed for the case. See Traceability & Materials for the records that support that investigation.
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.
A defined project route, scope and list of assumptions or information gaps.
An agreed milestone plan with required inputs, deliverables and review responsibilities.
Stage findings and action records identifying the revision, issue, owner and next decision.
A documented approval baseline for samples, specifications and production preparation as applicable.
Change-impact records and the agreed technical handover or production-release information.
BUYER QUESTIONS
Common questions about how we work
Start with your current product information and the decision you need to make.
Do all projects follow the full development sequence?
No. A new product needs concept and engineering development; an OEM transfer starts with the customer design package. Existing-product customization may focus on artwork, appearance and packaging approvals. The project plan selects the applicable reviews while keeping safety, acceptance and change-control decisions clear.
What does design freeze mean?
Design freeze establishes the approved revision used for the next committed work, such as tooling or production preparation. It identifies the drawings, BOM, specifications and applicable samples. Changes remain possible, but their impact and authorization must be recorded before affected work continues.
Is approving a sample the same as approving mass production?
No. Sample approval confirms the characteristics covered by that sample and the written specification. Mass-production release also depends on production readiness, required verification, current work instructions and resolution of applicable pilot issues. The approval record should say precisely what has been accepted and what remains open.
How are feedback and technical changes handled?
Provide consolidated feedback against a specific file or sample revision. We record the requested change, assess its effects on design, tooling, materials, tests, cost and schedule, and agree the action before implementation. The updated information must reach the teams using it; a verbal instruction alone is insufficient.
What happens when a review finds a failure?
The finding is recorded with its effect, owner and corrective action. The affected stage is not treated as complete simply because a meeting took place. Relevant checks are repeated after correction, and the release decision follows the agreed acceptance criteria. Serious unresolved safety issues prevent commercial release.
How should several customer teams coordinate an approval?
Identify the decision owner and collect design, quality, purchasing and commercial feedback against the same revision. Resolve conflicting instructions before issuing a consolidated decision. The approval record should identify the accepted scope, remaining actions and authorized next step so production does not rely on separate or contradictory messages.
What information helps investigate a problem after delivery?
Share the product revision, order or batch reference, affected quantity, use conditions and available photos, test results or samples. The issue is recorded and the relevant teams review available inspection and shipment evidence. Handling and response arrangements are agreed for the case. Corrective actions are tracked, their effectiveness is reviewed and confirmed permanent changes are carried into controlled documents.
YOUR NEXT STEP
Start a Project Review
Explain what exists today, what you want to change or create, and what the next decision must establish. Incomplete early ideas are welcome for assessment; mark unknowns so they become explicit review items.
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
- Your current stage: selected base product, existing design to change, new idea or production-ready design.
- Target users, intended use, sales markets and the essential product requirements.
- Available files and samples, their revisions, and authority to use the design and content.
- Expected quantities, budget constraints, target milestones and known technical uncertainties.
- Required tests, acceptance criteria and the status of any supporting reports.
- A decision owner and a practical route for consolidated feedback and written approvals.