Odoo business applications
Service businesses lose money in the gaps: the order that never became a project, the hour nobody booked, the ticket that was never invoiced. This page shows how we close those gaps in Odoo, and what project profitability looks like when the data is real.
Reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
The short answer
It covers how sold work gets delivered and paid for: the hand-off from a sales order to a project, planning and capacity, timesheets and expenses, field dispatch, helpdesk and SLAs, appointments, and the invoicing that follows. Done well, you can see profitability per project and per customer from the same records your team already fills in. Done badly, you have a task list and a separate spreadsheet of hours.
The test of a service implementation is not whether projects exist in the system. It is whether an hour booked on Tuesday shows up in the customer's invoice, the project margin and the payroll cost without anyone re-keying it.
That's why this family sits between sales and finance rather than beside them, and why the sections below follow the work rather than the apps.
The connected workflow
From the signed order to the invoice and the margin behind it. Each step names the app that carries it, or the custom work when the standard flow does not fit.
Step 01
A confirmed order creates the project and its tasks, with the sold hours attached, so delivery starts from what was actually agreed rather than a forwarded email.
Step 02
Who is available, for how long, with which skills. Shifts and assignments made against real capacity instead of optimism.
Step 03
Timesheets booked against tasks by the people doing the work, on the web or a phone, with locking and rounding rules that make the data trustworthy.
Step 04
Work orders scheduled and sent to the person on site, with the parts, the checklist and the customer sign-off captured where the job happens.
Step 05
Tickets from email, portal or phone, routed to teams, tracked against response and resolution targets, and linked to the customer and contract behind them.
Step 06
Clients see progress, documents, tickets and approvals without emailing an account manager, which is usually where service teams lose the most time.
Step 07
Time and materials, fixed price, milestones or recurring retainers, invoiced from the delivery records so billing matches what was actually done.
Step 08
Revenue against real cost per project, per customer and per person, which is the number a services business is actually run on.
The step teams underestimate is time capture. If the hours are late, incomplete or invented at month-end, everything downstream (billing, margin, capacity) is fiction, however good the reports look.
Grouped by job
Each item is from a system in production, with the client named.
Opsio runs Timesheet Profitability and Project Profitability modules on Odoo 18 Enterprise, so margin per project and per engineer comes from the same records the team fills in daily.
Automated timesheet locking and rounding rules, built for Opsio, stop retrospective edits and half-remembered hours from quietly rewriting last month.
Project recurrence, subscription and contract management, and recurring purchase orders, so a managed-services business does not recreate the same work every month by hand.
Opsio runs customised helpdesk workflows with a support portal and portal extensions. Keypear gives its engineering clients support ticketing inside the same portal they use for their work.
Slango runs an Admin, Finance, Director and Chairman approval chain with payment verification, automated notifications and Chatter-based audit history on Odoo 19 Community.
Opsio has service-delivery and task-workload dashboards built around how its managers actually allocate work, not the generic views that ship with the apps.
The honest three columns
Service management is well covered by standard apps. The custom work clusters in two places: making time data trustworthy, and showing clients what they want to see.
| Requirement | Standard Odoo | Configuration or OCA | Custom engineering (and why) |
|---|---|---|---|
| Projects and tasks | Yes, fully | Stages, task types, templates, analytic accounts | Rarely, beyond fields your delivery process needs |
| Timesheets | Yes, web and mobile | Approval, validation, reminders | Locking, rounding and rules that make hours auditable, as built for Opsio |
| Recurring work and retainers | Subscriptions on Enterprise | Plans, renewal reminders | Project recurrence and recurring purchase orders when delivery, not just billing, repeats |
| Helpdesk and SLA | Enterprise Helpdesk app | Teams, stages, SLA policies, email aliases | On Community, or when routing and escalation follow contract terms |
| Field service | Enterprise Field Service app | Worksheets, products, scheduling | Offline capture and device-specific workflows for crews without signal |
| Customer portal | Standard portal views | Portal access, document sharing | Portals that are the product, as at Keypear and Slango: approvals, verification, generated reports |
| Profitability reporting | Analytic accounting and basic reports | Analytic plans, cost rates per employee | The margin view your managers actually use, as built for Opsio |
If a service requirement needs code, it is usually to make the data honest or to give a client a view they will use without training. Both are worth paying for. Rebuilding Projects is not.
Edition and OCA
This family has more Enterprise-only apps than most, so the edition decision is worth making deliberately.
| Capability | Community | Enterprise | Notes |
|---|---|---|---|
| Project and tasks | Yes | Yes | Core in both |
| Timesheets | Yes | Yes | In both. The trust rules are custom either way |
| Helpdesk | OCA or custom | Yes | Enterprise app. Slango and Keypear run portal-based request flows on Community |
| Field Service | OCA or custom | Yes | Enterprise app |
| Planning and shift scheduling | –No | Yes | Enterprise app |
| Appointments | OCA or custom | Yes | Enterprise app |
| Subscriptions and recurring billing | OCA or custom | Yes | Enterprise app, and we have built the lifecycle on Community |
| Analytic accounting for margin | Yes | Yes | Available in both. The reporting layer is where the work is |
Helpdesk, Field Service, Planning and Appointments are the four Enterprise apps that usually decide this family. If your service delivery runs through a customer portal rather than internal apps, Community plus a custom portal is a serious option, and we have shipped it twice.
Data and boundaries
How we run it
We follow one sold job from order to invoice with the people who deliver it: who schedules, who books time, who talks to the client, who chases the bill.
Project structure, analytic model, cost rates, invoicing policy per contract type, SLA definitions and what the customer portal exposes. Written down with the reasoning.
Timesheets before dashboards, always. If the hours are not trustworthy, every report built on them is decoration.
Standard apps configured, OCA where it fits, then custom modules for locking rules, portals, recurrence and the margin views your managers will actually open.
A real project delivered end to end, including an awkward one: scope change, partial invoice, an escalated ticket.
Cutover with a rollback path, then close support through the first billing run and the first profitability review, until the numbers are trusted.
Evidence
Only projects where the service workflow described above is actually in place.
| Project | Industry | Odoo | Key capabilities | Technology |
|---|---|---|---|---|
| Opsio | Cloud managed services | Odoo 18 Enterprise | Cash Flow Forecast Report · Working Capital Report · Timesheet Profitability · Project Profitability | Odoo 18 Enterprise · Python · PostgreSQL · JavaScript · REST APIs |
| Kaypear Engineering | Process safety & engineering consulting | Odoo | Kaypear Base (Tank Design Models) · Kaypear Portal Theme | Odoo · Python · PostgreSQL · JavaScript · QWeb / XML |
| SLANGO | Civil society: national NGO umbrella body | Odoo 19 Community | Registration Portal · Registration Portal Theme | Odoo 19 Community · Python · PostgreSQL |
| iDT Labs | ICT consulting & software: HRIS SaaS | Odoo 9 Community | HRIS SaaS Management · Employee Management · Attendance Management · Leave Management | Odoo 9 Community · Python · PostgreSQL |
Read the projects
A managed-services provider running projects, timesheets, helpdesk and profitability, an engineering portal with staged approvals, and an association that replaced paper approvals entirely.
Cloud managed services
Accounting, HR and payroll, projects and timesheets, subscriptions, helpdesk and CRM on Odoo 18 Enterprise, with custom modules migrated from earlier versions and financial reporting built for a recurring-services business.
Process safety & engineering consulting
A client-facing portal where engineers run API 2000 fire-relief and breathing calculations through wizard forms, with the company’s engineering maths executed in the Odoo backend, a live input-audit tool, folder and batch organisation of tank designs, stage-based approvals, watermarked PDF reports with annexures and QR-code verification, plus sign-up, invitations and support ticketing.
Civil society: national NGO umbrella body
The Sierra Leone Association of NGOs replaced paper registration with a self-service portal: online applications with document upload, an Admin → Finance → Director → Chairman approval chain, payment tracking and verification, role-based access, automated notifications, dashboards and reporting, and Chatter-based audit history, on Odoo 19 Community.
Workflow review
Send us how you sell and deliver work: contract types, how time is captured today, whether you run a helpdesk or field crews, and what clients can see. You get the workflow mapped to Odoo, the decisions that matter, and what we would configure versus build. No obligation.
What clients say
Heliconia's Odoo Enterprise implementation, along with third-party system integration, has optimized our processes. Their expertise has been a game-changer.
Vladimir VukovicCEO, Mevalon ProdukteHeliconia delivered an impeccable Odoo Enterprise implementation with seamless integration. Their expertise has revolutionized our operations.
Kartson KrayChairman, TIMmunity GmbHQuestions
Yes, once cost rates and the analytic structure are set up properly, because the hours and the costs come from the same system as the invoices. Opsio runs timesheet and project profitability reporting on Odoo 18 Enterprise for exactly this reason.
The honest caveat: the reports are only as good as the timesheets, which is why we make time capture work before we build the dashboards.
Helpdesk, Field Service, Planning and Appointments are Enterprise apps, so for a conventional internal setup, yes. Projects and Timesheets are in both editions.
If your service delivery runs through a client-facing portal rather than internal ticket queues, Community plus a custom portal is a real alternative. Slango and Keypear both run request, approval and support flows that way.
Make it quick, make it visible and close the window. We build locking and rounding rules so periods close on schedule, add portal and mobile entry so booking takes seconds, and put the gap in front of managers weekly rather than at month-end.
Those three together are what changed the data quality at Opsio.
Yes, and how far you take it is a design decision. Standard portal access shows projects, tasks, tickets and invoices. Both Keypear and Slango went further: the portal is where clients submit work, track approvals and collect generated documents.
A good portal removes more internal work than any internal feature we could build.
Yes. Subscriptions cover recurring billing on Enterprise, and where the delivery repeats as well as the invoice we build project recurrence and recurring purchase orders, as we did for Opsio.
The design question is whether a retainer creates work each period, bills each period, or both.
Partly, and this is worth being precise about. The Enterprise field-service and POS-style apps handle intermittent connectivity better than the standard web client, but a genuinely offline workflow is usually a mobile application talking to Odoo over an API.
We build those as well, so the answer depends on how often your crews are actually out of coverage.
Through the employee record and the analytic account. Hours booked against a task carry the person’s cost rate into project margin, and the same records feed invoicing and the ledger. That is the whole argument for keeping service delivery in the ERP rather than a standalone tool.
The rest of the chain
Odoo earns its place at the hand-offs between departments, not inside any one of them. These are the families this one exchanges data with every day.
Every operational record eventually becomes a number in the ledger.
The order is where the work and the revenue both start.
What you promise has to exist, move and be costed.
People, hours and cost rates sit behind every delivered job.
Next step
Tell us how you sell and deliver work today, how time gets captured, and what your clients can see. We will map it to Odoo and show you which parts are configuration and which are engineering.