Online store development for companies that already sell

Someone re-types orders into the ERP by hand, someone else corrects stock levels manually. It's work that grows with sales instead of shrinking.

A free-shipping threshold, prices for regular customers, a product configurator. On a closed platform each one is a request to a supplier, not your own decision.

A few thousand SKUs, attribute filters and variants. The site slows down, the basket loses customers, and the layer that needs fixing isn't even visible in the admin panel.

Online store development is work that connects a sales platform to how the company actually runs: the catalogue, warehouse, payments, shipping and accounting. The store itself can go up in a week. The rest of the time goes into making sure nobody re-types data from one system into another after launch.

PrestaShop or WooCommerce, and when neither

The table above shows the differences between platforms. This is the rule we actually choose by, and in one of the four cases it ends with us advising against a build at all.

Where the time and budget go on this project

The split is a convention, since one team and one contract run the whole thing. It shows what the timeline is made of: data and integrations eat the most time, not drawing screens.

Design and build

Workshop, process map, screen design, store build and catalogue setup. You end up with a store ready to sell, documentation and a trained team.

Migration and integrations

Moving data from the old platform, a 301 redirect map, hooking up ERP, warehouse, BaseLinker, payments and carriers. We test the whole order path before the switch, from click to courier label.

Growth after launch

Technical care, feature development, campaigns and SEO. We measure this part by the store's profit, not by the number of screens built or a ranking position.

A store launched and left on its own usually drifts back to its pre-change result within a few months. That's why we measure the first three months after launch separately: the basket, the purchase path and returns. We only raise campaign budget once we can see which of those numbers have actually moved.

The same goes for migrations. Visibility in Google after a platform change needs time to settle, and no agency gets around that, us included. You can make that dip shallow and short, but all the work for it happens before the switch, not after.

Six objections that come up before the first quote

We answer each one with a checkable fact or a price, not a promise. If any answer doesn't convince you, say so on the first call, not after signing.

“Maybe our store doesn't need replacing at all”

Possible, and we check it ourselves. A technical audit for €860 net ends with a list of priorities, not an implementation offer. Sometimes fixing performance and integrations is enough, and then that's exactly what we recommend.

“An agency will make it pretty but it won't sell”

We co-build Surf Inc., a top-ten PrestaShop store in Poland, and we're responsible there for technology and marketing. Every solution we propose to you has already been through that profit and loss account, and results for other companies' stores are shown above, in our case studies.

“Our process is too unusual for an off-the-shelf store”

That's why we start with a process map, not a template. Configurators, price lists for regular customers, trade limits and orders from a file are built as modules, billed at €80 net per hour.

“We'll be left on our own after launch”

Post-launch care starts from €320 net a month and has a 24-hour response time written into the contract, on business days. You get documentation and access either way, whether you stay with us or not.

“We don't have the budget to build from scratch”

Then a ready-made subscription platform is often the better choice. We do not cut scope down to the point a build stops making sense. A project can also be split into stages, starting with the audit alone.

“We already have a store contractor”

We don't push you to switch. We usually start with a second opinion in writing: the audit shows what works in your current store and what's costing you sales. You can take that document to your own contractor.

We settle which platform to choose on the first call. It's usually decided not by technology but by the number of product variants, how the warehouse works and whether you also sell outside your own store.

• You want to own the code, the database and the access.
• You have unusual product variants or warehouse workflows.
• You also sell outside your own store and need to connect that.
• You don't want to pay a revenue commission for the store's whole life.

• Your current platform isn't the bottleneck: migrating is months of work.
• Every migration eats into some search visibility.

What you buy only after the store launches

A build ends on launch day, selling doesn't. We run the services on a store that's already live, and each one can be bought separately, without having to take a whole package along with it.

Cost, timeline and migration: questions before you decide

Building an online store: price, timeline, platform, B2B sales