Car and bots: a web platform for finding and ordering auto parts

Before the platform, parts sourcing was manual and fragmented: requests were collected outside a single system, operators handled them without a shared tool, and there was no monetization model for the services. The whole chain had to be automated and made manageable.

Access control added complexity: customers, operators and administrators each had to see only their own part of the system. That called for a role model, integrated payments and a transparent catalog where users could find the parts they need on their own.

We designed a multi-level role system with several user types and integrated payments to automate the business processes of finding and ordering parts. A customer submits a request or searches the catalog, an operator handles it, and an administrator manages access and services.

Monetization is built on paid services and subscriptions: a free trial, access to the full parts catalog and one-off sourcing requests. The interface uses a dark theme with a purple accent, and catalog search is complemented by search by OEM number.

An auto parts aggregator with an operator workspace and multi-level roles needs specific business logic that off-the-shelf marketplaces (Yandex.Market, Avito, Exist) don’t offer without heavy customization. Custom development let us implement a unique interaction model between roles and the logic for verifying parts before payment.

A 1C-Bitrix-based option was also considered, but its Marketplace edition did not support the required operator role model without substantial rework of the module.

The platform handles customers’ personal data and their vehicle data, so access is strictly separated by a five-level role model: each user sees only their own part of the system.

Payments are integrated through a certified payment gateway: subscriptions and one-off services are paid on the provider’s side, and the platform stores only the request and order data it needs to operate.

The service processes users’ personal data (authentication, order history, payment details). Data is processed under the requirements of the client’s jurisdiction, stored on locally hosted servers, and access is restricted by role.