Service

E-commerce development — built to take the order.

An online store is the system that carries an order all the way through — browse, cart, payment, delivery and stock. A simple store typically takes 2–4 weeks, and a platform with filters, payments and warehouse synchronisation takes 4–6. After a short brief we come back within 3–5 days with a structure, stages and a firm quote, and that stage is not billed.

Simple store: 2–4 weeks
Full platform: 4–6 weeks
Estimate: 3–5 days

E-commerce is the one place where page speed converts directly into money, and the arithmetic is unforgiving. Most storefront traffic arrives on a phone, often on a mobile connection, and every second a product page spends loading removes a share of the people who would have bought. A template store carries third-party scripts and plugin bundles it cannot shed; a purpose-built one carries what you chose to put in it. On our Smart Fashion project pages load in 0.8 seconds and conversion rose 65% after the rebuild.

Then: who holds the data.

On a hosted platform your customer list, order history and behavioural data live in someone else’s account, exported on their terms. Built on your own stack, the database sits on infrastructure you control — which matters the day you want to run a retention campaign, feed a recommendation model, or change vendor without asking permission to take your customers with you.

And the commission line. Marketplaces and hosted carts take a percentage of every order forever; a store you own converts that into a fixed build cost plus hosting. That trade only pays above a certain order volume, which we work out on the brief rather than assume. If the numbers say stay on the marketplace, we say so.

The hard part of these projects is payments, delivery and stock. Payment means acquiring, failed-transaction handling and refunds. Delivery means zones, tariffs and courier APIs. Stock is the one that bites — if the same item sells online and in a shop, without synchronisation you will sell something you do not have. We pin all three down before the estimate.

What the work covers

Included

Catalogue structure, categories and the product page
Filters, search and sorting
Cart and checkout
Payment provider integration
Delivery zones and courier service APIs
Stock tracking and synchronisation
Admin panel: orders, products, discounts
Technical SEO and product JSON-LD
Analytics and e-commerce goal tracking

Not included

Product photography
Filling the catalogue and writing descriptions
Signing the acquiring agreement with a bank
Running advertising campaigns
Setting up the warehouse and logistics themselves

What you receive

A working store on your domain
Repository and database in your account
Admin access and a written guide
Payments and delivery live, with test orders passed
Analytics and sales reporting
Monitoring and a 3-month warranty

What drives the price

We do not publish a price list: "a store" covers a twenty-item showcase and a thousand-SKU platform equally. These are what move a quote.

Product count and variants: size, colour, bundles, units of measure
Filter complexity and how search is expected to behave
Payments: how many methods, instalments, the refund path
Delivery: zones, tariffs, number of courier services
Stock: tracked by hand, or synchronised with 1C or a warehouse system

The structure, the stages and a firm quote arrive within 3–5 days of the brief. That stage costs nothing.

Stack

Chosen per project. A showcase can be built statically; a large catalogue arrives with its own database.

Frontend

Next.js
Astro
TypeScript

Backend

Django
FastAPI
PostgreSQL
Redis

Commerce

Payment API
Delivery API
1C

Delivery

CDN
Docker
CI/CD
Analytics

Stages

Brief and catalogue structure
3–5 days
Products, variants, payment and delivery rules. Output: a structure, stages and a quote.
Prototype and order flow
2–4 days
The whole path from catalogue to checkout, including the failed-payment and out-of-stock paths.
Design
3–6 days
Catalogue, product page, cart, checkout. Mobile first: most store traffic arrives on a phone.
Build and integrations
1–2 weeks
Catalogue, admin, payments, delivery, stock sync. A working link at the end of every sprint.
Test orders and release
3–6 days
Test orders with real payments, refund checks, load testing and a speed measurement.
Warranty and support
3 months
Monitoring, fixes and reading the sales reports with you. Then a support plan or your own team.

When you do not need this

A store costs more than a site and only pays back on order volume. We raise these on the brief ourselves.

Fewer than 20 orders a month, all through messengers

At that volume a catalogue page and a WhatsApp button do the same job. A store starts paying back when the conversations begin eating a manager’s day.

The product does not sell without a conversation

That does not go in a cart. A catalogue and an enquiry form outperform a checkout.

Stock is not tracked anywhere yet

A store does not tidy a warehouse; it makes the untidiness visible to customers. Decide where stock lives first, then connect a site to it.

A marketplace sells it all and that suits you

Your own store cuts the commission but makes you responsible for the traffic. A marketplace supplies both at once. With no advertising budget, your own channel can wait.

If one of these describes you, write anyway. We will tell you for free what is worth doing now — a catalogue, a store, or simply automating the process you already run.

Related work

Frequent questions

Would Shopify or a ready-made CMS be cheaper?

For a standard catalogue and a standard checkout, yes, and we say so directly. Shopify or a ready-made CMS is up in a couple of weeks. The difference appears where your product variants, discount rules or stock synchronisation do not fit the platform’s model: from there it is plugins, and plugins collide on every update. Your own platform removes that but starts slower — 2–4 weeks for a simple store. On the brief we cost both routes.

How do payments work in Azerbaijan?

Through local bank acquiring or a payment gateway. You sign the agreement with the bank — that part is legal; the technical integration, test payments and the refund path are ours.

Who fills the catalogue?

Usually you, through the admin panel; if there is an existing source — a spreadsheet, 1C, an old site — we handle the migration, and it is a separate stage visible in the quote.

Can it integrate with 1C or a warehouse system?

Yes. Stock, prices and orders can synchronise in both directions. We pick the frequency together: real time costs more, and several times a day is enough for most stores.

Will the store be found in search?

The technical side is delivered ready at launch: product JSON-LD, sitemap, speed, correct headings. Rankings depend on catalogue quality, descriptions and competition — anyone promising them overnight is inventing.

Tell us about the store

A short brief is enough: what you sell, how many SKUs, and how payment and delivery work today. We come back within 3–5 days with a structure and a quote.