Supplier Development / Sourcing Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: Supplier development/sourcing is not "rename the supplier-cooperation page". It is a chain from requirements and category strategy, make/buy, market scanning, long list, RFI/RFQ, samples/trial builds, audits (quality/capacity/compliance/finance), trial production/PPAP, award/contract, to performance/exit: the public page explains what you buy, how you find/evaluate/trial/award suppliers and how to contact you; internally you keep the evidence, reviews, approvals and records. Sourcing is also not "lowest price wins": separate technical/quality thresholds, total cost of ownership (TCO), delivery/capacity, compliance/ESG, financial resilience, IP/confidentiality. Page acceptance is not "how complete it looks", but whether a supplier can tell "do I qualify, what is next, when will I hear back", and whether internal teams can find the review/award evidence from the page. Information is current to 2026-11-06. This is a review of public rules and page practice, not legal, procurement or contract advice; specifics follow company policy, contracts and the Civil Code/PIPL/DSL.

This guide is for procurement, SQE, R&D, finance and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. Common problems: only "welcome to become a supplier"; unclear categories/thresholds; RFI and RFQ mixed; sample/tooling fees opaque; audit criteria unpublished; no trial/award milestones; the website promises "orders guaranteed/lowest price".

How does the sourcing page relate to cooperation, onboarding, RFQ, audit and sample pages?

The supplier cooperation page answers "how to cooperate/categories/notices/payment/ethics"; the onboarding/AVL page answers "admission documents/audit/AVL"; the quotation/RFQ page answers "how to quote"; the second-party audit page answers "how audits work"; the sample/first-article page answers "how to sign samples/FAI". The sourcing page is the front end: it links "requirements—market—RFI/RFQ—samples—audit—trial—award—contract" and tells suppliers which stage they are in, what is needed, who decides and how long. It does not replace the specialist pages, but suppliers should find them from it.

Common breakpoints: only "welcome to register"; unclear categories/thresholds; RFI and RFQ mixed; sample/tooling fees unclear; audit criteria unpublished; no trial/award milestones; contract/price terms unclear; no performance/exit rules; the website promises "orders guaranteed/lowest price". Separate "requirements—sourcing—validation—award—performance"; then procurement, SQE, R&D, finance and suppliers share one playbook.

This page map is editorial; company policy, contracts and regulations control.

How should category strategy and make/buy be accepted?

Before sourcing, define "what to buy, why, and where": category (direct/indirect, strategic/bottleneck/leverage/routine), requirements/specification/volume/lead time, make/buy (in-house capacity/investment/quality vs external availability/cost/risk), single/multi-source, domestic/imported, long/short term. The public page can state "focus categories/not handled/supplier types/region/capacity thresholds" without disclosing sensitive strategy, but a supplier should be able to judge "am I in scope". The page should state "category—requirements—make/buy—source—threshold", not "we purchase all kinds of products".

Acceptance checks: category list; requirements; make/buy; single/multi-source; region/capacity; thresholds. Common gaps: categories too broad; unclear requirements; no basis for make/buy; unexplained sole source; missing thresholds; "focus categories" written as everything.

Category/make-buy are editorial; company strategy and policy control.

How should market scanning and the long list be accepted?

Market scanning answers "which suppliers exist, where, how large, what capabilities, price bands and risks": industry directories/exhibitions/associations/customer-directed/existing supplier referrals/public tenders/databases; create a long list (name/location/category/scale/certification/customers/risk), then filter to a short list against thresholds. The public page can state "industry belts/supplier types/minimum capacity/certification/areas not accepted" and "how long initial screening takes". The page should state "channels—long-list fields—screening criteria—timeline", so suppliers do not "send documents and wait".

Acceptance checks: channels; long-list fields; screening criteria; timeline; confidentiality; deduplication. Common gaps: single channel; incomplete fields; no screening criteria; no response time; leaking other suppliers; duplicate contacts.

Market scanning/long list are editorial; company policy controls.

How should RFI, RFQ and quotations be accepted?

RFI (request for information) is for market/capability discovery and does not commit to an order; RFQ (request for quotation) is for pricing after specifications/volume/delivery/terms are clear. Do not mix them: RFI asks "what can you do/capacity/certifications/customers/price bands"; RFQ gives drawings/specifications/volume/delivery/currency/tax/trade terms/quote template/deadline. Quotations should support breakdown (material/processing/tooling/packaging/logistics/tax), versions, validity, Q&A, sealing/deadline and comparison; the page should state "is this RFI or RFQ, what is needed, deadline, how to ask questions"—not "give us a price first".

Acceptance checks: RFI/RFQ distinction; specification/volume; quote template; deadline/time zone; Q&A; sealing; comparison; records. Common gaps: RFI treated as RFQ; unclear specification; inconsistent quote basis; unclear deadline; early disclosure; no Q&A; no records.

RFI/RFQ are editorial; procurement policy and contracts control.

How should samples, trial builds and technical validation be accepted?

For samples, state: sample type (concept/functional/engineering/production-representative), quantity, delivery time, drawing/specification edition, material/process, test items/standards, sample sign-off/sealing, sample fee/tooling fee/freight, IP/confidentiality, failure/rework rules. For trial builds, state: small-batch quantity, process/tooling/gauges, process capability, first article/FAI, issue list/corrective actions. The page should state "sample fee/refundability/tooling ownership/test report/sign-off"—not "free samples until you are satisfied".

Acceptance checks: sample type; quantity/delivery; drawing edition; testing; sign-off; fees/tooling; IP/confidentiality; trial/FAI. Common gaps: unclear type; unlimited free samples; wrong drawing edition; missing test standard; no sign-off; unclear tooling ownership; no IP agreement.

Samples/trials are editorial; contracts and IP/confidentiality terms control.

How should supplier audits (quality, capacity, compliance and finance) be accepted?

Sourcing audits typically cover quality system/process capability, capacity/equipment/delivery, technology/R&D, EHS/compliance, finance/resilience, IP/confidentiality, customers/track record. The public page can state audit type (questionnaire/remote/onsite), scope, scoring/grading, nonconformity grading/CAPA and result use (pass/conditional/fail); it need not disclose specific customers/prices, but should say "an audit pass is not permanent". Findings must close the loop; critical/high-risk categories may add onsite/trial production. The page should state "what is audited, how, how long, how results are used"—not just "we audit".

Acceptance checks: audit type; scope; scoring/grading; nonconformity/CAPA; result use; re-audit; records. Common gaps: only "audit"; unclear scope; no scoring; open findings; unclear result use; no re-audit; missing records.

Audits are editorial; the second-party audit page, quality system and contracts control.

How should trial production, PPAP and award be accepted?

Before award there should be evidence of "readiness for mass production": small batch/trial, process capability/cycle time, tooling/gauges, first article/FAI, PPAP (if applicable), quality/delivery/cost review, capacity ramp-up, risks/rollback. The award should state: scope/share, price/terms, delivery, tooling/ownership, quality agreement, confidentiality/IP, performance/exit; approval needs review records/conditions. The page should show the milestones "trial—PPAP—award—ramp-up" and "what happens if it fails"—not "audit pass = order".

Acceptance checks: trial; process capability; PPAP; cost/quality review; award scope/share; contract/agreement; ramp-up; rollback. Common gaps: award after audit only; no trial; missing PPAP; price not agreed; unclear tooling ownership; no ramp-up/rollback; no approval record.

Trial/award are editorial; NPI/PPAP, contracts and quality agreements control.

How should contract, price and terms be accepted?

After award, put "price/currency/tax/trade terms, payment/terms, delivery/capacity, quality/acceptance, tooling/ownership/IP, confidentiality, change/PCN, warranty/spares, breach/termination, dispute resolution" into the contract/agreement. Price should consider TCO (material/processing/tooling/packaging/logistics/tax/quality cost/switching cost), not just unit price; annual reduction/raw-material index/FX rules should be defined. The public page may summarise payment/contract type/quality agreement/confidentiality, without specific prices/customers; do not write "lowest price/share guaranteed".

Acceptance checks: price/TCO; currency/tax; payment; delivery; quality/acceptance; tooling/IP; confidentiality; change; warranty; breach/dispute. Common gaps: unit price only; unclear payment; tooling ownership; no IP; no change clause; no warranty; no dispute clause.

Contract/price are editorial; contracts, tax and legal advice control.

How should performance and exit be accepted?

Award is not the end: score quality (PPM/8D), delivery (OTD/lead time), cost (annual reduction/VA-VE), response/service, compliance/ESG periodically; grade (strategic/preferred/qualified/restricted/exit); low performers get remediation/downgrade/exit; exit requires last-time buy, inventory/tooling/drawings/software handover, second source and customer approval. The page should state "dimensions/cycle/grading/exit"—not "supplier for life/never eliminated".

Acceptance checks: dimensions; cycle; grading; remediation/downgrade; exit; handover; second source; customer approval. Common gaps: no scoring; no cycle; unclear grading; no remediation; no handover; no second source; no customer approval.

Performance/exit are editorial; the supplier-exit page, contracts and customer requirements control.

How should the website sourcing page be written?

Suggested content: (1) focus categories/not handled; (2) supplier types/region/capacity/certification thresholds; (3) sourcing process and stages (RFI/RFQ/samples/audit/trial/award); (4) documents/timing/decision-makers at each stage; (5) samples/tooling/fees/IP/confidentiality; (6) audit scope/scoring/result use; (7) trial/PPAP/award/ramp-up; (8) contract/payment/quality agreement summary; (9) performance/exit; (10) contact/entry/version/update date. The public page explains thresholds/process/milestones/documents/contacts, not customer lists/prices/strategy; do not write "orders guaranteed/lowest price/approval guaranteed".

The English page should use consistent terms (sourcing, supplier development, RFI, RFQ, sample, trial production, PPAP, award, TCO, NDA, IP, exit) and state the review date. Link it to the supplier cooperation, onboarding/AVL, quotation/RFQ, second-party audit, sample/first-article, supplier portal/SRM and supplier-exit pages.

This page structure is editorial; external statements must be truthful and verifiable, per company policy and contracts.

What must not be written?

High-risk claims: "orders/share guaranteed" (cannot guarantee); "lowest price wins" (not price-only); "audit pass = award" (trial/PPAP/contract still needed); "free samples/free tooling" (cost/ownership unclear); "supplier for life/never eliminated" (performance/exit); "approval guaranteed" (review is not a formality); "we handle every category" (thresholds unclear); "customer list can be published" (confidentiality/authorisation); "one contract covers all factories/categories" (scope mismatch). These are inaccurate or misstate process/scope/responsibility.

Safer wording: "We focus on [categories]; suppliers must meet [capacity/certification/quality] thresholds; the process is [RFI/RFQ/samples/audit/trial/award], with documents/timing [link]; samples/tooling/fees/IP follow [rules]; award requires [trial/PPAP/contract]; performance/exit follow [rules]; specifics follow company policy and contracts." External promotion must comply with advertising/fair-competition law; customer/price/strategy data needs authorisation/redaction.

These red lines are editorial; false advertising is determined by the regulator/contract—not this article.

Go-live acceptance checklist

Ten checks: category/threshold, process/stages, documents/timing, RFI/RFQ, samples/fees, audit, trial/award, contract/performance, page wording, records/version. Each needs an owner, evidence and review date. The pass condition is not "the page welcomes suppliers", but that a supplier can tell "do I qualify, what is next, when will I hear back", and internal teams can find the review/award evidence.

Before go-live, run one real new product through: category/requirements → market scan → RFI/RFQ → samples → audit → trial/PPAP → award/contract → performance. Any step that fails is a gap in the page or policy.

This checklist is editorial; company policy, contracts and regulations control.

Who should read this, who should not, and what decisions does it support?

It suits procurement, SQE, R&D, finance and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies developing new categories/suppliers or whose sourcing page has long been "welcome to register". It does not suit spot purchasing, companies without supplier development needs, or teams wanting one page to replace audits/trials/contracts/legal advice.

Read it if you are developing suppliers; categories/thresholds are unclear; RFI/RFQ are mixed; sample/tooling fees are unclear; audit/trial/award are disconnected; or the website only says "welcome to register". Skip it if you guarantee orders, award on lowest price, treat audit as award, or offer unlimited free samples. It supports self-review of category/make-buy, market scan, RFI/RFQ, samples/audit/trial, contract/performance and page wording.

FAQ

What is the difference between supplier development and onboarding?

Development/sourcing is the front end: category strategy, market scan, RFI/RFQ, samples, audit, trial, award, contract; onboarding/AVL is the admission step ("documents + audit + approved vendor list"). The sourcing page should tell suppliers which stage they are in, what is needed and who decides; the onboarding page handles documents/questionnaire/AVL maintenance.

Must sourcing use a tender?

Not necessarily. Public tendering suits large-value, competitive or highly regulated categories; RFI/RFQ, invited quotations and sole source (with justification) are also possible. What matters is requirements/thresholds/comparison basis/review records/approval, not the form. If a project is legally subject to mandatory tendering, follow the applicable law.

Can a small supplier without mass-production experience qualify?

Yes, with capability evidence and risk control: samples/trial builds, process capability, audit, trial production/PPAP, capacity ramp-up, quality/delivery commitments; critical categories may start with a second source/small share/restricted use and expand after maturity. The page should describe a "new supplier path", not a blanket "must have 3 years of supply history".

How should sample and tooling fees be handled?

State sample type/quantity, sample fee/freight, tooling/fixture fee, tooling ownership/transfer, modification/rework, IP/confidentiality, and amortisation/refund after mass production. Do not offer "unlimited free samples" or hide tooling cost in the unit price; follow the contract/quotation and IP terms.

What if an audit fails?

Handle by nonconformity grade/remediation/CAPA/re-audit: minor items with a deadline, major items suspend/fail; critical categories may allow "conditional/restricted/small-batch trial" before award. The page should state result use/re-audit/exit—not "fail means blacklisted forever" or "relationships bypass the audit".

Can the website say "orders guaranteed/lowest price wins"?

Not recommended. "Orders/share guaranteed" cannot be promised, and "lowest price wins" is inaccurate (TCO, quality, delivery, compliance, resilience matter). State categories/thresholds, process/stages, documents/timing, samples/fees, audit/trial/award, contract/performance—use verifiable facts, not absolutes.

One-sentence takeaway

A Changzhou manufacturer's supplier development/sourcing page is not about "welcome to become a supplier". It should turn category/thresholds, market scan, RFI/RFQ, samples/trials, audit, trial/PPAP, award/contract and performance/exit into a reviewable process—so a supplier can tell "do I qualify, what is next, when will I hear back", and internal teams can find the review/award evidence.

Method and limitations

This is a review of public rules and page practice, not an audit, legal or procurement opinion on any company, product, contract or policy. No undisclosed customer, price, supplier or contract data were used. Processes, document lists, tables and acceptance items are editorial suggestions, not procurement/legal conclusions. Specific categories/thresholds, RFI/RFQ, samples/audit/trial, contract/performance depend on company policy, contracts, the Civil Code, PIPL, DSL and other applicable rules.

Sources and scope

Information is current to 2026-11-06. The following are official legal pages; their text controls.

1. Civil Code of the People's Republic of China: CAC. Contract formation/performance, liability, technology contracts (see the text).
2. Personal Information Protection Law of the People's Republic of China: CAC. Notice/minimization/retention/sharing of supplier contact and audit data (see the text).
3. Data Security Law of the People's Republic of China: CAC. Classification/grading and security obligations for drawings/technical data (see the text).