Skip to content
ORMUS

Projects

ROCAR

A vehicle listings and transport marketplace platform.

StatusOngoing
Open the site

The platform is publicly live. Work continues on new sections, search refinement and performance.

rocar.aimarket.az
The visitor opens the listing grid, chooses a sort order and pages through results.
rocar.aimarket.az — Mobile

The business problem

On a listings marketplace a buyer searches across dozens of parameters: make, model, year, mileage, body type, fuel, drivetrain, price range. Once there are that many filters an ordinary form slows down and people abandon the search halfway. And a buyer states what they want as a sentence, not as a filter set.

The ORMUS role

ORMUS is responsible for the technical side of the platform: the catalogue and search logic, filter handling, the listing page, system integrations, server infrastructure, the release process and technical support after launch.

User journey

  1. Entering the catalogue

    The visitor opens the listing grid, chooses a sort order and pages through results.

  2. Applying filters

    Make, price, mileage, body type and other parameters are set; the result count updates immediately.

  3. Free-text search

    The visitor writes the request as a plain sentence and the system turns it into filters.

  4. The listing page

    Photo gallery, technical specification, deal terms and the condition the seller states.

Key capabilities

  • Listings catalogue with sorting and pagination
  • Multi-parameter filter panel
  • Free-text search
  • Listing page with photo gallery
  • Dealer, rental and registration-plate sections
  • Mobile interface and saved listings

ROCAR is a public platform for buying and selling vehicles: a listings catalogue, precise filters, free-text search, the listing page, and dealer and rental sections. The ORMUS team runs the platform side, the search logic, the integrations and the release process.

Architectural approach

Reading the catalogue and writing listings are kept on separate paths: search queries run against a read-optimised index, while listing changes are written to the primary store. The split exists so a heavy filtered query cannot slow write operations down. Images are stored separately with their sizes prepared in advance.

Security and privacy

Seller contact details are not published on the listing page. Moderation and a reporting mechanism are in place. Server configuration, internal addresses and database structure are not disclosed.

Scope of work

  • Platform-side development
  • Search and filtering logic
  • System integrations
  • Infrastructure and release process
  • Ongoing technical support

Technology direction

Web platform, API integrations and server infrastructure. Specific architectural decisions are not disclosed.

Related services

Need something similar?

Describe your situation briefly and we will work out together how a system like this would fit your processes.