A web application for buying cars at Japanese auctions, built from scratch.
A private service for choosing and buying cars, motorcycles and machinery at Japanese auctions. Clients see lots from all major auctions, translate auction sheets, submit bid requests and follow a car from purchase to shipping. Staff have requests, purchases, money and containers in one admin panel. The interface is in Russian, English and Japanese, with prices in the currency of your choice.
Current Japanese auction lots in the catalog, with no local copy of the database.
They check the catalog, requests, money and access. An update ships only when every check passes.
From the start of development to launch on the client’s domain.
Auction API integration without a local database copy.
Lots come from an auction data provider whose rules forbid keeping a copy of the data. The catalog, lot pages and statistics are built from API requests the moment a page opens, and speed comes from caching and background refresh.
- Live data: lot prices and statuses are always current.
- Smart caching: auctions refresh often, results archive once a day.
- Fast pages: all API requests go out at once, not one by one.
- A provider outage does not stop the work: clients see the last saved copy of the data.
Catalog and lot page: from a filter to a translated auction sheet.
Cars, motorcycles and machinery in one catalog. You can search several makes and models at once, plus chassis, year, mileage, grade, color, transmission, auction and lot number. Filters show how many lots match, and lots you have already viewed are marked in the list. A lot page has a full-screen photo viewer with zoom and swipes, similar sales and a hint when you have bought this model before.
- Auction sheet translated into Russian by a neural network: the client gets an image with the sheet and its translation.
- Month of manufacture from the chassis number, even when the number is only on the auction sheet.
- Landed price calculator: auction fees, freight, customs duty, recycling fee. The administrator changes rates on their own.
- Sales statistics: an archive of past auctions — sold for how much, unsold, withdrawn. You can see right away how much to bid.
A two-step bid request and an account that runs until shipping.
The client enters an amount and lands on a review page: the bid is spelled out in words, and an amount that looks too high or too low triggers a warning. That way an extra zero does not cost a car. Before the auction starts the client can cancel a request on their own, and after it “My requests” shows the starting price and the result.
- Purchased cars: photos, auction and lot, purchase price, the final amount once agreed, and the car’s status.
- Balance: payments in and costs for each car.
- Containers: the client builds a container from their own cars and sees loading, the vessel and dates.
- A yard with fixed prices: buy a car whole or pick the parts you need.
A built-in CRM: requests, purchases, containers, money.
We did not plug in an external CRM. Everything staff work with is built into the service and tied to lots. Urgent requests, with only hours left before the auction, are flagged separately. A list of rejected requests shows who the site turned down and why, so a manager can place the request for the client in the morning. See how we design systems like this on the Custom CRM development page.
- Bid requests desk: filter by status, auction, day and manager, change status in one click, print a bidding sheet and export to Excel.
- The purchased cars table works like Google Sheets: paste from Excel, custom columns, percentages of the price, history for every cell. The client sees an amount only after it is approved, and that is when it is charged to the balance.
- Containers and dismantling: container costs are split between cars automatically, dismantling sheets export to PDF, Word and Excel.
- Money: each client’s balance with the author of every entry, the company-wide balance and an internal balance for accounting.
Manager chat, support through Telegram and push on the phone.
For every request the client talks to a manager: files, photos, “delivered” and “read” marks. A support window sits on every page, and you can write even without signing in — say, when you cannot sign in. The service installs on a phone as a PWA, so notifications arrive even when the tab is closed.
- Notifications on the site, by email and by push about request status, purchases, balance, containers and replies. Each client chooses which emails to get.
- The support chat is linked to a staff group in Telegram: staff can reply on the site or in Telegram, and the replies show up in both places. We build links like this as part of our Telegram bot service.
- Staff hear about new requests and messages right away: on the site, by push and in the staff group.
- Favorites and saved searches: named lists with notes, and alerts about new matching lots.
Built from scratch: a custom core, no frameworks.
The service is written from scratch around the company’s needs, without an off-the-shelf CMS, frameworks or third-party packages. There is nothing extra in it, it runs fast and does not depend on someone else’s updates. We launched it in two weeks; it has been in use since September 2026 and keeps growing with us on ongoing support. More on our approach on the Web application development page.
- More than 1,600 automated tests: an update ships only when every check passes.
- Our own PDF, Word and Excel exports and our own push notifications.
- The catalog and forms work even without JavaScript. The interface is tuned for phones, with light and dark themes.
- Nightly backups, health checks and outage alerts.
A private service with approval-based access.
This is a working tool for the company and its clients, not a storefront. A person submits a sign-up request, a manager reviews it and activates the account, and the password arrives by email. Roles are client, manager, administrator and super administrator, each with its own permissions.
- Two-factor sign-in for staff and a sign-in log.
- Sign in as a client to see the service through their eyes.
- Account blocking and an activity log for staff.
- Email and page texts are edited in the admin panel, along with usage statistics and backups.
2 weeks from start to launch.
Roles, request statuses, data model, provider rules, the service core.
Catalog and lot page on the live API, calculator, results archive.
Requests, clients, balance, purchases sheet, yard, client account.
Chat with push notifications, support through Telegram, the client’s domain.
Your project:
Tell us your task — within 24 hours we'll come back with an estimate and timeline.
And get a personalized proposal with pricing and timeline.