Web & Software Development How Celion Builds a Website: From First Message to Launch
Celion builds websites not as decoration, but for a business purpose: we map the customer journey, add security from the...
Starting December 12, 2026, new rules will take effect in Uzbekistan for e-commerce platforms, aggregators, online stores, and foreign online sellers. Our recommendation is clear: do not limit this work to replacing the public offer text. Checkout, returns, seller verification, complaints, and payment flows also need to be reviewed.
The requirements vary depending on the business model. But marketplaces, stores that take orders through Telegram, and subscription-based digital services all face the same problem: the rules stated on the website do not work in the actual process.
Law No. O'RQ-1173 was published on September 11, 2026, and its main provisions take effect on December 12. According to the text of the law on Lex.uz, the changes cover marketplaces, service and order aggregators, streaming platforms, direct online sellers, and foreign companies selling products to consumers in Uzbekistan.
A platform operator must verify that a seller has the required license, permit, or notification, monitor prohibited products, and publish its complaint-handling procedure. The principles behind recommendation and ranking algorithms must also be explained. Unjustified changes to customer reviews create legal risk for the platform.
The seller remains primarily responsible for customer claims. If the seller cannot satisfy a lawful claim, the operator may also be held liable, depending on the contract and applicable law. As a rule, there is also a requirement to provide at least 30 days' notice before changing platform rules or discontinuing e-commerce operations.
The NAPP notification procedure took effect earlier. Operators should verify their status and compare it against the NAPP register of e-commerce operators. The penalty established for failure to comply with the notification requirement is 20 base calculation units.
It is easy to write “refunds are available” on the public offer page. In practice, however, an operator must be able to open an order and see the payment date, reason for the return, responsible employee, and where the money was refunded—all in one place.
For example, a customer sees a product on the website, asks a question on Telegram, a manager manually enters the order into 1C or the CRM, and payment arrives through Click or Payme. If the same order number is not used at every stage, staff will have to manually piece together records from the website, messages, warehouse, and bank when a complaint is filed.
This is also where the hidden cost of running a marketplace appears. Verification does not end when a seller uploads documents during registration. A permit may expire, the product category may change, or restrictions may be imposed on the seller's operations. That is why verification should not be a one-time form. It should be an ongoing process that tracks statuses and expiration dates.
The requirement to use separate bank accounts for covered e-commerce transactions also means financial flows need to be reviewed. Uzbekistan-based platforms that settle payments with foreign sellers should separately verify their VAT registration and tax-agent obligations. A website developer cannot solve this alone. The finance specialist, lawyer, and product owner need to make decisions based on the same process map.

Do not begin with a list of website pages. Start with a single test order. Walk through the entire process, from product selection to refund, and identify where evidence, a status, or a responsible employee is missing. The following fields provide a practical basis for the review.
Then review everything visible to the customer. Does checkout clearly show the final price and identify the seller? Are the delivery, return, and refund terms easy to understand? Are the rules for posting and moderating reviews stated openly? Does the privacy policy match the data the website actually collects?
Not every business needs to rebuild its platform from scratch. If a company sells only its own products and the existing team can handle the order volume, correcting the fields in the CMS, CRM, and accounting system may be enough. A multi-vendor marketplace, however, should not manage verification, expiration dates, disputes, and audit logs manually. At that scale, the cost of fixing errors quickly exceeds the cost of automation.
Celion does not treat this kind of project as simply “adding new text to the website.” We first map the statuses for orders, sellers, payments, returns, and complaints. Then we determine where each piece of data should be stored: in the CMS, CRM, Odoo, or 1C.
The scope may include updating checkout and customer accounts, creating a seller-document verification interface, sending Telegram notifications to the responsible employee before a document expires, and linking Click or Payme transactions to order numbers. For marketplaces, the complaint queue and immutable audit log are designed separately.
Do not start by translating the law directly into code. Choose one real order and review it from beginning to end. If employees have to collect evidence from different chats and spreadsheets whenever a customer submits a claim, the process needs to be updated.

Celion's e-commerce web development and business systems integration service connects your website, CRM, Odoo, 1C, and payment flows into one working process. The review begins with a map of a single order, from checkout to refund.
Callback
Leave your details and we will contact you shortly.
Become a Partner
Leave your contact details and we will get back to you shortly.
Order Service
Leave your phone number and we will contact you shortly.