Customer Lifecycle

2026-04-28

Governed customer management on top of Odoo res.partner, layered across three progressive governance generations:

• V1 — Foundation. Service Accounts (SAs), memberships, role-based access.
• V2 — Stamps. x_sa_id / x_actor_id compatibility stamps on governed models.
• V3 — Association models. Dedicated assignment tables such as ov.sa_customer_assignment with full lifecycle history.

Start here

• Customer Lifecycle — End-to-End — the canonical walkthrough from bootstrap to archival, covering every stage, the data model, the API surface, and visibility policies.
• Sales Workflow — End-to-End — all 10 commercial workflows from product catalogue through invoicing, stock, subscriptions, helpdesk, and reporting. Includes governance gaps and the full API surface.
• Operations Setup Guide — step-by-step Odoo configuration checklist for operations and admin teams. Covers warehouses, products, accounting, SA governance, and helpdesk setup required before the sales workflow can run.
• Agent · Start Here — a task-oriented entry point for agents and automations working in this repo.

Key concepts

Concept	Where it lives
Three-level model (existence / SA-governed / actor-assigned)	Overview
SA hierarchy (seed → branch)	SA Hierarchy
Customer creation (plain vs SA-governed)	Stage 1 — Creation
Visibility policies (sa_wide, assigned_plus_unassigned, assigned_only)	Visibility Policy Reference
V3-canonical reassignment (expire old, open new)	Stage 4 — Reassignment
Membership revocation side-effects	Stage 5 — Revocation
One-active-assignment-per-SA constraint	Constraint
Legacy backfill	Backfill
Roadmap for Phase 2+	Roadmap
Product taxonomy (Odoo native + Wangvision PU)	Workflow 1 — Product Catalogue
Warehouse & stock management	Workflow 0 — Warehouse
Invoice governance gap	Workflow 3 — Invoicing
Subscription lifecycle	Workflow 6 — Subscriptions
Complete API surface (all 10 workflows)	API Surface Summary
Odoo modules reference	Reference — Odoo Modules
Operations pre-flight checklist	Operations Setup — Verification Checklist
Common config mistakes	Operations Setup — Troubleshooting

Contributing

1. Edit the Markdown sources under docs/.
2. Record progressive architecture decisions in docs/adr/.
3. Keep stable lookup material (terminology, external refs) under docs/reference/.
4. Preview locally with mkdocs serve.

---

Small notes: progressive architecture decisions are tracked in Architecture Decision Records; stable lookup material lives under Reference.