WooCommerce for an Excavator & Skid-Steer Attachments Company

What I Found — and Fixed

1. 01 Search that felt like Amazon, not WooCommerce. The default search had no typo tolerance, no SKU lookup, and sorted results alphabetically instead of by relevance. The obvious fix was a paid search service — instead, I spent one day checking whether the catalog actually needed one. It didn't: the whole thing fit in a 40 KB file the browser could hold in memory. No subscription, no per-query cost, and results that feel instant.
2. 02 Products that were live, but invisible. Most of the catalog was already synced to Google Shopping, but shipping costs, categories and feed errors kept hundreds of listings from actually showing to buyers. I replaced the old once-a-day feed with a direct connection to Google's own API and fixed the underlying data — approved listings went from 603 to 806. Read the full story
3. 03 A $2,496 mistake, caught before it shipped. While going through the shipping logic, I found a 394 lb product priced at a flat $28 to ship — its real freight cost was closer to $2,496. It had been live like that, unnoticed, every time someone ordered it. One weight-based rule fixed it for good. Read the full story
4. 04 A freight API doing six times the work it needed to. The shipping-quote integration was calling the carrier's API up to 6 times for a single 3-item cart. A caching fix brought that down to as little as 1 call — same result, 92% fewer requests overall.