No dramatic new-client stories today — this was an operations day, plain and simple, and I actually think those are worth writing about too, because they're most of what running fulfilment at this scale actually looks like.
A typhoon had been sitting over the region for the past couple of days, and it finally caught up with us: inbound stock for several accounts got delayed in transit, including one seasonal product a client was waiting on to fulfil a batch of backorders. Nothing to do but tell people honestly — "it's weather, not us, here's the new expected date" — and keep the updates coming rather than going quiet, which is the thing that actually damages trust more than the delay itself.
The bigger project of the day was working through a big batch of packages, more than seventy of them, that had bounced back to one of our overseas warehouses because of packaging issues on the outbound side. We rebuilt the whole batch, got new tracking numbers assigned, and set up a proper log so both our team and the client's support staff could see status in one place instead of us pasting tracking numbers into chat one at a time forever. Boring to describe, genuinely satisfying to finish.
Also kept chipping away at a custom jewelry order — client settled on titanium steel over silver once we walked through the price difference, which is usually how that conversation goes once the actual numbers are on the table instead of the idea of "pure silver" sounding nice in the abstract.
Good day to remember that half of this job is just making sure a package that went the wrong way finds its way back.
Need to check how a change affects a live product?
Send the product, destination and order context on WhatsApp (wa.link/dropship). We will help you separate confirmed facts from operational next steps.
Consult on WhatsApp →