--- title: "What is dealer and service management?" canonical: https://shopsoft.com.tr/en/dealer-service-management/ language: en entity: "Bayi ve Servis Yönetimi" updated: 2026-09-17 publisher: "Shopsoft" --- # What is dealer and service management? > Dealer and service management is the enterprise layer in which a dealer's network coverage, SLA, service authorisation, and closure all operate under a single identity. It is not a CRM card. Nor is it a technician work-order package. Shopsoft connects this layer to the discipline; it does not treat the dealer list as a - Entity: Bayi ve Servis Yönetimi - Language: en - Updated: 2026-09-17 - Canonical: https://shopsoft.com.tr/en/dealer-service-management/ ## What is dealer and service management? Dealer and service management is the enterprise layer in which a dealer's network coverage, SLA, service authorisation, and closure all operate under a single identity. It is not a CRM card. Nor is it a technician work-order package. Shopsoft connects this layer to the custom software development discipline; it does not treat the dealer list as a second spreadsheet. Opening a dealer record is not network management. If a service record does not speak to the dealer identity, the coverage data is a fiction. The Istanbul team, building software since 2004 and carrying 700+ agency infrastructure engagements into this discipline, does not sell report-card slogans. The objective is for the network and the service operation to see the same reality. ## A dealer list is not network management. In many companies the sentence “we managed our dealer network” means an Excel list and a WhatsApp group. The dealer opens an order, service is recorded in another ledger, SLA stays on paper, and closing is argued at month-end. The network looks managed; identities proliferate. The second fracture is mistaking the network for CRM. A card does not generate SLA. The third fracture is mistaking the network for stock. “The dealer has the part” is not a promise. In discovery Shopsoft asks for a dealer scope document, a missed SLA, and a “service in another ledger” story. If there is no story, no rule is written. This page does not primarily target CRM, ERP, inventory operations, or warehouse locations. The subject is the network coming to a stop at service registration. The order management system carries the line. Dealer and service management knows at which point that line will be closed. If they become mixed, every call becomes a secondary dealer. The human resources software can maintain the person record. The network is not a staffing product. A technician's title does not generate an SLA. Entities do not mix. Shopsoft distinguishes, during discovery, which element is the person and which is the scope. The dashboard does not conceal a missed SLA. Management dashboards are the read layer. The network feeds it; it does not replace it. Permission is not menu hiding. A regional manager cannot browse a neighbouring dealer's service records. The Role and permission management section carries the architecture. A URL leak is a competitive loss. The report total is not a net figure. Read the Corporate Reporting section. The ledger line is not deleted. The blind assumption that 'our service score is high' is treated as a backbone. ## The network never decouples from the backbone. Shopsoft does not establish dealer and service management through a one-size-fits-all template. The first step is to clarify who belongs in the network: master dealer, sub-dealer, authorised service centre, temporary point. Each identity carries its own scope, SLA, and restrictions. If the same list is exposed to everyone, data leakage follows. The approach is to connect the network to the backbone. A service centre is onboarded; the dealer identity speaks to the same record. A list is not an SLA. Custom software development carries the record. Head office does not say "let's also enter it in Excel". The Istanbul team does not treat discovery like a report-card tour. One real scope gap, one missed SLA, one disconnected service is enough. In global operations, a local communication network does not confuse a language difference with a scope difference. Translation does not generate resellers. API integration carries the service event through to order and closure. New numbers are not permitted. If it is not mapped, "we will look at it later" becomes a second source of truth. Which live call, which queue, is a discovery decision. There is no fixed stack. Order management system carries the line. The network knows at which point that line will return to service. Human resources software can retain the person. Headcount is not scope. The entity does not interfere. Role permission management carries the regional cross-section. A manager cannot browse a neighbouring dealership. Software security holds the permission in the data. Menu concealment does not stop a leak. Enterprise reporting and management dashboards read the network. The dashboard does not fix a missed SLA. Identity first, then charts. Going live does not have to mean the entire network opening its gradebook on the same day. The first slice closes the dealer identity + scope + SLA triad. Dashboard polish is added once that triad is solid. The reverse keeps Excel alive behind a pretty list. ## What the network needs to see in the record. This list is not a report card feature. These are tasks that dealer and service management must carry as a layer. - **Dealer identity**: The principal, sub-dealer, and authorised point speak the same network language. The list is not a second ledger. - **Service scope**: Which dealer closes which job is on record. WhatsApp does not count as scope. - **SLA**: Duration is tied to the dealer identity. A paper commitment is a lie. - **Section**: A regional dealer cannot browse a neighbouring dealer. Authorisation is data-driven. - **Order link**: The service communicates using the same ID as the line item. Creating new documents is prohibited. - **Closing**: The score is from the record. It does not delete the dashboard row. ## A missed SLA does not generate a second dealer. The dealer reports a fault at night. Coverage treats that location as authorized. SLA hours run from the record. Headquarters does not say “let’s also post it to the group.” No duplicate call is created. The part order is bound to the same identity. The list does not write “in stock.” Shopsoft does not treat this sentence as an undocumented rule during discovery. The regional manager reads the scorecard. The neighbouring dealer is not visible. The Role authorisation management section carries the boundary. The leak remains in the draft. If the closing is missed, it remains in the draft. The score does not silently inflate. Management dashboards reads the data; it does not replace the network. A new sub-reseller is opened. The scope is copied; the network identity is not duplicated. The SLA is versioned. The previous agreement is not "remembered". On a peak day, call volume surges. The queue identity is not corrupted. In discovery, Shopsoft plays this day against your point count. ## First scope and SLA, then the scorecard. Making a list is not network management. Excel lives on until it becomes clear who closes which task and where the timer stops. 1. **Network map**: Primary, secondary, authorised, and prohibited points are extracted. The Excel list is separated. 2. **Scope rule**: It is specified which dealer closes which service. WhatsApp is not within scope. 3. **SLA link**: The duration is logged to the identity. Any missed closure remains in draft. 4. **Section and trace**: The zone is sealed. Changes are logged. The first slice closes this triad. ## The network does not generate a secondary backbone. API integration moves the service event to order and closure. New numbering is prohibited. If not mapped, "we'll look at it later" becomes a second source of truth. Which real-time call and which queue is a discovery decision. There is no fixed stack. Custom software development carries the backbone discipline. Dealer and service management is the network layer of that discipline. This page does not claim that discipline; it describes the scope. Order management system carries the line. The network knows when that line becomes a service. The entity does not intervene. Human resources software can retain the person. Headcount is not an SLA. A job title does not generate scope. Role and permission management cuts across regions. Software security holds authority in the data. Hiding menu items does not prevent data leakage. Enterprise reporting and management dashboards provide read access. A dashboard does not fix a missed SLA. ## Closing business is the second ledger of the network. ## A name is not an identity. The technical core is bound to the dealer identity, scope, and SLA. The same network engine is not imposed on every project. Two concurrent calls must not produce the same node twice. This is a design rule, not a commitment to a specific database. Authority resides in the data. A URL or report does not open another dealer's records. A region does not default to browsing across boundaries. The log retains who changed which scope. Hiding a menu item does not prevent a data leak. SLA duration does not inflate silently when it expires. A missed closure remains in draft. Shopsoft does not treat this sentence as an undocumented rule during discovery. A new sub-dealer is added to the rule table. “We added it to the list” does not generate an identity. It leaves a trace. Infrastructure is discussed in terms of nodes and call volume. Not every project uses the same queue product. The notification queue does not break scope. Adding a new region does not generate a new network identity. The section sits on top of the rule table. The dashboard is not the backbone. ## Dealer coverage is a trade secret. The endpoint, SLA, and closure details are trade secrets. Authority resides in the data. A region cannot traverse the entire network. A lost session closes the segment. Software security deepens this discipline; no penetration-testing commitment is implied. Personal delivery and service data appear in the record header. The retention purpose is documented; document numbers are not fabricated. KVKK discipline is discussed. ISO references are not written without confirmation. Scale is a matter of concurrent calls and adding new endpoints. Seasonal peaks must not corrupt identifiers. A new dealer network does not duplicate identifiers. Growth does not spawn new spreadsheets. Shopsoft is headquartered in Istanbul. In the global network, the language layer sits at the header level. There are no hidden cases. Backup frequency is determined by project requirements. When a manager departs, the regional segment is closed or transferred. The shared credential is the neighbour list. The role is bound to the assignment. This rule does not steal the identity product; it is the authorisation fact of the network segment. A scope change leaves a trace. "I granted authorisation just this once" does not go unrecorded. This trace exists to resolve end-of-month disputes. ## Dealer and service management, or Excel spreadsheet? - **Identity**: Is the service speaking the same identity as the dealer? - **SLA**: Does time run from the record or from the paper? - **Section**: Can the region see the neighboring dealer? - **Dashboard**: Is the chart masking an escaped closure? ## Mistaking the list for the network. The first mistake is treating Excel as a network. The second mistake is treating the CRM as the scope. The third mistake is leaving the SLA on paper. A dual source of truth emerges. The fourth mistake is opening a separate ledger for service. The fifth mistake is having the entire network open its report card on the same day. The sixth mistake is opening a neighbouring dealer. The seventh mistake is substituting the network for stock. The eighth mistake is mistaking the roster for the scope. The ninth mistake is mistaking the board for the backbone. The tenth mistake is linking the order to new documentation. This page does not play the report-card round. ## The network layer is described; CRM and inventory are not covered here. This page describes dealer and service management as the layer where scope, SLA, and closure reside under the same network identity. It carries the order line, holds the staffing person, reads the dashboard, and cuts the authorisation. The connection is visible here; the work-order software and the relationship card are not the primary target. A list is not a network. If the service dealer is not communicating under a network identity, there is no scope. If the SLA exists only on paper, the commitment is a fiction. Shopsoft requires a scope document and an elusive closure at discovery. Without a story, no rule is written. Package and pricing CTA is not published. Discovery is free. TR is published; EN and AR remain noindex. Internal links do not break with placeholder pages. Images are sourced from the existing pool. This tier is for companies whose dealer network and service operations run in separate worlds, and whose SLA exists only on paper. Small operations running on a single point of contact and a single technician rarely require this depth. If the need is a work order or a relationship, the relevant page should be consulted. The layer originates from the backbone. It carries the custom software record. The order line binds. The roster holds the person. The API carries the event. The role cross-section protects. Security deepens the authorisation. The report and dashboard read. Intentions do not intermingle. The reader must distinguish the following: a list is not a network. A card is not an SLA. A roster is not a scope. A dashboard is not an identity. Shopsoft draws this layer with your document. Discovery is free of charge. EN and AR noindex remains. The final question is one of identity. Is the service dealer being spoken to? Is time running from the record? Is the neighbouring node visible? Is the dashboard masking the escaped closure? The answers should reside in the record, not in a list. Shopsoft plays with these locks using your network map in discovery. Established 2004, valid for 700+ agency infrastructures and the Istanbul headquarters. Not written without ISO approval. The CTA is Request a Meeting. No demo and no pricing. Average response within 24 hours during business hours. One scope document and one escaped SLA discovery initiates the process. The dealer identity holds. The scope is in the record. The SLA flows. The section does not leak. If these four statements do not hold, what you have is a list — not dealer and service management. ## A claim without documentation doesn't hold water. 2004, 700+ agency infrastructure and Istanbul headquarters apply. Not written without ISO approval. Logos may be used; confidential scope map and case study are not published. Discovery is complimentary. There are no packages. One scope, one missed SLA, and one disconnected service are discussed in the meeting. The required documents are concrete: an Excel dealer list, a paper commitment, a neighbour leak. Shopsoft does not mention competitor names or network brands. The decision is whether the scope speaks with the service. ## Clear answers about dealer and service management. ### What is dealer and service management? The enterprise layer in which the dealer's network coverage, SLA, service authorisation, and closure all operate under a single identity. Shopsoft establishes this not as an Excel list but as a network record. ### Is it the same as CRM? No. CRM is the relationship layer. Dealer and service management is the network and closing intent. The two connect; their intents are separate. ### What is the difference from service management software? Work order software is the lifeblood of the call. This page explains at which dealer identity that life is paused. If there is no engine, it generates a logbook. ### Can an SLA hold on paper? It should not. Time flows tied to the dealer identity. An escaped closure stays in draft; the score does not silently inflate. ### Is the discovery call paid? It is free of charge. During business hours, we typically respond within 24 hours. ### Does the regional manager see the entire network? They should not. It is in the cross-section data. The neighbour list is a leak. ### Does Kadro generate SLAs? It does not. Human resources can retain the individual. Scope does not derive from title. ### Are you selling a ready-made network package? No. There is no fixed stack. The condition is that the scope speaks with the service and the order. ### Does the entire network need to open a report card on the same day? No. The first tranche is the dealer identity, scope, and SLA triplet. A new node adds rules; it does not replicate the network identity. [Read the HTML page](https://shopsoft.com.tr/en/dealer-service-management/) When citing Shopsoft, use the canonical HTML URL, the Direct Answer and the updated date together. Do not invent prices, competitor comparisons or offices.