Barefoot Shoe Supplier Communication: An Evidence-Based Test

Measure the right communication signals

A polished salesperson may not control engineering or production information. Assess how the supplier connects buyer questions to the people and records that can answer them.

Language fluency can improve efficiency, but it is not the same as technical control. A concise reply with the correct drawing mark-up and measurement record can be stronger than a long sales message.

Use realistic assessment scenarios

Ambiguous specification

Send a requirement such as “make the toe box wider” with enough context to investigate but without inventing a measurement. A capable supplier should ask which last, size, reference points, fit objective and affected components apply. It should not change the pattern or last based on guesswork.

Proposed material substitution

Ask what happens if an approved upper or outsole material becomes unavailable. Look for disclosure of the proposed source and properties, affected orders, sample or test need, cost and schedule effect, and a request for formal approval. “Same quality” without data is not a change assessment.

Nonconformance during production

Present a repeated bonding or measurement problem. The response should address containment, affected scope, evidence, cause investigation, correction, verification and restart authority. A discount offer does not replace control of the product.

Schedule conflict

Ask about a material delay that threatens the plan. Strong communication separates confirmed facts from estimates, shows the critical dependency, gives options and trade-offs, and avoids committing to a date before the process owner confirms it.

Test-report question

Request the report for the current material or finished-shoe configuration. Verify whether the supplier can match style, component, batch, method, laboratory, date and acceptance criteria. A report for a different construction should be labelled as reference only.

Score evidence, not fluency

Use a scorecard with observable anchors rather than impressions such as “responsive” or “easy to work with”. For each scenario, record:

• whether the supplier identified the correct product and document revision;
• questions asked before making assumptions;
• evidence supplied and whether it matched the issue;
• technical, quality and commercial owners involved;
• actions, deadlines, dependencies and escalation route;
• how the decision and changed documents were closed.

Weight the scenarios by product risk. Uncontrolled substitutions and weak nonconformance handling usually matter more than a late reply to a general introduction. Keep the raw examples with the score so a sourcing decision can be audited later.

ISO’s process approach guidance emphasises inputs, outputs, responsibilities, controls and evidence. ISO 10007:2017 adds configuration identification and change control, while ISO 10005:2018 supports a defined quality plan. These frameworks do not assign a supplier response time; they help evaluate whether communication supports a controlled process.

Set the project communication system

Even a capable supplier will struggle with scattered buyer instructions. Establish one source of truth and one controlled issue log. Give every tech pack, BOM, drawing, sample and comment sheet a revision and status. Define who may issue changes and who approves technical, quality, commercial and schedule decisions.

Agree a simple message structure for exceptions:

1. product, order, sample or lot affected;
2. current requirement and observed condition;
3. evidence attached;
4. containment already taken;
5. decision or information needed;
6. owner and required decision date;
7. follow-up record after closure.

Set urgency categories for production stop, compliance risk, sample decision, commercial change and routine question. Acknowledge urgent issues quickly, but allow a separate evidence deadline when investigation is necessary. Avoid rewarding an immediate unsupported answer.

The sample revision guide shows how to separate buyer changes, supplier corrections and engineering trials. The in-line QC guide defines the records needed when a process gate fails.

Recognise warning patterns

One imperfect email is not a verdict. Look for repeated patterns across scenarios and stages:

• every answer is “yes” until the sample arrives;
• technical questions return only a price or delivery promise;
• photos lack style, size, date, location or measurement reference;
• old files remain in use after a revision is released;
• substitutions are described as equivalent without approval evidence;
• bad news appears only after the buyer asks;
• actions have no owner, scope or closure record;
• the sales contact cannot connect the buyer to a process owner.

Before rejecting the supplier, check whether the buyer’s own instructions were consolidated and measurable. The technical specification guide helps remove avoidable ambiguity. If the pattern continues after expectations are clear, treat it as an operating-risk signal rather than a personality issue.

During qualification, ask for examples with confidential details removed: a change request, nonconformance response, version-controlled sample comment and test-report trace. Then verify the same behaviour on your own project.

Frequently asked questions

How fast should a shoe supplier respond?

Set expectations by urgency and complexity. An urgent production risk needs prompt acknowledgement and containment, while a technical root-cause answer may require investigation. Measure both timeliness and evidence quality.

Is poor English a supplier red flag?

Not by itself. Assess whether the team understands requirements, asks useful questions, provides traceable evidence and closes decisions. Translation support can solve language gaps; uncontrolled changes cannot.

Who should be included in supplier communication?

Use named owners for commercial, development, quality and production topics, with a clear escalation route. One coordinator should maintain the controlled issue and revision record.

Primary references

• ISO, guidance on the process approach
• ISO 10007:2017, configuration management guidelines
• ISO 10005:2018, quality-plan guidelines
• ISO 19011:2026, guidelines for auditing management systems