Keep the shop.
Lose the headache.

Plugin conflicts. Worry every time something updates. A small change that turns into a project. Your shop can work differently.

If your shop is down right now.

Start with a backup, then talk to your host or support team. Follow WooCommerce’s conflict-testing guide on a test copy, so changing themes or turning plugins off does not interrupt live orders. Reproduce the failing journey there, and test again after each change. The guide was checked 12 November 2026.

A move is a planned project: a rehearsal, a switch you agree and a way back. It is not a way to recover a shop that is down today.

Should I leave WooCommerce?

Keep WooCommerce if it still fits the way your team works and a targeted repair or a new customer-facing shop can solve the problem. Consider Gax when you want someone else to run the shop software, and your essential ordering, payment and delivery needs fit the agreed setup. Check that fit before paying to move.

WooCommerce’s own support guide says most problems come from outdated software, theme conflicts and plugin conflicts. It says almost half of the contacts it receives come from third-party themes and plugins.

Repair is usually the right answer when one identified plugin or theme is the cause, and removing or replacing it ends the problem. If that is where you are, Revitt’s WooCommerce support is the repair route.

Plan the move when each fix reveals the next conflict, or when the shop work keeps landing on you and nobody can tell you what will break next.

For a real example of keeping WooCommerce, Revitt rebuilt The Embroidery Shed’s customer-facing shop while the team kept its familiar WooCommerce admin for products and orders. That is Revitt’s WooCommerce rebuild, not evidence of a completed Gax migration.

WooCommerce self-service guide, checked 7 November 2026.

Slow in the admin? That is a different problem.

A shop front can load quickly for customers while the admin crawls. On WordPress the shop front is often served from a cache, but each admin screen runs the shop software and its plugins again, so the products list, an order screen or a stock change has to be worked out on the server. A public WordPress support thread describes that split. One thread shows it is possible; it does not tell you how common it is.

Finding the cause is worth doing before you spend anything. Time the product page a customer sees, then the products list and an order screen in your admin. On a test copy, turn plugins off and back on one at a time, as WooCommerce’s conflict guide sets out. That points at a suspect rather than a verdict: a slow admin can come from your hosting, one plugin, a service your shop talks to, a background job or the size of your catalogue. Your host can tell you whether your plan meets WooCommerce’s own server requirements.

Then compare the three answers: a repair and what it buys you, the upkeep each month, and the full cost of a move. Sometimes a repair settles it. Sometimes the admin is slow because of how much software and hosting the shop is carrying, and a move is the better answer. Decide on the diagnosis and the whole cost, not on the frustration alone.

Our own test cannot answer this for you. It measured catalogue and basket requests on one CPU and 1 GiB of memory. It says nothing about how fast your admin screens feel, your page speed or your sales. What that test covers →

Who does the work each week?

Updates, backups, a plugin that breaks checkout, a payment provider that changes something, a developer’s invoice. On WooCommerce that work is yours to arrange: you, your host, a developer, or a mix of all three. Write down who does each job now, and what it cost you last year. Repeated repair bills, and one person who alone knows how your shop is wired, are real costs even when the shop is trading.

If the admin is quick and the bills are rare, a move has less to fix.

On Gax, hosting and platform updates are run by Revitt and included in the monthly price. Fixing a fault in Gax itself is not a chargeable change. Support responsibilities and response terms are agreed with you for your shop, so settle them before you commit.

If you would rather one company answered for the technical side, that is what Gax is: built, hosted and run by Revitt, and you deal with the people who do the work. Meet the team behind your shop. When you compare suppliers, check three things in writing: who actually runs the platform, what is included each month, and what is quoted separately.

Compare the whole cost before deciding.

Compare the same period on both sides. For your current shop, include hosting, paid plugins, maintenance and payment processing. For Gax, include setup, the monthly plan, any agreed migration or extra integrations, third-party subscriptions and payment processing. Gax charges no transaction fee; your payment provider still charges its own fees. Include the work needed to leave either platform later.

A move is not automatically cheaper. Use the plan requirements and cost comparison, then send us your shop address and the jobs it must keep doing so the scope can be agreed in writing.

What a move cannot promise.

Your theme’s code and your WordPress plugins do not run on Gax. Nothing here runs them. What a plugin does is rebuilt as a small integration, or planned with you first. Not every plugin has a like-for-like replacement. Extra custom integrations are agreed in writing and quoted before work starts.

Saved cards and stored payment details belong to the provider that holds them. Whether they can move is a separate check with that provider: some allow a planned transfer, many do not, and we assume nothing. Where a provider cannot transfer them, the customer enters their card details again.

What a move covers, line by line →

Bring the work you’ve already done.

On the growing shop plan, we agree in writing which products, options, customers and past orders move with you. We check those records together and agree the switch before customers see any change. The small shop plan uses standard setup: you enter your own products, photos and text.

The move, in four steps →

Small shop: £19.99 a month + VAT, with £299 + VAT setup. Growing shop: £99 a month + VAT, with £999 + VAT setup. What each price covers →

Your workflows, mapped before the move.

We map your theme and plugins before the move. Their code is replaced or rebuilt; it does not move into Gax.

Explore the shop examples: The Embroidery Shed for product options, decoration positions and a mixed size run; Trig Prints for a design tool, terrain and pricing that work together.

Custom plugins and unusual ways of working are the first thing to raise: tell us what you rely on.

A better way to add what you need.

We connect the tools your shop needs and build missing features around how you work. We agree what the setup includes, and quote anything extra before that work starts.

A shop that saves to your phone, live shop numbers and AI tool connections come with the shop. Revitt runs the move, with more than 15 years of hands-on ecommerce experience.

What moving actually changes, and the one catalogue and basket test →

Payments are the sticking point →