Case study
Dealer Kits & VISTA Ordering — PH/VN Rollout
About the client
A global automotive manufacturer operating a multi-market dealer accessories ecosystem. Dealers already ordered individual parts through a production accessories portal; the business needed a bundled accessory kits experience — accessory packs tied to real production vehicle orders, rolled out for new markets without rebuilding the core platform.
The challenge
- Dealers in PH and VN needed the same proven accessories portal architecture already live in other regions, with country-specific pricing, tax, and dealer mapping.
- Accessory kits (bundled packs per vehicle model) had no dealer-facing browse-and-order flow inside the existing portal.
- Kit orders had to attach to production vehicle orders from VISTA — VIN/NSC sync, dealer visibility, and fitment workflows — not generic cart checkout.
- Operations teams needed configurable workflows for kit-based ordering, status tracking, pricing overrides, and audit trails across multiple actors.
- Content had to support multi-language authoring for localized kit descriptions and labels.
What we built
01
Dealer kits web experience
- Kits listing grouped by vehicle model, with country-aware visibility and featured kits.
- Kit detail pages — gallery, included accessories, pricing summary, and handoff into the dealer ordering workflow.
- Admin authoring — create/edit kits, map accessories, manage visibility and ordering per country.
02
Kit management system
- Country-level kit configuration, accessory mapping, and pricing layers.
- Dealer-side price override support with full audit logging on pricing and kit changes.
03
VISTA integration
- API layer to fetch dealer vehicle orders, auto-populate VIN/NSC, and surface eligible production orders inside the portal.
- Sync handling, error recovery, and mapping between dealer, vehicle, and country contexts.
04
PH/VN portal rollout
- Reused existing authentication, accessories architecture, admin infrastructure, and order flows.
- Market configuration, environment deployment, QA, and production rollout for both countries.
05
Workflow & localization
- Extended the existing POE/workflow engine for kit-based order lifecycles — dealer selection, operational processing, fitment tracking, email triggers, and timeline visibility.
- Multi-language content authoring in admin for kit titles, descriptions, and labels.
Process flow
- 1Dealer places a vehicle order in VISTA.
- 2Order syncs into the Accessories Portal with VIN/NSC populated.
- 3Dealer logs in, selects the eligible vehicle, and browses available kits.
- 4Dealer selects a kit, adjusts accessory-level pricing where permitted, and creates the accessory order.
- 5Workflow routes the order through operational stakeholders through fitment and delivery tracking.
Outcomes
✓
Markets live
PH & VN accessories portal + dealer kits on shared architecture
~500 kit/accessory orders/month
Order capacity
Platform scoped for ~500 kit/accessory orders/month at initial rollout
10–11 weeks
Implementation
10–11 weeks end-to-end (discovery through go-live), reusing existing portal vs. greenfield build
production vehicle orders
Dealer workflow
Kit selection tied to production vehicle orders via VISTA — not disconnected catalog browsing
audit trails
Operations
Configurable workflows with audit trails on pricing overrides, kit edits, and order status
✓
Localization
Multi-language kit content authoring for market-specific descriptions and labels
Technologies
Backend
Laravel — APIs, workflow engine, VISTA integration, audit logging
Frontend
React — dealer kits experience and admin authoring
Database
MySQL
Infrastructure
AWS with existing portal hosting reuse
Related work
This engagement extends the broader enterprise dealer accessories platform — same ecosystem, new markets, and the dealer kits layer on top.