RAK Motors sells new and used cars and runs a workshop. Al Jawad Software House shaped Odoo so that a car sale, a repair job and an enquiry from the website all sit in one system, tied to the same customer.
Where the work gets hard
Two trades, one customer. Selling a car and repairing one need different paperwork, yet the customer is the same person.
Parts follow the job. A repair needs parts, and the purchase should be traceable to the job that needed it.
Credit. Staff need to know when an order is going ahead for a customer who is over an agreed limit.
What we implemented
Vehicles and printed paperwork
Vehicle records sit on the sales order, which is marked as a car sale or a repair. The motor vehicle sales certificate, the job booking (the repair estimate) and the vehicle delivery order all print from the same record.
Workshop jobs
A repair is a sales order linked to a workshop task. Time is recorded per job, and parts are requested from the task and linked to purchase orders. Where a customer has a credit limit, an order above it cannot be confirmed unless the user belongs to an approval group.
A public website
The website shows vehicles for sale and takes workshop bookings, sell or trade-in requests and job applications. The forms reach the team as emails.
How the work gets easier
| The usual way | With the new process |
|---|---|
| Car sales and repairs are handled apart | Both live on the same customer record |
| Parts are bought without a link to the job | Parts requests and purchase orders hang off the task |
| Credit is checked by memory | Odoo stops the order unless an approver steps in |
Staff spend less time reconciling paperwork and more time with customers.
Related solutions
- Odoo Field Service for Workshops
- Odoo Website
- Odoo Custom Development