How to Structure a Shenzhen Visit When Prototype and Production Questions Differ
Published: Read Time: 11 minutes

How to Structure a Shenzhen Visit When Prototype and Production Questions Differ

Plan a Shenzhen sourcing visit that verifies prototype development and production readiness as separate, evidence-based workstreams.

Executive introduction

A convincing prototype does not establish that a prospective sourcing route can manufacture the same design repeatedly under controlled production conditions. Prototype development is primarily concerned with translating a concept into a reviewable sample, resolving specifications, and managing revisions. Production verification asks different questions about process control, inspection, traceability, change authorization, product safety, and repeatability.

Structure a Shenzhen visit around these two independent questions. Review prototype evidence without treating it as proof of production readiness, and review the proposed production system without assuming that displayed equipment or promotional statements demonstrate routine capability. The objective at the pre-sourcing stage is not to approve a supplier. It is to determine what is supported by records or observation, what remains a claim, and what requires specialist review.

Use an evidence-based plan with defined objectives, scope, criteria, methods, and reporting categories. This reflects the audit-planning principles addressed by ISO 19011, while remaining a limited pre-sourcing verification exercise rather than a formal certification audit.

1. Define the Shenzhen verification task before scheduling visits

Primary decision

Determine whether a prospective sourcing route can support:

  • Prototype work: translating the product concept into a reviewable sample and resolving design uncertainties.
  • Production work: repeatedly manufacturing the approved design while maintaining defined safety, quality, and process controls.
  • Both stages: with a documented handoff from prototype approval to production control.
  • Neither stage: when essential claims cannot be supported with appropriate records or direct observation.

Do not treat a successful prototype as evidence of production readiness. The two stages require separate questions, records, observations, and conclusions.

Prototype questions

Structure the prototype portion of the visit around questions such as:

  • Can the party reviewing the design identify unresolved specifications?
  • Who controls drawings, bills of materials, revisions, and sample approvals?
  • Which components, materials, or processes remain provisional?
  • How are requested changes recorded and communicated?
  • What measurements or tests will define prototype acceptance?
  • Is the sample representative of the intended materials and processes?
  • Which prototype methods would need to change before production?
  • What safety-related assumptions require confirmation against applicable CPSC requirements or guidance?

Production questions

Treat production verification as a separate task:

  • Where would routine manufacturing actually occur?
  • Which processes would be performed at that location, and which would be outsourced?
  • What approved specification would control production?
  • How would incoming materials, in-process work, and finished products be checked?
  • How would nonconforming output be identified, segregated, reviewed, and resolved?
  • How would design or material changes be authorized?
  • What records would connect production output to inspections and tests?
  • What product-specific CPSC requirements, testing obligations, or certification duties need specialist confirmation?
  • Which claims can be verified through records, observation, or interviews?

Use Shenzhen research without treating it as verification

Use the China Hi-Tech Fair official site as a pre-visit research input. Review the current categories, themes, exhibitors, technologies, or participating organizations presented there, and use that information to develop a follow-up list.

This research can help identify capability areas relevant to the product concept. It cannot establish manufacturing capability, production capacity, product conformity, compliance status, or process control. Appearance on an event website is promotional or directory information until the relevant claims are checked at an operating location.

Build two evidence requests

Prepare and send two separate document requests before the visit. Ask for product-relevant records where available, but do not assume that receiving a document establishes effective implementation.

Prototype evidence request

Request:

  • Current drawing or specification revision.
  • Bill of materials or equivalent component list.
  • List of open technical questions.
  • Sample change history.
  • Prototype inspection or test plan.
  • Sample acceptance criteria.
  • Identification of temporary materials, tooling, or processes.
  • Proposed path from prototype work to a production-controlled design.

Production evidence request

Request:

  • Process flow or manufacturing sequence.
  • Defined inspection and test points.
  • Material and component controls.
  • Work instructions or equivalent process controls.
  • Product-relevant equipment or tooling control records.
  • Nonconformance and corrective-action procedures.
  • Change-control process.
  • Traceability approach.
  • Product-safety documentation relevant to applicable CPSC requirements.
  • Records supporting any certification or compliance claim.

The CPSC Business & Manufacturing guidance is an appropriate starting point for researching U.S. product-safety responsibilities. The applicable rules, tests, certificates, and records depend on the product category and intended use, so unresolved questions may require qualified product-safety or legal review.

2. Structure the city visit as separate verification blocks

Block A: Opening meeting and evidence alignment

Use the opening meeting to:

  • Confirm the legal and operating identity of the organization being visited.
  • Record the address and functions performed at the location.
  • Identify the people responsible for prototype engineering, quality, production, and product safety.
  • Confirm the proposed product, revision, and intended market.
  • Agree on which areas and records may be reviewed.
  • Distinguish statements that can be checked during the visit from statements requiring later evidence.

Before drawing conclusions, define the visit objective, scope, criteria, methods, evidence needs, and limitations. This structured approach is consistent with the planning principles described by ISO 19011, but it does not turn the visit into certification or guarantee product conformity.

Block B: Prototype verification

Focus on design translation rather than production-volume claims.

Review the specification

  • Compare the current sample with the current drawing or specification.
  • Mark dimensions, materials, functions, finishes, labels, and packaging details that remain undecided.
  • Record discrepancies without assuming which version is correct.
  • Confirm who has authority to approve a design revision.
  • Identify the sample and document revision being reviewed.

Trace one prototype change

Select one actual or proposed change and ask the team to demonstrate:

  1. How the change is requested.
  2. How feasibility is reviewed.
  3. How documents are revised.
  4. How the revised sample is identified.
  5. How acceptance is recorded.
  6. How obsolete versions are prevented from becoming the production reference.

If the team cannot demonstrate the full sequence, record the supported steps and the remaining gap. Do not infer a controlled process from an informal explanation.

Test prototype claims

For every material claim, classify the available support as:

  • Directly observed.
  • Supported by a record.
  • Reported in an interview only.
  • Not yet verified.

An interview statement can guide follow-up, but it should not be converted into a confirmed finding without suitable supporting evidence.

Block C: Production-system verification

Focus on repeatability, controls, and records rather than the appearance of the facility.

Walk the proposed process

Follow the expected sequence from incoming materials through finished-product release. At each stage, ask:

  • What specification applies?
  • Who performs the task?
  • What equipment, tooling, fixture, or software is used?
  • What characteristic is checked?
  • What record is created?
  • What happens when the result is unacceptable?
  • Is the step performed at this location or elsewhere?

If the proposed process is not operating during the visit, record that limitation. Displayed equipment, sample products, or a verbal explanation do not by themselves prove routine manufacturing capability.

Sample records across the process

Where access is permitted, select records that connect:

  • Incoming material identification.
  • In-process inspection.
  • Finished-product testing.
  • Nonconformance handling.
  • Release authorization.
  • Traceability identifiers.

Check whether the documents are current, relevant to the proposed product, internally consistent, and connected to the work observed. Record missing links rather than filling them with assumptions.

Address product safety separately

Use the CPSC manufacturer-facing resources to frame research into obligations for the intended U.S. market. The visit plan should:

  • Identify the product category and intended user.
  • Determine which CPSC rules or guidance require further review.
  • Ask how applicable safety requirements enter the product specification.
  • Ask what testing, certification, or recordkeeping may be required.
  • Seek the records supporting each product-safety claim.
  • Avoid accepting a general statement of “compliance” as sufficient evidence.
  • Escalate unresolved regulatory questions to a qualified product-safety or legal professional.

Block D: Prototype-to-production handoff review

Ask the prospective production team to explain:

  • What event freezes the approved product definition.
  • Which sample becomes the reference sample, if one is used.
  • How final drawings and bills of materials are approved.
  • How temporary prototype methods are replaced with controlled production methods.
  • How tooling, fixtures, software, labels, and packaging revisions are controlled.
  • How first production output would be checked against the approved design.
  • Which changes require buyer approval.
  • How safety-related characteristics remain controlled after handoff.

The handoff is not defined merely because a final-looking sample exists. It requires an approved product definition, controlled files, identified responsibilities, and clear conditions for accepting initial production output.

Block E: Closing meeting and gap classification

Classify every material issue before closing the visit:

  • Verified: supported by suitable evidence.
  • Partially verified: some support exists, but a defined gap remains.
  • Unverified: only a claim or incomplete evidence is available.
  • Not applicable: outside the agreed product or visit scope.
  • Requires specialist review: needs regulatory, engineering, testing, or legal expertise.

Confirm factual visit notes and outstanding requests, but do not issue a final sourcing conclusion when critical evidence remains unavailable.

3. Practical verification checklist

Verification item Prototype check Production check Evidence to seek Result
Organization and location Confirm who develops or modifies the sample Confirm who would manufacture and release production Organization details, site functions, direct observation ☐ Verified ☐ Partial ☐ Unverified
Product definition Identify the current sample and revision Confirm the production-controlling revision Drawings, specifications, revision records ☐ Verified ☐ Partial ☐ Unverified
Bill of materials Mark provisional components or materials Confirm approved material and component controls Bill of materials, specifications, receiving records ☐ Verified ☐ Partial ☐ Unverified
Change control Trace a prototype revision Verify authorization and implementation of production changes Change requests, approvals, revision history ☐ Verified ☐ Partial ☐ Unverified
Acceptance criteria Define how the sample is accepted Confirm measurable release criteria Inspection plans, test methods, approved criteria ☐ Verified ☐ Partial ☐ Unverified
Prototype methods Identify temporary tooling or manual work Confirm the intended routine production method Process descriptions, tooling records, observation ☐ Verified ☐ Partial ☐ Unverified
Process location Record where the prototype is made Record where each production step would occur Process flow, site walk, outsourcing records ☐ Verified ☐ Partial ☐ Unverified
Inspection controls Review sample checks Review incoming, in-process, and final checks Inspection instructions and completed records ☐ Verified ☐ Partial ☐ Unverified
Test capability Identify prototype tests and unresolved needs Confirm how routine or required tests would be managed Test plans, reports, equipment records ☐ Verified ☐ Partial ☐ Unverified
Product safety Identify safety assumptions in the design Confirm safety requirements are built into production controls Applicable requirements, specifications, test or certification records ☐ Verified ☐ Partial ☐ Specialist review
Nonconforming output Record how prototype failures drive revisions Verify segregation, disposition, and corrective action Procedures, examples, corrective-action records ☐ Verified ☐ Partial ☐ Unverified
Traceability Identify samples and revisions Connect materials, process records, tests, and released output Identifiers, logs, batch or serial records where applicable ☐ Verified ☐ Partial ☐ Unverified
Equipment and tooling Identify what was used for the sample Confirm production equipment and tooling controls Equipment lists, maintenance or control records, observation ☐ Verified ☐ Partial ☐ Unverified
Outsourced work Identify external prototype activities Confirm externally performed production steps and controls Process map, provider controls, relevant records ☐ Verified ☐ Partial ☐ Unverified
Reference sample Confirm whether a sample is approved Confirm storage, identification, and revision status Approval record, labeled sample, handling method ☐ Verified ☐ Partial ☐ Unverified
Handoff readiness List unresolved design questions Confirm prerequisites for first production output Handoff checklist, approved files, open-action list ☐ Ready ☐ Conditional ☐ Not ready
Promotional claims Separate descriptions from evidence Test capability and control claims at the operating location Records, interviews, direct observation ☐ Verified ☐ Partial ☐ Unverified
Visit limitations Record inaccessible records or processes Record idle, absent, outsourced, or restricted processes Visit notes and limitation log ☐ Complete ☐ Follow-up required

Evidence note template

Complete one note for every material finding:

  • Question:
  • Prototype or production:
  • Product and revision:
  • Location:
  • Evidence reviewed:
  • Direct observation:
  • Interview statement:
  • Gap or contradiction:
  • Required follow-up:
  • Owner:
  • Due point:
  • Decision impact:

Exit criteria

The Shenzhen verification task is complete only when the buyer can separately state:

  1. What was verified about prototype development.
  2. What was verified about production control.
  3. What remains unsupported.
  4. Which product-safety questions require further CPSC research or specialist review.
  5. Whether the prototype-to-production handoff is defined.
  6. What evidence is still required before supplier selection or an order commitment.

Final next move

Convert the checklist into a visit brief with two independent workstreams: prototype verification and production verification. Send the corresponding evidence requests in advance, and schedule only the Shenzhen locations capable of addressing the specified questions.

After the visit, issue separate conclusions for prototype suitability and production readiness. Keep unsupported claims on an open-action list, assign an owner and due point to each follow-up, and delay any sourcing commitment that depends on unresolved critical evidence.

Scope and limits

  • This article supports pre-sourcing research and visit planning. It does not approve a supplier, facility, product, or production process.
  • ISO 19011 provides guidance for auditing management systems. Using its planning concepts here does not create certification or guarantee product conformity.
  • The CPSC Business & Manufacturing resources should be consulted when researching U.S. product-safety responsibilities. Applicable rules, tests, certificates, and records depend on the specific product and intended use.
  • The China Hi-Tech Fair official site may support ecosystem and event research, but promotional or directory information is not verified operating capability.
  • No supplier, capability, certification, compliance status, capacity, quality level, or Shenzhen location is established by this article.
  • Product testing, regulatory interpretation, engineering validation, legal review, and formal audits may require qualified specialists.
  • Findings apply only to the product revision, records, processes, people, and locations actually reviewed.
  • Restricted access, idle processes, unavailable records, and outsourced work must be documented as visit limitations.

Image credit

O2O Sourcing industrial morning. Credit: O2O Sourcing. Source: O2O Sourcing. License: Site-owned image.

Sources

Sourcing information earns its value when it is verified, compared and turned into a decision.