Our starting price is 2,300 €, and below you can read what sits behind it and what pushes it up. These are our published prices, not a market average.
An online store is not a brochure site with a buy button added at the end. On top of everything a normal site involves, meaning discovery, architecture, design, implementation, testing and launch, a second project of the same size is added.
That second project is the product catalogue, the product page, the cart and checkout, payments, shipping, invoicing, customer accounts and the legal side. Each piece is a separate integration, with a separate provider, which can break separately and has to be tested separately.
The most expensive mistake in a store is not the design. It is the catalogue structure. Categories, attributes and product variants are decided at the start, and if they are wrong, at two hundred products the store becomes painful to run and you end up rebuilding it.
Categories, attributes, variants. This is where it is decided whether the store is easy or painful to run two years from now.
Gallery, description, stock, variants, related products.
The shortest path between "I like it" and "I paid". This is where most buyers are lost.
Integration with the processor you choose. The commission and the time until you are paid differ between them.
Couriers, shipping calculation, AWB generation, a link to your invoicing software or automatic issuing.
A customer account, order history, automatic emails, terms and policies.
The number of integrations is the main factor. A store with one payment processor, one courier and automatic invoicing costs differently from one that has to be connected to an ERP, three couriers and an existing stock system.
Next comes the number of variants per product, because a product with sizes and colours means a different structure from a simple one. Then the product data: if descriptions and photos arrive ready, the work goes much faster than if they have to be built.
As a time reference, a web project takes a minimum of 15 days and can run to a few months, depending on complexity. In a store, the integrations are what stretch the calendar.
Want the figure for your own store? It depends on how many products and how many integrations you have, and the configurator estimates it.
Calculate the range →Because a store is not a site with an extra button. On top of everything a brochure site involves, you add the catalogue, the product page, the cart, payments, shipping, invoicing, customer accounts and the legal side. Each of them is a separate piece, which can break separately.
Yes, and that is usually the healthier way. What has to be thought through from the start is the catalogue structure, meaning which categories, which attributes and which product variants exist. If the structure is wrong, at two hundred products the store becomes painful to run and you rebuild things that looked trivial at the start.
You choose it, we integrate with it. The real differences between processors are the commission, the time until the money reaches your account and what happens with returns. These are thirty-minute conversations, but they happen before implementation, not after.
It can be linked to your invoicing software or issued automatically on every order. It depends on what you already use in accounting, so we settle that in the first conversation.
The terms, policies and buyer information copy is part of the project as structure and as form. The legal content itself remains the responsibility of the company, because it depends on your activity, and we do not give legal advice.
A web project takes a minimum of 15 days and can run to a few months, depending on complexity. In a store, the time depends most on how many integrations are involved and how fast we receive the product data.
It comes after a conversation in which we find out how many products you have, which integrations you need and who prepares the product data.
