The short version
- A question sent at the end of the European day lands after the Asian factory day is over. Each one costs a full day, and product decisions rarely need only one.
- Send in your morning, not your afternoon. That single habit change converts a two day exchange into a same day one.
- Ask closed questions with options and a recommendation. Open questions cost an extra round trip every time.
- Keep one written record of what was agreed, per order, with dates. Supplier conversations drift across email, chat and calls, and the drift is where the mistakes live.
Small product brands with manufacturing in Asia run into the same wall. You spend the day working out a question, send it at 17:00, and the factory reads it the next morning their time, which is the middle of your night. Their reply raises a clarification. Now you are three days into a decision that would have taken five minutes in person.
The shape of the day
Take a brand in Amsterdam and a factory in Shenzhen. Roughly six hours apart, factory day 08:30 to 18:00 local.
| Amsterdam | Shenzhen | What is possible |
|---|---|---|
| 09:00 | 15:00 | Three hours of their day left. Send now and you get a same day answer. |
| 12:00 | 18:00 | The window closes. A message now probably waits until tomorrow. |
| 17:00 | 23:00 | Guaranteed next day. This is when most brands send. |
The window is real and it is short. Most small brands spend it on internal work and then write to the supplier once the internal work is done, which is precisely backwards.
Send in your morning
Invert the day. First hour: everything that has to cross to the supplier, sent, even if it is not fully worked out. Then internal work. The answers arrive during your afternoon or overnight, and tomorrow starts with information instead of a wait.
This feels wrong, because sending a half formed question feels unprofessional. It is not, as long as the question is honest about its state. "We are deciding between two lining materials. Before we finish, can you confirm which of these you can source in the quantity, and what the lead time difference is?" That is a useful question to receive, and it removes a round trip from the decision you have not made yet.
The same inversion applies inside the company. If your designer needs to see a sample before you can ask the factory anything, the designer's review belongs at the end of the previous day, not at 11:00 on the day you want to send.
Ask questions that can be answered in one word
Every open question costs an extra crossing. "What do you think about the packaging?" gets a reply asking what you mean, and now you have lost two days.
Three rules make questions cheap.
- Give the options. Not "how should we handle the label", but "A or B, and here is what each means for us."
- Give your recommendation. It lets them agree in one word, and they will tell you if it is wrong.
- Give the deadline and the default. "We need this by Thursday. If we do not hear, we will proceed with A." The default is what stops silence becoming delay.
Number your questions. A message with four numbered questions reliably gets four numbered answers. The same four in a paragraph reliably gets two.
One record per order
Supplier conversations spread across email, a chat app, a spreadsheet and two calls nobody wrote up. Six weeks later, nobody is sure whether the revised tolerance was agreed or only discussed.
Keep one document per order with a dated list of what was agreed. After every call or significant exchange, add two lines: what was agreed, and by whom. Send it to the supplier as a confirmation. That confirmation does double duty, because it also catches misunderstandings while they are still cheap to fix.
The thing to record is the same thing that matters in any decision log: what was decided and why the alternative was rejected. See the decision log template.
The internal half of the problem
Half of supplier delay is not the supplier. It is that the person on your side who knows what was agreed is in a meeting, or off, or has the answer in a thread nobody else can find. The factory replies at 03:00 asking to confirm one detail, and the reply waits on one colleague waking up and remembering.
This is what StandIn is built for. At the end of the day the person handling the supplier relationship spends about ninety seconds on a brief: what moved, what is open, what is blocked, what is next, mostly drafted from the work itself. When they are off, their StandIn answers from that brief, in their words, with a source under every answer. It never guesses, and when the answer is not in the record it says so and names who to ask. A colleague can confirm what was agreed on the tolerance without waiting for the one person who was on the call. See working across time zones.
Common Questions
Should we use a sourcing agent to bridge the gap?
An agent in the supplier's time zone removes the seam and adds a relay, which means you learn about problems later and in summarised form. Worth it for quality control on the ground, less so purely for communication timing.
Is chat better than email with overseas suppliers?
Chat is faster and much worse as a record. Use chat for speed and confirm anything that matters in writing to the order document the same day. What is only in chat is effectively unrecorded.
How do we handle their holidays?
Put the major manufacturing holidays in your own calendar a year out, with a reminder six weeks before each. The costly mistake is not the closure itself, it is the two weeks before it when capacity is already gone.
What if the supplier only answers slowly?
Check first whether your questions are answerable in one pass. Suppliers answer fast when the reply is one word and slowly when it requires interpreting what you meant. If the questions are clean and replies are still slow, that is a relationship question rather than a timing one.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.