Development
E-commerce development
A store is not a shop window, it is an operational tool: catalogue, payments, delivery, stock and orders have to work as one. We build it so your team can run it without a developer.
- Pricing
- From $1,400
- Timeline
- A base store takes around 7 days. With ERP integration, complex discount logic and a large catalogue, from 3 weeks.
A starting price. The total depends on scope, integrations and deadlines.
In short
An online store starts at about $1,400 and a base version takes around 7 days. That includes a filterable catalogue, product pages, cart, checkout, payment capture, delivery calculation and an order admin. Integrations with ERP, inventory, marketplaces and complex discount logic are scoped separately.
Catalogue structure decides whether you get traffic
In e-commerce the organic traffic lands on categories and filters, not the homepage: "buy X cheap", "X for Y", "X by brand Z". So we design the catalogue structure from keyword data: which categories and subcategories have demand, which filter combinations deserve their own indexable page, and which must be closed off so you do not breed duplicates.
Product pages get Product markup with price, availability and rating. That is what earns rich snippets and lets items surface in shopping blocks in search results.
Payments, delivery and orders
We connect payment capture — cards, instant bank transfer, instalments — and delivery pricing through the carriers you actually use. The order admin is shaped around your process: statuses, notes, exports, notifications for the manager and the buyer. If you run an ERP, a CRM or an inventory system, we wire up the exchange so stock and prices are not maintained twice.
Speed with a large catalogue
Thousands of products and dozens of filters make a store slow very easily. Next.js lets us serve categories statically with background regeneration, cache catalogue responses and load heavy parts as the user scrolls. Product images go to WebP and AVIF at several sizes, since on catalogue cards that is usually the heaviest thing on the page.
What the work includes
- Catalogue with categories, filters and search
- Product pages with gallery, specs and Product schema markup
- Cart and checkout, including guest checkout
- Payment capture: cards, instant transfer, instalments if needed
- Delivery pricing through the carriers you use
- Order and product admin shaped around your process
- SEO category structure and indexing rules for filters
- E-commerce analytics: the funnel from product page to purchase
- ERP, CRM or inventory integrations where required
How we work
- 01
Product and keyword structure
We work through the range and the demand, then design the category tree and filter rules.
- 02
Prototype of the key journeys
Catalogue, product, cart, checkout. A prototype shows where buyers will stumble.
- 03
Design
Catalogue and product layouts, mobile, availability and price states.
- 04
Build and integrations
Frontend, admin, payments, delivery, ERP or CRM exchange.
- 05
Test orders and launch
We run real payment and refund scenarios, then open the store.
Technology and tools
- Next.js
- React
- TypeScript
- Node.js
- NestJS
- PostgreSQL
- Docker
- Shopify
- WordPress
- Bitrix
Selected work
FEIARY Craft
Design for a leather accessories store. The style echoes street and tattoo art to tie the products to a bold youth aesthetic, while the palette signals premium quality. Built by Veltos.Tech together with Makar.
NA Consulting
A website for the NA Consulting agency. An interactive landing page packs the full story of the agency and its services into a minimalist layout. Calm colours convey trust and professionalism. Built by Veltos.Tech together with Aliya (finnikkis.github.io/maulaviyevadesign).
GoFiesta
A mobile app for finding parties and events abroad: tickets, travel companions and an organiser profile.
Frequently asked questions
How much does an online store cost?
From about $1,400 for a store with catalogue, cart, payments, delivery and an order admin. The number grows with product and variant count, filter complexity, how many integrations you need (ERP, inventory, marketplaces, carriers) and design requirements. ERP exchange and stock synchronisation is the most common reason an estimate goes up: it is a real engineering task, not a checkbox.
Which platform should the store run on?
For a small, standard range, packaged platforms like Shopify or Bitrix launch faster. A custom Next.js build wins when load speed on a large catalogue matters, when pricing and discount logic is non-standard, when you need deep integration with internal systems, or when the SEO structure you want is not something the platform will let you build. We cost both and show the first-year difference including licences and fees.
How will the store get search traffic?
Through categories and filters, not the homepage. We design the category tree from keyword data, open the filter combinations that have real demand to indexing and close the rest so duplicates do not pile up. Product pages get Product markup with price and availability for rich snippets. After that it needs content: category descriptions, specifications, reviews. That falls under the SEO service.
Can you connect ERP and marketplaces?
Yes. ERP exchange usually covers products, prices, stock and orders, with direction and frequency depending on which system is your source of truth. Marketplace feeds (Ozon, Wildberries, Yandex.Market) go through their APIs or an aggregation service. The thing to settle early is where the range is maintained: if it is edited in two places at once, drift is guaranteed.
What about payments and the legal side?
We connect the payment gateway to your legal entity: you sign the acquiring contract, we do the technical side and test payment, refund and receipt flows. We also add the required pages: terms of offer, privacy policy, consent checkboxes in forms. Have a lawyer review the wording of those documents. We supply the structure, not legal advice.
Want to talk it through?
Tell us what needs building. We will work through the task, propose an approach and send a staged estimate. No charge, no commitment.
Related services
- Website development, end to endWe build sites that still hold up a year later: from a one-page CMS build to a store or a web application on React and Next.js. One team for design, code, integrations and launch.
- UX/UI design for websites and appsWe design interfaces that survive contact with production: research, structure, UI kit and a clean handoff to the developers. Everything lives in Figma as components with real states and real breakpoints, not as a folder of flat mockups. The same process covers landing pages, corporate sites, e-commerce, web apps and mobile.
- SEO and GEO website promotionSearch traffic is the one acquisition channel that keeps working after the ad budget stops. We run two tracks in parallel: classic SEO for Yandex and Google, and GEO, the work of getting your pages quoted inside AI Overviews, Yandex Neuro, ChatGPT and Perplexity, where a growing share of queries now ends. It starts with an audit, never with buying links.
- Targeted and search advertisingPaid advertising brings traffic the day after launch, and burns budget just as fast when audiences are guessed at and nobody counts the leads. We build campaigns in the channels that genuinely work in Russia in 2026: VK Ads, Telegram Ads and Yandex Direct, plus Meta and Google Ads for projects selling abroad. Tracking goes in before launch, not after.
Terms used on this page
- Commercial ranking factorsCommercial ranking factors are the group of signals Yandex applies to commercial queries: visible prices, assortment breadth, contact and company details, delivery and payment terms, reviews and live chat, in other words evidence that buying here is actually possible.
- EmbeddingsEmbeddings are numeric vectors a model produces from text, images or products so that items close in meaning end up close in the vector space, which is what makes semantic search, recommendations and duplicate detection possible.
- Headless CMSA headless CMS is a content platform with no built-in templating layer: editors work in a familiar admin panel while a website, a mobile app and any other channel pull the same content over an API and render it themselves.
Further reading
- What a Website Actually Costs in 2026: The Estimate, Line by LineA practical breakdown of a web development estimate: what analytics, design, front end, back end and integrations actually cost, which expenses always show up after launch, and where cutting the budget is safe.
- What to Build Your Site On in 2026: Tilda, WordPress, Bitrix or Next.jsBuilder, CMS or custom code is not a matter of taste but of scenario and planning horizon. We break down three-year cost of ownership, the ceiling of each platform, and what it costs to move if you picked wrong.
- SEO in Yandex in 2026: what changed and what no longer worksLink buying is dead weight, templated copy pushes pages into the low-value bucket, and behaviour manipulation is no longer a grey tactic but a way to lose the site. Here is what actually drives Yandex rankings in 2026.