01 · Define the search
Find the manufacturer for a defined project—not “the best factory.”
A supplier can be credible and still be wrong for the product, development state, order structure, destination market or level of coordination required. Start by describing the project well enough that a candidate can decline, qualify assumptions or show relevant evidence.
This guide owns the informational task: how to search, screen and compare candidates. The separate commercial manufacturer page owns the later question of whether HACOLD’s proposed working model is relevant. Keeping those roles separate prevents an educational article from turning into a disguised supplier claim.
02 · Search brief
Define the supplier role and project constraints first.
Write the known inputs, mark open questions and identify which responsibilities the supplier must own. Do not hide gaps behind a generic request for price.
Product and range
- Product types, construction complexity and intended use.
- Style, colour and size structure of the proposed range.
- Material, trim, artwork, label and packaging status.
- Approved references and unresolved technical decisions.
Development need
- Pattern, tech-pack, material-sourcing and sample responsibilities.
- Sample type and the decision each round must prove.
- Version control, comment ownership and approval authority.
- Confidential-information boundary before file transfer.
Commercial context
- Estimated quantities by style/colour/size and future potential.
- Target market, delivery window and Incoterm requirement.
- Budget context without forcing an unsupported target price.
- Payment, currency and service-scope expectations.
Risk and evidence
- Destination-market, labelling and testing questions.
- Quality criteria, inspection evidence and escalation needs.
- Supply-chain visibility and subcontracting questions.
- Documents or site evidence required before each commitment.
03 · Candidate discovery
Build a broad lead list, then narrow it with the same gates.
Candidates may come from referrals, trade events, industry directories, sourcing partners, existing supply-chain contacts or targeted search. Discovery source is not verification. A paid marketplace badge, attractive booth, referral or search rank may justify investigation; none proves project fit.
- Record the source. Note who introduced the candidate and what was actually claimed.
- Confirm contact continuity. Use a business channel that can be tied to the entity under review.
- Run a basic fit screen. Product/process relevance, development scope, order model and destination readiness.
- Request evidence by claim. Ask for the item that would support the specific decision, not a generic document dump.
- Apply the same rejection rules. Referrals and incumbents should not bypass material risk gates.
04 · Evidence verification
Separate identity, capability, compliance and performance evidence.
One document rarely proves all four. Verify the legal and invoice entity, its relationship to the production site, the processes relevant to the product, the scope and validity of any compliance record, and the provenance of any case or performance example.
- Identity evidence
- Legal name, registration context, address or site relationship, bank/invoice entity and authorized commercial contact.
- Capability evidence
- Relevant product/process examples, equipment or workflow evidence, staff ownership and current constraints—not an unrelated product gallery.
- Compliance evidence
- Certificate/report issuer, subject entity/site, scope, standard/program, validity, findings and permission to verify.
- Performance evidence
- Permissioned case, order or quality record with product relevance, date, scope, limitations and no hidden customer identity claim.
- Supply-chain evidence
- In-house versus external processes, supplier/subcontractor disclosure, monitoring and escalation for the proposed project.
The OECD garment and footwear framework treats due diligence as an ongoing process for identifying, preventing, mitigating and accounting for supply-chain impacts.[1] ILO tools provide indicators and practical guidance for identifying forced-labour risk; they should inform investigation, not be reduced to a supplier yes/no checkbox.[2]
05 · Comparable request
Send the same decision-ready request to the shortlist.
A vague enquiry rewards confident sales language. A controlled request reveals whether the candidate asks useful questions, labels assumptions and understands the product. Share enough information for the screening stage, but do not send sensitive files before identity, confidentiality and access controls are appropriate.
- Company/market context and intended sales destination.
- Product/range summary and current development state.
- Available specification/reference and the safe sharing boundary.
- Quantity structure and timing target marked as estimate where needed.
- Requested service scope, quote basis and required separated costs.
- Quality, testing, labelling, inspection and documentation questions.
- Exact next decision: feasibility screen, quotation, sample proposal or evidence review.
Does the candidate identify contradictions, distinguish estimate from commitment, ask about destination requirements and state what cannot yet be confirmed? Useful uncertainty can be a stronger signal than instant agreement.
06 · Quote and sample
Use the quotation and sample to test the working relationship.
Normalize every quotation against specification version, quantity basis, material assumption, service scope, testing/inspection, packaging, Incoterm, payment, exclusions and validity. Then define a sample round that tests the highest-risk interpretation or operation—not a vague request to “check quality.”
- Questions and assumptions
- Does the candidate expose missing inputs and document the basis used for price, material and timing?
- Version discipline
- Can the team identify the current file, consolidate comments and record approved changes?
- Technical interpretation
- Does the sample and review demonstrate understanding of product-specific construction, fit, material and finish?
- Commercial clarity
- Are included/excluded services, third-party costs, payment triggers and change effects visible?
- Issue behavior
- When a problem appears, is it surfaced early with scope, options, owner and decision requirement?
Continue to the sample-approval framework when development control is the central question.
07 · Red flags
Slow down when the evidence and the promise diverge.
- The legal, invoice, bank, website and production-site identities cannot be reconciled.
- Every product, quantity, price and date is accepted before the specification is understood.
- Important answers remain in calls or chat but are not reflected in the quote or controlled record.
- Certificate scope, validity, site or issuing body cannot be verified.
- Customer logos, photos or case material are offered without permission or context.
- Subcontracting or external processes are denied, hidden or described inconsistently.
- A sample is presented as proof of bulk consistency without a production-control explanation.
- The candidate pressures payment or sensitive-file transfer before identity and terms are clear.
- Problems are minimized, blamed or concealed instead of scoped and escalated.
A single red flag may have an innocent explanation. The decision should depend on materiality, corroborating evidence, response quality and whether the risk can be controlled—not on optimism or blanket suspicion.
08 · First controlled commitment
Design the first order to test the unresolved risks.
A “test order” is not automatically small, cheap or low risk. It should have a written purpose, controlled product reference, realistic service scope, measurable checkpoints and a decision rule for what happens next. Never publish or assume an MOQ, lead time or available capacity before project review.
- List the hypotheses the first commitment needs to test.
- Define approved inputs, open conditions and the latest point each must close.
- Agree on sample/pre-production release, production visibility and quality evidence.
- Confirm destination-market ownership, documentation and shipment release.
- After completion, record issues, decisions and data that must carry into any repeat order.
09 · Decision scorecard
Score evidence and risk—not sales polish.
Use a weighted scorecard only after defining hard gates. A high average should not cancel a failure in legal identity, product safety, critical quality, ethical risk or another non-negotiable requirement.
- Project fit
- Product/process relevance, development need, order structure and destination readiness.
- Evidence confidence
- Identity, scope, recency, provenance, independent verification and open gaps.
- Development control
- Question quality, version discipline, sample purpose, approval records and change handling.
- Quality control
- Criteria, checkpoints, evidence, defect decisions, corrective action and release authority.
- Commercial clarity
- Comparable assumptions, exclusions, payment, ownership, change effects and delivery basis.
- Communication and escalation
- Named owners, update method, early-warning behavior, issue scope and decision speed.
- Due-diligence risk
- Supply-chain visibility, labour/human-rights/environmental risk process and destination obligations.
10 · Commercial hand-off
Change pages when the buyer question changes.
Use this article while building the search and shortlist. Move to clothing manufacturer fit in China when evaluating whether HACOLD’s working model belongs on the shortlist. Move to the apparel sourcing framework when coordination across the sourcing process is the main need.
Import preparation also depends on the destination. Australian Border Force publishes the official entry point for import requirements and declarations, while the UK Trade Tariff requires product details to determine classification and duty treatment.[3][4] Confirm current obligations with the applicable authority or qualified adviser before commitment.