Project E-OSHA moves all licensing and renewals into Odoo Enterprise (hosted on Odoo.sh). I already have every order landing in sale.order through an external API; now Phase 1 (our MVP) must turn those orders into fully-automated annual subscriptions for both Standard and Professional plans. Core requirements • Generate and renew licences from the moment an order is confirmed. • Each bundle creates one customer login tied to a single app. • Send reminder emails as the licence approaches its expiry date, then automatically block access if no renewal is detected. • Expose a REST API (token-based) so a separate customer portal can read licence status and remaining days. • Push real-time events to two existing PHP applications through secure webhooks. • Absolutely no core overrides, no hard-coded pricing, and no direct SQL writes—everything must respect Odoo upgrade paths and enterprise guidelines. Scope limits Phase 1 covers only the functional backbone: licensing logic, email jobs, sync services, and a minimal admin dashboard. Fancy UI elements, analytics, or self-service extras sit firmly in later phases; the detailed technical specification attached makes these boundaries explicit. Deployment & rollout Work will be developed on its own Odoo.sh branch, tested in staging, and released behind a feature flag for a staggered production rollout. I expect concise deployment notes and a simple smoke-test script so my team can validate the flow end-to-end. Deliverables 1. Clean, documented Odoo module(s) ready for Odoo.sh CI 2. OpenAPI or Postman collection for the public REST endpoints 3. Sample webhook payloads and signature scheme 4. YAML pipeline updates and rollback plan 5. Quick-start manual for admins When handing over, the module must run production-ready without manual database tweaks. If a feature is unclear, ask early—this is a business-critical system and we only have one chance for a safe launch.