The other route — on an existing platform

WordPress, PrestaShop and Shopify sites

My trade is custom work. But not every project deserves it. When the need is standard, WordPress, WooCommerce, PrestaShop or Shopify do the job for a fraction of the price — and I install those too, with the same care.

Describe my project

What I build

WordPress showcase site

A few pages, a blog, a form, your opening hours and your map. This is the commonest case, and the one where a well-installed CMS has nothing to envy custom work: WordPress runs a large part of the web, and runs it well.

WooCommerce shop

The shop grafted onto WordPress: you keep your site and your blog, and sell from the same admin. Excellent when it is the content that brings customers in — you do not separate what attracts from what sells.

PrestaShop shop

Catalogue, variants, carriers, VAT, invoices: PrestaShop handles all of that natively, and your data stays with you. The right call when the shop is the business and you want to keep control of your own rules.

Shopify shop

For when you want to sell without dealing with hosting, updates or security, and accept the monthly rent that represents.

Catalogue migration

I take your catalogue and publish it, variants included, from your file. Elsewhere, the quote steps up as soon as the number of references climbs. Here, a large catalogue does not become a budget of its own.

The three shops, known from the inside

PrestaShop 8 and 9, WooCommerce, Shopify: I know the rules each one has, what they really accept and what breaks in silence. The result: a catalogue that arrives complete, with no missing listing and no forgotten variant.

Taking over an existing site

A slow site, broken by an update, or left half-finished by the previous supplier. We put it back on its feet before talking about a rebuild: that is often the most profitable spend.

Speed and search, even on a CMS

Compressed images, plug-ins cut back to the strict minimum, titles and descriptions properly written, structured data. A CMS is no excuse for a slow site.

How it works

  1. 01

    The custom test

    First question, and it is free: does your need already exist as a plug-in? If it does, the CMS wins. If you have to work around the tool by the second function, it loses — and I will say so plainly, even though the invoice is smaller.

  2. 02

    Choosing the platform

    WordPress for content, WooCommerce to sell from that content, PrestaShop for a catalogue you want to control, Shopify to sell quickly with nothing to administer. All four are good tools: the choice follows your situation, not my habits.

  3. 03

    Installation and styling

    A clean install, a theme matched to your identity, plug-ins chosen one by one. No all-in-one theme loading forty components to use three.

  4. 04

    Content and going live

    Pages, products, images, redirects if the site already existed. Search visibility is prepared here, not afterwards.

  5. 05

    Handover

    You leave with your own access and enough to manage your content alone. That is the difference between a site that lives and a site frozen on delivery day.

Why this page exists

The top of this site says “No template. No theme. Custom only.” That is my trade and what I stand for. But if you have read this far, you may have a simple project and a tight budget, and you deserve an honest answer rather than a quote that sends you away.

A tradesperson who wants five pages, their opening hours, their photos and a form does not need me to write a site line by line. WordPress does that very well, for far less and far faster.

Where the real line lies

It is not between cheap and expensive. It is between a need someone has already solved and a need that belongs only to you.

A blog, a showcase, a classic catalogue with basket and carriers: all of that exists, it is proven, and rewriting it would be waste.

On the other hand, a player that follows the words of a song, a search cut down to make and budget, a radio that keeps playing as you change page, a match analysis generated from real statistics: nobody sells that as a plug-in. Trying to get there by stacking modules costs more than writing it, and gives you a site twice as slow.

What does not change

Whichever route you take, the underlying work is the same: compressed images, fast pages, a silo structure, titles and descriptions written one by one, structured data. A slow WordPress site is not a fate, it is a badly installed one.

Still hesitating? Describe your project in two lines: I will tell you which of the two routes costs you less, including when it is the one that earns me less. Or read first about custom websites.

Frequently asked questions

Why is this cheaper than custom work?

Because a large part of the work is already done: the admin panel, user management, the catalogue, the basket and payments already exist and are maintained by thousands of contributors. I do not write those bricks, I assemble and tune them. The time spent is therefore much shorter.

WordPress, WooCommerce, PrestaShop or Shopify — which one?

WordPress alone if the heart of the site is content and you are not selling yet. WordPress with WooCommerce if the content brings the customers and the shop is grafted onto it: everything stays in one admin. PrestaShop if the shop is the business, with a real catalogue, variants and VAT rules you want to control. Shopify if you want to sell without touching the technical side and the monthly subscription does not bother you. We look first at what you sell and to whom; the platform comes after.

Are my products included in the price?

No. The price builds the shop, it does not fill it: those are two separate lines on the quote. First line, building the shop — categories, variants, carriers, VAT rates. That work is the same whether you have 10 products or 10,000, so it is a fixed price. Second line, entering your products: charged separately, per batch of 100 listings. It is on that second line that I do not play the usual game: elsewhere the rate steps up as soon as the number of references climbs, here a large catalogue does not blow up the quote. Send me your product file and a few photos: I quote on what I can see, never blind.

And if I have no product file?

Then that is the first thing to build, and it is charged separately: the references, prices, descriptions and photos have to be gathered. A well-filled spreadsheet is worth several days of typing saved — including for you, later, the day you change tools. If the information exists nowhere, we start with a short batch of the products that actually sell, and fill in afterwards.

When should I move to custom work?

The sign is always the same: you start working around the tool. A paid plug-in doing three quarters of what you wanted, then a second to make up for the first, then a developer to make them live together. By that point the sum of the patches exceeds the price of building it properly — and the result stays fragile.

Is search engine work included, even on a CMS?

Yes, and it is exactly the same work as on a custom site, because it happens before the tool is chosen: who buys what you sell, in which words those people search, where they are, and what your competitors forgot to cover. That is where the sections, the titles and the pages to write come from. A WordPress organised around that plan does far better than a WordPress filled in as you go. None of which promises a position in Google: nobody can guarantee that.

Who handles the updates afterwards?

That is the real trade-off of a CMS, and it has to be said before signing: WordPress and PrestaShop need regular updates, or the site becomes a way in. Either you do them, and I show you how, or we arrange ongoing cover. Shopify handles it itself, which is what you pay for every month.

Can we start on a CMS and move to custom later?

Yes, and it is often the right path: get live quickly and cheaply, watch what visitors actually do for a year, then build the functions that use has revealed. You keep the domain name, the content and the search visibility earned — nothing is lost.

Will you take over a site built by someone else?

Yes, provided we look at what is inside it first. A site overloaded with badly configured plug-ins can be repaired; a site built on a theme abandoned five years ago has to be redone, and saying so straight away saves you paying twice.

The other trades

Page updated on — written by Yvan Barbaggio.

A question that is not on the list? Ask it in two lines, I answer within 48 working hours.

Revenir en haut de la page