Having an online shop built: platform, cost and the choices that matter
Almost every conversation about an online shop starts with the platform. Shopify or WooCommerce, template or custom. That is the wrong first question. Your order process decides what you need, and the technology follows.

Start with the order process, not the platform
Before you spend a single euro, sketch out once how an order moves through your business. Where the stock comes from, who packs it, which shipping methods really exist, what happens with a return, and which system the order eventually has to land in. Nine times out of ten, that is where the complexity sits, not in the design of the product page.
That sketch is also your selection criterion. A store with forty products, one warehouse and two shipping methods fits comfortably on a standard platform. If you sell fresh produce with delivery slots, or supply B2B with customer-specific prices and ordering on account, a ready-made theme mostly buys you future workarounds.
The three routes, and what they cost in practice
In the Dutch market you see roughly three routes. The amounts below are market ranges, not a quote: the scope decides where in the range you land.
Route one is an existing theme you set up and fill yourself. Route two puts your own design on the front end of a standard platform, with ordinary commerce underneath. Route three builds your own front end on a commerce API, with your own logic inside.
| Route | Investment and lead time | When it fits |
|---|---|---|
| Ready-made theme | €0–€1,000, days to weeks | You want to find out first whether there is demand |
| Your own design on a standard platform | €2,500–€15,000, 4–10 weeks | The brand has to be right, the logistics are normal |
| Custom or headless | From €15,000, from three months | Pricing rules, multiple markets, ERP integrations |
For most brands, the middle route is the right one. You get a store that looks like your brand, and you inherit the dull things a platform already does well: payments, tax rules, discount codes, transactional emails and the security of payment data. Those are exactly the parts you do not want to maintain yourself.
The monthly bill weighs more than the build
The build cost is the start of the investment, not the total. A Shopify Basic plan in the EU costs around €30 to €40 a month, excluding VAT. WooCommerce itself is free, but then you pay for hosting, backups, updates and someone to keep on top of it all. On top of that come your payment provider's transaction fees, the two to five apps you actually use, and the link to your accounting or stock system.
The item that is routinely forgotten is content. Product photography, copy, sizing, ingredients or specifications: work that comes back every time your range changes. Agree no rhythm for it, and within six months you have a store with thirty good product pages and two hundred half-finished ones.
The most expensive online shop is the one you have to rebuild after eighteen months, because the order process never fitted it.
Four things that cost you more often than design
1. Tax settings
In the Netherlands, food falls under the reduced VAT rate of 9 percent and everything else under 21 percent. Set that up wrong and every order is wrong, and you only notice when your accountant calls. We saw this up close at Harvest Deli: the product categories were right, the store's tax setting was not. Check it before you go live, with one test order per product type.
2. Product data and URL structure
An online shop is an SEO project with a shopping basket attached. Clean product routes, one URL per product, no duplicate variants of the same page, and canonicals that are correct. At Harvest Deli we moved the product pages to a clean /products/ structure, with permanent redirects from the old addresses. Do it during the build, not as a repair afterwards.
3. Shipping and returns rules
Shipping rules are rarely as simple as the quote suggests. Weight bands, free shipping above a set amount, collection, delivery slots, shipping restrictions per country. And then the returns process, which often is not a process at all but an email address. Write both out before anyone starts building.
4. Payment methods
In the Netherlands, almost everyone expects iDEAL. In other markets the list looks different, and the payment method you are missing is the order you do not get. Look at the rate per method too: it varies widely, and with low average order values it makes a real difference.
A second country is not a translation
Selling across the border is a second project, not a language switch. For Dangerous Street we built a storefront with a Germany-first set-up: language, payment methods and returns terms per market, alongside the mandatory registrations that come with selling to German consumers, such as packaging registration and producer responsibility. That is not design work, but it decides whether you are allowed to sell legally.
In practice: only open a market once you can serve it. A half-German store with Dutch returns terms costs you more in confusion than it brings in. See how we approached it in our cases.
When custom work really pays for itself
Custom work is not a status symbol. It is an answer to complexity you cannot design away. These are the signs we see most often:
- You have pricing agreements per customer or per customer group.
- Your product range lives in another system, and that system has to stay in charge.
- Customers configure their product before they order.
- You sell in several countries, currencies or legal entities.
- You have fifteen apps tied together and they get in each other's way.
Recognise none of these? Then custom work is probably the most expensive way to build something a standard platform can already do. Recognise a few, and want to keep Shopify for the checkout? Then read how headless Shopify works.
How we approach it
We are a digital studio in Amsterdam, and we start every e-commerce project with the order process and the numbers behind it. What such a project covers, from range structure to checkout, is on our page about having an online shop built. What a project costs depends on your range, your order process and the platform that suits it; we scope it step by step. Every project starts with a free thirty-minute introductory call, with no obligation.
Still torn between a new website and an online shop? Read what a website costs first, or look at the five signs your current site is costing you customers.
Frequently asked questions
Shopify or WooCommerce?
Shopify if you want to sell, not administer: updates, security and payments are taken care of, for a fixed monthly fee plus transaction costs. WooCommerce if you want to keep everything in your own hands and already work with someone who takes hosting and maintenance seriously. The wrong reason to choose WooCommerce is that it looks free: the maintenance is the price.
How long does it take to build an online shop?
With us, focused sites usually land in six to eight weeks. For stores and platforms, three to four months is more realistic, depending on the number of integrations. The lead time is rarely set by the build itself, but by product data, photography and decisions about shipping and returns.
Can I migrate without losing my Google rankings?
Yes, if you plan it as part of the project. You record every old URL, map it to the new one, set up permanent redirects, keep the titles and copy that already rank, and submit a new sitemap. Traffic loss in a migration almost always comes down to redirects nobody wrote out.
