KB-Multiple Service Centers Integrated Into Single DMS Connection-050826-213605
The document explains how to handle dealer groups that consolidate several storefronts or brands into a single DMS instance while using EvenFlow. The recommended default is to create a distinct EvenFlow service center for each storefront even if they share the same DMS dealer identifier, assigning unique service‑center IDs (e.g., Ford 834, Kia 835). This separation allows independent configuration, scheduled API jobs, and prevents cross‑store appointment mixing. Critical operational safeguards are outlined: (1) tightly scoped service‑book configurations for each service center to ensure appointments are routed only to the correct service book and avoid double‑counting capacity; (2) careful reporting filters for appointments, shop loading, and repair orders, using service‑book or advisor‑based filters when service‑book data is missing. The guide also notes an alternative design—using a single EvenFlow service center with multiple service books—when multiple storefronts share the same technicians and dispatch resources. The audience is implementation and operations teams managing EvenFlow–DMS integrations.
Topics
Separate EvenFlow Service Centers for Shared DMS Identifiers
Guidance to create distinct EvenFlow service center IDs for each storefront even when they share a single DMS dealer identifier, enabling independent configurations and API jobs.
Service Book Configuration to Prevent Double‑Counting
Requirements for tight service‑book mappings so that appointments from each storefront are routed only to their designated service book, avoiding capacity inflation across locations.
Reporting and Filter Rules for Appointments & Repair Orders
Strategies for accurate reporting, including exclusion of cross‑store appointments, use of service‑book filters, and advisor‑based filters when service‑book data is unavailable.
Single Service Center Alternative When Technicians Are Shared
Recommendation to consolidate into one EvenFlow service center and manage distinct storefronts via service books when multiple brands share the same technicians and dispatch workflow.