SAMTIA B2B E-Commerce Platform — Technical Documentation¶
Audience: Technical Manager · Solution Architect · newly onboarding developer Goal: understand the whole platform — architecture, applications, integrations, business workflows, deployment and major components — without reading source code.
Generated from: live source scan of addons_lp_ecommerce/ (Odoo 19 modules) and
next_ecommerce/ (Next.js 15 portals).
Scope rule applied: only features reachable from a visible menu, screen or active API route are documented. Dead code, commented-out models and unregistered views are excluded — see 016 — Exclusions.
Index¶
| # | Document | Covers |
|---|---|---|
| 001 | Project Overview | What the platform is, actors, portals, glossary |
| 002 | System Architecture | C4 context & container views, request lifecycle |
| 003 | Repositories and Structure | The two repos, folder responsibilities |
| 004 | Odoo Modules | Module catalog, dependency graph, responsibilities |
| 005 | Domain Model | Custom models, extensions, ERD, inheritance |
| 005.1 | Model & Field Reference | Every model and every field, in full, with descriptions |
| 006 | API and Controller Architecture | Envelope, controller inheritance, endpoint catalog |
| 007 | Authentication and Authorization | Session login, password reset, guards, Access Management |
| 008 | Sales Order Lifecycle | Portal state machine, sequence diagrams |
| 009 | Feature Catalog | Every shipped feature with a technical description |
| 010 | Next.js Application Architecture | Layers, routing, state, HTTP client |
| 011 | Navigation and User Journeys | ERP Back Office menus, portal menus, journeys |
| 012 | Real-Time and Messaging | WebSocket, chat, presence, notifications, chatter |
| 013 | Master Data and Configuration | Startup config, SMTP, system parameters, crons, env vars |
| 014 | Deployment Architecture | Odoo.sh branches, portal Docker pipeline, environments |
| 015 | External Integrations and Dependencies | Third-party and platform dependencies |
| 016 | Architecture Decisions and Customization Points | Why it is built this way; where to extend |
| 017 | Odoo.sh Environments Guide | Branch topology, environment URLs, release step sequence |
| 018 | Release and Build Process | Step-by-step commands to cut and ship a release, both repos |
| 019 | Developer Quick Start | Where code lives and step-by-step recipes to add a model, API, portal screen or real-time feature |
Reading Paths¶
New Technical Manager (1 hour) → 001 → 002 → 004 → 008 → 011 → 014
New Backend Developer → 002 → 004 → 005 → 006 → 007 → 013 → 016
New Frontend Developer → 002 → 010 → 011 → 006 → 007 → 012 → 014
Cutting your first release → 014 → 017 → 018
Building your first feature → 019 → then 006 / 010 / 012 as the recipe points
Terminology (used consistently throughout)¶
| Term | Meaning |
|---|---|
| Customer Portal | Customer-facing Next.js app served at/ |
| AMP / Account Management Portal | Internal Next.js app served at/admin/* |
| ERP Back Office | The Odoo web client itself (ERP UI) |
| Customer | A B2B customercompany (res.partner, is_company = True) |
| Portal user | An end user belonging to a Customer company |
| Account Manager | Internal employee owning one or more Customers |
| Portal state | The B2B order status shown in both portals, distinct from Odoo's nativestate |
| AMM | Access Management Module — role/permission engine (access_management) |