← All workBalaji SankarCase study 03 / 12
Vehicle platform / dealer operations2026NDA · name withheld

Vehicle DealerHub

I merged a standalone upfitter portal into the main dealer dashboard of a vehicle platform: one login, one design system and one codebase, with no business logic lost.

Client

A vehicle platform for fleets, dealers and upfitters

Role

Senior frontend engineer

Timeline

2026

Stack
ReactTypeScriptViteTanStack RouterTanStack Queryshadcn/uiTailwind CSSZoddate-fnsKeycloak
Outcomes
70+

Shared components reused instead of rebuilt

✦

Two frontends merged into one deployment, one login and one design system

Thechallenge

Getting work vehicles into a fleet involves the buyer, the dealer that sells the chassis and the upfitter that turns it into a working truck or van. The platform had separate web apps for these groups.

The upfitter portal ran as its own deployment with its own design system, state layer, router and login, so upfitters and dealers got different experiences and the team was maintaining two frontends for closely related order workflows.

How Iapproached it

01

Spec first

I read the legacy portal end to end and wrote a migration requirements doc covering every screen, business rule and edge case, mapping each legacy component to its dealer-dashboard equivalent before writing any code.

02

Re-platform, don’t copy

MUI Joy became shadcn/ui and Tailwind on the dashboard’s tokens, Redux and RTK Query became React Query with scoped context, React Router became file-based TanStack Router, Yup became Zod and moment became date-fns.

03

Reuse what exists

Upfitter screens were built from the dashboard’s existing order-tracking components and page layout, so they look and behave like the rest of the product.

04

Ship in phases

The core migration went out in phases, with analytics kept continuous throughout.

Highlightsworth showing

  • (01)

    Open and completed order workflows, bulk CSV and Excel import, filtering, search, export and upfitter profile management moved into the unified dashboard.

  • (02)

    Magic-link login retired in favour of the dashboard’s Keycloak SSO, so auth pages didn’t need migrating at all.

  • (03)

    New screens built from a 70+ component internal library rather than a parallel UI kit.

  • (04)

    Datadog kept alongside Amplitude and PostHog so monitoring history survived the cutover.

Have a project like this?

Tell me what you’re building or what’s broken. I’ll tell you straight whether I’m the right person for it.

Next caseProcurement / spend analytics / B2B SaaS2022 - presentSimfoni Suite→