Custom WordPress development
Custom plugins, editor blocks, WooCommerce and integrations with your ERP or CRM. WordPress run as a software project: code in Git, staging, and deployments that are not done by hand in production.
Soamee develops on WordPress: custom plugins, editor blocks, WooCommerce stores, API integrations with ERP and CRM, performance optimisation and headless architectures with the front end in Astro or Next.js. WordPress fits when the site is mostly content and the team wants to edit it without going through development. It stops fitting when it is asked to be an application. We work with the code in Git, a staging site with a copy of production and automated deployment, and we always start from an audit of what is already there: plugins, PHP version, theme code, performance and security.
What we build on WordPress
Six areas of work. Most projects combine two or three.
Custom plugins
The business logic no plugin in the directory covers: pricing rules, private areas, approval flows, importers. Modern PHP, WordPress hooks and tests, in a plugin that does not depend on the theme.
Editor blocks
Custom blocks and patterns with theme.json so the content team can assemble pages from the editor without leaving the design. No visual builders loading extra CSS and JavaScript.
WooCommerce
Extensions, custom checkout, payment gateways and order and stock sync with the ERP. Details on the WooCommerce page.
API integrations
We connect WordPress to ERP, CRM, email platforms and in-house services through the REST API, webhooks and queues, with retries and a log of what is sent.
Performance
We measure with real Core Web Vitals, check which plugin adds each query and each script, and sort out caching (object and page) and images. Measure first, then change.
Headless WordPress
WordPress as the CMS with the front end in Astro or Next.js. For sites that want to keep the WordPress editor and need a faster, more controllable front end.
The difference is in how the work is done
Most problems in a WordPress site come from how it was built and maintained, not from WordPress.
Is your WordPress giving you trouble, or not scaling?
Request the audit →An update, tested before it goes live
We back up the database, apply the updates on staging, and an automated test walks through catalogue, cart and checkout. If something fails, it fails on staging and a customer never sees it.
On the right, an example WP-CLI session. Plugin names and versions are illustrative.
$ wp plugin list --update=available --format=tablewoocommerce 9.x availableseo-plugin x.y available$ wp db export --tables=wp_options staging-before.sql$ wp plugin update --all$ npx playwright test --project=checkout✓ catalogue, cart and checkout clean on staging# only if the tests pass does it get promoted to productionWhen WordPress, and when something else
WordPress is a good option if…
- The site is mostly content: blog, pages, editorial catalogue.
- The marketing team wants to publish and edit without opening a ticket.
- You need a WooCommerce store and the custom logic fits in extensions.
- You already have a WordPress site with years of search rankings you should not throw away.
A different architecture fits better if…
- The product is an application with states, role-based permissions and long processes: custom software.
- The front end needs speed and full control but the team wants to keep the editor: headless WordPress.
- Maintaining the current WordPress costs more than rebuilding it: migrating to Astro.
- The store has grown to need a managed platform: Shopify Plus.
How we start
Audit
We review active plugins, PHP version, theme code, slow queries and security status. The result is a prioritised list of what to fix, what to rewrite and what to leave.
Environment
We put the project in Git, with a reproducible local environment in Docker and a staging site with a copy of production.
Development
Plugins, blocks or integrations in short cycles, with code review and tests on the flows that move money or data.
Deployment and support
Release to production from the pipeline, close watch over the first days and, if you want it, an ongoing maintenance plan.
Tech stack
Frequently asked questions about WordPress development
Do you build custom WordPress plugins?
Do you work with WooCommerce?
Can you take over a WordPress site that already exists?
When do you not recommend WordPress?
What working environment do you use?
Tell us what your WordPress does and what it lacks
We review the site and tell you what can be fixed, what is worth rewriting and whether WordPress is still the right tool.
Tell us your challenge. We'll propose a solution.
No commitment. Within 24 hours, you'll receive a proposal with scope, timeline and budget. No fine print.