One customer, one vehicle, one order
Four object types, vehicle, customer, work and money, that every module reads and writes. There is no second copy to fall out of date.
Omnetic DMS Core
Nineteen modules. One record. This is the one you buy first.
Omnetic DMS is the vehicle, customer, work and money record every other module reads and writes. Everything on this page exists so the other nineteen never have to be integrated with each other.
TMBJJ7NE0N0123456
One vehicle · every module that touched itOne vehicle
- SourcingDay 01
Candidate in Wien, landed cost 508 400
- CarAuditDay 04
48 photos, 3 findings, condition certified
- Price ReportDay 04
32 comparables · recommend 589 000recommend 589 000
- WorkshopDay 06
Preparation 2.4 h, parts 4 000
- Used Car SalesDay 07
Published to 3 portals and the dealer site
- CRM · BRAIN™Day 39
Enquiry answered in 4 min, viewing booked
Eight modules, forty-one days, one record. No integration between any two of them, because there is nothing between them to integrate.
Digital Deal
Day 41Offer adjusted, cover added, signed 16:42
Accounting
Day 41Invoice posted, margin 78 020
One vehicle · every module that touched it · Sample data · not a dealer's record
- Best fit
- Everyone in the business · Site manager · IT or transformation lead · Principal or CFO
- Operational job
- Keep vehicle, customer, work and money as one event-driven record that every selected module reads and writes, so the dealership can add capabilities without re-keying data or maintaining integrations between them.
- What you get
- A governed customer and vehicle record linking work, documents and postings.
The problem
A suite is products that were once separate companies.
You can tell from the outside: the same customer exists three times, a price change has to be made twice, and every report needs someone to explain why two numbers differ. Omnetic was built the other way round, one record first, modules as views onto it. Which is why this page is short: most of what a DMS page normally promises is simply absent as a problem.
Events, not overnight files
A signature, a work order or a price change emits an event other modules react to immediately, which is why the workshop knows about a sale the same minute.
Configuration, not customisation
Markets, brands, entities and roles differ by configuration. Nobody maintains a private fork of the system for one country or one group.
The four objects
Vehicle, customer, work, money
Select an object to see what it holds and which modules write to it.
The vehicle, from candidate to third owner
Identity, specification, condition, cost, position, publication state, work history and ownership, all on one object, whether the car is stock, a customer's own, or a fleet unit.
A car sold and later serviced is the same record, which is what makes a changeover conversation possible years later.
- Holds
- VIN, equipment, condition and findings, landed cost, market position, listings, work history
- Written by
- Sourcing, Carvago BUY™, CarAudit, Autotracer, Price Report, Stock Report, Sales, Workshop, Fastback
- Never
- Duplicated per department, or re-keyed between them
The customer, across every department
Contacts, the cars they have owned, opportunities, orders, invoices, policies, consents and every message, so the service desk and the salesperson are looking at one person.
Consent is part of the record rather than a spreadsheet, which is what makes marketing defensible.
- Holds
- Identity, contacts, vehicles owned, opportunities, transactions, documents, consents, communication
- Written by
- CRM, Sales, Digital Deal, Workshop, Rental, Vehicle Insurance, BRAIN™
- Never
- Split into a sales contact and a service contact
The work, whoever it is for
Orders, their items, the parts reserved against them, the hours recorded on them and who pays for each, customer, brand or the business itself.
Sales preparation and customer servicing are the same object type, which is why they can compete honestly for the same bay.
- Holds
- Work orders and items, parts reservations, hours, payer, status, approvals
- Written by
- Workshop, Planner, Warehouse, Time-keeping, CarAudit, Sales
- Never
- Internal preparation hidden from the capacity plan
The money, posted once
Documents, postings, payments, stock valuation and margin, created by the event that caused them, in the entity and currency that owns them.
Because the posting carries its vehicle and order, a group figure can always be opened down to the deal underneath it.
- Holds
- Invoices, postings, payments, valuation, margin, entity and currency
- Written by
- Accounting, Sales, Workshop, Warehouse, Rental, Vehicle Insurance
- Never
- Re-keyed from a folder of documents at month end
Scope is a property of the role
A Brno advisor and a group controller open the same objects and see different amounts of them. Permissions live on the data, not on the screen, so a report cannot leak what a role may not read.
Every read and write is logged with the user, the time and the previous value, which is what makes the audit trail worth having.
- Holds
- Roles, site and entity scope, field-level rights, audit entries
- Applies to
- Every module, every API call and BRAIN™ alike
- Never
- Bypassed by an integration or a prompt
The nineteen
Everything that reads and writes this record
Turn on what you need. Adding a module later does not migrate anything — it starts writing to vehicles that already exist.
Sales & customer
Inventory & profit
Sourcing
European vehicle sourcing by landed cost.
Carvago BUY™
Cross-border buying in selected markets.
Price Report
Market pricing from comparable sales.
Stock Report
Stock ageing and margin monitoring.
CarAudit
Mobile inspections and damage records.
Autotracer
Vehicle history and mileage checks.
Fastback
Trade remarketing in selected markets.
Service & operations
On the record itself
Omnetic BRAIN™
Reads the record under the acting role's permissions, proposes, a person approves.
Open Platform
The same objects and events exposed to your own systems.
Security & Trust
Roles, residency, audit and recovery objectives.
By role
Who this changes the day for
Everyone in the business
Stops re-typing what a colleague already entered, which is the single largest source of wasted time in a dealership.
Site manager
Answers a question once rather than reconciling three versions of it first.
IT or transformation lead
Has no integrations to maintain between modules, and one permission model to govern instead of nine.
Principal or CFO
Gets a number the sites recognise, because it was built from the events they produced.
Rollout & migration
Leaving a legacy DMS without a lost weekend
Master data migrates
Customers, vehicles, suppliers, parts catalogue and chart of accounts.
Open items migrate
Stock on hand, open orders, open work orders and open balances.
History is archived
Closed deals and invoices stay searchable as read-only records.
One site first
The pilot proves the configuration; later sites inherit it. Timings pending delivery sign-off.
System relationship
Omnetic DMS Core in the connected product system
One shared record connects decisions, open interfaces, access governance and the team’s daily work without a second copy of the customer or vehicle.
Omnetic DMS Core
Outcome & proof
What we can and cannot claim yet
Answered only as far as the published facts go. What this page cannot yet claim it does not claim: the time saved by not re-typing is the most persuasive number here and nobody has measured it, and migration effort is indicative until delivery signs it off.
Platform scope
2,200+ dealers, 8 markets and 42 brand certifications; the last figure is still being reconciled with the Workshop integration count.
Nineteen modules, one record
The count is verifiable in the product navigation and matches nineteen modules attached to DMS Core.
Time saved by avoiding re-entry
It is the central benefit of one record, but no percentage or number of hours is published without a measured baseline.
Migration duration and effort
A concrete timeline follows only after scope confirmation and delivery sign-off.
Questions buyers ask
Pick one car and follow it
Tell us how many systems it passes through today and how many times its details get typed. That number is the business case, and it is yours rather than ours.
Book a platform walkthroughThe car
One recent unit, from the day you first saw it to the day it was invoiced.
The systems
Every place its details live today, including the spreadsheets.
The re-typing
How many times the same VIN, price or customer gets entered by hand.