When a small custom WordPress plugin beats another off-the-shelf one
I'll start with the unpopular part: most of the time you should not get a custom plugin. A well-maintained plugin used by thousands of sites has been tested in ways a one-off build never will be. If one does what you need, install it.
But consider a hypothetical WordPress or WooCommerce site. A business needs one specific thing, such as a delivery-day rule, a custom field on an order or a small integration with their booking system. Nothing does exactly that, so they install a big multipurpose plugin, use a small part of it, and add a snippets plugin with some code copied from a forum to fill the gap. Now the site depends on three things to do one job.
Signs a custom plugin is the better fit
- You're using a large plugin for one small feature. You carry its updates, settings screens and possible security issues for something a small, focused piece of code might handle.
- The logic is specific to your business. Pricing rules for your trade customers, how your orders get tagged for your courier. No plugin author will build that exactly.
- You have undocumented code in your theme's
functions.php(which is lost if you switch themes) or a pile of snippets in a snippets plugin that nobody fully understands. Snippets plugins survive theme changes, but undocumented snippets are still hard to maintain. - Two plugins are fighting. Sometimes the fix is a small plugin that replaces the overlap rather than another patch on top.
- You need to connect to a system with an API (a CRM, an inventory tool, an internal spreadsheet service) and the available connectors are either missing or overkill.
Signs you should not go custom
- Payments, security, backups, SEO basics, forms, caching. Use established plugins. These are hard to get right and well served already.
- The requirement is still changing every week. Wait until the process settles.
- Nobody will be around to update it. A custom plugin is small, but it still needs checking when WordPress, WooCommerce or PHP versions move.
What "done properly" looks like
If you do commission a custom plugin, from me or anyone else, these are fair things to expect:
- It's a plugin, not theme code. Functionality belongs in a plugin so it survives a theme change. That's the approach WordPress's own developer handbook describes.
- It uses WordPress hooks (actions and filters) instead of editing core, theme or other plugins' files. That makes updates far less likely to overwrite or break it, though it still needs testing after major updates.
- Inputs are sanitised and outputs escaped, with capability checks on any admin action. These are the basic security practices in the official handbook, and they're not optional.
- For WooCommerce, it uses WooCommerce's CRUD APIs for orders rather than reading database tables directly. Depending on the store, orders may live in the newer High-Performance Order Storage (HPOS) tables or the legacy posts tables; the CRUD APIs work with both, and the plugin should be tested on the configuration(s) your store uses.
- It's in version control and you get the code. You should own it and be able to hand it to another developer.
- There's a short README: what it does, where its settings are, what to check after updates.
Questions to answer before you brief anyone
- What exactly should happen, step by step, and for which users? (Customers, staff, admins.)
- What happens today, and how long does it take someone by hand?
- What plugins have you already tried, and where did they fall short?
- Which other plugins or services does it need to work alongside?
- Who will notice if it stops working, and how quickly?
Write those answers down and you'll get far more accurate quotes, whoever you ask.
Where I fit in
I build custom WordPress plugins and fix WordPress and WooCommerce sites. Often the right advice is "you don't need a custom build, change this setting" or "replace these two plugins with one", and I'm happy to say so. When custom does make sense, I aim to keep it small, documented and yours.
If you've got a WordPress or WooCommerce site doing something awkwardly, send me a note describing the job it needs to do.