Order #2417Monstera Deliciosa129,00 złOnline stores for companies in Gdańsk and across Poland
A store on an off-the-shelf platform usually ends in the same place: the sales process has to be bent to what the platform can do. First one plugin arrives, then another, and a year later nobody knows why the stock levels drift apart.
We build it the other way round — a store shaped around how you actually sell and release goods. Catalogue, cart, payments and delivery are one path, not four modules glued together with plugins.
What the scope covers
- Analysis of the assortment and of the goods release process, before any design
- A purchase path designed around the way you sell
- Catalogue, cart, payments and delivery as one process
- A seller panel you can work in without a developer
- Integrations with warehouse, ERP and accounting — no re-typing of orders
- Stock and prices in one place, without drift between systems
- Performance verified before launch: the store has to open fast on a phone
- Accessibility: the purchase path can be completed with a keyboard and a screen reader
- Hosting, SSL certificate, backups and monitoring configured within the implementation
- The technical side of GDPR and consumer duties: a consent mechanism, a place for the terms, retention of order data
- Documentation, handover of accesses and full ownership of the code
Hosting, the SSL certificate, backups and the technical side of GDPR duties are configured as part of the implementation — they belong to the agreed price, not to a separate line item. Ongoing care of a running system, meaning updates, monitoring and support, is a separate subscription, quoted at handover.
How we work
Sales analysis
We look at the route from order to released goods — including what happens outside the system today: on paper, on the phone, in a private message.
What we need from you Access to the warehouse and order handling people, not only to the owner.
Designing the purchase path
We design the customer route from catalogue to confirmation and the order route from cart to warehouse. Both have to agree, because it is one process seen from two sides.
What we need from you Complete data on the assortment, variants and delivery methods.
Integrations
We plug in the warehouse, ERP, payments and carriers — first on the test environment, where a fake order costs nothing.
What we need from you Contacts at the system vendors and test credentials.
Tests on real orders
We walk the whole path on the real assortment, including a return and a correction — because that is where the gaps usually show.
What we need from you A person who will go through the purchase as a customer and say what annoyed them.
Launch and care
Move to production, training for the staff, handover of accesses. Ongoing care is a separate agreement.
What we need from you A date on which the store can be switched over outside the sales peak.
Platform or custom store — when the costs meet
Work out in which month a custom store matches the cost of an off-the-shelf platform.
The monthly sum of every paid plugin, theme and integration.
Fill in every field — without them there is nothing to calculate. We substitute no default values, because each of them would be our assumption rather than yours.
This is arithmetic from the assumptions you entered, not our forecast. Every number in the result comes from the fields above — there are no market averages and no estimates of ours in it.
Common questions
Would an off-the-shelf platform not be cheaper?
At the start it almost always is, and for simple selling it is a sensible choice — we say so plainly instead of pushing a custom store. A custom one starts to pay off when the process no longer fits the platform and the cost starts coming from workarounds: manual re-typing, more plugins and drifting stock.
Will you migrate our current store?
Yes — products, customers, order history and addresses. Migration is a separate stage with its own tests, because that is the moment when data is easiest to lose.
What happens to our search rankings after the change?
Old addresses get redirects, and the structure and structured data are built together with the store. We do not promise positions or traffic growth — we promise that the change will not erase what you already have.
Can a non-technical person run the panel?
That is the goal and we verify it before launch: adding a product, correcting a price, handling a return and issuing a document all have to be possible without a developer.
Who pays for the store hosting?
Configuring hosting, the SSL certificate, backups and monitoring is part of the implementation scope. Ongoing care of the running store — updates, monitoring, support — is a separate subscription.
Will the store be accessible to people with disabilities?
We design the purchase path so that it can be completed with a keyboard and a screen reader, and we verify that before launch. Whether your company falls under the act implementing the European Accessibility Act depends on its size and type of sales — that is a question for a lawyer, not for us.
How long does building a store take?
It depends on the assortment and the number of integrations — usually from a few weeks to a few months. The schedule is produced together with the scope and the fixed price, before work starts.
Let us talk about your project
Pick a time for a call or leave your number — we call back during working hours.