A web application for buying cars at Japanese auctions, built from scratch.
A service for a buying agent: clients from Russia and the CIS browse lots, get a full landed price and submit a bid request, then a manager takes the deal all the way to shipping the car in a container. Lots live with the data provider, whose rules forbid keeping a copy of the database. So every page is built from live API requests.
Current Japanese auction lots in the catalog, with no local copy of the database.
They check the catalog, requests, calculations and access so updates break nothing.
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.
- Protection from provider outages: automatic retries and a slow response log.
Catalog and lot page: from a filter to a full landed price.
Cars, motorcycles and machinery in one catalog. Filters by make, model, year, grade and mileage show how many lots match. A lot page has photos, the auction sheet with decoded grades, neighbouring lots and similar sales from the archive.
- Landed price calculator: auction fees, freight, customs duty, recycling fee. The administrator changes rates on their own.
- A 3-month results archive: average, minimum and maximum price, with a chart.
- Three languages and five currencies: Russian, English, Japanese.
- A fast catalog even with many filters applied.
A built-in CRM: requests, clients, money, purchases.
We did not plug in an external CRM. Everything a manager works with is built into the service and tied to lots. A bid request moves through clear statuses, each request keeps a history, and the client gets an email at every step. See how we design systems like this on the Custom CRM development page.
- Bid requests desk: filters, one-click status changes, inline editing.
- Client card and balance: you can see who added an entry and who voided it.
- The purchased cars sheet works like a spreadsheet: paste from Excel, undo, custom columns, Excel export.
- Container and dismantling sheet: a parts catalog with export to PDF, Word and Excel.
Client account, chat and support through Telegram.
Clients sort favorites into lists, save searches and get emails about new matching lots. They talk to their manager in a chat with attachments. The service installs on a phone as a PWA, so notifications arrive even when the tab is closed.
- Push notifications on the phone without installing an app from a store.
- The website support chat is linked to a Telegram group: staff reply in Telegram and the answer appears in the visitor’s window. We build links like this as part of our Telegram bot service.
- Auction sheet translation on request and a “My purchases” section with statuses.
- A yard with fixed prices: a car can be added from a phone right on site.
Built from scratch: a custom core, no framework.
The service is written from scratch around the agent’s needs, without an off-the-shelf CMS or heavy frameworks. There is nothing extra in it, it runs fast and does not depend on someone else’s updates. After launch it stays with us for ongoing support. More on our approach on the Web application development page.
- Pages open instantly: the server builds them, not the browser.
- Emails to clients at every step of a request.
- Exchange rates update automatically, with a fallback source.
- Automated tests for key scenarios.
A private service with approval-based access.
Anyone can sign up, but using the service requires administrator approval. Roles are client, manager, administrator and super administrator, each with its own permissions.
- Two-factor sign-in through an authenticator app.
- Sign in as a client, so support sees exactly what the client sees.
- Account blocking and an activity log for staff.
- New sections can be switched on or hidden with one setting.
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.