A factory visit can give you better questions. It cannot give you a magic stamp that says “supplier approved.”
Walking a production floor, meeting the people who answer your technical or commercial questions, and seeing how a product version moves through the operation can add context that a quote and video call cannot provide. It can also create a false sense of certainty if the visit is unplanned, access is limited, or observations are treated as proof of things they do not establish.
A useful visit is an evidence-gathering exercise. You decide what questions matter, ask for permission to discuss and observe defined areas, preserve what was said and seen, separate supplier statements from your own observations, and route follow-up through the right owners. This guide shows how to plan a factory visit in China around that disciplined approach.
Scope boundary: This is general operational education, not travel, immigration/visa, safety, security, legal, regulatory, labor/social-audit, product, testing, certification, engineering, quality, customs, tax, contract, payment, logistics, insurance, or investment advice. A visit does not establish that a factory is genuine, compliant, safe, capable, ethical, suitable, or approved. It is not an audit, inspection, certification, or acceptance decision.
Decide what the visit is meant to answer
“Visit the factory” is not an objective. Before you contact the supplier, write down the product, order, supplier relationship, and decision question that make the visit worthwhile. You might need to clarify whether the supplier understands the current product version, how the team tracks a sample or packaging change, who owns a production handoff, or what records exist for a specific supplier statement. Those are concrete questions a visit can help frame.
The U.S. Consumer Product Safety Commission lists visiting applicable factories as one possible affirmative supplier-diligence step, alongside specifications, documentation, and controls around materials and components.1 The same guidance does not make a visit a verdict. Use the visit to collect information and records; keep product, safety, quality, compliance, and commercial conclusions in their proper review routes.
| Visit purpose | Product/order scope | Useful question | Record to request or preserve |
|---|---|---|---|
| Supplier relationship review | Named supplier and current products | Who owns key product and communication handoffs? | Contact/role map, relevant messages, open-item list |
| Product-version review | Product ID and revision | Which version is the team using at each handoff? | Revision log, sample/approval references, supplier acknowledgment |
| Component or packaging question | Defined component or pack-out version | What information does the supplier rely on for this item? | Supplier statement, source file, photo/record reference, open review route |
| Production-flow understanding | Defined product/process area | What sequence does the supplier describe for the current version? | Visit notes linked to version, not a capability conclusion |
| Evidence-gap follow-up | Specific missing or unclear record | Who can provide the record, and by when? | Request log, owner, due date, and response |
If your purpose is “see if they are a good factory,” narrow it. Good for which product, which market, which stage, and which decision? A vague visit often produces vague notes.
Set the scope with the supplier before you arrive
A respectful visit starts with an agreed agenda. Tell the supplier who is attending, why you want to visit, which product or order you want to discuss, the areas or records you hope to cover, and what kind of follow-up you expect. Ask what access limits, confidentiality rules, photography rules, recording rules, safety procedures, identification requirements, and scheduling constraints apply.
Do not assume you can enter any area, handle samples, take photos, ask workers questions, or view documents. Get the supplier’s permission and follow the site’s rules. If a requested area or record is not available, record that fact without guessing why. A restricted area can be a real limit, a confidentiality need, a safety rule, or a scheduling issue. It is not proof of a problem.
| Pre-visit item | Confirm before the visit | Why it protects the record |
|---|---|---|
| Attendees and roles | Names, roles, language needs, and who may speak for each side | Prevents later confusion about who said or agreed to what |
| Date, duration, and agenda | Product/order/version and planned discussion blocks | Keeps the visit focused on the reader’s decision question |
| Access boundaries | Permitted areas, documents, photos, samples, and conversations | Respects site rules and makes limits visible |
| Evidence approach | Note format, allowed photos, document-request process | Avoids turning an informal observation into an unsupported claim |
| Follow-up route | Supplier contact, internal owner, request list, and expected next action | Moves unanswered questions into a controlled process |
NIST’s Manufacturing Extension Partnership describes supply-chain mapping as a process that can collect supplier, part, routing, transportation, and tier information in a repository that teams can review, share, and update.2 Treat the visit as one input to that record. It should add context to existing supplier and product information, not replace it.
Build a proof map before the meeting
A proof map is a short table that connects each question to the information you hope to gather and the limit of what that information can show. This is the difference between taking many photos and collecting usable evidence.
| Question area | Visit evidence to collect, if permitted | What the evidence can support | What it cannot prove by itself |
|---|---|---|---|
| Supplier identity/contact | Signage, business-card/contact record, supplier-provided location reference | That a named party represented itself at the location on the visit date | Legal identity, ownership, authorization, or ongoing operations |
| Product/version control | Current sample, document references, labels, revision discussion | Which version was presented or discussed | That every future unit will match it |
| Process description | Supplier explanation and permitted observations | How the supplier described or showed a process on that day | Capacity, quality level, safety, or future performance |
| Materials/components | Supplier statement and records they choose to provide | What information the supplier provided about a component | Product compliance, suitability, authenticity, or authorization |
| Packaging/pack-out | Current artwork, carton, label, or packing discussion | What configuration was displayed or described | That it meets all requirements or will ship unchanged |
| Open issues | Clear question list and named supplier contact | Which questions still require follow-up | A decision that has not been made |
CPSC recommends detailed specifications, documentation, supplier diligence, and controls against unauthorized substitutions in supply chains.1 Bring the relevant current product/version record. Do not try to reconstruct critical specifications from memory in a conference room.
Run the visit as an observation log, not a scorecard
During the visit, write down the date, time, location/area, attendees, product/order/version, question asked, supplier statement, your direct observation, record or photo reference if permitted, and follow-up owner. Use plain language. “Supplier representative stated that the material arrives from a named source” is different from “material source verified.” “Observed cartons labeled with product code X in the permitted storage area” is different from “warehouse controls are adequate.”
A good note makes its limit clear. It says what was observed, by whom, under what access conditions, and what still needs review. This protects the supplier from overstatement and protects your team from treating a visit memory as evidence.
| Note type | Better record | Avoid |
|---|---|---|
| Supplier statement | “Supplier contact stated [statement] during the visit; supporting record requested.” | “Confirmed.” |
| Direct observation | “Observed [item] in [permitted area] at [time], linked to photo/note ID if allowed.” | “Factory has strong controls.” |
| Document shown | “Supplier displayed [document description]; copy/status/follow-up recorded.” | “Document is valid.” |
| Access limit | “Supplier did not permit access to [area/record]; reason stated if provided.” | “Supplier is hiding something.” |
| Discrepancy | “Visit discussion differs from current record [ID]; routed for clarification.” | “Supplier made a false claim.” |
You do not need to chase every topic in one day. Prioritize the questions tied to the current decision. If a new issue appears, add it to a follow-up log rather than derailing the entire visit.
Ask questions that reveal the handoff, not just the showroom
A showroom sample and a production floor can both be useful, but the transition between them is often where sourcing misunderstandings begin. Ask about the handoffs: how a version reaches the team, who receives a packaging change, how a supplier records an open question, what happens when a component is unavailable, or where a finished sample/order record is stored.
These questions do not require the supplier to expose confidential methods. They invite the supplier to explain its own process and point to the records it uses. Listen for clear version references, named roles, and a path for follow-up. Record answers as supplier statements until the relevant owner reviews them.
The International Trade Administration advises businesses to select partners carefully and to continue due diligence as they expand.3 A factory visit belongs inside that ongoing process. It is not the last step before a purchase order or the only source of supplier information.
Handle discrepancies without turning them into accusations
Visits sometimes reveal a difference between a quote, a sample, a document, an email, and what people describe in person. That is valuable. Do not demand an instant explanation or decide who is right while standing on the floor. Capture the exact difference, link both records, ask what the supplier understands the current version to be, and send the issue through the relevant internal route.
For example, if a packaging display differs from the current artwork file, write down the product/version identifiers, who presented the display, what the source file says, and which owner will reconcile them. If the supplier offers a change, treat it as a proposal. It needs the same version control and qualified review as any other change.
The product revision-control guide can help keep working, released, and superseded product records separate. Use it before and after the visit so a useful observation does not turn into an uncontrolled instruction.
Close the loop within ten business days
The value of a visit fades fast if notes sit in a notebook. Within one business day, store the visit log, permitted photos, document references, access limits, and open questions in the project record. Within three business days, send the supplier a factual follow-up list that distinguishes requests, clarification questions, and items that require internal review. Within ten business days, review the evidence with the relevant owners and update the decision/issue log.
| Timing | Action | Output |
|---|---|---|
| Before the visit | Confirm scope, access, agenda, evidence rules, and current product version | Approved visit brief and proof map |
| Visit day | Capture statements, observations, records, limits, and open questions | Dated observation log with source links |
| One business day after | Store and label all materials; separate facts from interpretations | Shared evidence folder and visit summary |
| Three business days after | Send focused follow-up requests and questions | Supplier request log with owners and dates |
| Ten business days after | Route decisions, reconcile discrepancies, and update next steps | Updated risk/decision/revision records |
Use the factory-audit limitations guide to keep the distinction between a visit and a formal audit clear. The remote supplier assessment guide and supplier verification checklist are useful companion records when a visit cannot answer every question.
Make the visit one part of a stronger supplier record
The best output from a factory visit is not a pile of photos or a gut feeling. It is a better record: updated supplier contacts, a clearer version trail, a list of source documents, a precise set of unanswered questions, and a follow-up path that owners can use.
Add meaningful observations to the supplier scorecard with their source/date and avoid reducing the visit to a single score. A visit is a snapshot under defined access conditions. It can improve your questions and your evidence. It cannot replace ongoing due diligence, product controls, qualified review, or the decisions your organization needs to make.