Service Bay & Garage
Run your workshop like a pro. Service bays with equipment flags, auto-numbered job cards, full vehicle capture from the Fleet app, mechanic commissions and A4 & 80mm job cards — all on the trusted Sales & Accounting workflow.
Bay types with equipment flags — lift, pit, alignment, balancing, diagnostics and A/C — so every job lands in a bay that can actually do it.
Auto-numbered job cards (JC/YY/00001) — one clean reference per job, with a self-healing bay-status cron that never leaves the board wrong.
Full job-card lifecycle — Confirm → Start → Complete → Invoice — verified live on the AminiTech demo.
From drive-in to invoice, one clean workflow
Every screenshot below is a real screen from a working Odoo 18 install — verified end-to-end on our live demo.
Every job on one auto-numbered card
Open a job card and it takes its own number the moment it is created — JC/YY/00001, sequential, never repeated. Customer, bay, mechanic, promised time, complaint and diagnosis all sit on one screen, right beside the standard Sales order lines. New drive-ins default to a Walk-in customer so nobody is ever blocked at the counter.
Pull the vehicle straight from Fleet
Pick a vehicle from the Fleet app and its registration, make, model, VIN / chassis and odometer fill in automatically — the driver becomes the customer too. Or type a plate by hand for a first-time visitor. Because every card links back to the Fleet vehicle, the next visit shows that vehicle's full service history.
Confirm → Start → Complete → Invoice
Drive the whole job from one row of buttons. Starting work stamps the start time and marks the bay busy; completing it stamps the finish time and frees the bay. A defensive 5-minute cron re-syncs every bay from its live job cards, so a browser close or a cancelled order never leaves a bay stuck as occupied. Then Create Invoice posts exactly what the customer owes.
A bay board that matches jobs to equipment
Register each service bay against its station and flag exactly what it carries — vehicle lift, inspection pit, wheel alignment, wheel balancing, diagnostic tools, A/C service gear — across six bay types from General Service to Body Work. The board shows each bay's live status, assigned mechanic and jobs completed today, so the service manager always knows what is free.
Work performed and technician notes, kept
Beyond the complaint and diagnosis, capture a full write-up of the work performed plus private technician notes on every card. It is a permanent record of what was actually done to the vehicle — useful for warranty questions, comebacks and the next mechanic who opens the car.
Pay mechanics on the labour they earned
Flag employees as mechanics and give each an optional commission rate; leave it at zero to inherit the company default. The Mechanic Commissions report pays on labour lines only — parts are excluded — and is pre-grouped by mechanic so the end-of-month payout for each person, and the total, read straight off the screen.
Labour and parts as proper products
Set up your labour as service products with a category and an estimated duration, and your spares as stock parts — A/C re-gas, brake inspection, full service, oil change, tyre rotation and more ship as demo data. Turn on price-lock in Settings and unit price, discount and tax become read-only on job-card lines, so the catalogue price is what the customer pays.
Live in an afternoon
In Service Bay → Configuration, add each bay against its station and tick its equipment, then set up your labour services (with category and duration) and spare parts. Demo bays, services and parts ship with the module, so you can walk a job end to end before touching a keyboard.
New job card, pick or auto-default the customer and pull the vehicle from Fleet, assign a bay and a mechanic, add labour and parts, then run Confirm → Start → Complete and Create Invoice. Print the A4 job card for the customer or the 80mm thermal receipt for the counter.
The complete forecourt suite
Buy only what you need — every module shares the same foundation, data and security. Start with the free Base module and add the rest as you grow.
Other Odoo services we offer
Common questions
What does it need to run?
How are job cards numbered?
Do mechanics really earn commission?
Does it capture full vehicle history?
What reports and prints are included?
Is it part of a bigger suite?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Fleet (fleet) • Sales (sale_management) • Inventory (stock) • Invoicing (account) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4866 |
| Technical Name |
aminitech_petrol_service |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module