The Stratum Framework: A Four-Layer Architecture for Odoo Implementations
Most Odoo implementations are built as a single monolithic block. Configuration, business logic, custom models, and Odoo core are all mixed together. This works until it does not. The first major version upgrade, a new consultant taking over, or a second environment being provisioned exposes the problem. Everything breaks because nothing was separated.
The Stratum Framework solves this by enforcing a strict four-layer separation from the first commit. Each layer has a defined scope. Nothing crosses layer boundaries. The result is an implementation that can be upgraded, replicated, and handed over without archaeology.
The Four Layers
Client Configuration
Company settings, pricing rules, user permissions, email templates
Changes without code. Can be reset without redeployment.
Implementation Module
Business-specific workflows, custom views, client reports
Isolated per engagement. Upgrades do not touch other layers.
Base Architecture Module
Custom models, security groups, ACLs, API abstraction, automations
Version-controlled. Reusable across engagements. Never modified directly in production.
Odoo Core Platform
Standard Odoo modules: Sales, Purchase, Helpdesk, Inventory etc.
Preserved for upgrade safety. Never modified directly.
L1: Odoo Core Platform
Standard Odoo modules are never modified directly. No monkey-patching, no core hacks. This layer is preserved exactly as Odoo ships it, which means upgrades apply cleanly every time.
L2: Base Architecture Module
Custom models, security groups, access control lists, API abstraction layers, and automation rules live here. Version-controlled, reusable across engagements, never modified directly in production. When you need a second environment, you deploy this module. No database dump required.
L3: Implementation Module
Business-specific workflows, client-facing views, custom reports, and process automation live here. This layer is isolated per engagement. Upgrading L1 or changing L2 does not break L3.
L4: Client Configuration
Company settings, pricing rules, user permissions, email templates, and lookup data. This layer changes without code. A configuration error does not require a developer to fix.
Deployment
Every Stratum engagement is deployed through a Git-controlled pipeline: Development to Staging to Production. A new environment is provisioned by deploying the version-controlled modules. No database dump. No environment drift.
See how the Stratum Framework applies to your project
Start with a Feasibility Assessment. You get a written review, a module recommendation, and an architecture roadmap, all within 2 to 5 working days.