
The question
I received very different quotes for an online shop. How much should it actually cost, and where does the money go?
Quotes for an online shop can differ several-fold and, often, they do not even describe the same thing. One includes only installing a theme, another includes integration with invoicing, couriers and stock, and another says nothing about what you pay monthly after launch.
Instead of a figure, this guide gives you the cost structure, so you can compare quotes on the same elements. The starting prices of our packages are shown on the service pages at the end of the guide.
If you want us to handle this for you, see our service WooCommerce / PrestaShop online shop or our service Complete online shop.
Start-up costs (one-off)
These are the costs of building the shop, before the first order:
- Platform and theme setup, including adapting the design to the brand.
- Category structure, filters and uploading the initial catalogue.
- Payment and delivery methods, with shipping cost rules.
- Legal pages (terms, privacy, returns) and cookie settings.
- Integrations: invoicing, couriers, inventory management, marketplaces.
- Basic SEO setup, speed checks and administration training.
Recurring costs (monthly or annual)
A shop has ongoing expenses even if you change nothing on it. Ask for these to be listed separately in the quote:
- Domain and hosting, or the subscription to a hosted platform.
- Annual licences for the theme and plugins, or app subscriptions.
- Maintenance: updates, backups, monitoring and fixes.
- The subscription to the invoicing software and, if applicable, the inventory management software.
- Payment processor fees and courier costs.
The costs you forget
Many budgets are exceeded because of things that appear in no development quote:
- Product photos and descriptions: often the biggest piece of work.
- Your or your team’s time for the catalogue, orders, returns and customer relations.
- Promotion: a new shop does not get traffic on its own.
- Adjustments in the first weeks after launch, when real requirements appear.
- Returns and products damaged in transit.
Three scenarios, from simple to complex
Cost grows mainly with the number of integrations and the amount of automated work, not with the number of pages. Three common situations:
- A shop just starting out: small catalogue, card and cash-on-delivery payment, one courier, invoices issued from the invoicing software. The focus is on a well-configured platform that is easy to manage.
- A growing shop: several hundred products, daily orders, automatic invoicing, AWB (shipping label) generated from the shop. Integrations become the main part of the project.
- Selling on several channels: shop, marketplaces, perhaps a physical store too. Stock and orders must be synchronised across channels, with error alerts and ongoing maintenance.
How to compare two quotes fairly
Ask each supplier the same questions and get the answers in writing:
- What exactly is included: how many products uploaded, which integrations, how many rounds of changes?
- What monthly or annual costs will there be after launch, and who pays them?
- Who owns the accounts, domain, hosting and licences? Can you take them over at any time?
- Who handles updates, and what happens if a plugin breaks after an update?
- What happens to SEO if the shop replaces an existing site (redirects)?
- What does the handover look like: training, documentation, administrator access?
How to reduce cost without compromising the shop
Start with what brings in sales from day one and add automations in stages, once you see where time is being lost. A simple, fast, correctly configured shop is worth more than one full of features nobody uses.
Do not cut back on things that are hard to fix later: the category and URL structure, accurate product data, the legal pages and backups.
