We’re building a two‑sided marketplace in the used‑vehicle industry. One side is a dealer portal, where car dealerships can list and trade inventory with one another. The other side is a consumer portal, where private individuals can list their vehicles for sale or trade. The two portals share a common database so vehicles can flow seamlessly between them. Users on each side have different permissions and experiences. Key Objectives • Help dealerships source or offload vehicles quickly by connecting them directly with other dealers. • Provide consumers with an easy, transparent way to get multiple purchase or trade‑in offers from dealers. • Use data and simple AI logic to suggest vehicles that are likely to sell faster or match dealer demand. • Keep branding and business names hidden—use placeholders in your code and documents. Core Features for the Dealer Portal • User Accounts: Allow multiple dealership users to sign up, with roles and permissions (owner vs. staff). • Inventory Management: Dealers can add, edit, and delete cars with details like year, make, model, VIN, mileage, color, price, and photos. • Trading/Wholesale Listings: Dealers can mark vehicles as available for trade or wholesale, filter and search other dealers’ listings, and request swaps. • Offer & Negotiation System: Dealers can send offers to each other for trades or purchases. Offers can be accepted or declined. • Basic Messaging: Optional chat or message threads attached to each offer for negotiation. • Dashboard & Notifications: A summary page showing new offers, pending requests, and accepted trades, with email alerts. Core Features for the Consumer Portal • Listing Form: Consumers can list their car by entering details and uploading photos. They receive an estimated value via integration (for example, a VIN decode API). • Dealer Offers: Dealers can view consumer listings (within selected regions) and place purchase offers. Consumers can view and compare offers. • Accept/Decline: Consumers accept one offer, which triggers contact info exchange with that dealer. The listing then comes off the market. • Simple Account or Guest Flow: You can allow guest listings or require an account for follow‑ups and notifications. Shared and Admin Functions • Central Database: Cars, offers, trades, and users all exist in a shared backend. A car can switch from “private/dealer‑only” to “public/consumer‑listed” status. • Admin Panel: Admin can see all users, vehicles, offers, and logs. Ability to deactivate accounts or moderate content. • Analytics: Basic reporting (number of vehicles listed, offers made, acceptance rate, etc.). • Integrations (Phase 2+): Vehicle lookup for automatic specs (e.g. VIN decoder); optional pricing data sources; email service for notifications. Technical Guidance • Build in a modern web stack or no‑code platform with user authentication, role‑based permissions, and a relational database. • Keep the codebase organized so that dealer and consumer flows are separated but share models. • Use environment variables or configuration files to store real brand names, API keys, and URLs (so they don’t appear in the repo).