Frequently asked questions

No. DMS Core plus whichever modules solve today's problem, some dealers start with Price Report and CarAudit, others with Workshop and Planner. Adding one later is configuration, not a project.

This page is the product you buy: the record, its four objects and how modules attach to it. The Platform page is the architecture argument, the integration model and the implementation path around it.

Yes. A local accounting ledger, a group data warehouse or an OEM portal can stay where it is and connect through Open Platform. What you cannot keep and still get the benefit is a second customer or vehicle database.

The AI layer of the platform. It observes the vehicle, customer and stock records, decides what is worth attention, and acts inside your workflow, drafting, scoring, checking and publishing, under the permissions and approval rules you set.

If your data is already in Omnetic, BRAIN™ works the moment it is enabled. External systems connect through Open Platform, portals, telephony, OEM feeds and your own tools, and BRAIN™ then reads those events like any other.

It stays inside the platform's residency, permission and audit rules. Contribution to shared model improvement is a contractual choice and defaults to no.

Lead capture and drafting help from day one because they need no configuration. Pricing and stock recommendations need a few weeks of your own history to be worth trusting.

No. Advisors see suggestions inside the screens they already use. An administrator sets the autonomy level per action; there is nothing to prompt-engineer.

Per action, per role and per site. You can disable a capability entirely, require approval, or allow automatic action within limits, and change it later without touching anything else.

If DMS Core is live, CRM is configuration rather than implementation, activity types, states, segments and notifications for your business.

Customers, vehicles and open opportunities migrate with the DMS. Closed history is kept as a searchable read-only archive rather than half-imported.

Available in eight product markets. Connections and local configuration vary by country.

Yes, fields, activity states, segments and notifications are configured for you during implementation. Configuration, not a private fork of the product.

Where a brand link exists it is configured per brand and market, and order status flows onto the vehicle record. Where it does not, ordering stays in the brand portal and Omnetic tracks the resulting vehicle.

That is the intended setup. New and used share the customer, the workshop and the ledger; a trade-in taken against a new car becomes used stock without leaving the platform.

Available in eight product markets. Connections and local configuration vary by country.

We will review your portals, website, finance and insurance partners with you. Available connections and services depend on your market and setup.

Transactions can be exported to an external accounting system or handled in Omnetic Accounting. The supported package and export format are confirmed for your setup.

Plan the transfer of vehicles, photos, customers and open deals before go-live. Agree how your closed history will remain available as a searchable archive.

No. You configure which levers are theirs, typically finance term and optional products, and price is not among them unless you make it so. The advisor sees every change as it happens.

It depends on the country and the document. Signature methods are configured per market, and some documents may still require a wet signature at handover. Per-market detail is pending legal review.

No. Your site advertises the stock; Digital Deal is what happens after a specific customer and a specific car are matched. The two connect through the same stock feed.

Then they come in and the advisor opens the same deal, with everything they adjusted already there. That is the point of the module, the choice of channel is theirs and it costs nothing to change.

Availability, general, pilot or announced, is confirmed with your team, per market, before any commitment. This page describes the module; it does not state a launch status.

It depends on the model and the market. Referring a contact generally does not; acting as an insurance dealer does, and the requirements differ per country. Per-market regulatory detail is pending legal review.

The insurers connected in your market. The list per country is pending publication, until then this page shows insurers as A, B and C rather than implying full coverage.

The policy sits on the vehicle and the customer with its renewal date, so it appears in your CRM as a dated opportunity rather than being forgotten a year later.

Availability can be published to your own website through Open Platform, so an online request checks against the same calendar the desk uses rather than a copy. Whether a self-service booking journey ships as standard needs product confirmation.

With CarAudit on a phone at handover and again at return. The two inspections are compared, so new damage is evidenced with photographs rather than argued about at the desk.

Yes, vehicles, reservations and permissions are scoped per site like everywhere else in the platform, so a desk sees its own fleet while a fleet manager sees all of them.

From the classified and auction platforms connected to Sourcing, in one search. The named platform and country list is confirmed per market during scoping rather than published on this page.

Yes. The tool finds and analyses; your buyer decides and transacts. Sourcing as a service is the alternative for a team with no time for the administration, you choose the cars, we handle the rest.

Yes, through Open Platform. Purchases and their costs can flow into a third-party system of record, though the margin analysis is sharper when your own cost history lives in Omnetic.

Listings and sale signals are cleaned, normalised for trim, extras and mileage, then modelled against time to sell. The comparable set remains attached.

It combines asking and achieved-price signals, cleansing before modelling and VIN-level equipment resolution inside the DMS workflow.

Listing lifecycle patterns distinguish a likely sale from withdrawal, repeated reduction or relisting.

The vehicle's history, current competitor set and market trend are combined, with the comparables and modelled effect shown beside the suggestion.

Yes. Configure fastest turn, maximum margin or a hybrid per site, plus automatic limits or approval.

Entered data is compared with VIN-derived fuel type, year and specification, then photos, equipment and category are checked.

Yes. The report template follows the checklist and can have a customer-facing version without internal data.

The source confirms Android and iOS. Minimum versions and tablet support must be confirmed before publication.

Yes, through Open Platform. The tightest workflow is when Omnetic holds the vehicle record.

Coverage varies by country and category. A per-country coverage table is not yet confirmed.

The result says so; absence of records is not presented as verification.

Yes. A verification code helps the recipient confirm that it belongs to the vehicle.

A transaction provider sits between buyer and seller. Provider identity and exact flow must be confirmed per market.

No. The decision is vehicle by vehicle; Fastback can be used for stock that does not fit the retail route.

The available inspection, photographs and findings attached to the vehicle record.

Yes. Parts are reserved and consumed against the order, so cost lands on the job and vehicle. Warehouse shows stock across sites before another part is ordered.

Planner shows bay and technician capacity together, including sales-preparation work competing for the same hours. A conflict appears before the booking is promised.

Against the order item through Time-keeping. That makes labour recovery traceable and lets the team explain an overrun afterwards.

Yes. Planner proposes and the foreman decides. An override is recorded, and affected downstream work is re-sequenced rather than left inconsistent.

Work is planned per site with group visibility for permitted users. Whether a job can be proposed automatically at another site needs product confirmation.

Competences are configured and maintained per technician, brand certifications, specialisations and any other rule the plan should respect.

Yes. One stock card shows what is where, so a part at another branch is visible before a new one is ordered.

Yes, minimum and maximum per warehouse. ABC analysis can propose levels from movement; whether reordering then happens automatically needs product confirmation.

An open work order reserves what it needs, and the reservation follows order status. If the job changes or is cancelled, the part returns to free stock.

Supplier, workshop issue and counter prices are separate per category, with a configured minimum margin. A breach is blocked until an authorised override, which is recorded.

Yes, terminal, PC, tablet or phone, including remote workplaces. Which channel was used remains part of the record.

Working time, responsibilities and statuses are configured per person and Planner respects that availability. The exact rota scope is confirmed during product scoping.

Attendance per employee, time per order and order item, labour recovery, configured surcharges and overtime, and the journey log; printable, with graphic overviews exportable to Excel and PDF.

No. A group can keep a local statutory ledger and let Omnetic send context-rich postings to a supported integration. Using Omnetic Accounting removes that export step and keeps the drill-down in one system.

Entities and currencies are platform configuration. The exact statutory support and consolidation flow are confirmed for the markets in scope.

Retroactive corrections and recalculation are supported in the source. What a closed period permits depends on local rules and the configured ledger.

Operational module screens reflect their live records. Reporting refreshes its warehouse on a configured schedule; the interval is confirmed and documented for the deployment.

Yes, custom views can be tailored to the required content and visualisation. Whether your team configures them or Omnetic delivers them is agreed in scope.

Yes. A group with its own warehouse can take a governed event stream or scheduled extract through Open Platform and retain the same shared data model.

No. Contract engine, credit, accounting and collections stay where they are; this covers the physical vehicle.

Then inspection baseline and live history are unavailable. Portfolio coverage is disclosed before commitment.

It is dated, photographed and attributed; legal sufficiency remains a market-specific legal question.

Yes for units you own, under scoped, logged permissions, not unrelated dealer or customer data.

It handles the vehicle after recovery; legal notices, collections and recovery process remain outside scope.

No. The same pricing and inspection tools work without a group layer, and the source recommends starting with two modules.

Price Report and CarAudit can start from a stock list and training; full DMS migration takes longer. No unsupported duration is promised.

Yes. Transactions can export with the vehicle attached; supported packages are confirmed per market.

The record and inspection are configurable, but comparable depth varies by vehicle type and must be confirmed honestly.

Current stock, customers and open deals migrate; closed history remains searchable as an archive.

No. R-EVENTS explicitly says nothing is scheduled.

Ageing stock: deciding to cut before the market does. It has no confirmed date or speaker.

Only when a date exists; the source intentionally blocks registration before then.

They remain on this page and join the matching Academy path as on-demand lessons.

Yes when confirmed; organiser and partner logos require consent.

No. Sites keep stock, P&L, decisions and permissions; definitions of vehicle, customer and margin are shared.

Yes as market configuration. Certified accounting coverage must be confirmed per market; otherwise postings export to a local ledger.

Brands, sites and entities are configuration; importer-link availability still varies by brand.

Yes. Open Platform can provide an event stream or extract so the warehouse models one definition set.

Open items and master data migrate, history stays searchable and cut-over is planned against statutory close.

No for reading. Sign-in is only required to save progress and resume where you stopped.

No. The source names confirmed lessons and labels remaining counts as outlines to be written with role experts.

A confirmed webinar becomes a dated lesson with questions, then joins its Academy path as a recording.

No. Academy teaches practice; broken workflows and waiting customers belong in support.

No. The source explicitly says certificates are not shipped and the placeholder remains hidden.

No. The source explicitly recommends an order based on the first problem, with further modules added when justified.

A local ledger, group warehouse or OEM portal can remain where needed; duplicate customer and vehicle records are the problem to remove.

No. The source publishes no universal ROI figure; impact is modelled on your own assumptions and identified as an estimate.

Confirmed per brand and market before the project. Where no link exists, ordering remains in the portal and Omnetic tracks the downstream vehicle.

Approval requirements vary by brand and must be confirmed commercially; no blanket approval is claimed.

Yes as configuration, while each brand keeps its own rules and reporting definitions.

The claim is built from the work order; submission without a human step depends on the brand interface.

Open items and master data move; brand reporting continuity is scoped explicitly around cut-over.

Partially. Covered dealers contribute live data; others show no data. Coverage is stated per market before commitment.

They can see the exact scope, every read is logged and unrelated margin, brands and personal data remain outside it.

That is the Open Platform mechanism, but named interfaces and markets require confirmation.

No. It gives existing standards an auditable source on the vehicle.

Yes through a scoped event stream or scheduled extract via Open Platform.

Yes. A service-only operation can use Workshop, Planner, Warehouse and Time-keeping without sales modules.

Yes, if recovery should be measured; clocking is against the order item from terminal, tablet or phone.

Availability can publish through Open Platform; a standard self-service journey still needs product confirmation.

Tyre storage supports larger sets and intervals are configurable, but heavy-vehicle depth needs validation.

Yes. Where no connector exists, existing ordering stays and Omnetic tracks reservation and cost.

Partly. Stock, workshop and parts work, but damage maps and market data remain car-shaped; bike-only businesses should validate fit carefully.

Commercial workflow works, but axle, tachograph, driver-hours and heavy compliance are outside the confirmed model.

No. Rental, workshop, parts and accounting can operate without a showroom funnel.

Bookings can use Open Platform; named aggregator connectors require confirmation.

Start with the dealer solution and add Rental as one module; this page is for businesses where fleet operation is the business.

One confirmed benchmark. Empty themes remain visibly empty instead of implying a publication programme.

The open summary lets readers judge value first; only raw observations and per-platform detail request contact information.

Not until author, reviewer, weights and data window are published. The source explicitly blocks the score today.

Ageing, landed cost, workshop hours and network visibility are research themes, not promised dates.

The named specialist roles, their coordinated conversation and the custom builder are illustrative concepts. For current Omnetic capabilities, see BRAIN™, Stock Report, Price Report and Lead Management.

BRAIN™ reads the vehicle and customer record under the same permissions as the person using it. A prompt does not widen a role or site boundary.

A person approves consequential actions, with the approver and outcome recorded. Discounts, price changes and contracts are outside the automatic tier described by Omnetic.

BRAIN™ shows reasoning and confidence alongside its recommendation. The coordinated progress view on this page is illustrative, not a capture of shipped progress UI.

The recommendation should state uncertainty and keep supporting data visible. The illustrations show the review boundary; they do not provide measured performance or a release commitment.

We prepare the demo around your business type, role and market. When arranging it with our team, tell us which workflow or problem you want to explore so we can agree on what to cover.

Yes. When arranging the demo, tell us which systems you use and what you need to connect. The options depend on the product, interface and your setup. Our team will review them with you.