Native Auto360 modules
Dealer, vehicle, service, Truck360 and control workflows.
AUTOMOTIVE ENTERPRISE ECOSYSTEM
Connected by Numerish.
One connected operating model for automotive distributors, multi-brand dealers, workshops and fleets—with governed handoffs to manufacturing and OEM systems.
Auto360 governs automotive operations. Manufacturing360 independently owns factory and supplier workflows. Proprietary vehicle systems and OEM data remain under their manufacturers’ authority.
Subscriptions and specialist automotive packages depend on approved commercial terms; OEM integrations require separate authorisation.
Connected automotive operating model Concept illustration · not live integration status
Cross-industry product architecture Governed source ownership
Dealer, vehicle, service, Truck360 and control workflows.
Defined role contracts across the relevant portals.
Proposed plan-dependent workflow ceiling.
Vehicle, service, decision and evidence lineage.
*The metrics describe product scope and proposed workflow limits, not independently certified deployment, active subscriptions or authorised external integrations.
Build a connected operating model for manufacturers, OEMs, suppliers, importers, distributors, dealer groups, workshops and fleet operators—without confusing separate products or authorisation boundaries.
Factory planning, production, APQP, PPAP, PFMEA, control plans, genealogy and quality remain with the manufacturing solution.
Explore Manufacturing360Bring vehicle, parts, warranty and distribution handoffs into governed workflows where OEM, supplier and transport connectors are authorised.
Explore integrationsManage stock, VIN and vehicle appraisal, customer journeys, dealer networks, reservations, F&I and sales approvals.
Explore dealer journeysCoordinate service bookings, version-controlled estimates, technicians, repairs, QC, parts and governed vehicle release.
Explore aftersalesConnect cars, commercial vehicles, trucks and trailers with condition inspection, defects, reinspection and human oversight.
Explore inspection modulesOne connected platform does not mean one all-inclusive licence. Manufacturing360, advanced inspections, specialist payment/finance services and external OEM connections have distinct subscription and independent commissioning requirements. The value chain shown above is an integration architecture, not a claim that every connector is active.
From individual workshops to manufacturer networks, choose the business workflows and capacity you need. Source systems, country rules, product licences and independent approvals remain separate.
Licensed internal users, dealer rooftops, stock units, storage, AI credits, workflow tasks.
Qualified technicians, bays, active repair orders, parts operations and workflow activations.
Brands, legal entities, countries, dealer rooftops, VIN allocations and approved provider connections.
Active fleet units, site/branch coverage, telemetry subscriptions, inspections and service volume.
Independently commissioned OEM connections, partner API calls, records, integration event volumes.
Factories, engineering programmes, users, production lines, authorised MES/PLM sources and quality throughput.
Plants, authorised source connectors, OT read-only events, data retention, model evaluations and AI usage.
Contracted connected vehicles, OEM data and energy sources, charging sites, data volume and AI processing.
Commercial scope: The five dealer editions are proposed separately. The seven specialist industry packages require an approved enterprise quotation; displayed capabilities do not represent active OEM provider connections.
Explore package optionsUnify automotive handoffs through approved contracts, versioned source data and accountable people. The OEM Integration Studio maps the paths; manufacturer connections require independent agreement, access and commissioning.
Licensed CAD/CAE, PLM, driveline modelling, eBOM/mBOM and engineering-change effectivity.
Production planning, line and shift visibility, process holds and serial genealogy through manufacturer-authorised source systems.
Governed production-event context, equipment monitoring and independently qualified AI for advisory use.
APQP, PPAP, PFMEA, control plans, customer dispositions, EDI JIT/JIS and corrective actions.
Factory-to-importer shipment, WMS/LES, customs, vehicle allocation and dealer stock intake without duplicate ledgers.
Owner-authorised vehicle data, OEM-issued software campaign status, EV battery and charging information.
Multi-brand dealer operations with governed finance, warranty, repair and owner service records.
Plan partner integration safely without claiming access to proprietary factory or vehicle systems. Every partner must authorise data rights, provide verifiable source credentials and pass independent readiness controls.
Each journey is designed around eight governed stages. The responsible OEM, manufacturing, dealer, finance or service system must execute and independently approve its own tasks.
The integration architecture does not establish an approved connection to any named vehicle manufacturer. Vehicle software/OTA installation, ECU commands, factory PLC/SCADA control, statutory releases, financial journals and OEM approvals remain under their authorised owners.
Start with the outcome your team needs. Each journey connects source records, assigned roles, approvals and evidence while preserving the authority of payment, accounting and external providers.
Bring vehicle acquisition, appraisal, pricing, contract and delivery into one governed sequence instead of separate spreadsheets and handoffs.
Outcome: a traceable deal and vehicle-release decisionKeep estimates, technician tasks, parts, repair changes, QC and customer communications linked to the same vehicle and repair order.
Outcome: accountable repair execution and approved releaseSupport trucks, tractor units, trailers, buses and specialised assets with defect-controlled inspection journeys. AI findings support review; they do not certify roadworthiness.
Outcome: reviewed inspection evidence and traceable handoffTrack commercial evidence, payment/provider receipts, statutory bookkeeping, consent and period close without pretending Auto360 is the finance ledger.
Outcome: defensible, separately approved business recordsWorkflow boundary: The diagrams illustrate intended, governed actions. Real payment, OEM, statutory, notification and vehicle-safety decisions remain with their authorised systems or human reviewers; availability varies by licence and commissioning.
Explore the 28 native Auto360 modules or switch to the 12 automotive manufacturing workflow families in separately licensed Manufacturing360. Use the filters to see which product owns each activity.
Search by module, task, vehicle process or manufacturing workflow.
Dealer setup, branches, identity and activation controls.
Dealer & stockCustomer records, KYC context and consent handling.
Dealer & stockVIN, stock, appraisal, pricing, reservation and disposal.
Dealer & stockTrade-in valuation, evidence and acquisition decisions.
Dealer & stockCommercial review, discounts, approvals and negotiations.
Sales & F&IVersioned vehicle quotes and controlled commercial changes.
Sales & F&IOrder, contract and fulfilment lifecycle.
Sales & F&IFinance submissions, lender conditions and compliance.
Sales & F&IOwnership, document and registration handoff.
Sales & F&IBooking, vehicle check-in, intake and estimates.
AftersalesRepair assignment, execution, QC and vehicle release.
AftersalesTechnicians, bays, workshop tasks and job control.
AftersalesReceiving, issue, backorder and return traceability.
AftersalesClaims, exception reviews and OEM evidence handoffs.
AftersalesPayment requests, refunds and verified provider receipts.
Control & financeSource-to-journal handoff and reconciliation evidence.
Control & financeConsent, privacy rights, legal hold and audit trail.
Control & financeControlled manufacturer connectivity and external evidence.
Control & financeProvider identity, readiness and independent certification.
Control & financeTrial balance, exception control and reviewer closeout.
Control & financeTruck, bus, trailer, chassis and equipment context.
Truck360Pre-trip, post-trip, annual and lifecycle inspections.
Truck360Trailer-specific safety inspection records.
Truck360Axle configuration, brakes, tyres and measurements.
Truck360Equipment identification, tests and safety checks.
Truck360Severity, correction and reinspection workflow.
Truck360Governed evidence, inspector/checker and rule-pack lineage.
Truck360Advisory AI assessment with mandatory human decision.
Truck360Distinct Manufacturing360 workflows connect product engineering, plant quality, suppliers and OEM handoffs. These are not additional Auto360 native modules.
OEM program charter, customer-specific requirements and timing reviews.
Manufacturing360 · separately licensedLaunch readiness, design and feasibility reviews with risk evidence.
Manufacturing360 · separately licensedBOM revision, engineering change effectivity and affected serial ranges.
Manufacturing360 · separately licensedFailure modes, preventive actions, risk priorities and evidence.
Manufacturing360 · separately licensedInspection characteristics, measurement controls and reaction plans.
Manufacturing360 · separately licensedPPAP submission packs, dimensional results and customer review evidence.
Manufacturing360 · separately licensedSupplier process audits, qualifications, requirements and traceability.
Manufacturing360 · separately licensedWork orders, released BOM, component lots and VIN / serial lineage.
Manufacturing360 · separately licensedOEM call-off, sequence windows, shipping labels and dispatch authorisation.
Manufacturing360 · separately licensedVDA process audit scope, auditor competency, findings and corrective action.
Manufacturing360 · separately licensedNonconformance containment, root cause, 8D actions and effectiveness.
Manufacturing360 · separately licensedForward and backward genealogy, affected serials and recall containment.
Manufacturing360 · separately licensedMFG-AUTOMOTIVE-OPERATIONS, subject to independent PricingHub approval. The manufacturing workflow catalogue does not demonstrate OEM certification, live factory execution, approved customer PPAP or industrial machine actuation. Actual commissioning, access and supplier/OEM receipts must be verified.Try fewer keywords, change product scope or reset.
Auto360 extends the shared Numerish WorkflowStudio360 engine rather than creating another workflow silo. Teams can configure role-aware task sequences while the server guards authoritative state and evidence.
Illustrative two-lane example. Parallel design supports up to four independently governed lanes where entitled. Mandatory approvals cannot be bypassed by conditional logic.
Create controlled steps, assign responsible roles, review the design and publish a version-pinned workflow with separate approval.
Guide optional tasks using allowlisted, server-read source fields—no executable scripts or arbitrary client logic.
Coordinate two to four canonical workflow lanes while preserving maker/checker separation and tenant scope.
Identify overdue handoffs and escalation evidence. External SMS, emails or notifications need separately commissioned providers.
Opt-in encrypted offline reference drafts are a pilot capability. Task submission, approvals and authoritative updates require online validation and recent MFA.
A complex automotive system should not require every team member to understand every menu. Guided Experience starts with the job, shows the available next action and points to the evidence or person needed to move forward.
My Work TodayView actual role-filtered WorkflowStudio360 tasks.
Contextual next actionKnow what is missing and which authorised actor comes next.
Module-aware permissionsUnlicensed or inaccessible modules do not become available through a link.
Evidence-first navigationRevisit related VIN, branch, repair or approval context.
Auto360 is intended to reduce the operational cost of fragmented information and repeated handoffs. Actual outcomes depend on adoption, process maturity and purchased modules—not guaranteed savings.
Keep customer, vehicle, deal, repair, inspection and warranty context connected so the next team does not start from zero.
Better continuity across departmentsUse clear task ownership, guided intake, controlled quotes and workflow checkpoints to identify repetitive work.
More time for customer-facing workEnforce role boundaries, recent MFA, maker/checker review and versioned post-approval records where applicable.
Defensible business decisionsApply a common operating model with tenant, entity, branch and portal boundaries without duplicating a finance ledger.
Improved oversight across sitesBring bookings, estimates, technician work, quality review, parts and warranty events into connected processes.
Fewer disconnected handoffsUse shared Numerish Identity360, WorkflowStudio360, API360 and separately licensed finance or manufacturing functions as needs grow.
One extensible operating frameworkUnderstand what belongs to Auto360, what requires specialist licensing and which Numerish services govern cross-product operations. Integration design is not the same as an active provider connection.
Dealer, customer, VIN, workshop, service, Truck360 and automotive source records.
Advanced vehicle condition assessment and human-reviewed inspection intelligence.
Plant, OEM and supplier production quality belong to the dedicated Manufacturing360 extension.
Governed identities, workflows, licensing, messaging, finance and API handoffs.
Licensing boundary: Auto360 does not automatically grant AutoInspection360, Automotive Manufacturing360 or every ERP360 control service. Subscription, provider onboarding and production acceptance must be verified for each deployment.
Build an editable scenario using your own sales, workshop and inspection volumes. The calculator separates potential time released from cash-equivalent value, applies adoption, realisation and overlap factors, and deducts your full entered costs.
Explore five proposed dealer editions and seven specialist packages for workshops, distributors, fleets, OEM integration, manufacturing and connected EV operations. Pricing and availability require separately approved commercial terms.
Indicative packaging only · PricingHub governs approved offers
Focused dealer and aftersales teams.
Growing dealerships with configurable operations.
Multiple dealership locations under group oversight.
Complex multi-branch automotive operations.
Contracted multi-entity, multi-country scope.
These sectors require independent procurement quotations, not an invented fixed tariff. OEM data, plant systems and supplier costs remain separately governed.
Bays, technicians, repair orders, service and quality control.
Auto360 with contracted scopeDealer networks, markets, VIN allocation and permitted OEM data.
Auto360 with contracted scopeActive fleet capacity, inspections, maintenance and authorised telematics.
Auto360 with contracted scopeApproved source access, OEM integration rights and partner governance.
Auto360 with contracted scopeIndependent Manufacturing360 base plan and automotive extension.
Separate Manufacturing360 licenceFactory data, APS/MES evidence and qualified OT monitoring.
Separate Manufacturing360 licenceOwner-consented vehicle and energy data, battery and charging.
Auto360 with contracted scopeWe can map brands, countries, sites, users, vehicles and third-party dependencies into an accountable enterprise proposal.
Request package consultation*Proposed capabilities—not an active grant. Conditional routing, parallel approvals and geographic capacity depend on approved PricingHub entitlements and independent acceptance. Provider connectors, OEM integrations and industrial data access require separate commissioning.
Specialist extensions are separate. Auto360 and Automotive Manufacturing360 are independently purchasable. No manufacturing price, bundle discount or guaranteed regional availability is authorised by these cards.
Validate modules, users, locations, workflow limits, integrations and country requirements against an approved PricingHub quote.
Operational and software controls are only one layer. Country requirements, manufacturer approvals, external integrations and regulatory certifications are evaluated separately for each authorised deployment.
Single sign-on integration, tenant-aware permissions, explicit role scopes and recent MFA for protected operations.
Valid state transitions, versioned committed records, audit lineage and controlled amendments.
Payment settlement, Accounting360 journals, OEM decisions and notification delivery require their genuine source receipts.
Automotive quality and safety, ISO security/privacy frameworks and IFRS dependencies are mapped for assurance; mapping is not certification.
Software availability depends on your approved plan, market and provider commissioning. Safety-sensitive operations, external signatures and production eligibility require independent verification. Specific connectors, statutory packs, OEM integrations and independent certifications should not be assumed active without commissioning evidence.
Still evaluating the right edition or automotive workflow? We can map your operational requirements to the relevant module, licence and deployment plan.
Talk to the Auto360 teamIt covers the contracted Auto360 modules, operating scope, users and resources identified in your approved PricingHub entitlement. The overall catalogue contains 28 modules, but a plan does not necessarily enable all modules or every external integration.
No. Auto360 maintains automotive operating records and handoff evidence; Accounting360 is responsible for authoritative journals and financial reporting. Payment Gateway Hub or an approved provider confirms payment states.
Workflow Studio supports controlled templates and design/publish flows. Advanced conditional routing, parallel approvals and SLA policy are governed features, subject to plan approval, permissions and production acceptance.
No. APQP, PPAP, PFMEA, manufacturing quality and plant operations belong to the separately licensed Manufacturing360 automotive extension. Auto360 remains focused on dealership, service and fleet source operations.
The proposed commercial scope includes dedicated workshop, distributor, fleet, OEM integration, manufacturing, industrial intelligence and connected-EV packages. Specialist packages require an independently approved enterprise quote.
No. Connections require actual manufacturer agreements, licensed data access, approved APIs and independent commissioning. A described integration capability is not a certified partner relationship.
No. Vehicle software, OTA installation, ECU functions and factory PLC/SCADA control stay with authorised OEMs and operators. Approved read-only source integration is independently governed.
Guided Experience360 prioritises jobs, points to required evidence and routes a user into permitted modules. It cannot bypass MFA, an independent checker, subscription limits or real external-provider receipts.
No. The calculator is a planning model driven by editable examples. It is not an independently measured benchmark and does not retrieve certified Auto360 subscription prices. Enter your own approved annual fees and implementation costs.
No. Relevant standards and country-law controls can be mapped to the product, but actual certification, manufacturer approvals, privacy-law compliance, financial reporting and production eligibility depend on independent, deployment-specific evidence.
See how OEM and manufacturing integrations, dealer operations, workshops, inspections and fleets can share an accountable vehicle lifecycle across separately licensed Numerish products.