odoomspcase-studyimplementation

How an Australian MSP Replaced Spreadsheets with Field Service Management Software in Odoo

Stratum ERP||3 min read

TL;DR: We implemented Odoo 18 SaaS for an Australian MSP, replacing spreadsheets and disconnected tools with a nine-stage gated ticket lifecycle, role-based access across five teams, automated SLA enforcement, a customer portal with service verification, and a B2B REST API. The entire system was structured using the Stratum Framework's four-layer architecture.

What Was the Problem?

Techsource, an Australian managed service provider, was running service delivery across spreadsheets, email, and a disconnected accounting system. Tickets had no formal lifecycle. SLAs were tracked manually. Clients had no visibility into service status. Billing was disconnected from delivery.

What Did the Client Need?

A single system handling the entire service delivery workflow: from ticket creation to invoice. Specifically: ticket lifecycle governance (not a three-stage pipeline), role-based access matching their organisational structure, SLA enforcement with automated escalation, a customer portal for client visibility and approvals, billing connected to service delivery, and API access for their larger clients to create tickets programmatically.

What Was Built?

Nine-stage gated ticket lifecycle: Request, Triage, Assigned, In Progress, Pending Client, Pending Third Party, Resolved, SVR Pending, and Closed. Each stage has configurable transition rules. A ticket cannot move from Assigned to In Progress without an engineer being assigned. A ticket cannot move to Closed without a completed Service Verification Report approved by the client.

Role-based access across five roles: Client, Operations, Support, Accounts, and Admin. Each role sees different fields, different stages, and different actions.

SLA enforcement using Odoo's native SLA module with multi-layer policies. Each ticket carries both a client-facing SLA and an internal KPI SLA. Pre-breach alerts fire at configurable intervals. Escalation actions trigger automatically on breach.

Customer portal with SVR approval: when a ticket is resolved, the client receives a service report in the portal that they must review and approve before the ticket can be closed and invoiced.

B2B REST API integration enabling Techsource's larger clients to create tickets directly from their own systems. The API handler includes authentication, input validation, and structured error responses.

Australian GST and BAS compliance configured in the Accounting module.

How Was It Structured?

The entire implementation follows the Stratum Framework: a four-layer architecture methodology for Odoo implementations that separates client configuration (L4), implementation logic (L3), base architecture (L2), and Odoo core (L1) into distinct layers for upgrade safety, environment reproducibility, and zero configuration drift.

Layer 1 (Odoo Core) was preserved untouched. No modifications to Helpdesk, Accounting, or CRM base modules.

Layer 2 (Base Architecture) contains the custom data models, security groups, API handler, and automation rules. This module is version-controlled in Git and deployable to a fresh environment without a database dump.

Layer 3 (Implementation Module) contains Techsource-specific logic: the nine-stage lifecycle configuration, SVR workflow, and client-specific billing rules.

Layer 4 (Client Configuration) contains all settings Techsource can change through the UI: SLA thresholds, email templates, user permissions, and pricing rules.

This separation means Odoo updates apply to Layer 1 without affecting the other layers.

What Was the Outcome?

Techsource now runs their entire service delivery operation in a single system. Tickets are governed. SLAs are enforced automatically. Clients have portal visibility. Billing pulls from service delivery data. And the system is structured to survive upgrades and team changes.

Read the full case study with technical detail

If you run an MSP and want to see what a structured implementation would look like for your operations, start with the Feasibility Assessment ($400 to $1,200) or book a free 30-minute call. Book your assessment