Why a plugin and not code in the theme?
The theme changes with the design; the plugin holds the business logic and keeps working if you change theme. That is why Woodofy is a plugin and not a folder inside each store’s theme.
I build custom WordPress and WooCommerce plugins when none in the plugin directory does what your business needs. Code of its own with versions, not patches in the theme. Woodofy is a plugin that three production stores share, and ix-wp-envsync is published as open source.
Plugins for WordPress and WooCommerce, from the idea to the installed version
Code of its own under version control, and a package that installs the same way on every site
A fix is published once and reaches every site that uses the plugin
Remote from Havana
Concrete problems that already came up in a real project, not a list of promises.
In Cuba the customer picks a province and a municipality, and shipping depends on weight and zone. Woodofy solves it in one plugin, not with patches in every store.
Three stores share the same core. On 8 October 2026 three versions were released in a single day and all three stores got the same code, without touching each one by hand.
API permissions, nonces on AJAX requests and no customer data in the error log. It was hardened in the core and protects all three stores at once.
ix-wp-envsync is an open source plugin, licensed GPL-2.0 or later, that installs like any other and is run from WP-CLI.
Also, Woodofy Stats is a multi-vendor plugin with per-region analytics and Jest and PHPUnit tests that runs on 2 stores, and WC Caribbean Online is a WooCommerce payment gateway with an external wallet over an API, HPOS-compatible. Woodofy is in the three-store case and ix-wp-envsync has its own page.
You tell me which piece of your business logic no extension covers. If you already have a plugin of your own, I read its code before touching anything.
We decide what goes in the plugin and what in the theme. The logic lives in the plugin and keeps working even if you change theme.
I write the plugin under version control with security in mind from the start: permissions on the API, nonces on AJAX and no customer data in the error log.
The plugin goes through staging before it reaches production, also when WordPress or WooCommerce update.
Each fix is released once and reaches every site that uses the plugin. We agree who maintains it: me, or I leave it ready for your team.
The theme changes with the design; the plugin holds the business logic and keeps working if you change theme. That is why Woodofy is a plugin and not a folder inside each store’s theme.
We agree it when we talk about scope: I can maintain it, or leave it ready for your team. On Woodofy I joined in July 2026 to maintain, harden and extend it.
Yes. Woodofy existed since 2025, created by the team, and I added location-based shipping, checkout fields, security and translation. Before touching anything I read the code that is already there.
Changes go through staging before they reach production. Woodofy and ix-wp-envsync are released with a version number, so you know which code runs on each site.
Tell me what you sell, to whom and what has to happen. I reply within 24 h.