Auto Parts CRM
The current Version 5.0 Admin dashboard, shown with the public demo's sample data.
Introduction
MEE Auto Parts is a US aftermarket parts operation where a single sale touches quoting, order entry, invoicing, e-signature, carrier handoff, and payment follow-up.
The team was fast on the phone and slow on the paperwork. Leads were tracked in one place, orders in another, invoices in a third, and shipping status nowhere at all. Every handoff between those systems was a re-typed record and a chance to lose a sale.
We designed and built the CRM that holds all of it on one record — from the first inbound call to a signed invoice and a tracked delivery.
The vision
Replace six tools with one operating system for the business. We mapped the real path of a part — inquiry, quote, order, invoice, signature, carrier, delivery, payment — and built a single application around that path.
The measure of a CRM is not how much it can store. It is whether the person on the phone can see the next action without opening a second tab.
Design principle behind the Auto Parts CRM
Sweating the details
A tool people live in for eight hours a day earns its keep in the small decisions — where an action sits, what a colour means, how much a table can carry before it stops being readable.
The number first, the label second
Every card leads with the figure at display weight, then explains it. A manager scanning the dashboard reads values before they read words.
Status is a colour, not a sentence
In transit, invoiced, active, converted — each state has one chip treatment used identically across leads, orders, shipments, and users.
Actions sit on the object they act on
Invoice controls live on the order. Convert-to-order lives on the lead row. Nothing important hides behind a menu two levels deep.
Dense, but never cramped
Tables carry eight columns at a comfortable 44px row height, on a soft blue-white canvas that keeps long shifts easy on the eyes.
Palette
- Action blue
#2563EBPrimary actions, links, active nav - Ink
#0B1830Headings and figures - Slate
#66748BBody copy and helper text - Confirm
#0F7A4DPaid, active, invoiced states - Attention
#D97706Follow-ups and partial payments - Exception
#DC2626Delays and outstanding balance
Old meets new
Four places where a sale quietly leaked, and what replaced each one.
- 01Before
Leads lived in three places
Inbound calls, marketplace inquiries, and follow-ups were split across spreadsheets, inboxes, and personal notes. Nobody could say what was still open.
NowOne pipeline with honest statuses
- 02Before
Quotes did not become orders
Converting a quote meant retyping customer, vehicle, and part details into a second system — so quotes went cold while the paperwork caught up.
NowOne action promotes a lead
- 03Before
Invoicing stalled on signatures
Invoices were generated outside the workflow, emailed manually, and chased over phone. No one could see whether a customer had signed.
NowGenerate, send, sign, re-issue in place
- 04Before
Shipping was a black box
BOL and PRO numbers sat with the carrier desk. Sales had no way to answer 'where is my part?' without forwarding the question.
NowBOL and PRO on the order itself
- 01Lead captured
- 02Quoted
- 03Converted
- 04Order built
- 05Invoiced
- 06Signed
- 07Shipped
- 08Reported
The product in operation
The finished product connects dashboards, leads, orders, invoices, shipments, replacements, and role-based access. The separate project page documents each workspace in detail.
See how every operational workspace connects.
Explore the interfaces, role boundaries, shipment controls, replacement workflow, and complete order record on the Work page.
Outcomes
What the team got.
- 7workspacesDashboard, Leads, Orders, Shipments, Costs, Notes, User Center
- 3access rolesAdmin, sales agent, and shipping account — each sees a different app
- 6lead stagesProspect through converted, with reasons captured on every drop-off
- 1record end to endThe same order carries quote, invoice, signature, and shipment
- A quote becomes an order in one action, carrying customer, vehicle, and part detail with it.
- Invoice generation, delivery, signing, and re-issue happen inside the order — never in a side channel.
- Every order answers 'what happened and who did it' from a single timeline.
- Sales, admin, and shipping work from the same data with three different levels of access.
- Delays are counted as their own metric, so exception handling is the first job of the day.
- Revenue, paid, partially paid, and outstanding balance are visible without exporting anything.
Next.js · React · TypeScript · Node.js · REST APIs · PostgreSQL · PDF generation · E-signature flow · Role-based auth
Have a workflow that lives in six tools?
We design and build internal systems that hold an entire operation on one record — from first inquiry to final payment.