Contents
A manufacturer replies, says your shoe looks possible, and asks for a logo and quantity. You have a conversation underway. You may still lack the information needed to request a useful sample or compare a quotation.
The first reply is a working document. Read it against the enquiry you sent, mark what each statement actually resolves, and choose a small next decision. An enthusiastic answer can leave important conditions open; a brief answer can also contain a useful request for information your team has not supplied.
Keep the reply attached to your input
Before interpreting the supplier’s answer, retrieve the exact reference, files and questions behind it. A response to a mood image has a different scope from a response to an identified technical pack.
Record the enquiry date, product reference and file revision. If the original enquiry needs rebuilding, use the footwear RFQ guide to organise your inputs and the requested response. If you sent several shoes or changed an attachment, ask which version the supplier reviewed. A message saying “we can make this” is difficult to use if “this” could refer to more than one product.
Then identify your immediate decision. You might need to establish whether the project warrants a development discussion, obtain a defined sample proposal, or clarify a quotation. Avoid treating the first reply as approval for every later stage.
Tag the information before judging
Use four simple labels beside the questions you sent:
- Answered: the response identifies the relevant project condition and gives the information requested.
- Conditional: an answer depends on a stated assumption, choice or later review.
- Needs buyer input: the supplier needs a file, quantity breakdown or decision from your team.
- Not addressed: the reply does not resolve the question, and the reason is unclear.
These labels describe the conversation. They are not a supplier score. For the broader decision about whether a supplier fits the project, see How to Evaluate a Shoe Manufacturer. A conditional answer may be appropriate when you have not selected a material. A request for a reference file may expose a gap in your enquiry rather than a problem with the supplier.
Keep an answer beside its conditions. If a quantity applies only to an existing sole or selected material, do not carry the number into a comparison sheet while dropping that qualification. When the wording is ambiguous, retain the original message and write a question beside it instead of silently rewriting it as a firm commitment.
Read an illustrative first reply
The following message is an invented teaching example, written for this guide. It is not an actual manufacturer or customer exchange:
We can make your reference. MOQ depends on colours. Samples are available. Please send your logo and target quantity.
A useful reading separates the statements rather than judging the whole message as “good” or “bad.”
| Reply statement | What it establishes | What remains open | Focused follow-up |
|---|---|---|---|
| “We can make your reference.” | The supplier expresses interest in the reference. | Which file was reviewed, and what has been checked? | Which reference version did you review, and what needs a development check? |
| “MOQ depends on colours.” | Colour choices affect the proposed quantity basis. | Whether the basis is per style, colour, material or another condition. | Please identify the quantity basis and the choices that change it. |
| “Samples are available.” | The supplier offers a possible sampling route. | Existing sample or project-specific development; included work and exclusions. | What type of sample are you proposing, and what work would it include? |
| “Send your logo.” | A buyer input is requested. | Whether artwork is needed now and in what format. | What artwork is needed for the next step, and which placement should we specify? |
| “Send target quantity.” | The supplier needs planning input. | Whether a total is sufficient or a breakdown is needed. | Would you like quantities by style and colour, and how should provisional figures be marked? |
For a fuller breakdown of quantity conditions, use What to Clarify About Shoe Manufacturing MOQ.
Do not send every possible follow-up at once. Choose the unresolved items that prevent your next decision. If the immediate task is to understand the sample offer, its scope and required inputs may take priority over a complete bulk-production discussion.
Ask about evidence without jumping to approval
If a reply contains “tested,” “approved” or another broad assurance, ask what object and claim it refers to. A material report, a prototype assessment and a report for a finished shoe answer different questions.
Ask for the document reference, identified material or sample, test method and relevant conditions. SATRA’s discussion of preferred test methods explains why the method and its suitability matter when interpreting test information.[1] A test name alone does not resolve whether the information answers your project question.
Record that a document was received separately from your assessment of its relevance. If you need specialist interpretation, assign that review before relying on the claim. This guide does not prescribe a universal testing programme or establish compliance from an email.
Write a focused second message
Make the next email easy to answer: identify the project, acknowledge useful information, supply missing buyer inputs, and ask the few questions needed to move forward.
Adapt this template to your actual enquiry. Replace the bracketed fields before sending:
Thank you for reviewing [product reference and file revision]. Our next decision is [the decision we need to make].
We have attached [requested input], and our provisional quantity breakdown is [your actual breakdown and assumptions].
Could you confirm which reference you reviewed, the basis of the quantity requirement, and the type and scope of the sample you propose? Please flag anything you cannot assess until further development information is available.
Once those points are clear, we can agree on the next action and who will handle it.
Remove questions already answered. If your input is provisional, say so. Avoid inserting an arbitrary deadline or treating an unconfirmed sample offer as an agreed order.
Close the loop in a reply record
Keep a short record beside the original messages: project reference and revision; supplier statement; its conditions; unresolved question; information owed by your team; next action and owner; and the written response that closes the item.
When a later answer changes a condition, update the record visibly. Preserve the earlier exchange so colleagues can understand the change. A conversation is ready to advance when the information required for the next decision is clear enough for that decision—not when every conceivable question has been answered.
Start by reading one reply this way. Identify the most useful answer, the buyer input still owed, and the question that blocks the next step. Those three observations usually give the second message a clearer purpose than another broad request for “more details.” When several suppliers have answered on a comparable basis, build a shortlist before sampling to decide where your first sample budget can answer the most useful question.
