Marketplace véhicules · Belgique
A dealer will never re-key their stock.
That single constraint decides whether a vehicle marketplace exists at all. A professional seller already keeps their fleet in AutoScout or mobile.de. Asking them to retype forty vehicles into a third site is the same as having no stock. AutoMotoMarket.be starts from that.
See the live systemThe problem
A used vehicle marketplace is judged on catalogue depth the day it launches. With no listings there are no buyers, and with no buyers no dealer spends time publishing.
The blocker is not the listing form. It is that the stock already exists elsewhere, in AutoScout, in mobile.de, or in a CSV or XML export from the garage's own management software. Each with its own format, photos, trim fields and availability rules.
On top of that sits a trust problem specific to the Belgian market: without mileage history a used vehicle listing is worth nothing, and a buyer has no way to tell a serious seller from anyone else.
What we did
We built the ingestion first and the interface second. The site accepts CSV and XML import and synchronises with AutoScout and mobile.de stock, so a dealer connects the fleet they already maintain instead of retyping it.
Every source lands in the same listing object, with the same handling of photos, trim and withdrawals. A sold vehicle has to disappear on both sides, otherwise the catalogue lies and the buyer does not come back.
For trust, sellers are verified by email and shown as verified, the official Car-Pass accompanies listings, and the ranking rules are published rather than kept quiet.
The site runs on Next.js and Vercel in French, Dutch and German, with search filtered by price, fuel, location and mileage. Private sellers list free; dealers take a subscription at EUR 79 per month.
Where it stands
The site is live and open. You can run a search, open a listing, see a verified seller badge and read the ranking rules without contacting us.
The commercial model runs both ways: free listings for private sellers, a EUR 79 per month professional tier with stock import.
We publish no audience or transaction figures. Those belong to the operator and were not given to us for publication.
- Next.js
- Ingestion de flux CSV et XML
- Synchronisation AutoScout et mobile.de
- Vérification e-mail
- Abonnement professionnel
- Vercel
This is the reference to look at if your problem is feed integration. Wiring AutoScout and mobile.de is the same work as wiring an ERP, a PIM or a supplier: normalise, deduplicate, make the operation replayable, and handle withdrawals properly.
Common questions
- Can you integrate a source you have not seen before?
- Yes. The work is not about the brand of the source but about its contract: format, frequency, volume, deletion semantics and behaviour when it fails. We always start with a feed inventory, because that is what turns a range into a commitment.
- What happens when a feed goes down?
- That question decides the architecture. A catalogue showing vehicles that are already sold does more damage than a catalogue that is briefly incomplete, so freshness and withdrawal rules get decided before development, not after the first incident.
- Does this transfer outside automotive?
- The domain changes, the problem does not. Several sources of stock or catalogue data that must become one reliable truth is the same mechanism for parts, property or supplier references.
Does your stock live in several systems?
Describe your sources and what falls out of sync, with no confidential code or personal data. We scope the feed inventory before proposing anything.
Describe my problem- Technical debt: what it costs and when to repay itHalf of what gets called technical debt is not debt. How to tell deliberate borrowing from ordinary mess, how to make the cost legible to a board, and why some of it should be left exactly where it is.
- Zero downtime data migration: dual write to cutoverThe new system shadows the old one in silence, the copies are proven to match, and the rollback lever stays live until the end. The full playbook, priced, limits included.
- System architecture principles that survive productionAn architecture is not judged on a diagram. It is judged the night a service goes down, the month the team doubles, the year the product pivots. These are the principles we apply to every system we build.
- Azure for an SMB: architecture, costs, GDPRLessons learned from deploying Azure architectures for European SMBs, Function Apps, App Services, container workloads, and the practical advice I wish someone had given me earlier.
- ParkAgenda · Operations SaaS for airport parkingMulti-channel bookings reduced to a single queue, then shuttles, staff scheduling, vehicle condition capture and on-site payment.
- Pavimmo · CRM migration with zero business interruptionYears of client history cleaned, mapped and reconciled, with the source system in production from the first day to the last.