DWOR Sub Dealers Network
DWOR Sub Dealers is an automotive sub-dealer network portal that consolidates dealer profiles, vehicle inventory, and buyer inquiry workflows into a single, searchable web platform. The solution digitised a previously offline, spreadsheet-driven dealer-management process and brought it online with role-based access for network administrators and individual dealers.
Business Context
Business Problem
The DWOR dealer network managed hundreds of sub-dealers through WhatsApp groups and manual Excel sheets. Buyers had no way to discover authorised dealers online, and the network had no visibility into inquiry volume or conversion rates. The client needed a digital presence that could establish trust with buyers and give the back-office team a live dashboard to manage dealer records and leads without technical expertise.
Technical Architecture
Architecture Decisions
Chose Next.js (App Router) for SSR/SSG hybrid rendering - dealer listing pages are statically generated at build time for SEO, while the inquiry form and admin dashboard are client-rendered SPAs. MongoDB was selected for its flexible document schema, allowing each dealer profile to carry variable attribute sets (brands carried, service specialities, regions). REST API routes are handled via Next.js API handlers to keep the stack unified. JWT authentication secures the admin panel.
Technology Stack
Architecture Details
Engineering Challenges
Technical Challenges
Building a performant, SEO-friendly dealer directory with dynamic filtering (region, brand, vehicle type) without sacrificing page load speed. The dealer profiles required real-time data updates without full page reloads. Designing a role-based admin panel that non-technical staff could operate confidently was a significant UX challenge on the backend.
Performance Optimizations
Static generation of dealer listing pages with ISR (Incremental Static Regeneration) set to 1-hour revalidation. Image optimisation via next/image with WebP conversion. Lazy loading of dealer cards below the fold. Minimal JavaScript bundle through route-level code splitting.
Scalability Details
The architecture supports horizontal scaling on Vercel edge functions. MongoDB Atlas can scale vertically or switch to sharding if dealer count exceeds 10,000 records. The API layer is stateless and can be extracted to a microservice if required.
Constraints & Tradeoffs
Budget constraints meant using Vercel free tier and MongoDB Atlas free cluster for MVP. ISR was chosen over full SSR to stay within Vercel serverless invocation limits. Image hosting relies on external CDN URLs rather than a dedicated asset store - a known limitation to address in v2.
Delivery & Impact
Measurable Impact
Launched within 90 days. 250+ dealer profiles onboarded in the first month post-launch. Inquiry volume increased from ~10/month (WhatsApp) to 150+ structured web inquiries within 60 days. Admin team reduced dealer-record update time by 80% compared to the previous Excel workflow.
Client Outcome
The client now has a professional online presence that ranks on Google for local automotive dealer searches. The structured lead inbox replaced WhatsApp chaos and gave the business owner clear data on inquiry sources and conversion. The platform became the primary sales channel for the network within 3 months of launch.
Reflection
What Would Be Done Differently Today
In hindsight, I would introduce a dedicated asset upload system (e.g., Cloudinary or AWS S3) from day one instead of relying on external image URLs. I would also instrument dealer inquiry funnels with analytics events earlier in the project to provide the client with conversion data from week one rather than retrofitting tracking later.
Project Details
Ready to Start Your Project?
Let's discuss how we can help bring your vision to life with innovative technology solutions.