Odoo Automotive Workshop Platform – Website, Vehicle Booking, Payments, Technical Forum & Future ERP

We are building USG Auto, a specialist automotive workshop in Riyadh, Saudi Arabia. We need an experienced Odoo techno-functional developer/team, not only a web designer.

Our goal is to use Odoo as the main digital system for the business.

PHASE 1 – REQUIRED NOW
1) Professional bilingual website
Arabic + English
Modern premium automotive design
Responsive on desktop, tablet, iPhone and Android
Main pages: Home, About, Services, Offers, Book Appointment, Technical Knowledge, Forum, Contact, Policies, Customer Portal where appropriate
Content must be editable by our staff without programming
2) Vehicle database and vehicle-specific services

Customer selects:

Make → Model → Year → Engine → Trim/configuration if needed

After selection, customer sees only compatible:

Services
Prices
Durations
Offers

Vehicles, services, prices, durations and compatibility must be editable inside Odoo and preferably importable by Excel/CSV. Do not hard-code this data into website pages.

3) Appointment booking

Each service has a duration and the booking system must prevent overbooking based on available resources such as technicians, bays and future dyno capacity.

Management must be able to:

Change service durations
Change capacity
Set working hours/holidays
Block times/days
Add appointments manually
Reschedule/cancel
Override restrictions

Initial booking rules:

Minimum booking notice: about 1 hour
Normal customers: about 2 days ahead
Outside-Riyadh customers: about 3 days ahead

All rules must be configurable.

4) SAR 100 booking deposit

Appointment is confirmed only after payment of SAR 100.

The deposit should be recorded as an advance and credited toward the final invoice when applicable.

Payment gateway should preferably support:

Mada
Visa/Mastercard
Apple Pay

Developer should recommend the suitable Saudi gateway.

5) Cancellation/rescheduling

Initial rules:

One free reschedule if requested at least 4 hours before appointment
Late cancellation/reschedule may forfeit SAR 100
New appointment requires a new deposit
Management can manually override
Customer must accept policy before payment
Changes must have an audit history

All rules must remain configurable.

6) Tabby and Tamara

Integrate both for eligible larger workshop invoices and/or online orders.

Requirements:

Payment status updates automatically in Odoo
Cancellations/refunds handled correctly
Developer must specify existing Odoo module vs custom API
Clearly list module cost, integration cost and recurring fees
7) Notifications

Initially by email:

Booking confirmation
Payment confirmation
Reminder
Reschedule
Cancellation

System should be ready for future SMS/WhatsApp. Arabic and English templates must be editable.

8) Technical Knowledge / Articles

We will publish original automotive technical articles and real workshop cases such as Ford Taurus front sensor retrofit, SYNC 4 upgrades, 360 camera retrofits, programming and transmission diagnostics.

Articles should support:

Text
Photos/videos
Vehicle information
Categories/tags
Author/date
Related services
Related forum discussions

Public technical content must be search-engine indexable with proper SEO basics: clean URLs, page titles, metadata, sitemap, canonical handling and sensible structured data.

9) Automotive enthusiast forum

Preferably within Odoo if practical.

Possible categories:
Ford, GM, Mopar, German Vehicles, Programming, Retrofits, Electrical Diagnostics, Engines, Transmissions, Performance and Technical Cases.

Users should be able to register, post topics/replies and upload relevant images. Moderators need standard moderation controls. Public discussions should be indexable where appropriate.

10) Online shop readiness

System should support future sale of parts, retrofit kits, electronics, merchandise and prepaid services.

Odoo should remain the main business system. Future Salla integration may be added as a sales channel.

11) Management dashboard

At minimum:

Upcoming appointments
Calendar
Deposits
Cancellations/reschedules/no-shows
Popular services/models
Revenue
Customer booking history
PHASE 2 – FUTURE WORKSHOP MANAGEMENT

Phase 2 is not required to be fully developed now, but Phase 1 must be designed so it can be added later without rebuilding the system.

Future requirements include:

Customer and vehicle records with VIN, plate, mileage, vehicle history, previous visits, quotes, invoices, findings and photos
Reception check-in from phone/tablet with customer complaint, mileage, fuel level, warning lights, existing damage, photos/videos, documents and signature
Mobile-friendly employee interface/PWA for technicians and staff
Technician workflow: view assigned vehicle, complaint/history, add findings, comments, photos/videos, measurements, DTCs, scan reports, recommendations, parts requests, start/stop labor time and update status
Work-order stages such as Received → Inspection → Diagnosis → Estimate → Waiting Approval → Waiting Parts → Work in Progress → QC → Road Test → Ready → Delivered
Remote customer quotation approval/rejection, including individual items and audit trail
Parts/inventory: part numbers, suppliers, cost/selling price, stock locations, vehicle compatibility, reorder levels, purchase orders, receiving, issuing/reserving parts to work orders, returns, transfers, barcodes and serial tracking for major assemblies
Parts reports: monthly/yearly consumption, fast/slow moving stock, turnover, usage by vehicle/manufacturer and suggested reorder quantities
HR: employees, attendance, leave, roles, labor hours, productivity and efficiency
Accounting: Saudi VAT, ZATCA e-invoicing, invoices, supplier bills, deposits, credit notes, expenses, payments and bank reconciliation
Customer portal: vehicles, appointments, repair status, quotes, approvals, photos/findings, invoices, payments and service history
Future dedicated customer/employee apps can be added later, so architecture should remain API-friendly
TECHNICAL / OWNERSHIP REQUIREMENTS
Use standard Odoo functionality whenever practical; custom-code only where needed
System must remain maintainable by another qualified Odoo developer
USG Auto must own/control domain, Odoo admin, hosting, database, Git repository, all custom source code, payment accounts, email accounts and business data
No encrypted or developer-locked custom modules
Custom development must be documented
Staging environment required before production updates
Backups and restore procedure required
Arabic RTL must be properly tested
Important screens must be tested on iPhone, Android, tablet and desktop
Role-based permissions for management, reception, technicians, parts, accounting and customers
Developer should recommend Odoo edition/version and hosting and explain why
ACCEPTANCE TEST

Final Phase 1 milestone is only accepted after this complete workflow works end-to-end:

Select vehicle → see correct compatible services/prices → choose service → system checks duration/capacity → choose available slot → pay SAR 100 → booking confirmed → notification sent → booking appears correctly in Odoo → admin can manage/reschedule/cancel it correctly.

Tabby/Tamara and the agreed Knowledge/Forum functions must also be demonstrated.

PROPOSAL MUST ANSWER

Please start your proposal with:

USG ODOO

Have you built Odoo for an automotive workshop/service center before? Show examples if available.
Which Odoo edition/version and hosting do you recommend?
Which requirements are standard Odoo and which need custom development?
How will you structure Make/Model/Year/Engine/Trim and service compatibility?
How will you prevent appointment overbooking?
Which Saudi payment gateway do you recommend?
Can you integrate Tabby and Tamara?
Have you worked with Saudi ZATCA?
Can you implement the Technical Knowledge and Forum sections?
Will the future employee workflow work well on phones/tablets?
Will all source code and Git repository belong to USG Auto?
What paid third-party modules and recurring costs are required?
What is your fixed Phase 1 price and timeline?
Divide Phase 1 into milestones.
What post-launch bug-fix/support period is included?
What is your hourly/day rate for future work?
Give a rough estimate/approach for Phase 2 separately.

Generic bids will not be considered. Phase 1 is the project being awarded now. Phase 2 is future scope and should be priced separately.