---
title: "Custom WordPress plugin developer for WooCommerce"
description: "Custom WordPress and WooCommerce plugins with their own code and versions. One plugin running in three stores and another published as open source."
url: https://lazarosantana.dev/en/services/custom-wordpress-plugin/
---

service · plugins · WordPress and WooCommerce

# Custom WordPress *plugin*

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.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See the case](https://lazarosantana.dev/en/cases/tiendas/)

What I do

Plugins for WordPress and WooCommerce, from the idea to the installed version

How

Code of its own under version control, and a package that installs the same way on every site

Result

A fix is published once and reaches every site that uses the plugin

Mode

Remote from Havana

// what it solves

## What it solves

Concrete problems that already came up in a real project, not a list of promises.

01

### Logic no extension covers

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.

02

### One codebase, several sites

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.

03

### Security reviewed in one place

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.

04

### Code you can read

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.

// proof

## Real proof

**3** production stores running the same plugin, Woodofy

**270+** commits in ix-wp-envsync, an open source plugin

**15*+*** own plugins in production

**GPL** open license of ix-wp-envsync, with the code on GitHub

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](https://lazarosantana.dev/en/cases/tiendas/) and ix-wp-envsync has [its own page](https://lazarosantana.dev/en/projects/ix-wp-envsync/).

case 03 · WooCommerce stores · Cuba

### Three stores, one engine

A WooCommerce plugin with Cuban addresses, zones and shipping, shared by three production stores.

*tubandeja.com*

Home page of tubandeja.com, one of the three stores

// how it works

## How it works

01 · the idea 02 · plugin or theme 03 · development 04 · staging 05 · versions

01

### The idea

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.

- business logic
- existing plugin
- scope

02

### Plugin, not theme

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.

- separate logic
- no theme patches

03

### Own code

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.

- versions
- nonces
- permissions

04

### Staging

The plugin goes through staging before it reaches production, also when WordPress or WooCommerce update.

- staging
- production
- updates

05

### Versioning

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.

- version per site
- maintenance
- for your team

Shipping depends on weight and zone, and no extension does that

That is business logic, it goes in a plugin

And if I already have one?

Before touching anything I read the code that is already there

example conversation

✓ approved plugin settings · mockup

hardened once in the core

local *→* staging *→* production

changes never reach production without going through staging

three versions in one day

// questions

## Frequently asked

### 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.

### Who maintains the plugin after delivery?

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.

### Can you extend a plugin that already exists?

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.

### What happens when WordPress or WooCommerce update?

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.

// let’s talk

## Got something like this in mind?

Tell me what you sell, to whom and what has to happen. I reply within 24 h.

[Request a quote](https://lazarosantana.dev/en/contact/#form)
