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 one checkout field, and the old code tempted me into a week-long refactor. I shipped the field with two WooCommerce hooks instead, a reminder that a working feature on time beats a perfect rewrite that never ships.
A WooCommerce client needed clean URLs for an old custom event plugin, and the Rewrite API alone kept getting fragile. Here is why a proper object-oriented routing system holds up better as a WordPress site grows into an application.
A WooCommerce add to cart button was failing silently for some users, with no logged errors to go on. Here is how a few lines in wp-config.php turn on WordPress error logging so you can see what is actually breaking on a live site.
A client’s custom events plugin had grown into tangled procedural code that broke every time they touched it. This is how object-oriented programming, and the pattern behind WordPress hooks, keeps a plugin maintainable as it grows.
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 client added an email signup form with a heavy marketing plugin and wrecked his site speed. Here’s how to build a lightweight form that posts to your provider’s REST API instead, with full control and no bloat.
Duplicated pricing logic across half a dozen WooCommerce templates turned a 30-minute change into a day of risky edits. The DRY principle, and one function as the single source of truth, is the fix.
A junior dev fixed a 404 by flushing WordPress rewrite rules on every page load, which wrecked performance. Here’s how to register rules on init and flush them only once, when they actually change.