We build catalogue and dealer systems for automotive parts suppliers, where a dealer finds the right reference without calling to ask.
Parts are found by number, not browsed by category. These are the parts that make it a different system.
Thousands of references, searched by OE number, by cross reference or by vehicle. The person on the other end finds the part without calling to ask which one fits.
Each dealer logs in, sees the range they are entitled to, their own prices and the stock behind them. The orders that used to arrive by phone and email arrive in the system instead.
Dimensions, materials, certificates and which vehicles a part fits, held against the part rather than in a folder somebody maintains by hand.
What is in each location, what is reserved and what is on the way. A dealer sees availability rather than a promise.
Different territories and different agreements carry different prices. The price comes from the agreement rather than from whoever answers the phone.
The same data produces the PDF catalogue and price list the trade still asks for, generated rather than rebuilt by hand every season.
Both situations are routine for us. Tell us which one applies and we will shape the first call around it.
The process runs in five steps, in the same order on every project. You can stop after any of them.
You outline how your range is managed and how dealers order today. We ask a few questions and tell you whether a custom system is worth building for it. If it is not, you hear that on the same call.
We go through the detail together. How many references, how cross references are held, how prices are agreed per territory, what your accounting software is, and what has to keep working while we build.
You receive a document that states what will be built, in what order, on what timeline, and at what cost. You read it before anyone signs anything.
The agreed scope becomes a signed contract. The confidentiality and intellectual property terms are set out in the same document, rather than in a separate one or at a later stage.
Development starts and we deliver working software at regular intervals. A preview environment goes up within the first week, so you can follow progress in the product itself.
Every system we write is built for one company. We do not sell a ready-made product. Tell us what you want to do and we will reply the same working day, and you get the scope, the timeline and the price in writing before anything is signed.
You do not need the technical side to judge this. Here is what changes on the business side.
The catalogue answers the questions that used to go to the one colleague who knew the range. That person gets their week back.
Availability, prices, technical data and order history are in front of them. The calls that used to interrupt the day stop arriving.
Fitment and cross references are on the record, so the order is checked against the vehicle rather than against memory. Returns cost more than the margin on the part.
Which references, how often, at what value. The conversation about a distributor agreement starts from the figures.
New references, new prices and a new printed catalogue come out of the same data, rather than out of a file somebody edits for three weeks.
Cross references, fitment and supersessions live in the system. The business keeps running when the person who knew it all is away.
The questions to put to anyone quoting for a parts catalogue, and the commitments we make on each of them.
If you carry a short range and sell to a handful of accounts, a spreadsheet is cheaper than anything we would build. You will hear that on the first call.
A product catalogue and dealer portal for a wheel hub manufacturer, with PDF catalogue output and dealer-specific ranges. The case study is on this site.
Your accounting and stock systems stay where they are. We build the catalogue and dealer side and connect the two, so nothing has to be switched off.
You know the scope, the timeline and the price before you commit. We would rather lose the project at the scoping stage than argue about what was included halfway through it.
Who owns the code, and whether we may name the work as a reference, are both settled in the contract before the first line is written.
We stay inside the conventions the ecosystem already has and we do not invent project-specific abstractions nobody else would know. Any developer can continue the project without a rewrite.
We create modern solutions using cutting-edge technologies

Production-grade React applications with SSR

Elegant PHP framework for web artisans

Building interactive and responsive user interfaces

Relational database design, migration and tuning

Document database modelling and aggregation pipelines

Custom applications and legacy system modernisation

Server-side JavaScript for scalable applications

Backend development and data processing solutions

Progressive JavaScript framework for modern web UIs

Type-safe JavaScript for enterprise applications

Modern web development with React, Next.js, and Node.js

Modern utility-first CSS framework
An automotive parts business runs on references rather than on products. The same hub carries an OE number, three competitor equivalents, a supersession from two years ago and a list of vehicles it fits, and the buyer may arrive holding any one of those. A catalogue that cannot be searched from all of them sends people back to the phone, which is where the cost actually sits.
A system built for this trade starts from the reference and hangs everything else off it. Fitment and cross references make the catalogue searchable, the dealer account decides which range and which price appear, stock is shown per warehouse so availability means something, and the printed catalogue is generated from the same data rather than rebuilt by hand each season. Where the work is wider than the parts side, readcustom software developmentinstead.
Tell us how your range is managed today. If a custom system is not worth building for it, you will hear that on the first call.
We reply the same working day