BACKGROUND:
Have you implemented the Odoo community in a Saas offering? Do you have experience creating and installing paid apps in Odoo? Are you comfortable with the database, the application server, and the web server configuration in a multitenant environment?
CURRENT PROJECT STATUS:
We have an Odoo community(v17) instance that is running on AWS in a multitenant environment. Each customer is assigned a separate company in the same database. Data isolation is enforced using record rules and access rights. While simple and Ideal for businesses managing multiple brands this option is not strict enough for true SaaS. It is also causing implementation errors. As a result, the project has not been able to go live with the current setup. We want to transition from a shared-database multi-company setup to a true SaaS multi-tenant architecture in Odoo Community 17.
PROJECT SCOPE & DELIVERABLES:
Given remote access to AWS server you will:
1. System Assessment & Planning: Assess current AWS setup (EC2, database, Odoo configurations).
• Analyze existing multi-tenancy setup (record rules, access rights).
• Review Nginx/Apache configurations and database management.
• Inspect Payment Gateway errors (logs, API credentials, response handling).
• Decide on Multi-Tenancy Approach:
• Option 1: dbfilter method for database routing.
• Option 2: Dockerized Multi-Tenancy (one Odoo instance per tenant).
2. Multi-Tenancy Implementation Option 1: DBFilter-Based Multi-Tenancy
• Configure Odoo database manager (dbfilter) for routing users.
• Adjust Nginx/Apache settings to correctly direct subdomains.
• Modify record rules and security settings to enforce tenant data isolation.
• Implement automated database provisioning for new tenants.
• Test login redirections and tenant switching.
3. Multi-Tenancy Implementation Option 2: Dockerized Multi-Tenancy (Alternative Approach)
• Set up Dockerized Odoo & PostgreSQL instances per tenant.
• Configure Docker Compose/Kubernetes for orchestration.
• Automate database creation for new tenants using scripts.
• Test scalability, security, and performance.
4. Payment Gateway Fixes
• Debug & resolve issues in:
• Mpesa Paybill
• Paystack
• PayPal
• Stripe
• Verify API credentials, webhook URLs, and error handling.
• Conduct end-to-end payment testing for all methods in POS and shopping cart.
5. App Deployment & Configuration
• Install & configure the following Odoo community apps:
• Odoo Ticketing App: https://apps.odoo.com/apps/modules/17.0/helpdesk_support_app
• POS Stock Sync Module: ttps://apps.odoo.com/apps/modules/18.0/abichinger_pos_stock
• POS Kitchen Screen: https://apps.odoo.com/apps/modules/18.0/abichinger_kitchen_screen
• Ensure app compatibility with Odoo 17.
6. White Labeling & Branding
• Update UI branding (logo, colors, email templates).
• Customize the customer portal & dashboard.
• Modify Odoo’s front-end & back-end appearance for branding consistency.
7. Automated Subscription & Onboarding
• Implement self-service signups for new customers.
• Auto-provision new Odoo instances (per database or Docker instance).
• Configure automated onboarding emails for new customers.
• Integrate payment processing for subscriptions.
• Test subscription flow and ensure smooth user experience.
8. Go-Live & Testing
• Conduct final system & security tests.
• Perform UAT (User Acceptance Testing) with sample tenants.
• Optimize performance & fix any remaining issues.
• Deploy production and monitor post-launch.
Delivery Time: To be agreed with the project team. We would like to go live as soon as possible without compromising quality.