Case study

UVBikes Delivery Marketplace Platform

A logistics-commerce/backend case study: a vendor-based delivery marketplace with Telegram web app ordering, catalog, cart, online payment initiation, vendor cabinet, courier workflow, administrator panel, and background workers.

Platform scope Workflow

Case summary

A Telegram-first marketplace rebuilt as a full delivery platform

The second version was built from scratch after a simpler prototype validated the strategy. The goal was to avoid a separate mobile application and give customers, vendors, couriers, and administrators a practical marketplace workflow through Telegram-connected interfaces.

Problem

Operations outgrew a simple bot

Administrators, couriers, shops, and restaurants needed easier control, better product presentation, order handling, vendor operations, courier flow, and delivery-price logic.

Our role

Full platform ownership

The work covered every layer: backend, Telegram web app, bot integrations, catalog, cart, vendor cabinet, courier workflow, admin panel, payments, OpenAPI, workers, and deployment.

System surface

Customers, vendors, couriers, administrators

The platform connected customer ordering, vendor catalogs and order fulfillment, courier acceptance/completion, administrator rules, payment collection, and background tasks.

Result

Telegram ordering became marketplace operations

Vendors and couriers received separate operational flows, while administrators received one layer for orders, vendors, couriers, delivery rules, tasks, and commercial settlement logic.

Why it matters

Delivery rules must match real operations

Bike-courier delivery needed pricing based on real riding dynamics, route behavior, fixed-gear movement patterns, average speed, vendor commissions, order count, order value, and courier labor cost.

Workflow

From Telegram ordering to marketplace operations

The project began as a Telegram-centered ordering flow: users interact with a bot, open a catalog through a web app, add products to a cart, calculate delivery, create an order, and initiate payment.

As the system developed, it became a multi-context delivery marketplace: vendors manage catalogs and order statuses, couriers accept and complete deliveries through Telegram, and administrators supervise vendors, couriers, delivery rules, global add-ons, background tasks, and platform settings.

  • Telegram web app catalog and cart flow
  • Order creation with delivery calculation
  • Online payment initiation and status handling
  • Vendor confirmation and fulfillment workflow
  • Courier acceptance and completion flow

Platform scope

Core modules

User

Catalog and cart

Telegram web app catalog opening, vendor and product retrieval, cart creation, quantity management, delivery calculation, order creation, and order status tracking.

Vendor

Vendor cabinet

Order lists, order detail views, product management, add-ons, product images, bulk import, vendor users, locations, and manual/internal delivery creation.

Courier

Courier Telegram workflow

Courier authorization, views for new and active deliveries, order acceptance, delivery completion, and status updates through a Telegram-based workflow.

Admin

Administrator panel

Management of vendors, couriers, orders, delivery rules, global add-ons, partner/payment settings, tasks, users, roles, settings, and background processes.

API

OpenAPI layer

Documented API endpoints for authentication, vendors, products, cart operations, delivery calculation, order lists and statuses, and payment initialization.

Workers

Background processing

RabbitMQ and Supervisord-backed workers, cron scheduling, product imports, operational tasks, logs, and deployment separation across application contexts.

Commerce and delivery

Catalog, order, payment, and delivery lifecycle

The platform centralizes product catalog publishing, product and add-on management, user cart creation, address validation, delivery-price calculation, order creation, online payment initiation, vendor order processing, courier dispatch, and delivery completion.

The payment integration boundary supports payment initialization, QR retrieval, confirmation, cancellation, token generation, notification, success, and failure handling at a high level without exposing payment-provider details.

  • Vendor-specific products and add-ons
  • Address lookup and delivery-price calculation
  • Order status lifecycle across roles
  • Online payment initiation and result handling
  • API and Telegram bot operational logs

Data and access

Built for sensitive commerce workflows

The platform handles user contact and authentication records, Telegram identifiers, visible vendor and restaurant records, vendor users, courier records, delivery addresses, order contents, comments, payment statuses, file uploads, logs, and operational task data at a high level.

Vendor identity is part of the marketplace workflow: customers can see which shop or restaurant they order from, and vendors manage their own catalog and orders.

  • Separate user, vendor, courier, and administrator contexts
  • Token-based API access for documented API scenarios
  • Role and right checks for vendor and administrator functions
  • Separate payment initiation and status handling
  • Background workers for imports and scheduled tasks

Operational impact

One layer for marketplace delivery operations

The platform gave a delivery marketplace a single operational layer for user ordering, vendor fulfillment, courier dispatch, payment initiation, and administrator supervision.

The implementation also supported a commercial model where vendors pay for platform usage based on received orders, order value, and courier labor cost.

  • Visible vendor and restaurant storefronts inside Telegram-connected ordering
  • Separate workflows for vendors, couriers, administrators, and customers
  • Delivery-price logic designed for real fixed-gear bicycle courier dynamics
  • Commercial settlement logic based on orders, order value, and courier work

Engineering

Technical emphasis

The implementation emphasizes a multi-role delivery workflow, Telegram web app and bot-based commerce, documented API integrations, cart/order/payment lifecycle management, vendor catalog operations, courier delivery status workflow, address validation, delivery-price calculation, MongoDB-backed storage, RabbitMQ workers, and maintainable separation across application contexts.

Back to projects Security and confidentiality Contact us
  • Telegram commerce workflow
  • Vendor cabinet and courier bot workflow
  • OpenAPI-documented integration layer
  • Delivery calculation and payment integration boundary
  • Background workers and long-term maintainability