Odoo 17 Enterprise Backend UI / Dashboard Redesign for Temple360

# Odoo 17 Enterprise Backend UI / Dashboard Redesign – Temple360

We are looking for an experienced **Odoo 17 developer** to redesign the backend UI/navigation of an existing **Odoo 17 Enterprise installation hosted on Odoo.sh**.

We are developing a branded temple-management solution called:

**Temple360 by Speartech – Powered by Odoo**

This is primarily a **backend UI/navigation customisation project**, NOT a complete ERP redevelopment.

## Current System

Our current Odoo backend uses the standard app launcher with grid icons for Accounting, POS, Inventory, Purchase, Events, Employees, Website, Helpdesk, Documents, CRM, etc.

We want to transform this into a more professional Temple360 interface.

## 1. Left Sidebar Navigation

Replace/supplement the standard Odoo app-grid navigation with a **permanent and collapsible left sidebar**.

Example structure:

### Devotee Services

* Devotees
* Prayer & Services
* Booking & Reservations
* Donations & Ubayam
* Events & Festivals

### Counter

* Counter Services / POS
* Service / Kitchen Orders

### Operations

* Inventory
* Purchase
* Documents
* IoT

### Finance

* Accounting
* Petty Cash
* Expenses
* Payroll

### People

* Employees / Volunteers

### Digital

* Website
* Appointments
* Subscriptions

### Management

* Dashboard
* Reports

### Support

* Helpdesk

### Administration

* Apps
* Settings

The final menu structure will be confirmed during development.

Sidebar requirements:

* Temple360 branding
* Maroon/gold/cream colour scheme
* Menu icons
* Expandable/collapsible categories
* Active-menu highlighting
* Collapsible sidebar
* Responsive design
* Smooth navigation between Odoo applications

The normal Odoo application should open in the main content area.

## 2. Existing Odoo Menus & Actions

The sidebar must integrate with Odoo's existing menu/action architecture.

We do NOT want fragile hard-coded URLs/action IDs where avoidable.

For example:

**Accounting → existing Odoo Accounting**

**Inventory → existing Odoo Inventory**

**Counter Services → existing Odoo POS**

The underlying Odoo functionality must remain intact.

## 3. Role-Based Navigation

The sidebar should respect existing Odoo access rights/security groups.

For example, Counter Staff may only see:

* Devotees
* Prayer Services
* Bookings
* Donations
* POS
* Events

Finance users may see:

* Accounting
* Donations
* Purchase
* Expenses
* Reports

Administrators can see everything they are authorised to access.

Users should not see menu items for which they have no access.

## 4. Temple360 Home Dashboard

We would like a branded **Temple360 Home** page instead of relying only on the standard Odoo app launcher.

Possible dashboard elements:

### KPI Cards

* Today's Prayer Bookings
* Today's Donations
* Today's Counter Transactions
* Upcoming Events
* Pending Items

### Quick Actions

* New Prayer Booking
* Record Donation
* Open Counter
* Register Devotee
* Create Ubayam
* Search/Print Receipt

Some KPIs may depend on our existing custom modules. Please specify what is included in your quotation.

## 5. Temple360 Branding

We will provide:

* Temple360 logo
* Brand colours
* Background artwork
* Other available branding assets

The backend should have a **professional, clean, modern Temple360 appearance**.

Where appropriate, user-facing terminology may also be changed, for example:

**Point of Sale → Counter Services**

**Events → Events & Festivals**

We prefer UI/menu-level changes rather than unnecessary modification of underlying Odoo models.

## 6. Top Navigation

Where practical, integrate the Temple360 design into the top navigation while retaining existing Odoo functionality such as:

* Organisation/company selector
* Search
* Notifications
* Activities
* User profile
* Existing systray functions

## 7. Development Requirements

Development should preferably be contained within a dedicated custom addon such as:

`temple360_backend_theme`

We do **NOT want Odoo core files directly modified** unless there is an exceptional reason that is discussed and approved beforehand.

Requirements:

* Odoo 17 Enterprise
* Odoo.sh compatible
* OWL/Odoo 17 web client compatible
* Desktop/laptop optimised
* Tablet/iPad responsive
* Good performance
* Compatible with existing custom/third-party modules where reasonably possible
* Maintainable for future Odoo upgrades

Development and testing must first be performed on an **Odoo.sh staging/development branch** before production deployment.

## 8. Third-Party Theme Option

We are open to using an existing Odoo 17 sidebar/backend theme as the foundation if it reduces development cost and time.

However, you MUST disclose:

* Theme/module name
* Cost
* Licence
* Odoo 17 Enterprise compatibility
* Odoo.sh compatibility
* Any recurring/per-database licence
* Whether it can be used in a commercial solution deployed to multiple customers

Do not introduce undisclosed paid dependencies.

## 9. Deliverables

Successful freelancer should provide:

* Temple360 sidebar navigation
* Temple360 Home dashboard
* Branding integration
* Role/access-aware navigation
* Responsive interface
* Odoo 17 Enterprise/Odoo.sh compatibility
* Complete source code for custom development
* Installation/deployment instructions
* Basic technical documentation
* Staging testing
* Production deployment assistance
* Agreed post-delivery bug-fixing period

## 10. Source Code / IP

Temple360 is intended to become a commercial Speartech solution.

All custom code specifically developed and paid for under this project must be provided to us upon completion.

Any third-party/proprietary code, themes, modules or licensing restrictions must be disclosed BEFORE development starts.

## Required Experience

Please apply only if you have good experience with:

* Odoo 17
* Odoo Enterprise
* Odoo.sh
* OWL
* JavaScript
* XML/QWeb
* SCSS/CSS
* Odoo Web Client
* Menu/action architecture
* Security/access groups
* Backend themes/dashboard development

Previous Odoo sidebar/backend UI experience is strongly preferred.

## When Applying

Please provide:

1. Years of Odoo experience
2. Odoo 17 experience
3. Examples/screenshots/videos of similar Odoo UI work
4. Brief explanation of your technical approach
5. OWL experience
6. Odoo.sh experience
7. Estimated completion time
8. Fixed or milestone-based price
9. Any third-party modules/themes you intend to use
10. Included post-delivery support period

**IMPORTANT: Start your proposal with "TEMPLE360 ODOO17" so we know you have read the requirements.**

## Final Objective

We want Odoo to feel like a polished, purpose-built **Temple360 temple-management platform**, while retaining Odoo's functionality, permissions, stability and future upgradeability.

**Temple360 by Speartech – Powered by Odoo**