Webshop development,custom store buildswith a business mindset.

An entry-level webshop with a few hundred products goes live in 2–6 weeks. With custom branding, migration and several integrations 6–12 weeks is typical, and 3–6 months for a complex or B2B system. In practice what usually stretches the deadline is not development but preparing the product data and the content.

A hosted platform makes sense if your processes are standard, you have a few hundred products and you want to launch fast. A custom webshop pays off if you have your own business logic, need deeper integrations, or the monthly fees and limits of the hosted platform already cost you measurable revenue. At the survey we will tell you honestly if yours is the first case.

The typical range is between €3,900 and €45,000 net: an entry store €3,900 – 7,500, a custom webshop €7,500 – 18,000, a complex or B2B system €18,000 – 45,000. The price is driven by the number of integrations, the state of the data to be migrated and the custom business logic, not by the design. At enterprise scale, on Magento 2, the range moves up.

A detailed price table and a three-year total cost calculation are in our webshop development prices 2026 article.

There is no per-feature licence fee. Monthly costs are hosting or a VPS plus the maintenance package you choose: Basic €70–180, Operations €180–400, Partner €400–1,000 net per month. The store works without maintenance too, but skipping security updates and monitoring costs more in the long run.

The product count alone does not decide it. Custom development can be justified with fifty products if the pricing is complex or it has to connect to an ERP, and a well-built WooCommerce can be enough for five thousand simple products. The deciding factors are the business logic and the integration needs.

On our own WebPot CMS + WShop system, on WooCommerce and on Magento 2, and we also take over custom PHP, OpenCart and PrestaShop stores. Because we can work in several directions, we have no interest in forcing a single platform onto the project.

WShop is the webshop module of WebPot CMS: a PHP system we developed ourselves, in which the parts responsible for speed, that is server-side rendering, CDN image optimisation in WebP and AVIF and caching, are built in rather than assembled from plugins. That way the store stays fast on lower server requirements, with no maintenance burden from plugin conflicts.

Your database and your product data are always yours and can be exported at any time. With WooCommerce and Magento the whole code base is yours as well. On our own WShop system we hand over the custom development built for the project and the data, and the terms for using the framework are set out in the contract; we do not build in locks that block you from leaving.

The goal is to stay within the Core Web Vitals thresholds on real data, on mobile too. That takes server-side rendering, image optimisation, caching and database tuning. On a large catalogue this is a work stream of its own, not a by-product. Speed is not only a ranking factor: it is directly linked to cart abandonment.

For a smaller store good quality shared hosting is enough, but depending on traffic and catalogue size a dedicated VPS soon becomes necessary, and with Magento it is practically mandatory. We also run Ubuntu VPS servers ourselves; the details are on the VPS server page.

Yes. We migrate from Shoprenter, Unas, WooCommerce, PrestaShop, OpenCart and Magento: products, categories, customers, orders and content are moved over with data cleaning. We build a 301 redirect map for the old URLs so that rankings and link equity are not lost.

Not with a properly executed migration. The key is a complete URL inventory, gapless 301 redirects, carrying over headings and meta data, preserving the structured data and watching indexing after go-live. A temporary fluctuation of a few weeks can happen; a lasting drop should not.

Yes, this is a common job. We start with a technical audit: what is in the code base, how upgradable it is, where the security and data loss risks are, what is missing from the documentation. From that we produce a risk list and a prioritised plan, and only then does the actual development start.

For payments SimplePay, Barion, Stripe, PayPal, bank transfer and cash on delivery, with instalments on request. For shipping Foxpost, Packeta, MPL, GLS, DPD and Express One, with a map-based pickup point selector, automatic label generation and tracking.

Yes. The order automatically becomes an invoice in the invoicing tool you choose, and the report goes to NAV immediately. We test the error paths through before go-live (cancellation, correcting invoice, partial delivery, return), because here a fault has immediate accounting consequences.

The European Accessibility Act applies to e-commerce services from 28 June 2025, and its practical benchmark is WCAG 2.1 AA across the whole customer journey. Micro-enterprises with fewer than 10 employees and under EUR 2 million turnover are subject to lighter rules. We build new stores with an accessible structure by default, and for an existing one we recommend an order of work after an audit.

From 13 December 2024, the manufacturer name and contact details, for a non-EU manufacturer the details of the responsible person in the EU, the product identifiers and image, plus safety and warning information in plain language. In practice this means new product attributes and template changes, not a paragraph in the terms.

Only if the measurement is reliable. For that we build GA4 server-side tracking with Enhanced Conversions and Consent Mode v2 support, so the ad platforms see real revenue rather than an estimate. After that the return per channel, the basket value and the customer lifetime value become meaningful.

Only if its content arrives rendered server-side, with structured data. AI answer engines do not run a browser the way a user does: if the product data loads only from JavaScript, it is left out of the answer. Our WShop system provides server-side rendering and Product structured data by default; on WooCommerce and Magento we set this up separately.

Yes, that is a basic requirement. The handover includes admin training and short documentation, so that day-to-day work – adding products, changing prices, running promotions, editing text, handling orders – never needs a developer. For bulk uploads we build CSV or XML import and supplier feed processing.

We supervise the first period: we watch the error log, the payment transactions, the measurement and the indexing. After that there is an optional maintenance package covering security updates, backup checks, monitoring and prioritised bug fixing, with a monthly status report.

Yes, the webshop produces an automatic product feed for price comparison sites, Google Shopping and the Meta catalogue. The feed reflects real prices and stock, so it needs no manual upkeep. We also connect the review integration of price comparison sites, because ratings improve the click-through rate too.

Yes, coupon handling and promotional pricing are part of the system, and for newsletters we connect either a built-in solution or an external provider. Custom loyalty logic, such as points or a regular-customer price level, can also be built. The goal is for a returning customer to cost less than acquiring a new one.

Yes, we build API-based integrations: stock and price sync from an ERP, automatic invoicing, orders written back into the management system. Stock across several sales channels can be kept in sync as well. Integration is the most common custom development item in webshop projects.

Yes, price levels per customer group, custom discounts, quantity pricing and quote-based selling can all be set up. For larger B2B needs Magento 2 is the strongest base; for smaller ones the custom price logic of WShop is enough. Login-gated prices and net price display are covered too.

Yes, multiple languages, several currencies and per-country shipping rates can all be handled. For sales within the EU we also help set up the OSS VAT rules, and we adapt the payment and courier integrations to the target countries. It is worth flagging at the start, because it affects the structure.