WooCommerce or a custom-built shop? What we learned moving one to the other

This year we moved an online shop off WooCommerce onto a platform written from scratch. Not because WooCommerce is weak — but because it had come to cost more than it gave back. This article is about how to tell whether you are in that situation. Or, more likely, how to tell that you are not.

"More likely" because in most cases the right answer is to stay on WooCommerce. Let us start there.

When WooCommerce is the right call — which is nearly always

If you sell physical products with size and colour variants, courier delivery and card payment, WooCommerce does everything you need. It is mature, it has ready-made integrations for Romanian couriers and invoicing, you can run it yourself, and you can always find someone to work on it.

That last point matters more than it seems. A WooCommerce shop can be taken over by any developer. A custom-built one can only be taken over by someone willing to learn another person's code — and that costs more, or cannot be found at all.

The rule we use: if you cannot name a concrete feature WooCommerce is unable to deliver, you have no reason to leave it.

"I want it faster" is not a reason — a properly optimised WooCommerce is fast. "I want a special design" is not a reason — the theme is custom-built either way. "I want to be independent" is not a reason, it is a feeling.

What happened at Cary Studio

The client is a curative pedicure salon in Bistrița. It started simply: a site with online booking. Then they wanted to sell the products used in the salon — we added WooCommerce, the natural choice. It worked.

Then came the requirements that no longer fitted.

• Gift vouchers that validate at the front desk. Not just a discount code — a voucher with a PDF emailed out, a QR code printed on it, which the receptionist scans with her phone and marks used on the spot, exactly once.
• Bookings and orders in one place. The salon had the diary in one system and orders in another. They wanted one working day, not two dashboards.
• An app for the team. The staff work between two clients, phone in hand. A WordPress admin panel designed for a desktop does not get used in that situation — it gets abandoned.

Plugins exist for every one of these. We evaluated them. The problem was not that they do not exist, but that three plugins from three different authors, which have to talk to each other and to the booking system, form a chain where any link can break at an update. And when it breaks, it does not break in your office.

What we built instead

A platform in PHP and MySQL, no framework, written around the salon's workflow: its own shop, bookings, vouchers and the team app, all on the same database, with 250 automated tests running on every change.

A few things we could only do once free of the platform's constraints:

• Payment confirmed solely through the server-to-server notification. Nobody can mark an order paid by returning to a URL in the browser. The notification's signature is verified cryptographically, and the same notification received twice does not produce two payments.
• Stock deducted inside a transaction with row-level locking. Two simultaneous buyers, one last item — exactly one gets it. Not "usually", but guaranteed.
• Invoicing that does not block the order. If invoice issuing fails, the order proceeds and the administrator gets a retry button. In a chain of plugins, an invoicing error stops everything.
• Vouchers issued only on confirmed payment, voided automatically if the order is cancelled, with a QR generator written in PHP.

What it actually cost

Here I will be honest, because nobody writes about this part.

The threshold, from our experience: a custom shop starts to make sense from roughly €3,000 upwards, and only if you have a feature the platform cannot deliver. Below that you are paying for independence rather than capability — and independence is not something you can sell to your own customers.

The four questions that decide it

1. Can you name the missing feature? If the answer is a feeling ("it feels clunky", "I want something of my own"), stay on WooCommerce. If it is a concrete sentence — "I want the voucher scanned at the desk and marked used" — then the conversation is real.
2. How many plugins have to cooperate? One or two, fine. Beyond four, mutually dependent, you have already built a custom system — just out of parts you do not control.
3. Who maintains it in two years? With WooCommerce, anyone. Custom-built, whoever wrote it or someone willing to learn. Ask this before, not after.
4. What happens when the platform changes? WordPress changed its editor and broke entire themes. A plugin abandoned by its author becomes your problem. How much does that hurt you?

A middle road few consider

You do not have to choose black or white. You can keep WooCommerce for the catalogue and orders — where it is very good — and write only the piece that does not fit: your own voucher module, a separate app for the team, one specific integration.

At Cary Studio we did not take that route because the bookings, the vouchers and the salon app all had to talk to each other. When three quarters of the system is custom, there is little point in the last quarter being anything else. But if your case is a single piece, the hybrid is cheaper and safer.

In short

• Stay on WooCommerce if you cannot name the concrete missing feature.
• Migration makes sense from ~€3,000 upwards, and only for a functional reason, not an emotional one.
• More than four interdependent plugins = you already have a custom system, without control over it.
• Ask from the outset who maintains it in two years.
• The hybrid — platform plus one custom-built piece — solves most borderline cases.