A WooCommerce shop was updating stock by hand with a daily CSV export. A custom WordPress REST API endpoint, secured with a permission callback, lets the warehouse system push stock changes straight into the site.
A client wanted WooCommerce to reward customers who hit their step goals on a fitness tracker. Making the API call on every page load fell apart fast, so here is how we synced the data with a background job and a custom table instead.
A founder tried to build a new business model by stacking five subscription, booking, and membership plugins on WooCommerce. Here’s why that breaks, and why your core logic should be your own code, not a plugin.
A WooCommerce checkout threw intermittent 500 errors and the logs were useless. Here’s how logging with context, the user, their cart, the gateway, turns a noisy debug.log into error logging you can actually act on.
A freelancer rebuilt WooCommerce from scratch and left a store that broke on every plugin update. Here is why building with WordPress hooks and filters beats fighting the framework.
A client WooCommerce order emails looked fine in Apple Mail but broke in Gmail. The reason: Gmail strips CSS from the head. Why inlining your styles is the only reliable fix.
A WooCommerce shipping module was one 800-line if/else function. Refactoring it with the strategy pattern turned adding a new carrier from a 40-hour job into an hour of work.
A client needed three custom post types fed by three APIs. Instead of writing near-identical save functions, I defined one PHP interface as a contract and a single function to save any CPT that implements it.
I got a Slack message from one of our project managers. A client’s WooCommerce shop, a big one with thousands of products, was crawling. Product…
A client needed to import users from a clean CSV and a messy pipe-delimited file. The strategy pattern kept the importer clean instead of a tangle of if/else blocks.