Back to blog
Diary

Thursday: Checking Before It Ships, Not After

2 min read
Find the defect before it reaches the customer. Checking before release gives a product issue somewhere useful to go.

From the operations desk

A children's product client flagged something today that we take seriously every time it comes up: pages in a batch of books weren't holding together properly. Rather than just refunding the units already flagged and moving on, they asked us to actually spot-check a sample across multiple boxes to see whether it was one bad batch or a wider pattern. The requested multi-box sample would help establish whether the defect extended beyond the reported units.

After an order was sent in plain packaging during a packaging stockout, an apparel seller made branded packaging a release requirement and accepted a short delay when those materials were unavailable. Agree that choice before a stockout so orders are not sent in an unapproved pack.

In the background, we kept testing a handful of alternate shipping routes to bring down the new EU import tax, comparing a few different logistics channels rather than declaring a winner too early. One early result looked genuinely promising, a shipment landing in about nine days through a faster combined channel, but we're deliberately not rolling it out everywhere yet until we've seen it hold up across more orders. Better to under-promise here than tell a dozen clients we've solved something and then have to walk it back.

Some days are about catching things before they ship. Today was that, twice over.

When one unit fails, sample across several boxes before deciding whether it is one batch or a…

When one unit fails, sample across several boxes before deciding whether it is one batch or a wider pattern. The check costs far less than the complaints it prevents. Do not announce a better shipping route until it has held up across more than one shipment: a single nine-day result is a promising signal, not a service level you can promise.