OEM, Distributor, Dealer, Supervisor — one platform, four tiers.

Nested Dealers is GetAFix for multi-tier distribution networks where an OEM (or a brand) operates through Distributors, who in turn operate through their own Dealers, each with Supervisors and Team Leads on the floor. The OEM solution focuses on the OEM ↔ Dealer relationship; Nested Dealers adds the Distributor tier in between, with full data isolation per distributor, scoped employee management, and territory-level rollups. If your model has at least three tiers between the brand and the customer, Nested Dealers is the right fit.

Three patterns we see most often. (1) Auto-aftermarket OEMs running detailing, lubricants, cleaning, accessories or coating brands through distributor + dealer networks. (2) Manufacturers of consumables/services that ride on a partner network — every dealer is independent, but the brand experience must be consistent. (3) Master-franchisors with regional sub-franchisees who themselves operate multiple stores. The world's largest passenger-vehicle detailing brand runs 100+ franchise stores in India on this exact pattern.

Each distributor has their own data scope; their dealers and employees are theirs. The OEM sees a rolled-up view across distributors but cannot drill into a competing distributor's margin or commercial terms. Each role — Country Head, Zonal Manager, Regional Manager, Area Manager, Distributor Owner, Dealer Principal, Supervisor — has a login with explicit, audit-logged scope. We can also operate in "shared SKU master, isolated commercials" mode if you need it.

Yes. KPIs are configurable at OEM, distributor and dealer level. You can set targets centrally and let them cascade, or allow distributors to set dealer targets within bounds. Footfall, conversion, avg ticket, CSI, attach rate, service-package mix — all native KPIs. Custom KPIs (e.g., "% of cars that opt for premium package") are configurable without code.

SKUs, packages, prices, service catalogues and SOPs live at the OEM (or distributor, depending on your model). When HQ updates a price or SOP, it propagates to every dealer instantly — with version history, effective dates, and an acknowledgement trail. No more "the Pune dealer is still on last quarter's pricing".

Multi-level approval out of the box. A dealer or distributor raises a PO; it routes through ASM → RSM → HO (or whichever ladder you configure). GRN is matched against the PO line items, exceptions are flagged, and partial / over-receipts trigger their own workflow. Every step is digital, time-stamped, and reportable.

Same platform, mobile-optimised view. The supervisor logs in with their identity, picks the allocated dealer (some supervise multiple), and gets a tailored screen — choose dealer, record footfall by department, update job cards, time-track the technician, close out the job. Reports are downloadable on the phone.

Stock is tracked per dealer. The distributor sees aggregated stock across their dealers, with auto-replenishment triggers based on velocity. When a dealer's consumable hits a reorder point, a transfer or PO is raised automatically. HO (or the OEM) can route slow-moving stock from one dealer to another via inter-dealer transfers, with full audit.

Yes — that's the most common configuration. Dealers run their own pricing, their own staff, their own customer relationships. What the OEM and distributor get is a consistent operating platform, real-time KPI visibility, and brand-standard SOPs. Dealer commercials remain the dealer's.

Slice-and-dice reporting at every tier. Country Head builds country reports, ASM builds territory reports, dealer principals build dealer-specific reports. We provide a curated library of pre-built reports plus a self-service builder — drag-and-drop dimensions, filters, exports. No SQL, no IT ticket.

A master dealer template at HQ holds the SKUs, packages, services, roles and SOPs. A new dealer is cloned from this template and customised for territory specifics. Most dealers are live in 5 – 10 days end-to-end, including data import. Compare that to the typical 2 – 3 months of bespoke setup.

Yes. GetAFix is cloud-agnostic — runs on AWS, Azure, GCP or on-prem. You can bring your own database licence (Postgres, MySQL, MS-SQL) and keep the data inside your VPC. We also stream operational data into your warehouse (Snowflake, BigQuery, Redshift) or lake (S3/ADLS/GCS as Parquet/Iceberg) so your analytics team can use the stack they already own.

Every action — login, permission change, PO approval, KPI target update, master-data edit — is logged with who, when, from where and from which device. The audit log is queryable and exportable. We support SAML / OIDC for enterprise SSO and have role-scoped logs for compliance reviews.

A typical 100-dealer network goes live in three phases over 6 – 10 weeks. Phase 1: HQ + 5 pilot dealers (2 – 3 weeks). Phase 2: scale to 30 dealers (next 2 – 3 weeks). Phase 3: rest of the network (final 2 – 4 weeks). The bottleneck is usually data migration from legacy systems, not the software itself — we run that in parallel.

We migrate it. Free data migration is included in every paid plan. We pull from spreadsheets, legacy DMS, POS exports, paper records (where it's feasible), and stand them up in GetAFix as the canonical record. Data quality issues (duplicate customers, inconsistent SKU codes) are surfaced and resolved during onboarding, not after.