ABS Integration Functional Area¶
This functional area covers the integration between OVES's Odoo system and the ABS (Asset-Based Services) microservices architecture, using n8n as the integration layer.
Overview¶
The ABS integration enables OVES to manage people, products, services, assets, billing, and payments across multiple systems:
- Odoo: System of record for people & money
- ABS/Thing/Client microservices: Systems of record for services, assets, and distributor ownership
- n8n: Integration glue between systems
Key Documents¶
OVES ABS–Odoo Integration Handbook¶
A comprehensive technical implementation guide covering:
- Scope & First Principles: Business summary and source-of-truth boundaries
- Customer Management: People and partner handling across channels
- Multi-Company Setup: OVES operating entities and currency management
- Franchise/Distributor Management: Internal and external distributor handling
- Asset Management: FLEETs and ITEMs (Thing Service)
- Service Plans & Subscriptions: ABS service bundles and Odoo subscriptions
- Billing & Payments: Invoice generation and payment processing
- Inventory Integration: Stock management and consignment handling
- Integration Patterns: n8n workflows and data synchronization
- Deployment Matrix: Capability comparison across Odoo editions
- SOPs & Checklists: Operational procedures and field references
CRM–ABS Integration Strategy¶
A strategic planning and deployment guide covering:
- Strategic Design Principles: Clear role definitions and interface implications
- Information Flow: Odoo → ABS integration patterns
- Trigger Methods: Deployment compatibility matrix for different Odoo editions
- Phased Integration Plan: Step-by-step deployment approach (Cloud → .sh → On-Prem)
- Developer Instructions: Forward-compatibility and upgrade considerations
- Deployment Decision Matrix: Odoo.sh vs On-Prem comparison
Integration Architecture¶
System Context Overview¶
The following diagram shows the high-level integration between Odoo and the external microservices:

Figure 1: Odoo ⇄ ABS/Thing/Client Integration System Context
Core Data Model¶
The following diagram shows the Odoo core data model structure for ABS integration:

Figure 2: Odoo Core Data Model for ABS Integration
Source-of-Truth Boundaries¶
| Domain | System of Record | Odoo Storage | Write Rules |
|---|---|---|---|
| People & Companies | Odoo | Full identity; ref holds external IDs |
Odoo owns create/update/merge |
| Distributor ↦ Fleet ownership | Client MS | Distributor as res.partner; Fleet as account.analytic.account |
Client pushes creates/updates |
| Fleet ↦ Item assignment | Thing MS | Optional mirrors: stock.production.lot, stock.location |
Thing pushes item events |
| Commercial documents | Odoo | Full ledger & statuses | ABS/Thing/Client consume facts |
Key Integration Points¶
- Customer Management: Portal users, contact deduplication, multi-channel handling
- Multi-Company: Currency, tax logic, website/POS scoping
- Asset Tracking: Fleet ownership, item serialization, station topology
- Subscription Management: Service plans, billing cycles, entitlement enforcement
- Payment Processing: Token management, auto-charging, reconciliation
Migration Considerations¶
Phase Integration¶
This functional area spans multiple migration phases:
- Phase 2: Company structure setup (multi-company configuration)
- Phase 4: Contacts and partners (distributor hierarchy)
- Phase 6: Sales and pricing (subscription setup)
- Phase 7: Additional modules (inventory integration)
Team Responsibilities¶
- IT Team: n8n workflow setup, API integration, data synchronization
- Finance Team: Multi-company setup, currency configuration, billing integration
- Sales Team: Subscription management, customer portal setup
- Manufacturing Team: Asset tracking, inventory integration
Related Functional Areas¶
- Sales - Subscription and customer management
- Finance - Multi-company and billing setup
- Inventory - Asset tracking and stock management
- Products - Service product definitions
Quick Reference¶
Key Odoo Models¶
res.partner- Customers and distributorsres.company- OVES operating entitiesaccount.analytic.account- Fleet representationsale.subscription- Service plan subscriptionsstock.production.lot- Item serial trackingstock.location- Station topology
Integration Events¶
people.changed- Customer updatesfleet.upsert- Fleet ownership changesitem.create/move- Asset placement eventssubscription.invoice- Billing events
For detailed implementation guidance, refer to the Integration Handbook.