Openfront Dealership
Vehicle inventory, leads, deals, test drives, trade-ins, finance intake, and service.
Openfront Dealership combines a public vehicle inventory with the operator work that follows an inquiry: leads, test drives, trade-ins, deals and approvals, finance intake, service appointments, repair orders, parts, tasks, and reporting.
Finance forms are lead intake, not underwriting or lender decisions. Current source does not establish payment processing, credit compliance, identity verification, e-signature, or DMS/accounting parity.
Architecture and schema
DealerGroup and active group membership are the tenant root; Rooftop and RooftopMembership narrow staff and operational scope. Relationship hooks and custom commands validate rooftop ownership for submitted IDs. The graph includes dealer groups, rooftops and memberships; makes/models, vehicles, images, history, condition and price records; inventory acquisition, stock, feed, merchandising and reconciliation records; leads and interactions; test drives and trade-ins; deals and approvals; financing applications and lender submissions/decisions; service appointments, service orders, repair lines/packages and parts; delivery work, tasks, audit/outbox events, and dealership profiles.
Public routes cover inventory/detail/compare, contact, financing, service, test-drive, and trade-in intake. Operator routes under /dashboard/platform cover overview, vehicles, CRM, deals, delivery, finance, test drives, trade-ins, service, and analytics.
Main workflow
A buyer browses a published vehicle and submits an inquiry, test-drive request, trade-in, finance inquiry, or service request. Staff qualify the lead, schedule work, and move a deal or service order through controlled internal steps. Sensitive financial inputs should be minimized and routed through a purpose-built secure boundary rather than copied into generic notes.
Bounded GraphQL operations
Public intake mutations submit inquiries, test drives, trade-ins, financing, and service requests with rooftop scope and abuse controls. operatorProjections, operatorWorkspaces, and inventoryWorkspace provide task reads. Named commands cover lead ownership/activity, deal pencils and transitions, financing queue/decisions, inventory acquisition/stock/feed/merchandising/reconciliation, test-drive workflow, trade-in appraisal, service orders, tasks, membership changes, and delivery completion. Finance operations record applicant and lender workflow evidence; they do not underwrite or originate credit.
Setup and onboarding
Use a disposable PostgreSQL database. runDealershipOnboarding creates a synthetic dealer group, rooftop, membership, profile, and evaluation records. Run it against an isolated current database, verify that a second execution does not duplicate tenant identity, and inspect all seeded names, inventory, leads, applications, and appointments before publishing screenshots. The local seed is not a hosted demo.
Integrations
The current payment decision is N/A because deal and service fields record externally handled facts. There is no payment adapter directory. Inventory-feed and financing/lender models/routes are local intake and evidence boundaries; no lender, credit bureau, DMS, OEM, e-signature, accounting, identity, or payment adapter was found. Do not claim external execution until adapter authentication, consent, mapping, retries, reconciliation, and privacy controls are implemented and tested.
Security and deployment
Protect income, credit-range, contact, vehicle-history, deal, approval, and service records. Deal and approval transitions need immutable evidence and restricted raw edits. Railway builds then migrates at start. Current source has targeted onboarding/payment/platform checks, but the repository README's env.example instruction points to a missing file and must not be copied as a setup guarantee.
Before deployment, verify public-intake rate/abuse controls, cross-group/rooftop and membership denial, relationship changes, financing-field privacy, inventory acquisition/feed reconciliation, deal/service terminal states, reviewed migrations, audit/outbox, restore, and responsive customer/operator routes. Current source does not underwrite credit, originate loans, settle payments, provide external vehicle history, or establish dealer/lender/compliance certification.