Single site
- Scope
- Praha-Chodov
- Permissions
- Role-based, one site
- Ledger
- One entity, CZK
- Reporting
- Site P&L, live
Platform
Not a bundle of tools. One record everything else is built on.
A dealership platform is only worth the connections inside it. In Omnetic the vehicle, the customer, the work and the money are one object. Every module reads and writes to it, and nothing has to be reconciled afterwards.
The record
Customer
Petr Novák · returning
Octavia 2.0 TDI
- Price
- CZK 589 000 · synced
- Purchase + preparation
- CZK 512 400
- Gross margin if signed
- CZK 76 600
- Market position today
- −1.2% · 34 days
- Finance · 48 months
- CZK 9 840 / mo
BRAIN™ observes this object, recommends the next action, and executes only what a role allows.
- Purchase + preparation
- CZK 512 400
- Gross margin if signed
- CZK 76 600
The record · Vehicle · Customer · Work · Money · Illustrative workflow
- Best fit
- Dealer operations, IT, finance and transformation teams
- Operational job
- Keep vehicle, customer, work and money on one governed record.
- What you get
- Connected operational views with shared data, permissions and audit history.
The record
Vehicle, customer, work and money: one object
Four module families read and write the same record. BRAIN™ observes it, recommends the next action, and executes only what a role allows.
Group · 6 sites
- Scope
- 6 sites · CZ SK AT
- Permissions
- Site, brand and group roles
- Ledger
- 3 entities · CZK, EUR
- Transfers
- Internal, no re-invoicing
The same object at two scopes: what one site sees of it and what a six-site group sees. Sample values, not a customer's configuration.
Architecture principles
Six decisions that make it a platform
Suites are assembled from products that were once separate companies. A platform is assembled from one data model outward. The difference shows up on the day two departments disagree about a number.
One object, many views
Sales, workshop and accounting open different screens onto the same vehicle. There is no copy to fall out of date.
Events, not nightly files
A signature, a work order or a price change emits an event other modules and external systems react to immediately.
Permissions travel with the data
Scope is a property of the role, not of the screen. A site manager sees the same object with less of it.
AI is a participant, not a layer
BRAIN™ reads the record under the same permissions as a person and writes only what a person approves.
Configuration over customisation
Markets, brands and entities differ by configuration. Nobody maintains a private fork of the system for one country.
Open at the boundary
What belongs outside stays outside and connects. The platform does not demand that you replace everything at once.
Module activation
Turn on what you need. The record does not change.
Adding Workshop later does not migrate anything. It starts writing to vehicles that already exist. Removing a module removes a view, not history.
Market availabilityAll marketsSelected marketsPartner-dependent
- DMS CoreWrites: The vehicle, the customer and the ledgerTypical start: Always firstMarkets: All markets
- Price ReportWrites: Market positionTypical start: Week 1-2Markets: Selected markets
- CarAuditWrites: Condition and photosTypical start: Week 1-2Markets: All markets
- Workshop · PlannerWrites: Work orders and hoursTypical start: Month 2Markets: All markets
- AccountingWrites: PostingsTypical start: Month 2-3Markets: Selected markets
- Vehicle InsuranceWrites: Policies and attachmentsTypical start: Partner link readyMarkets: Partner-dependent
- Carvago BUY™ · FastbackWrites: Supply and remarketingTypical start: Partner link readyMarkets: Partner-dependent
Typical start periods in a staged rollout, not a commitment. Availability depends on local data sources, registration rules and finance partners; every module page states its markets.
System relationship
The platform around record
Integration model
Open where it matters, closed where it counts
OEM systems, banks, classifieds, accounting exports and your own tools connect through documented APIs, webhooks and certified partner links. Data governance is not a page in a contract. It is a permission on the object.
What connects, and how
REST + webhooks
Self-serveYour systems, your data warehouse and your website connect directly.
OEM links
Per brandOrders, registrations, warranty and campaign data.
Classifieds
Per marketPublishing, price sync and enquiry capture back to the record.
Finance & insurance
PartnerQuotes and contracts inside the deal, not in a second portal.
Accounting export
Per marketWhere a local ledger stays outside, postings leave in its format.
Inside the boundary
One governed record
Data governance
Your data stays yours. Access is scoped by role and site, every read and write is logged, and an export of your own records is a request, not a negotiation.
Multi-market governance
Entities, currencies, VAT treatment, document templates and languages are configured per market. Group roles cross those boundaries; site roles do not.
Security & availability
EU-hosted infrastructure, an audit trail on every record change, documented recovery objectives, and local implementation and support teams.
Every connection crosses the same boundary and lands on the same record, under the permissions written inside it. An illustration of the integration model, not a product screen.
Implementation path
Live on the first module before the second is configured
Nobody switches a dealership over a weekend. The path below is how groups actually move: one site, one module, then the rest with the pattern already proven.
Four phases: two weeks to agree the record, six weeks of pilot on one site, three months of site-by-site roll-out, then ongoing operation.
Weeks 1-2
Agree the record
Which entities, sites, brands and roles exist, and what a vehicle means in your business. Everything later inherits this.
- Who is involved
- One decision-maker, one operations lead, one finance lead. Not a steering committee.
- You end with
- A configuration document, a migration list, and a dated plan for the pilot site.
Weeks 3-8
One site, real cars
Stock, pricing and inspection go live first because they pay for themselves fastest and touch the fewest people.
- Who is involved
- The pilot site's used-car team, trained in a morning and supported daily for the first fortnight.
- You end with
- Live pricing and inspections on real stock, and a measured before-and-after you can show the group.
Months 3-6
Site by site, module by module
Sales, workshop and accounting follow in the order your business can absorb. The configuration is already proven.
- Who is involved
- A named lead per site plus your own super-users from the pilot, who now train the next site.
- You end with
- Every site on the same data model, with legacy systems switched off rather than left running in parallel.
Ongoing
Change is configuration
A new brand, a new country or a new module is a configuration task, not a project with a business case attached.
- Who is involved
- Your administrators, with local support in your language and an Academy path for new staff.
- You end with
- Quarterly platform releases you adopt, not upgrade projects you survive.
Continue
Go deeper into the platform
Four pages carry the detail this overview only frames.
- 2,200+
- dealers run their business on Omnetic
- 8
- European markets
- 42
- brand certifications supported
Omnetic DMS Core
The vehicle, customer and ledger objects every module writes to.
Open DMS CoreOmnetic BRAIN™
What the AI observes, what it may execute, and who approves it.
Open BRAINOpen Platform & Integrations
APIs, webhooks, OEM links and the certified partner catalogue.
Open integrationsSecurity & Trust
Residency, roles, audit, recovery objectives and procurement answers.
Review securitySee the topology on your own structure
Bring your entities, sites and brands. We will model them in the demo rather than describe them in a slide.
Book a platform walkthroughThe records
Where vehicle and customer identity live today.
The hand-offs
Which changes arrive late, copied or incomplete.
The scope
Who needs access across sites, brands and entities.