Dealer management system for Škoda

Škoda DMS – NVS

NVS (New Vehicle Sales) is the new-car sales module of a dealer management system used by Škoda dealerships, rebuilt from legacy DMS3 screens into a modern React application.

Role
Senior Frontend Developer
Web
Internal system – not publicly accessible
Škoda DMS – NVS – desktop, tablet and phone
WCAG 2.2AA accessibility target
3languages: Czech, Slovak, English
2colour modes: light and dark
~500automated test files
< 2.5 sLCP performance budget

About the project

The challenge

The original DMS3 screens were dense, server-rendered pages: a long filter column on the left, tables with dozens of narrow columns and almost no feedback. They worked, but only on a large monitor and only for people who already knew them by heart.

The solution

A new React application that keeps every business rule of DMS3 but rebuilds the experience around common tasks: the most used filters in one row, readable tables that each user can set up, detail pages with tabs, keyboard shortcuts, dark mode and a layout that also works on a tablet or phone.

My role

I work on it as Senior Frontend Developer: screen architecture, shared components (data tables, filters, forms, dialogs), the Škoda Flow design system theme, translations, performance and tests.

What I built

  • Stock list and stock card with tabs for equipment, pricing, handover, documents and after-sales support, each tab with its own URL
  • New-car offers with configurations, discounts and a prototype AI sales assistant that suggests vehicles from a conversation
  • Shared data table: server paging or infinite loading, sorting, column order, visibility and width saved per user, keyboard navigation
  • Filters stored in the URL, so a filtered list can be shared and the user returns to the same place after opening a detail
  • Škoda Flow design system on top of MUI, light and dark mode, Czech, Slovak and English with locale-aware number and date formats
  • Performance budget (LCP under 2.5 s, CLS under 0.1), route-level code splitting, subsetted brand font, WCAG 2.2 AA as the accessibility target

Redesign

Before and after

Drag the slider to compare the original DMS3 screen with the new NVS module.

Stock list
NVS (new) – Stock list
DMS3 (original) – Stock list
DMS3 (original)NVS (new)
Offers list
NVS (new) – Offers list
DMS3 (original) – Offers list
DMS3 (original)NVS (new)

Anatomy of a screen

The stock list, piece by piece

NVS stock list with numbered callouts
  1. Quick search and the most used filters in one row
  2. More filters and table settings open in side panels
  3. Sortable column headers with a menu for each column
  4. Prices aligned right and formatted for the user's language
  5. Row actions: view or edit, also from the keyboard
  6. Progressive loading instead of hard paging
Škoda DMS – NVS – key screens
Key screens

Use cases

Built around everyday tasks

Find anything with ⌘K
01

Find anything with ⌘K

A command palette opens from anywhere: jump to a screen, create a new record or search by text without touching the mouse.

Filters that fit the job
02

Filters that fit the job

The most used filters stay in the toolbar, the rest live in a searchable side panel. The filter is stored in the URL, so a filtered list can be shared and restored.

Everyone sets up the table
03

Everyone sets up the table

Column order by drag and drop, visibility, pinning, table or card view and page size, saved for each user.

Stock card with tabs
04

Stock card with tabs

A summary of the car on the left, tabs for equipment, pricing, handover and documents. Every tab has its own URL and loads only when opened.

Offer overview
05

Offer overview

Every configured car of an offer with prices, discounts and the final price in one view, ready to discuss with the customer.

Theming

Light and dark mode

The user picks light, dark or the system setting. Every colour comes from Škoda Flow tokens, so both modes keep the same contrast rules.

Dark mode
Light mode
LightDark

Accessibility

Designed for WCAG 2.2 AA

Table row selected with the keyboard, with a visible focus outline
Alt+Shift+K jumps into the table, ↑↓ select a row, Enter opens it
WCAG 2.1.1

Keyboard

Everything works from the keyboard: arrows move through table rows, Enter opens a record, Alt+Shift+K jumps into the table and Ctrl+K opens the command palette.

WCAG 2.4.7

Focus visible

A 2 px outline in the primary colour marks the focused element and is never removed without a replacement.

WCAG 1.4.3

Contrast

Text meets 4.5 : 1, large text and controls 3 : 1. A unit test checks the contrast of the whole theme palette.

WCAG 2.5.3

Label in name

The visible text of a button is always part of its accessible name.

WCAG 1.4.10

Reflow

Screens work at 200 % zoom and 320 px width without horizontal scrolling.

WCAG 4.1.2

Name, role, value

Semantic components, correct ARIA states and dialogs with a focus trap and focus return.

Contrast of key colour pairs

  • Primary text and links#31694b / #ffffff6.46 : 1AA
  • Text on the Electric Green button#161718 / #78faae13.75 : 1AAA
  • Body text#161718 / #ffffff17.95 : 1AAA
  • Electric Green on a dark surface#78faae / #23242511.91 : 1AAA

How it is verified

  • axe-core audits in Playwright on the main pages and panels
  • jsx-a11y lint rules on every commit
  • Component tests find elements by role, so an inaccessible element fails
  • Manual keyboard-only pass of every new screen

Design system

Škoda Flow, translated to code

One file of design tokens drives the MUI theme: colours, type scale and one size scale shared by buttons, chips and pagination.

AaBrand primary#31694b
AaElectric#78faae
AaEmerald#0e3a2f
AaMint light#e8fff1
AaOn surface 900#161718
AaSurface#f1f1f1

Type scale (px)

h1 32/40Stock card
h2 28/36Stock card
h3 24/32Stock card
h4 20/28Stock card
body1 14/20Stock card
caption 12/16Stock card

One size scale

Filtersmall · 32 px
Filtermedium · 44 px
Filterlarge · 52 px

Performance

A performance budget from day one

LCP< 2.5 sLargest Contentful Paint · target
CLS< 0.1Cumulative Layout Shift · target
INP< 200 msInteraction to Next Paint · target
  • Route-level code splitting, each screen and tab is its own chunk
  • Data loaded in route loaders before render, no request waterfalls
  • Brand font subset to Latin, Czech and Slovak with metric-matched fallbacks, so swapping fonts does not move the layout
  • Heavy libraries (date picker, drag and drop, editor) load only when needed
Škoda DMS – NVS – mobile version
Designed for phones too

Live preview

Scroll through the site

Škoda DMS – NVS – desktop
Škoda DMS – NVS – mobile

Technologies

  • React 19
  • TypeScript
  • Vite
  • TanStack Router
  • TanStack Query
  • TanStack Form
  • TanStack Table
  • Zustand
  • MUI
  • Škoda Flow
  • Zod
  • use-intl
  • Vitest
  • Playwright
  • axe-core

Customer names, VIN codes and user names in the screenshots are blurred.

Planning something similar?

Tell me what you are working on and I will get back to you with a proposal for the next steps.

Get in touch