Catalogue and product data
Variants, sizes, colours, bundles. We build the category structure the way a customer searches, not the way the warehouse stores things — the two are rarely the same.
Stratos / Services / Ecommerce web design
The basket
is not the finish line.
It is the start.
In ecommerce, design is the least of it. The customer decides where the shipping cost appears, and leaves where a form field makes no sense.
We do not open a shop. We build a selling process.
Half of online store development is engineering; the other half is deciding what the customer sees and when. We help with that half too, because that is where the revenue comes from.
The system
What goes into
building an
online store?
Payment and delivery
Card, cash on delivery, transfer, couriers and pickup points. The shipping cost appears in the basket, not in the last step before payment — that is where most orders are lost.
Invoicing and stock integration
If you have invoicing or warehouse software, we connect it. Stock, price and orders originate in one place, and nobody types anything twice.
Conversion tracking from day one
Not bolted on afterwards. Add to basket, checkout started, basket abandoned and purchase — so that after the first month you know where the customer was lost.
Why from code
No template,
no plugins.
Most online store projects start with a template and eight plugins on top. That works until you ask for something none of them does — from there the ninth plugin overrides the first.
We build from code, so the store does exactly what it needs to and no monthly security update arrives for somebody to run. In return it is faster: it carries no code you will never use.
If the store already exists and only the visibility is missing, this page is not the answer — SEO is, and the work there is putting the category and product pages right.
Let's work out what your store has to do.
What does an online store cost?
It depends on how many products you have, with how many variants, and what it has to connect to. A few-hundred-product store can run on the monthly fee; a several-thousand-item system tied to an ERP is priced per project. You get a concrete figure after the free consultation.
How long does it take?
A typical store is six to ten weeks from signature to launch. The longest stage is not the engineering but the product data: the photography, the descriptions and the variants. If that is ready we finish sooner; if it is not, we help with it.
Can you take over an existing store?
Yes. First we look at what can be saved — product data and order history almost always migrate, the template and the plugins rarely do. If the existing system works and only visibility is missing, we say so before rebuilding anything.
Do I get an admin interface?
Yes, and it is cut down to the few things you will actually do: adding products, changing price and stock, handling orders, coupons. Not a twenty-item panel of which you use three.
Who is responsible for legal compliance?
We build in the required material — terms, right of withdrawal, privacy, cookie handling — and tell you what is missing. The substance of those texts is a lawyer's responsibility, not ours; if you do not have one, we say so in time.
What if the store grows?
It is built for that. A new language, a new market, a new payment method or a warehouse integration can be added later, because it is code and not bounded by a template. You do not have to decide everything at the start.
Where to next
Related pages and reading.