How a fashion label lost $180k in six weeks to a single silent payment error

This is one of the cases we get called in on most often: a store that looks like it’s working. Orders are coming in, support is quiet, conversion rate looks normal. But revenue is down and no one can explain why.

The symptom

In this case, a fashion label on WooCommerce noticed their revenue was about 14% below forecast for six weeks running. Not a crash — a slow bleed. Their checkout completion rate in GA4 looked normal. Their payment gateway dashboard showed normal approval rates. Nobody flagged it.

The diagnosis

When we got access, the first thing we did was check the order status distribution in WooCommerce. We saw an unusually high ratio of “pending payment” orders that were never transitioning to “processing.” These weren’t abandoned carts — the customer had reached the payment step, submitted, and the order was created, but the gateway callback was timing out before it could update the order status.

The root cause: a hosting provider had silently changed their outbound request timeout from 30s to 8s as part of a “performance optimization.” The payment gateway’s webhook was taking 9-12 seconds on average. Every single one was timing out.

The fix

We patched it in three steps: increased the timeout threshold, added a retry queue for failed webhooks, and implemented a reconciliation job that catches any orders stuck in pending for more than 15 minutes and re-queries the gateway directly.

We also rebuilt their order status monitoring so this class of issue surfaces as an alert within 30 minutes rather than six weeks.

The numbers

$180k recovered in the 30-day window after the fix. That’s money that was sitting in a pending queue — some of it we were able to manually process, the rest was refunded and recaptured.

“They found the leak in 20 minutes. The old agency spent two months on it.” — Client, fashion label