Home / Common problems / Supplier Communication Problems in Denim Sourcing
Supplier Communication Problems in Denim Sourcing
Why denim programs stall in time zones, terminology and verbal promises, and how a single written channel keeps every decision traceable.
The symptom
The questions take days to answer, and the answers contradict each other. Sales says one thing, production says another, and the factory floor made a decision last week that nobody communicated. The buyer discovers the decision when the sample arrives looking different from the brief. Nothing in the exchange was dishonest; the information simply never had a single place to live, and by the time the program needed it, the verbal chain had already broken.
Why communication breaks down
The causes are structural, which is why goodwill alone does not fix them.
- Time zones. A production day ends before the buying day begins. One round of clarification costs a full day, and a program with ten open questions loses two weeks without anyone noticing a delay.
- Terminology. Trade words carry different meanings at each end of the chain. A fit sample, a counter sample, a pre-production sample and a shipment sample are distinct stages, and a brief that says sample without naming the stage gets whichever one was nearest.
- Verbal culture. On a production floor, decisions are made in conversation and the record lives in memory. A commitment made on the floor never reaches the person writing the purchase order, and the buyer never hears it at all.
- Multiple uncoordinated contacts. Sales, merchandising, the wash house and the pattern room each hold a piece of the truth. When the buyer talks to all of them in parallel, the pieces never assemble into one picture.
Controlling communication with written routines
The fix is not more communication. It is fewer channels with a stricter habit.
- Name a single point of contact. One channel carries every decision, and internal coordination behind that channel is the supplier's job, not the buyer's. Parallel conversations are the mechanism by which contradictory commitments get made.
- Confirm every decision in writing the same day. The routine is simple: a call or meeting ends with a written summary that states what was decided, and silence within an agreed response window is treated as a question to re-raise, not as agreement.
- Define the terminology in the order. The program documents define the sample stages, the milestone names and the inspection terms once, so later messages can use short labels instead of paragraphs and still mean exactly one thing.
- Keep a decision log. A running record of decisions and their dates turns every later dispute into a lookup. The purchase order references it, which gives the log contractual weight instead of remaining a courtesy.
What the routine looks like in a week
The discipline is easier to judge with a concrete rhythm. A program in development runs a short written cycle: the buyer's questions for the day are collected into one message through the named channel; the answers return in writing with the stage each answer belongs to; and any decision with a number, a date or a specification attached is repeated in a confirmation line so the decision log captures it verbatim. Meetings end with a summary sent the same day, and unresolved points are listed as open rather than left to tone of voice. Nothing in the cycle adds cost. What it removes is the silence in which parallel conversations and contradictory commitments grow, which is where most sourcing programs actually lose their footing.
How jeans handles it
jeans exists precisely at this junction. As a sourcing coordination service, it gives the buyer one window into the production chain: the brief is translated into written specifications, the factory's questions come back through the same channel, and every decision returns to the buyer as a written confirmation. The working sequence behind this, from enquiry through approval to release, is set out on the wholesale process page, and the role and standing of the service are described on the about page. Buyers who want to raise a program can start on the contact page, and the exchange that follows follows the same written routine described above.
Questions buyers ask
How fast should a supplier answer a production question?
A response window is agreed in the program documents, and the specific hours are Pending until confirmed. What matters more than the absolute speed is the routine: an answer that arrives within the window, in writing, through the named channel, even when the answer is that an answer needs another day.
Is it rude to demand written confirmations?
In practice the opposite holds. Written confirmation is standard discipline in export apparel, and suppliers serving professional buyers expect it. The habit protects the supplier as much as the buyer, because it prevents the floor from being blamed for a commitment nobody actually made.
What is the difference between the sample types?
Fit sample, counter sample, pre-production sample and shipment sample sit at different stages and serve different decisions. The program documents define each stage once, which is why the definitions belong in the order rather than in an email thread.
Can I talk to the factory directly?
That depends on the program structure and is confirmed per program. What the single-channel routine protects against is not direct contact itself but uncoordinated contact, where two parallel conversations produce two different commitments.
What is a decision log and who keeps it?
A running written record of every decision, its date and its confirmation. The coordinator keeps it as part of program management, and the purchase order references it, so any later question about what was agreed has a document to answer it.