How to
How to coordinate merch suppliers across multiple time zones
A working guide for procurement, production and operations teams in Mexico on how to work with suppliers in Asia, Europe and the Americas without losing approval windows, delivery cadence or traceability. How to design the asynchronous workday, where to place the critical decisions, and which tools to use so 14 hours of difference do not become 14 hours of silence.
Why time zone is an operational problem, not a calendar curiosity
Most procurement teams in Mexico work with suppliers in at least two additional time zones: one in Asia (China, Vietnam, Bangladesh, India) for catalog textiles and generic tumblers, and one in Europe (Spain, Italy, Portugal, Poland) for glassware, crystal and finer finishes. Operating with a third zone — the US West Coast, Vancouver, Santiago de Chile — is increasingly common for merch with digital components.
Time zone is not a curious fact. It is an operational constraint that defines when you can expect a reply, when you can escalate and when your supplier is closing for the day. An email sent at 17:00 Mexico City time arrives in Shanghai at 7:00 the next morning, in working hours; an email sent at 17:00 Shanghai time arrives in Mexico City at 4:00 in the morning, outside any reasonable schedule. Without a discipline of communication windows, decisions pile up in one zone and resolve late in the other.
In practice, merch programs that cross three time zones tend to fail for the same reason: a decision that needed a 24-hour reply ends up taking 72 hours, not because the supplier is slow, but because the Mexico team sent the question just as the Asian supplier was closing for the day. The flow below addresses exactly that friction.
What this guide proposes is a seven-step operational protocol that any account manager, project lead or senior buyer can apply when the supply chain crosses Asia, Europe and the Americas. It is designed for programs of 500 to 50,000 pieces, not for mega-productions that need their own project office at destination.
What this guide is not: it is not an excuse to skip learning to work with your supplier. Long-term relationships still require calls, video and trust; the time-zone protocol is the nervous system that keeps the operation alive while trust is being built.
Before moving to the flow, it is worth pinning down two ideas that separate a procurement team that operates across three zones from one that merely survives with one. The first: every supplier lives their own day, and the supplier's day is not negotiable. The second: your decision window is not the supplier's reply window; it is the intersection of the two, and that intersection shifts from one day to the next if your chain includes both Asia and Europe. Designing your workday so that critical decisions fall into the intersection is half the work.
The 7-step coordination flow
- Map of zones and overlap windows. Build a table with each supplier's time zone (referenced to UTC, not the country's local time) and mark the overlap windows with your team in Mexico City. For East Asia (UTC+8) the real overlap with Mexico (UTC-6 standard time) is zero to one hour; for Central Europe (UTC+1) it is two to three hours in the European morning. Define in which window each decision crosses.
- Document the asynchronous workday. For each supplier, define three things: the start of their working day, the close, and the cut-off for urgent emails. Add them to the supplier's documentation. A well-documented asynchronous workday prevents a junior buyer from emailing the Asian supplier at 22:00 Mexico City time expecting an immediate reply.
- Place critical decisions inside the overlap. Color approvals, sample validation and run releases cannot sit in the supplier's inbox waiting for the Mexico team to react 14 hours later. Schedule the brand team for the overlap and resolve there. If there is no real overlap, delegate the approval to a responsible party with extended hours or use written asynchronous approval with an explicit SLA.
- Set one daily email cut-off per supplier. A single daily update email per supplier, sent in their local morning, with the status of pending decisions, approvals to close and the next critical windows. More emails generate more noise and less response. The daily cut-off is the frequency that preserves traceability without saturation.
- Separate synchronous from asynchronous decisions. Synchronous decisions (physical sample approval, product video, alignment call) require overlap. Asynchronous decisions (file review, drawing validation, PO signature) can live in the written flow with a 24-hour SLA. Mixing the two saturates the overlap with things that did not need it.
- Design the escalation route by zone. When an Asian supplier does not deliver a first response within 24 hours, escalation is not waiting another 24. It is escalating to the account manager with the operations director in copy; the response is negotiated in the next overlap with Europe or with the supplier's regional office, if they have one. Define that route in writing before you need it.
- Measure and review quarterly. Once per quarter, measure average response time per supplier, decisions missed due to lack of overlap and accumulated over-cost from waits. The metric reveals whether the chain needs reordering, supplier consolidation or a small regional office. Without the metric, the zone problem normalizes itself.
Common pitfalls that cost hours and over-budget fees
The first pitfall is treating the supplier's time zone as if it were yours. Sending an email at 17:00 Mexico City time expecting the Asian supplier to read and reply before close is wishful thinking. Your afternoon is their night; their morning is your small hours. Design the communication around the receiving zone.
The second pitfall is having no daily cut-off. Without a cut-off, emails pile up, priorities get lost and the supplier reads the silence as the project not being urgent. One email per day, at the same hour, with the same structure, fixes the cadence.
The third pitfall is using the overlap for everything. If the only hour you can talk to your European supplier is the European morning, do not waste it on update calls; use it for approvals that actually require synchrony. The rest goes in writing.
The fourth pitfall is trusting the supplier to flag their own delays. An Asian supplier that detects a delay on the production line does not always report it immediately; sometimes they absorb it silently rather than lose the order. The metric and the quarterly review are what expose the delay the supplier did not tell you about.
The fifth pitfall is failing to document decisions taken inside the overlaps. A verbal decision on a video call with a European supplier, without minutes or a closing email, is a decision that will be reinterpreted the following week. Close every call with a three-line email: what was decided, what is pending, who is responsible.
Tools, templates and references
Zone map: a table with supplier, city, UTC offset, local opening and closing hours, overlap window with Mexico City, primary contact and escalation contact. Printable version and project-folder version.
Daily cut-off template: an email with five fixed blocks — pending decisions, approvals to close, next critical windows, open risks and next scheduled email. Same template, same hour, same recipient per supplier.
Synchronous vs asynchronous matrix: a list of the program's typical decisions, marked as synchronous or asynchronous, with the SLA and channel for each. Helps the account manager know what is discussed by email and what requires a call.
Zone-by-zone escalation route: a document with the escalation chain per regional supplier, names, emails and phone numbers, and the deadline for activating the next level. Printed and signed by the operations director.
Operating references: IANA time-zone database (tz base), brand manual for asynchronous approvals, applicable NOM for the product, master supply agreement with communication and SLA clauses, and quarterly metric log per supplier and per zone.