How to Compare Potential Factories When Product Fit and Proof Do Not Align

A factory may appear technically suitable yet provide little evidence supporting its claims. Another may send an extensive document package that says very little about the product you intend to source. Neither situation should be resolved by intuition, presentation quality, or document volume.

The practical response is to evaluate product fit and proof separately, convert uncertain claims into verification questions, and run a bounded Finding a factory verification task. The objective at this stage is not to approve production. It is to determine which candidates have enough relevant and credible support to enter the sourcing shortlist.

Frame the mismatch before comparing factories

Define the two comparison dimensions

Product fit asks whether the factory’s stated processes, equipment, material experience, production controls, and capacity appear relevant to the specific product.

Proof asks whether current, traceable documented information supports those claims and any applicable product-safety obligations.

A polished website, presentation, or questionnaire response is not proof. Conversely, extensive certificates, procedures, and test reports for unrelated products do not establish fit for the proposed product. Treat fit and proof as two separate findings rather than averaging them into one general impression.

Conceptual image for documenting questions and findings—not an image of a factory or verification activity. Photo by Markus Winkler on Unsplash, used under the Unsplash License.

Classify each potential factory

Use a simple two-axis comparison before requesting more information:

Product fit	Available proof	Preliminary interpretation	Verification priority
Strong	Strong and relevant	Promising candidate, subject to validation of document identity, scope, and applicability	Confirm authenticity and consistency
Strong	Weak, incomplete, or unrelated	Capability may exist, but the sourcing decision is not yet supported	Request product-specific evidence
Weak or uncertain	Strong but unrelated	The factory may have organized systems without demonstrating suitability for this product	Test technical and process fit
Weak or uncertain	Weak	Insufficient basis for advancement	Deprioritize or close the review

This classification prevents a common comparison error: allowing strength on one axis to conceal weakness on the other.

Convert impressions into testable gaps

Rewrite broad claims as questions that can be answered with relevant evidence:

• “We make similar products” becomes: “Which documented process records show experience with the relevant materials, tolerances, construction, or safety-critical features?”
• “We have quality procedures” becomes: “Which controlled procedure applies to this proposed product and production process?”
• “We can meet U.S. requirements” becomes: “Which CPSC requirements has the factory identified as applicable, and what evidence supports the proposed compliance approach?”

Classify each missing answer:

• Mandatory gap: Evidence connected to an applicable legal, safety, or non-negotiable product requirement.
• Material gap: Evidence needed to evaluate process capability or quality controls.
• Preference gap: Desirable experience or documentation that is not essential to the present decision.

Apply a firm decision rule: strong apparent fit must not compensate for missing mandatory evidence, and unrelated documentation must not compensate for weak product fit.

Plan a distinct Finding a factory verification task

Write a bounded verification objective

Use a task statement such as:

Verify whether each candidate can provide relevant, controlled, and internally consistent evidence for the product’s highest-risk manufacturing and product-safety requirements before it enters the sourcing shortlist.

Keep this task distinct from:

• General supplier discovery
• Price negotiation
• Sample approval
• Contracting
• A formal certification audit
• Final product compliance testing

A bounded objective prevents the review from expanding into an unfocused request for every document the candidate possesses.

Establish product-specific verification criteria

Create a short requirements list covering only what is necessary for the comparison:

• Product definition and intended market
• Materials and critical components
• Safety-critical features
• Required manufacturing processes
• Inspection or testing stages
• Applicable CPSC requirements for a U.S. consumer product, where relevant
• Certificates, testing, labeling, or records when an applicable rule requires them

CPSC obligations depend on the product category, intended users, applicable rules, and U.S. market context. Use the CPSC Business and Manufacturing guidance to identify product-specific questions rather than assuming every consumer product follows the same testing, certification, labeling, or recordkeeping path.

Request documented information deliberately

Request named evidence tied to each criterion instead of asking for a generic “quality document package.” The ISO guidance on documented information emphasizes maintaining and retaining the documented information necessary to support processes and provide confidence that they are carried out as planned; it does not make document volume a substitute for effective processes or conformity. See ISO’s Guidance on the requirements for Documented Information of ISO 9001:2015.

Potential requests include:

• A relevant process flow or work instruction
• Inspection or test procedures
• Redacted example records for a comparable process
• Equipment or process-control records relevant to critical operations
• Responsibility and approval information
• Document titles, dates, versions, and scopes

Allow sensitive commercial information to be redacted if the remaining content can still demonstrate relevance and control. Record “not provided,” “not applicable,” and “provided but not relevant” as different outcomes.

Apply an audit-inspired review method

Use the structure of ISO 19011, Guidelines for auditing management systems, to improve review discipline without calling the task an independent audit or certification:

1. Define the objective, scope, and criteria.
2. Identify the evidence needed.
3. Review documents and claims consistently.
4. Follow evidence trails where statements conflict.
5. Record findings based on verifiable information.
6. Separate confirmed facts, unresolved points, and reviewer interpretation.
7. Communicate the result and required follow-up.

This approach helps make candidate reviews repeatable. It does not establish conformity with a management-system standard.

Set evidence-quality tests

For every submitted item, check:

• Identity: Is it clearly associated with the candidate and relevant production site?
• Scope: Does it cover the proposed product, material, process, or market?
• Currency: Is the date or revision visible, and is the item still applicable?
• Control: Are ownership, approval, revision, or retention controls apparent where appropriate?
• Traceability: Can the claim be followed to a procedure, record, test result, or responsible function?
• Consistency: Does the evidence agree with questionnaire answers and other documents?
• Relevance: Does it prove the exact point under review rather than a nearby but different claim?
• Limitations: Are redactions, exclusions, assumptions, and missing links recorded?

Practical verification checklist and decision record

Use the same checklist for every candidate

Copy this checklist into the working file for each candidate. Add evidence references rather than relying on unrecorded impressions.

Check	Action	Evidence to request or inspect	Acceptable result	Escalate when
Product definition	Send the same controlled specification or requirements summary	Written acknowledgment, questions, and stated assumptions	Candidate confirms the reviewed version and identifies uncertainties	Response refers to another version or leaves critical requirements unaddressed
Claimed product fit	Map each major capability claim to a requirement	Process description, relevant instruction, equipment or control information, and a redacted comparable record	Evidence directly addresses the required material, process, or critical feature	Evidence is generic, promotional, or limited to a different product
Manufacturing route	Ask where and how critical operations occur	Process flow, operation sequence, inspection points, and responsibilities	Proposed route is coherent and supported	Operations, responsible parties, or production locations are unclear
Outsourced work	Identify processes not performed at the reviewed site	Outsourced-process controls, responsibilities, and available records	Outsourced steps and controls are disclosed and traceable	A critical external process is omitted or unsupported
Document identity	Link each item to the candidate and site	Title, issuing organization, site, date, revision, and approval details	Source and applicability are identifiable	Ownership is missing or the item appears disconnected from the candidate
Document currency	Confirm current applicability	Revision history, effective date, or approval status	Current status is clear	Only superseded or undated material is available
Process control	Test whether claimed controls are documented and usable	Instructions, control criteria, and example records	Instructions and records support the same control approach	Procedures lack corresponding records or conflict with them
Inspection and testing	Identify checks tied to critical requirements	Inspection plan, method, acceptance criteria, responsibility, and redacted results	Method, criteria, responsibility, and results align	Only test names are supplied, without scope, methods, criteria, or traceability
Nonconforming output	Ask how failures are identified and controlled	Procedure or records covering identification, segregation, review, and disposition	Process is defined and supported by relevant evidence	Response relies on informal correction or undocumented judgment
Personnel responsibility	Confirm ownership of critical activities	Role descriptions, authorization, and relevant competence records	Responsible functions are identifiable	No owner can be linked to a critical control
Applicable CPSC obligations	Identify product-specific U.S. requirements where relevant	Candidate’s requirement assessment and proposed supporting evidence	Response addresses the applicable product category and intended market	Candidate makes a blanket compliance claim without identifying requirements
Required testing or certification	Confirm conditionally under the applicable rule	Relevant reports, certificates, or supporting records when required	Evidence matches the product, rule, scope, and responsible party	Evidence concerns another product, component, model, market, or period without a justified link
Labeling and traceability	Check requirements applicable to the product	Proposed labels, marking information, or traceability records	Required information connects to the intended product and production	Generic examples are offered without demonstrated applicability
Cross-document consistency	Compare answers, process documents, and records	Consolidated evidence log	Names, sites, dates, processes, and responsibilities are consistent	Contradictions remain unexplained
Missing evidence	Ask why an item is unavailable	Written explanation, alternative evidence, and proposed completion action	Gap is transparent and has a credible resolution path	Unsupported assurances replace evidence or the explanation repeatedly changes
Verification closeout	Summarize findings and invite correction of factual errors	Findings log and candidate response	Confirmed, unresolved, and rejected claims are separated	Material contradictions or mandatory gaps remain

Maintain an evidence log

Use one row per requirement or claim:

Requirement or claim	Candidate response	Evidence reference	Relevance	Status	Gap or contradiction	Required follow-up
Insert one product-specific criterion	Quote or summarize without embellishment	Record title, date, revision, and page or section	Direct, partial, unrelated, or unclear	Confirmed, conditional, unresolved, or not supported	State the missing link	Name the next verification action

Avoid entering “approved” merely because a file was received. The evidence reference should make it possible for another reviewer to locate the relevant passage and understand why it supports—or fails to support—the claim.

Compare candidates without hiding mismatches

Prepare two conclusions for every candidate:

• Fit conclusion: Strong, conditional, weak, or not established.
• Proof conclusion: Sufficient for the present decision, incomplete, conflicting, or not supplied.

Add a short rationale linked to evidence-log references. Do not combine the conclusions into an unexplained total score.

Apply these decision gates:

• Advance: Relevant fit and sufficient proof for pre-sourcing shortlisting.
• Advance conditionally: Plausible fit with a small, clearly defined evidence gap.
• Hold for targeted verification: Strong fit claim but material proof gaps or contradictions.
• Deprioritize: Organized evidence does not demonstrate product fit.
• Stop: A mandatory requirement cannot be supported or a material contradiction remains unresolved.

Final next move

For each remaining candidate, select the single highest-risk unresolved claim. Send a time-bounded, product-specific follow-up request stating:

1. The exact claim being tested
2. The evidence already reviewed
3. The missing link
4. Acceptable evidence types
5. The decision that will follow

For example: “Your process description identifies an inspection after the critical assembly operation, but the submitted record does not state the acceptance criteria or reviewed product. Please provide a redacted inspection instruction and corresponding example record showing the criteria, product or process scope, date, and responsible function. If the link cannot be established, the candidate will remain on hold.”

Move only candidates that satisfy the defined gate into the next sourcing activity, such as deeper technical review, sampling, or a separately planned remote or on-site assessment.

Scope and limits

• This method supports pre-sourcing comparison and verification planning. It does not determine whether a factory will consistently produce conforming goods.
• ISO guidance on documented information helps structure proportionate evidence requests; more documentation does not automatically demonstrate stronger capability.
• ISO 19011 provides guidance for auditing management systems. Applying its principles here does not make the review a certification audit or establish conformity with a management-system standard.
• A certificate, test report, procedure, or sample record must still be assessed for identity, scope, currency, relevance, and consistency.
• CPSC obligations depend on the specific consumer product, intended users, applicable rules, and U.S. market context.
• The checklist does not replace legal advice, laboratory testing, required product certification, sample validation, contract controls, or ongoing production oversight.
• Remote documentary review may not establish that a described process is implemented consistently at the proposed production site.
• Record uncertainty explicitly. Do not convert missing or restricted information into either approval or an allegation.

Image credit

The selected photograph is a conceptual editorial image for turning factory claims into documented questions and findings. It must not be presented as an image of a factory, supplier, manufacturing process, or verification activity.

• Image: “white and black typewriter on green grass during daytime”
• Photographer: Markus Winkler
• License: Unsplash License
• Placement: Opening discussion of converting claims into verification questions

Sources

• ISO, “Guidance on the requirements for Documented Information of ISO 9001:2015”
• ISO 19011, “Guidelines for auditing management systems”
• U.S. Consumer Product Safety Commission, Business and Manufacturing guidance