PH Konzulta s.r.o.

About the client

PH Konzulta s.r.o., based at Zlatovská 27 in Trenčín, is an authorized Honda service and dealership for both passenger cars and motorcycles. The company was founded in 2003, employs 17 people, and is led by Ing. Pavel Horal (CEO). The commercial side covers car and motorcycle sales including accessories (clothing, car accessories, oils); the service side runs Honda servicing in two halls — one for cars and a separate one for motorcycles (the most heavily loaded segment in summer).

The challenge

PH Konzulta used DMS Honda from the manufacturer as its main system. While functional, it no longer met the company’s current needs — a legacy environment, tree-structured modules, insufficient filtering, no parameterization, and no openness to integration with modern systems. Specific issues:

• DMS Honda does not allow attaching photos or videos to service operations — a fundamental limitation for quality control
• Print-based service requests are sent to the workstation on paper — there is no modern digital flow
• The warehouse is organized in a central rack with an inter-operation warehouse in the workshop, but without barcodes/QR codes — searching takes time
• Complaints and invoice records sit in DMS Honda but without integration to modern tools and banks
• Training materials and manuals are not available — onboarding new staff is difficult
• Accounting and payroll run in the external MRP system, which the company wants to keep

The solution

Modulario proposed a deployment as a cloud/web application accessible via browser and mobile app, with implementation in 6 phases (4–6 months). The solution replaces DMS Honda and integrates with the retained systems:

Modulario modules

• Sales and CRM — customer and contact records, price quotation creation, order management, discounts and campaigns, communication history, SMS notifications to customers, calendar, sales KPI dashboard
• Service (MESS) — service planning (rack, location, levels), service job management, real-time progress monitoring (scanner, photos, videos), recording and write-off of service operations, terminals for reporting operations, job status checks via A4 Checklist, SMS notifications
• Procurement — supplier records, issuing orders to suppliers, delivery tracking, supplier rating, approval workflow
• Warehouse — stock records and parts movements, material receipt/issue, batch and expiration tracking, use of barcodes/QR codes with rack labels
• Invoicing — invoice issuance and number series, receivables records, payment tracking, bank integration for automatic payment matching, reminder system, export to MRP accounting
• BI and reporting — control panels, KPI indicators, analytical tools, job times, norms, costs, employees; SmartBoard as an information dashboard (sales/service/customer)
• AI features — OCR for documents (invoices, delivery notes) with automatic data recognition and prefill into the system; predictive analytical models for inventory planning and optimization, trend analysis, and demand prediction

Integrations and architecture

• MRP — the accounting and payroll system kept by the company; Modulario exports issued invoices and sales/stock movement data for accounting evaluation
• Banking systems — online banking for statement import and payment matching
• Cloud architecture with access via web browser or mobile app, encryption of sensitive data, detailed access rights for different roles
• Prepared for future deployment of a customer-support chatbot, AR service instructions, and IoT sensors on machines

Implementation in 6 phases

1. Detailed analysis and design (months 1–2) — workshops with key users, detailed process modeling, functional specification, and prototyping of key screens
2. Implementation of base modules (months 1–2) — master data (customers, products, materials), Sales/CRM, Procurement, Warehouse
3. Implementation of service and supporting modules (months 1–2) — Service (MESS), TPS, Quality and dispatch, AI features
4. Integrations and data migration — in parallel with F2/F3, links to MRP, the bank, one-time migration of historical data
5. Testing and training (month 1) — UAT, integration tests, role-based training
6. Go-live and fine-tuning (month 1) — cut-over, increased AMCEF support in the first weeks, stabilization