Most sourcing problems are not manufacturing problems. They are reading problems. A Chinese supplier's email is usually accurate about what it says and uninformative about what it means — and the phrases that sound most reassuring are the ones that carry the least information.
Why the gap exists
Three things stack on top of each other.
First, the English is often assembled from templates and translation tools. It is formal, grammatically careful, and constructed to sound agreeable — because it was written to maintain a relationship, not to convey a constraint.
Second, in Chinese business communication, avoiding a direct refusal is a social obligation rather than a conversational option. Delivering a flat "we cannot do that" is understood as damaging the relationship, so the refusal arrives as a hedge, a delay, or a request for more information. Read literally, a hedge looks like agreement.
Third, the person writing to you is frequently not the person who will make the product. A sales representative confirms what they believe the factory can do, and the gap between that belief and the production floor is where specifications quietly die.
None of this is deception. It is two communication systems producing a sentence that both parties can read as good news, and only one of which is describing production capability.
Agreement is not confirmation
The single most useful habit in supplier communication is to stop treating a positive reply as a confirmation of capability.
| Reply | What it usually means | What it does not mean |
|---|---|---|
| "No problem" | I have received and understood your request | The factory has checked feasibility |
| "We will try our best" | There is a difficulty I am not going to name | The difficulty has been solved |
| "Same quality as your sample" | I will aim for the sample | Material, process and tolerance have been matched |
| "It is almost finished" | Production is under way | Any specific completion percentage |
| "Yes, we can do OEM" | We accept the order type | We can manufacture to your drawings |
| "This is our best price" | The opening position | The final price |
| "The engineer said it is fine" | Someone expressed an opinion | Anyone signed a document |
| "We will arrange soon" | It is on someone's list | It has a date |
Read the right-hand column and the same email becomes a list of things that are still unknown. That list is the actual project plan.
How to ask a question a factory can answer
Most buyer questions are unanswerable, which is why they attract uninformative answers.
"Can you make this?" invites a yes, because the cost of saying yes in the conversation is zero and the cost of saying no is a lost order. The factory is not being evasive; the question asked for a preference, not an assessment.
Ask instead for a choice with consequences:
- Instead of "Can you do this material?" — ask "Between these two materials, which will you use, and what changes in the unit price and lead time?"
- Instead of "Is the tolerance possible?" — ask "What is the tolerance you will hold on this dimension, and what is your inspection method for it?"
- Instead of "Will quality be the same?" — ask "Which line will produce this order, and who signs the first-article approval?"
- Instead of "When will it be ready?" — ask "What is the date of your next milestone, and what has to be true for that date to hold?"
A question with two options and a cost attached is answerable in any language. A question with a yes/no answer is not a question at all — it is a request for reassurance, and reassurance is what you will get.
Send pictures, not adjectives
Words like "premium", "matte", "sturdy" and "similar to the photo" do not survive translation. They do not survive within one language either, but the failure is faster across one.
What travels reliably:
- A photograph with the important dimension annotated, rather than a description of the dimension.
- A physical sample, with the accepted one marked and dated.
- A marked-up drawing showing which tolerance is critical and which is cosmetic.
- A previous product as a reference, with a note on what specifically must match and what may differ.
When a buyer sends an adjective, the factory substitutes its own interpretation, and it is almost always the cheaper one. That substitution is not dishonest — it is the only reading available.
Silence is information
A factory that goes quiet for three days before quoting has told you something about its capacity. A factory that replies within ten minutes to every message has told you something about its sales staffing, which is not the same as its production capability.
Both signals are useful, and neither is about you. Treat slow replies during a busy season as a prioritisation signal rather than as rudeness, and treat very fast, very agreeable replies during a technical discussion as a reason to ask for specifics rather than as a reason to relax.
The worrying pattern is not slowness. It is a supplier that becomes fast and vague at the moment the questions get technical.
Put the agreement in writing — but not more writing
The fix for ambiguity is not longer emails. It is fewer, more specific, and signed ones.
- One document that states what will be made, to what tolerance, in what material, packed how.
- One approved sample that both parties have dated and kept.
- One record of every change after that point, with who asked and who agreed.
Then, when something is disputed later, the conversation is about a document rather than about recollection. Suppliers take written documents far more seriously than conversational commitments for a simple reason: documents are what their own production floor gets handed.
Where this goes wrong in practice
- The comfortable yes. A buyer asks five yes/no questions, receives five yeses, and believes the specification has been agreed. Nothing has been checked.
- The translated specification. A brief written in marketing language arrives at the factory as a brief in marketing language, and each department interprets it differently.
- The verbal change. A modification agreed on a call, never written down, becomes a defect at inspection and an argument at the claim stage.
- The polite escalation. A problem raised as a gentle suggestion is understood as optional. Escalation in this context is not rudeness; it is clarity about consequences.
- The assumption of shared context. Your launch date, your customer's expectations and your margin are not visible to the factory. If they matter, they have to be stated as requirements.
Frequently asked questions
Is "no problem" a bad sign?
Not on its own. It is a neutral acknowledgement and it is used constantly, including by suppliers who will perform well. The signal to watch is whether specifics follow it. A "no problem" followed by a named material, a stated tolerance and a date is a real answer. A "no problem" followed by nothing is an acknowledgement of your message.
Should I write in simple English or ask for a Chinese-speaking contact?
Simple English works better than elaborate English, and far better than idioms. Short sentences, one question per message, numbers instead of adjectives. If a technical discussion becomes genuinely difficult, asking whether an engineer can join is more productive than repeating the same explanation more slowly.
Does this mean I should not trust what suppliers tell me?
It means trust should attach to verification rather than to tone. The suppliers who are most reliable are often the least effusive — they answer the specific question, name the constraint, and give a date they intend to keep. Being agreeable and being capable are different properties, and only one of them can be checked before the goods arrive.
Next step
Clear communication only helps if the brief behind it is specific. See how the Understand stage turns requirements into a factory-ready brief, or read how to verify a supplier before the conversation gets commercial.