Workshop scheduling
Bookings sit in a diary, technician time sits on paper, and the job card is written for a technician rather than for anyone reading it later.
We build the systems a dealership runs on: vehicle inventory keyed to the VIN, workshop scheduling, a parts catalogue that survives supersession, telematics ingest and warranty claims that reconcile. This is the dealer, fleet and aftersales end of automotive software development, not software that runs inside the vehicle. If what you want is a vehicle marketplace, the classified app page is the one you want.
Tell us what you are building
Dealer management system development builds the systems a dealership runs on: vehicle inventory keyed to the VIN, workshop scheduling, a parts catalogue that survives supersession, warranty claims that reconcile, and telematics joined to service history. Phase one typically runs 12 to 18 weeks. The hard part is separating the vehicle, the asset and the customer.
Our work
We have no dealer group, workshop network, fleet operator or parts distributor among our clients, and saying so is cheaper than you finding out on the second call. What we have built is the two things a dealer system is made of: one stock and order model spanning businesses that each kept their own view, and a catalogue and costing layer over a bill of materials that keeps resolving as items change.
Symptoms
Six failures, and they arrive in this order. Find yours here before reading anything about modules, because what breaks decides what gets built and in which sequence.
Bookings sit in a diary, technician time sits on paper, and the job card is written for a technician rather than for anyone reading it later.
A manufacturer replaces a part number and you get orphaned stock, failed lookups and quotes that cannot be fulfilled.
Someone re-keys claims into a manufacturer portal, and rejections come back weeks later with no pattern anybody tracks.
Scope
Six pieces of work, and the first one decides what the other five cost. The hour range for each is published further down, with the arithmetic.
A catalogue that stores the supersession chain rather than the endpoint, so an obsolete part number still resolves and still explains itself.
Claim grade fields captured at the point of repair instead of reconstructed weeks later from notes written for a different reader.
Invoicing and statutory output behind its own adapter, so a new market or a new OEM requirement becomes an adapter rather than a migration.
Modelling
Because this is an identity problem before it is an integration problem, and collapsing the three into one is what makes it expensive later. A vehicle is a VIN, and it outlives everything attached to it. An asset is a financial position with a contract and an owner who may not be the driver. A customer is a connection that starts and ends.
Answerable only when sale, finance, service and parts hang off the VIN. Hang them off the account and the question dies at the first resale.
A contract has to be able to change vehicle, and a vehicle has to be able to change contract. One merged object allows neither.
Service history keyed to the customer disappears when the car does. Keyed to the VIN, it follows the car into the next owner's workshop.
Definition
A dealer management system is the operational software a vehicle dealership runs on. One system holds vehicle inventory, the sales and finance deal, the service department's bookings and job cards, the parts counter, and the accounting that ties them together, usually across more than one rooftop. It is the system of record, which is why most projects here are integrations with it rather than replacements of it.
Vehicle stock, the deal, finance and delivery. This is where the VIN either becomes the spine of the system or becomes an attribute of a customer record.
Invoicing, statutory output and floorplan interest against vehicles held in stock. A multi rooftop group needs this consolidated and rarely gets it.
Honest answer
We do not sell a dealer management system and we do not rank them, so we are the wrong people to name one. For an Indian dealer group one local constraint belongs on the shortlist early: GST e-invoicing, mandatory for B2B invoices above Rs 5 crore aggregate annual turnover since 1 August 2023. Past that, judge a candidate on three things rather than on a feature list.
Ask for the API documentation before you watch the demo. A documented API and a nightly export are the same requirement and a very different project.
On this vertical more than any other, the answer is often a module in your current licence. We read the licence before scoping a build and say so when that is the answer.
Most dealer systems are strongest at sales and weakest at aftersales. If service, parts and warranty are your problem, test those and ignore the sales demo.
Interfaces
Five counterparties, and the question to ask each one before you design anything. None of them are self service.
Ask what it will expose and accept, then verify by calling it. If the answer is a nightly file drop, this is a reconciliation project, not an integration.
Deposits, service payments and counter sales. The move that saves the most work is keeping card data out of your own systems entirely.
By operation
Find your operation in the first column. Dealer management system capability is the constraint in every row, because a documented API and a nightly export are the same requirement and a different project.
| Operation | What breaks | What we build |
|---|---|---|
| Franchised dealer group | Manufacturer systems, your dealer management system and your own reporting disagree, and the manufacturer's numbers decide your margin. Sales and aftersales are separate companies sharing a car park. | One vehicle record spanning sale, finance, service and parts, reconciled against the manufacturer feed rather than maintained beside it. |
| Independent workshop network | No OEM feed, so parts identification depends on the person at the counter and the catalogue is whatever the supplier last emailed. Job history is per site, not per vehicle. | A parts catalogue with supersession and cross-reference at its centre, and service history keyed to the VIN. |
| Fleet and leasing operators | The asset, the contract and the vehicle are three different things, and a model that holds only one of them cannot answer for the other two. Utilisation, maintenance cost and residual value each live somewhere else. | Asset and contract modelled separately from the vehicle, with telematics and workshop cost joined on the VIN. |
| Parts distribution | Supersession chains, and superseded-by-superseded, make catalogue integrity the whole job. A wrong cross-reference is a returned part and a lost customer. | A catalogue that stores the chain, so a lookup on an obsolete number still resolves and still explains itself. |
| Mobility and rental | Vehicles move between locations and states faster than any nightly batch, and availability is the product. Damage and cleaning states matter as much as mechanical ones. | Real time vehicle state with location and condition as first class fields, and availability computed rather than kept by hand. |
Five operations, one shared week one decision, and it is a modelling decision rather than a software choice. If what you actually want is a vehicle marketplace rather than the systems behind the vehicle, that is a different build and it is classified app development, not a dealer platform.
Compliance
Not a badge wall. These are the instruments that change the data model, the consent surface or the delivery date. The five EU rows are quoted or paraphrased from the Official Journal texts on EUR-Lex, never from a competitor's page. Each row carries the date it was last read, so you can see which ones are fresh.
| Instrument | What it forces the software to do | When |
|---|---|---|
| EU Data Act, Regulation (EU) 2023/2854 | Data from a connected product has to be made accessible to the user, and to third parties the user names. On a dealer or aftersales build that decides who may read vehicle generated service data and on what terms. | Two dates, and they are not the same thing. The regulation says it shall apply from 12 September 2025, which is general application. Separately, the obligation in Article 3(1) applies to connected products, and the services related to them, placed on the market after 12 September 2026, which is the date a vehicle data buyer plans around. Both have passed. Read 17 November 2026. |
| Owner permission is the gate | Access is user mediated rather than automatic. A workshop or a distributor gets vehicle data because the user granted it, which makes consent capture and revocation a screen somebody has to design, build and audit. | With the Data Act, from 12 September 2025. Read 17 November 2026. |
| Regulation (EU) 2019/2144, general vehicle safety | The type approval frame that makes UN regulatory acts on software update processes mandatory. Its recitals treat those UN Regulations as something to be applied on a mandatory basis as soon as possible after they enter into force. It binds the manufacturer, not you, and it is why an OEM's rules about software reaching a vehicle are not negotiable at the dealer counter. | The text reads that it shall apply from 6 July 2022, with named articles applying from 5 January 2020. Read 17 November 2026. |
| UN Regulation No. 155, cyber security | Cyber security and a Cyber Security Management System as a condition of vehicle type approval. It binds the manufacturer. For your build it is the constraint on what may be written back to a vehicle, and on what an OEM will let your systems touch at all. | Published in the Official Journal of 9 March 2021 at L 82/30. We state no entry into force date: EUR-Lex says only the original UN/ECE texts have legal effect and sends the reader to UN/ECE status document TRANS/WP.29/343, which we have not read. Read 13 November 2026. |
| UN Regulation No. 156, software updates | Software updates and a Software Update Management System as a condition of type approval. It defines RXSWIN as an identifier set by the vehicle manufacturer representing the type approval relevant software of an electronic control system. That matters at design time: the manufacturer's software identity already has a defined name, so your vehicle record should not invent a second one. | Published in the Official Journal of 9 March 2021 at L 82/60, with the same caveat as R155. We state no entry into force date for it either. Read 13 November 2026. |
| PCI DSS v4.0.1 | Multi-factor authentication for all access to the cardholder data environment, not only administrative accounts. Deposits, service payments and parts counter sales all touch it. The practical move is shrinking that environment so card data never reaches your own systems. | The 51 future dated requirements in version 4 became mandatory on 31 March 2025, per the transition timeline published by the PCI Security Standards Council. Read 13 November 2026. |
| India, GST e-invoicing | B2B scope, which in this sector means fleet contracts, trade parts sales and inter-branch transfers rather than the retail service invoice. Above Rs 10 crore turnover there is a 30 day window to report an invoice to the Invoice Registration Portal. | Mandatory above Rs 5 crore aggregate annual turnover from 1 August 2023, under the GST e-invoicing notifications. Confirm the threshold before you contract, because it has stepped down several times. Read 13 November 2026. |
We hold none of these approvals: no type approval, no payment card assessment, and no certification or attestation of any kind. We build the records that let you satisfy them, and we keep each regime behind its own adapter, because type approval, data access and fiscal output change on their own timetables. One boundary, stated plainly. ISO 26262, ISO/SAE 21434, AUTOSAR, MISRA and ASPICE govern software that runs inside the vehicle. They are other people's work: we do not build to them, and we will say so on the first call. For the side of this estate where the part is made before it is fitted, see manufacturing software development.
Transparency
We publish the hours, module by module, with the six things that move them in the table below. A fixed price follows discovery, because the largest single variable is what your dealer management system can actually expose.
Phase one
750 hours
The worked example below, summed across six modules that each publish their own range.
Typical timeline
12 to 18 weeks
The long pole is separating the vehicle, the asset and the customer, not the integration work.
Useful hours
510 to 980
Every module at its minimum, through to every module at its maximum.
| Driver | Hours |
|---|---|
| What your dealer management system can exposeEstablish it first by calling the interfaces. Every other number on this page depends on the answer. | Highest impact |
| Whether the VIN is already the spineIf history hangs off the customer account, this is a data migration with a business rules problem attached, not a schema change. | High |
| OEM feeds in scopeEach one is a separate portal, format and credential. The first is a build, the third is cheaper, and none of them are self service. | High |
| Telematics volume and retentionIngest is straightforward. Deciding resolution and retention per signal is the part that gets deferred and then costs storage forever. | Medium |
| Single site or groupA group adds one stock model across rooftops, inter-branch transfers and consolidated reporting, none of which a single site needs. | Medium |
| Connected or two way servicesRead only telemetry is comparatively simple. Anything writing back to a vehicle brings consent capture and a scoping exercise with it. | Low to medium |
| Module | Hours |
|---|---|
| Dealer and inventory model | 80 to 160 |
| Service scheduling and workshop | 100 to 190 |
| Parts catalogue and supersession | 90 to 170 |
| Telematics ingest and join | 110 to 200 |
| Warranty and claims | 70 to 140 |
| Fiscal and compliance output | 60 to 120 |
Delivery
Five phases, each named by the artifact it hands you rather than by a stage in a generic waterfall, so you can ask to see one. The first phase exists partly to find out whether the build is needed at all.
Phase 01
A written statement of what the dealer management system, the OEM feeds and the telematics provider can each expose and accept, produced by calling the interfaces. If the capability is not there, the honest scope is smaller than the one you asked for, and the document says so.
Phase 02
Vehicle, asset and customer separated on paper, with the VIN as the spine and the registration demoted to an attribute with history. Agreed before anything is built against it.
Phase 03
A parts catalogue in which an obsolete number still resolves, and can explain why it resolved the way it did.
Phase 04
Scheduling, job capture and claim grade fields recorded at the point of repair instead of reconstructed for a portal weeks later.
Phase 05
Telemetry joined to service history on the VIN, with fiscal output behind its own adapter, so whole life cost is a query.
It is the operational software a vehicle dealership runs on: vehicle inventory, the sales and finance deal, workshop bookings and job cards, the parts counter, and the accounting that ties them together. In a group it spans more than one rooftop. Because it is the system of record, most work in this sector integrates with it rather than replacing it.
There is no single answer and we do not rank products, because we do not sell one. The useful test is what a system will let out, so ask for API documentation before you watch a demo. Then test service, parts and warranty, which is where most dealer systems are weakest.
We do not rank CRMs either, and the decision that matters more than the product is what the CRM is allowed to own. If the customer record owns the vehicle, service history disappears at the first resale. Key the history to the VIN, let the CRM own the relationship, and the question becomes a much smaller one.
It depends which half of the industry you mean, and the two halves share almost nothing. Inside the vehicle, engineering teams work in toolchains built around in-vehicle safety and cyber security standards, which is not work we do. Around the vehicle, a dealership runs on a dealer management system, a parts catalogue, a telematics platform and a warranty portal. We build against that second set.
The worked example on this page is 750 hours across six modules, and 12 to 18 weeks as a squad. The full span is 510 hours at every minimum and 980 at every maximum. The long pole is not the integration work, it is separating the vehicle, the asset and the customer.
Directly they bind the vehicle manufacturer, as a condition of type approval: R155 covers a Cyber Security Management System, R156 a Software Update Management System. Both were published in the Official Journal of 9 March 2021, at L 82/30 and L 82/60, read on EUR-Lex on 13 November 2026. We state no entry into force date, because only the original UN/ECE texts have legal effect. Indirectly they are your problem anyway: they decide what a manufacturer will let your systems touch.
Two dates, and they are not the same thing. The Data Act, Regulation (EU) 2023/2854, says it shall apply from 12 September 2025. Separately, the obligation in Article 3(1) applies to connected products, and the services related to them, placed on the market after 12 September 2026. Both dates have passed. Both come from the Official Journal text read on EUR-Lex on 17 November 2026. For your build it means vehicle generated data has to be accessible to the user and to third parties the user names, so consent and revocation are screens you have to build.
Four steps with a shape attached to each, so booking a call is a known quantity.
Bring the name of your dealer management system, your OEM list, and one question about a vehicle you currently cannot answer. Those three things tell us more than an hour of description.
What your dealer management system can expose, and what it already does. On this vertical the second question removes scope surprisingly often.
The modules, the hour ranges and the arithmetic, not a headline figure. If the honest answer is a configuration change, the document says that.
You choose whether we build it, your team does, or your vendor does. The document is useful in all three cases and it is yours either way.
Almost every question on this page resolves to whether the vehicle is your spine or an attribute of a customer record. We will read your dealer management system capability, tell you which it is, and give you the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
Vehicle identity and service history live here
Workshop, counter and group reporting
Telematics ingest and device estate
The ingest queue in front of the telematics feed
Maintenance prediction on the telemetry join
Warranty packs and supplier paperwork
The vehicle marketplace and listings product
Where the part is made before it is fitted
Parts distribution and the dealer supply chain
Every sector we build for, in one place
Cost, telematics and operations posts that apply directly to dealer, fleet and aftersales work.