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...
On November 12, 2026, WB Taxi was recognized in Uzbekistan as a digital platform operator holding a dominant position in the taxi order aggregation market. This does not mean that WB Taxi is the country's largest taxi service or that it has overtaken Yandex Go.
The decision has a different practical effect. WB Taxi's fares, commissions, terms for drivers, and requirements for switching to another platform will now face stricter antitrust oversight. That does not mean prices will fall immediately. Competition in the taxi market will no longer be assessed solely by the number of apps, but also by platform rules and the terms governing data use.
According to the Competition Committee's announcement dated November 12, 2026, WB Taxi LLC was recognized as a digital platform operator holding a dominant position in taxi order aggregation services. The announcement did not disclose the company's market share, revenue, or number of active users.
That is why claims that "WB Taxi has taken over the market" are misleading. A digital platform's dominant position is not determined by market share alone. Network effects, user numbers, business customers, or revenue may also be considered. This procedure is established by Cabinet of Ministers Resolution No. 256.
For comparison, historical data from the Tax Committee showed that Yandex Go accounted for roughly 85% of taxi receipts recorded in 2024. This older figure does not confirm the situation in 2026. It does, however, show that there is no basis for interpreting WB Taxi's new legal status as proof of market leadership.
There is another clear distinction: holding a dominant position does not mean the law has been violated. The status means that certain platform decisions will be examined more closely. For example, giving one group of drivers unjustifiably worse terms or artificially making it harder to switch to another service could attract the regulator's attention.
For passengers, the first question is simple: will rides become cheaper? At this point, there is no basis for answering "yes." Dominant platform status does not mean the government will set fares. Prices will continue to depend on demand, the number of available drivers, location, and the platform's calculation rules.
For drivers, the commission rate alone is not a sufficient benchmark. If a lower commission comes with fewer orders or longer pickup distances, net earnings will not increase. Instead of focusing on an advertised "reduced commission," drivers should look at how much they actually keep from each completed trip.
Businesses that use corporate transportation need to base their choice on even more practical criteria. Can the platform find a car on time? Is the receipt sent to accounting automatically? Can an employee's expense be assigned to the relevant project or branch? Providers should be selected based on answers to these questions.
The impact of this decision is particularly broad because of the market's scale. According to Tax Committee data, 329,1 million trips were recorded through aggregators between January and August 2026. At that scale, an unclear fare rule or a barrier to leaving a platform does not remain an issue within a single company. Hundreds of thousands of drivers and customers feel the effects.

We do not recommend connecting every company to several taxi platforms at once. If trip volumes are low and a transportation disruption would not halt operations, additional integrations and separate record-keeping only create unnecessary complexity.
But if transporting employees, couriers, or customers is part of daily operations, dependence on a single provider should be measured. A simple formula is enough: trips completed through the most-used aggregator ÷ all trips. If this figure is rising, prepare an alternative booking channel and data export process in advance.
Many companies overlook the cost of reconciling receipts manually. An aggregator may appear cheaper, but if an accountant must manually match every trip to an employee, branch, and project each month, the price difference is consumed by working hours. For a business using 1C or Odoo, there is a more useful benchmark: how cleanly does trip data flow into the accounting system?

The WB Taxi decision is not relevant only to taxi companies. A business building a marketplace, delivery service, or another service aggregator should store fare changes and partner terms in a form that can be reviewed later. User requests and complaints must not disappear either.
For a project like this, Celion can build a corporate transportation web portal, an administrator panel, and integrations using APIs or exports authorized by the aggregator. For example, an employee submits a trip request through a Telegram bot, and the responsible person approves it in a web panel. The expense is then sent to the relevant project and department in Odoo or 1C.
If the platform itself is being built, include fare versions and partner consent in the product architecture from the outset. Do not postpone the complaint queue or data export functionality either. An audit log added later often remains incomplete: the reason behind an earlier decision or the exact terms shown to a user may be impossible to reconstruct.
The rule is simple. If the failure of an external platform would stop a core operation, or if linking expenses to internal accounting is difficult, design the integration and an alternative process now. Waiting for the market or regulator to change will only make the work more expensive.
Celion's custom web application and API integration service can connect a corporate transportation portal and Telegram-based booking flow with expense accounting in Odoo or 1C.
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.