I get asked, more often than any other automotive question, whether Acumatica can run a car dealership end to end — VIN-level vehicle inventory, F&I (finance and insurance) deal structuring, service department scheduling, parts counter. The honest answer, and the one I lead with in every dealership conversation: no, not as a native fit, and nobody selling you otherwise is being straight with you.
Acumatica has no dealer management system, and does not claim to
A real automotive DMS — CDK Global, Reynolds & Reynolds, DealerSocket — handles VIN-specific vehicle inventory with floorplan financing, deal desking and F&I product attachment, factory warranty claim submission, and service scheduling with technician flat-rate time, as an integrated, purpose-built product refined over decades for exactly this workflow. Acumatica Manufacturing and Distribution Edition were not built for that job, and the realistic, common pattern in the market is exactly what it looks like elsewhere: dealers keep their DMS for the sales floor and service lane, and integrate it to Acumatica for financial consolidation — GL posting of closed deals, parts and service revenue, multi-rooftop consolidated reporting. I have seen this integration built against CDK and against Reynolds & Reynolds, and it is squarely an integration project (REST API or the DMS vendor's own export feed, mapped to Acumatica GL batches), not an Acumatica configuration project.
// Nightly job: pull closed deals from the DMS export feed, post as a
// summarized GL batch per department (sales, F&I, service, parts) per rooftop.
var batch = new PXGraph<GLBatchEntry>().CreateInstance<GLBatchEntry>();
foreach (var dept in dealClosingsByDept)
{
batch.GLTranModuleBatNbr.Insert(new GLTran {
BranchID = RooftopBranchMap[dept.Rooftop],
AccountID = DeptRevenueAccount[dept.Code],
SubID = dept.CostCenterSub,
CuryDebitAmt = dept.NetRevenue
});
}
batch.Save.Press();What genuinely fits, if a client insists on Acumatica-only
Parts operations at a dealership (parts counter, inventory, purchasing from OEM parts distribution) map reasonably onto Distribution Edition, similar to independent auto-parts distribution. Service department scheduling and technician dispatch can be approximated with the Field Service module (appointments, technician assignment, time and materials against a case), though it lacks flat-rate labor guides and OEM warranty claim integration that a real DMS service module has built in. Neither is "the same as a DMS" — both are partial, and I say so explicitly rather than let a client discover the gap during UAT.
You can model vehicles as serial-tracked stock items with the VIN as the serial number, which gives you basic in/out inventory tracking. It does not give you floorplan interest accrual, DMV/title workflow, or trade-in appraisal — all deal-desking functions a real DMS handles as core features. Treat this pattern as "good enough for a very small independent lot doing simple cash/consignment sales," not as a dealership solution.
Wrapping up
For a multi-rooftop dealership group, the realistic and honest recommendation is: keep a purpose-built DMS for the sales floor and service lane, and use Acumatica as the financial consolidation and multi-entity reporting layer behind it, connected by an integration. Building a from-scratch DMS replacement inside Acumatica is a multi-year custom development project, not an implementation — I tell every dealership prospect this on the first call, because it changes the entire scope conversation.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.