Ecommerce website development, custom webshops with a business mindset.

An entry-level webshop with a few hundred products typically goes live in 2–6 weeks. With a custom design, migration and several integrations, 6–12 weeks is typical, and a complex or B2B system usually takes 3–6 months. In practice, it's usually the preparation of the product data and content that determines the timeline.

A hosted system makes sense if your process is standard, you have a few hundred products and want to launch quickly. A custom webshop pays off if you have your own business logic, need deeper integrations, or the hosted platform's monthly fees and limits are already causing measurable lost revenue. During the assessment, we'll tell you honestly if your case is the former.

The typical range is between €3,900 and €45,000 + VAT: an entry webshop is €3,900 – 7,500, a custom webshop is €7,500 – 18,000, and a complex or B2B system is €18,000 – 45,000. The price is driven mainly by the number of integrations, the state of the data to be migrated and the custom business logic, with design a smaller item by comparison. At enterprise scale, on a Magento 2 basis, the range shifts higher.

For a detailed price table and a 3-year total cost calculation, see our ecommerce website development prices 2026 article.

There's no per-feature licence fee. On a monthly basis, the cost comes from hosting or a VPS, plus the maintenance package you choose: Basic €70 – 180, Operations €180 – 400, Partner €400 – 1,000 + VAT a month. The shop works without maintenance too, but skipping security updates and monitoring gets more expensive in the long run.

The number of products alone isn't decisive. Custom development can be justified with just fifty products if the pricing is complex or you need to connect to an ERP, and a well-built WooCommerce can be enough even with five thousand simple products. The deciding factor is the business logic and the integration needs.

Four things are needed to get started: product data (name, price, image, description, stock), a decision on shipping and payment methods, the legal texts (terms and conditions, privacy policy, right of withdrawal) and a decision on who runs the day-to-day operations: order processing, packing, customer service.

The technical side is our job, but the quality of the product data determines how fast the launch will be. It's worth starting with a spreadsheet: if that's in good shape, the upload can be handled by import, not by hand.

Rarely, because of the technology, since the code and the design age quickly. What's worth buying is the running business: the established domain, the search rankings, the customer lists and the supplier relationships.

Before buying, it's worth having the system reviewed: what state the code is in, whether it can be updated, where the security risks are and what the real traffic is. We carry out this audit for a fixed price, and afterwards it may also make sense to move the content and the business to a new system.

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

WShop is the webshop module of WebPot CMS: an in-house PHP system where the parts responsible for speed, namely server-side rendering, CDN-based image optimisation in WebP and AVIF format, and caching, are built in from the start rather than assembled from plugins. This keeps the shop fast even with lower server requirements, and there's no maintenance burden from plugin conflicts.

Your database and product data are always yours, exportable at any time. With WooCommerce and Magento, the entire codebase is yours too. With our own WShop system, we hand over the custom development done for your project and the data, and we set out the terms of using the framework in the contract; we don't build in any lock-in that would block you from leaving.

The goal is to stay within the Core Web Vitals thresholds on live data, on mobile too. That takes server-side rendering, image optimisation, caching and database tuning. With a large catalogue, this is a workstream of its own, not a by-product. Speed isn't just a ranking factor: it's directly linked to cart abandonment.

For a smaller shop, good-quality shared hosting is enough, but depending on traffic and catalogue size, a dedicated VPS soon becomes justified, and with Magento it's practically mandatory. We also offer our own Ubuntu VPS server hosting and operations; the details are on the VPS server page.

Yes, we also build Shopify webshops. Shopify is a hosted system: a fast launch and stable operations, in exchange for a monthly fee and transaction costs, and integrations with local invoicing, couriers and payment providers are handled through apps. If your shop needs custom processes or deep integration, WooCommerce, our own WShop or Magento 2 is more flexible. We give platform-independent advice to help you decide.

When you already have a working WordPress site and the webshop joins it, or when you're starting with a few hundred products, simple pricing, and content (blog, knowledge base) also plays an important role. In this range, WooCommerce gets there quickly and cheaply.

You'll feel its limits once ten to twenty plugins are holding the site together: every update becomes a risk, and speed suffers too. With a larger catalogue, complex pricing or an ERP connection, our own system or Magento 2 is the more stable foundation. We also take on maintenance and speed optimisation for WordPress webshops we didn't build ourselves.

Yes. We migrate from Shoprenter, Unas, WooCommerce, PrestaShop, OpenCart and Magento too: transferring products, categories, customers, orders and content with data cleansing. We build a 301 redirect map for the old URLs so your search rankings and link equity aren't lost.

Not with a properly executed migration. The key is a complete URL inventory, full 301 redirects, carrying over the headings and meta data, preserving the structured data and monitoring indexing after launch. A temporary fluctuation of a few weeks can happen; a lasting drop shouldn't.

Yes, that's a common task. We start with a technical audit: what's in the codebase, how updatable it is, where the security and data-loss risks are, and what's missing from the documentation. This produces a risk list and a prioritised plan, and actual development only starts after that.

For payment: SimplePay, Barion, Stripe, PayPal, bank transfer and cash on delivery, with instalment payment on request. For shipping: Foxpost, Packeta, MPL, GLS, DPD and Express One, with a map-based parcel point picker, automatic label generation and tracking.

Yes. An invoice is generated automatically from the order in your chosen invoicing system, and the data is reported to NAV immediately. We thoroughly test the error paths (cancellation, corrective invoice, partial delivery, return) before launch, because a mistake here has an immediate accounting consequence.

The European Accessibility Act has applied to ecommerce services since 28 June 2025, and its practical benchmark is the WCAG 2.1 AA level across the entire customer journey. Microenterprises with fewer than 10 employees and turnover or balance sheet total of no more than €2 million are exempt from the service requirements. We build new shops with an accessible structure by default, and for existing ones we recommend a priority order for fixes after an audit.

For details, see our is it mandatory to make a webshop accessible? guide.

Since 13 December 2024: the manufacturer's name and contact details, for non-EU manufacturers the details of the EU-based responsible person, the product's identifiers and image, and safety and warning information in clear language. In practice, this means new product attributes and template changes, not just a clause in your terms and conditions.

Only if the measurement is reliable. For this, we build GA4 server-side tracking with Enhanced Conversions and Consent Mode v2 support, so the ad platforms see real revenue, not an estimate. After that, you can interpret the return by channel, the cart value and the customer lifetime value.

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

Yes, that's a basic expectation. Handover includes admin training and short documentation, so you don't need to call a developer for day-to-day tasks – adding products, changing prices, promotions, editing text, order handling. For bulk uploads, we build a CSV or XML import and supplier feed processing.

We supervise the first period: we watch the error log, the payment transactions, the tracking and the indexing. After that, you can choose a maintenance package that includes security updates, backup checks, monitoring and priority bug fixes, with a monthly status report.

Yes, and for a webshop this isn't a mere formality: terms and conditions, a privacy policy, a right of withdrawal notice with a sample form, complaint handling and a cookie notice are all part of the mandatory set, together with your real company details and your shipping and payment terms.

A solicitor is responsible for the legal content of the texts; we don't give legal advice. What we handle: implementing them, working cookie consent, the withdrawal form and correctly displaying the pre-purchase information at checkout. If you don't have a solicitor, we can recommend one who works with ecommerce.

Yes, the webshop automatically generates a product feed for Árukereső, Google Shopping and the Meta catalogue. The feed reflects real prices and stock, so it doesn't need manual maintenance. We also connect the review integration for price-comparison sites, because ratings improve the click-through rate too.

Yes, coupon handling and promotional pricing are part of the system, and for the newsletter we connect a built-in solution or an external provider. Custom loyalty logic, such as a points scheme or a loyal-customer price tier, can also be developed. The goal is for a returning customer to be cheaper than acquiring a new one.

Yes, we build API-based integrations: stock and price sync from the ERP, automatic invoicing, order feedback into the enterprise management system. Stock across multiple sales channels can also be kept in sync. Integration is the most common custom development item in webshop projects.

Yes, price tiers 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 foundation; for smaller ones, WShop's custom pricing logic is enough too. Login-only pricing and net price display are also supported.

Yes, technically that's a webshop with supplier feed processing: automatic import of products, prices and stock, margin rules and forwarding the order to the partner. The quality of the feed is decisive: incomplete product data won't make a well search-optimised shop.

From a business point of view, it's worth knowing that dropshipping doesn't exempt you from your obligations: towards the customer, you're the retailer, so the delivery time, the warranty and the GPSR product information are your responsibility. We discuss this during the assessment, because it affects the process too.

Yes, multiple languages, multiple currencies and country-specific shipping costs 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's worth mentioning this right at the start, because it affects the structure.