# WordPress and WooCommerce

> WooCommerce inherits both WordPress's flexibility and its main weakness: a plugin ecosystem that has to coexist cleanly. A good part of my work is understanding what's been layered on over time before proposing a fix or an improvement.

- Source canonique : [https://allaux.fr/en/wordpress-woocommerce](https://allaux.fr/en/wordpress-woocommerce)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## What I do on WordPress and WooCommerce

- **Troubleshooting plugin conflicts** — Diagnosing an error or a malfunction caused by the interaction between several extensions.
- **Custom plugin development** — A specific feature built as a proper plugin rather than bolted onto a theme.
- **Migration to or from WooCommerce** — Carrying over a catalogue and order history from another platform, or the other way round.
- **Performance** — Cutting the number of queries and page weight, often tied to a build-up of active plugins.
- **Security** — WordPress is a frequent target for automated attacks; updates and configuration hardening.
- **Building specific features** — Pricing, shipping or availability rules that don't exist in any standard marketplace extension.
- **ChatGPT Ads extension for WooCommerce** — OpenAI pixel and Conversions API, compatible with HPOS, the block checkout and consent plugins: built and installed by me. ([/wordpress-woocommerce/extension-chatgpt-ads](/wordpress-woocommerce/extension-chatgpt-ads))

## The real risk is the plugins

WordPress itself is a stable system. What makes a WooCommerce site fragile is almost always a build-up of plugins, sometimes poorly maintained, that interact badly with each other or with a core update. Before adding a new extension, I check whether the need can be covered another way, or whether a plugin already in place has a redundant feature.

Block-based page builders make visual layout easier, but also add a further layer of code to maintain. I work with what's already in place, without forcing a tool change unless a concrete problem justifies it.

## On plugin count

> A site with a lot of plugins isn't automatically badly built, but every extension added increases the risk of conflict at a future update. I flag it when I spot one that duplicates another, rather than simply adding one more to answer a one-off request.

## FAQ

### Do you work with Elementor or other page builders?

Yes, I can work on them, without imposing them by default. If they're already in place, I work with them rather than proposing a full rebuild with no clear technical reason.

### How many plugins is reasonable to have?

There's no universal number: it depends more on how well each plugin is maintained than on the total count. An audit helps spot redundancies or risky extensions.

### What hosting do you recommend for WooCommerce?

Hosting sized for WordPress and its database, with properly configured caching. Generic shared hosting quickly becomes limiting once the catalogue or traffic grows.

### Do you migrate from Shopify or PrestaShop to WooCommerce?

Yes, in both directions depending on the need. Carrying over the catalogue and orders is prepared with a prior audit of the existing data.

### Do I need a custom theme, or is a marketplace theme enough?

A marketplace theme often works very well as a base. I customise it rather than start from scratch, unless the design you want strays too far from what the theme can cleanly do.