What drives the price
The price depends less on the number of pages than on the logic around an order: how many products and variants, where stock comes from, how delivery is calculated and which systems the store exchanges data with. Start covers a mid-size catalogue, online payments, delivery and a manager panel, enough to move sales from chat threads into a system. Business adds 1C sync, a customer account, rewards, a second language and orders passed to your CRM. Chain is for companies with several warehouses, separate retail and wholesale prices and a mobile app. The tiers are compared in the table below, and the final amount is fixed in the contract.
How the work goes
The first days go into how an order lives today: who takes it, where stock is checked, how it reaches the courier and what happens on a return. That produces a process map and a product card with the right attributes. Then comes the design of the catalogue, product page and checkout on a phone, followed by the build: catalogue, cart, payments, delivery, admin panel. Every two weeks you review a working version and place real test orders on it, with payment and refund. Before launch we migrate products and customers and reconcile stock and prices. Bugs found after launch are fixed free of charge, with no time limit.
Local specifics
Buyers here pay through Payme, Click and Uzum, with Humo and Uzcard cards or in cash to the courier, while companies pay by invoice; the store has to accept all of these and show the accurate status of every payment. Stock and prices often live in 1C, so the sync is set up to keep the site from selling what is not in the warehouse. The interface is built in Uzbek and Russian, notifications included. Confirmation codes and order statuses go out by SMS through Eskiz using approved templates, and the manager gets each new order in Telegram. For delivery we connect your own couriers or delivery services with pricing by city zone.
Common mistakes and risks
The most painful mistakes involve money and data. A payment goes through, yet the order stays unpaid because the payment provider response is never re-checked. The price or order total can be changed in the browser if the server does not recalculate it. Cheap and AI-generated builds sometimes expose the order list with customer phones and addresses, or keep payment keys in the page code. And orders get lost when the 1C sync fails and nobody notices. We recalculate every amount on the server, reconcile payments and monitor the sync. Your engineer may check the code against the contract: an unfulfilled item means a 10% refund.