Building or rebuilding an online shop
The rest of this site is about shops that already exist and are going wrong. This section is about what comes before: choosing a platform, knowing what you will pay, preparing what you have to supply, and deciding whether a rebuild is really the right answer. It also states, page by page, when I am not the answer.
The platform follows the catalogue, not the design
Almost every build request I receive opens on appearance: a theme, a home page, an identity. That is the least decisive part. What settles the platform is the shape of what you sell: how many references, how many variants per reference, how many different prices for one product, how many carriers, and whether a back-office system has to talk to the shop.
PrestaShop is built around the structured catalogue: variants, per-group pricing, carrier rules, multiple VAT rates, multistore. WooCommerce is a WordPress extension: it shines when editorial content weighs as much as selling, and it costs in plugins what PrestaShop costs in hosting. Shopify removes the server and the upgrades, but you rent everything and pay monthly for each function you add.
None of the three is better in the abstract. What exists are catalogues for which one of the three costs twice as much as the others over five years.
Six decisions that get expensive when taken late
- The platform, chosen on catalogue structure and on who will run the back office day to day, not on the mock-up.
- What happens to existing URLs in a rebuild: with no inventory beforehand, earned rankings go on launch day.
- Who supplies the catalogue, in what format, by what date. This is the leading cause of delay, far ahead of development.
- Payment methods and carrier accounts: they depend on third parties, they take weeks, and they do not speed up.
- What you own at the end: domain, hosting, code, database, backups. Agreed in the quote, never afterwards.
- The maintenance budget for year two. A shop with no maintenance line becomes a shop that is down.
Pages that carry this subject further
-
Custom development
What I actually build beyond configuration: modules, back-office screens, connections.
-
Rates
How I bill, fixed price or day rate, and what moves an estimate up or down.
-
Choosing e-commerce hosting
Shared, dedicated, managed: what each option allows and what it rules out.
-
PrestaShop developer
How I work on the platform that accounts for most of my projects.
In this section
-
Building a PrestaShop store: who it fits, and who it does not
PrestaShop is built for a catalogue with structure. Cross-referenced variants, per-group pricing, multiple carriers, several VAT…
-
Building a WooCommerce store: what WordPress imposes
WooCommerce is not e-commerce software, it is a plugin adding selling to a publishing system. That sentence explains most of it…
-
Building a Shopify store: what you gain, what you rent
Shopify sells one precise thing: the disappearance of infrastructure. No server, no upgrades, no security patch to apply, no…
-
PrestaShop site rebuild or repair: which to choose
A PrestaShop site rebuild resets things that worked. Before ordering one, you need to know what actually bothers you: in half the…
-
Rebuild: preparing the ranking handover before you start
Rankings are not migrated on cutover day. They are prepared before the first line of the new site is written, because the…
-
Opening a shop: what to prepare beforehand
An e-commerce project almost never stalls on development. It stalls on the catalogue that is not ready, unusable photos, the…
-
Online shop budget: what costs money and why
What costs money in a shop is almost never what people expect. Theme and layout are cheap. What you pay for is the catalogue, the…
-
Realistic timelines for building an online shop
Development time is almost never what delays an opening. It is approval rounds, the catalogue that does not arrive and…
-
Taking over a site left by a previous supplier
Taking over a site is not an administrative act, it is a technical decision. Before accepting, I look at three things: what has…
-
What you must own at the end of a project
At the end of a project you must be able to leave with the site without asking anyone’s permission. It is not a matter of trust…
-
When hiring a developer makes no sense
Some of the projects that reach me do not need me. Twenty products with no variants, a standard catalogue, no business system to…
Frequently asked questions
Should the platform be chosen before or after the mock-up?
Can I start small and change platform later?
Does a rebuild improve rankings?
Do you work with designers or agencies?
Will you take over a site someone else started?
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.