What I like best about Odoo is its unified My Account customer portal paired with the Microsoft 365 Outlook add-in, which ties our client communications, quote tracking and opportunity logging together in one stack. As the sales ops and CRM platform manager for our Austin B2B consulting firm, our whole sales team lives inside Outlook every day, and this tight Outlook integration cuts roughly three hours from my weekly pipeline auditing and CCPA data validation work. We previously evaluated Prophet-CRM and other inbox-native CRM tools, but Odoo’s built-in self-service dashboard for clients fills a gap we couldn’t get from those standalone email CRM platforms.
The tile-based customer portal is my standout feature. Your Invoices, Your Orders, Addresses and Connection & Security panels let our consulting clients review proposal quotes, download engagement invoices, update their billing details and manage their portal access without flooding our sales reps with follow-up emails. When a mid-sized business client signs on for our strategic advisory work, I enable only the tiles relevant to their contract scope; they can view their active service orders and billing history, but they cannot see our internal margin data or other client pipeline records. This role isolation mirrors the least-privilege access model I enforce for all our CRM tools, and it makes CCPA compliance easier because client PII stays contained within Odoo’s permission boundaries instead of being copied across Outlook folders and shared spreadsheets.
The Outlook plugin is the feature our sales team relies on most heavily. Reps can turn an incoming client email into an opportunity, log call notes or attach the message directly to an existing lead without leaving their inbox. Two-way contact and calendar sync keeps meeting invites, follow-up tasks and contact records aligned between Microsoft 365 and the Odoo CRM pipeline. Last quarter, we rolled this out for our four senior account leads, and they no longer have to duplicate contact entries or manually copy email threads into the CRM chatter. The pipeline dashboard pulls all that logged activity automatically, so when I run forecast reviews, I can verify that every open opportunity has documented email activity tied to it.
One unexpected benefit I’ve discovered is how the portal’s built-in edit history simplifies privacy requests under CCPA. If a consulting client reaches out to view, export or delete their stored personal data, I can pull a timestamped trail of all portal changes: address edits, invoice downloads and security setting updates. Before Odoo, I had to pull records from our Prophet-CRM instance, Outlook contact lists and separate billing spreadsheets, stitching together records manually, which created delays and gaps in our audit trail. The portal also reduces trivial inbound requests; clients can pull their own invoices and confirm service order status, freeing sales reps to focus on discovery calls and deal progression.
Suggestions: My top request is more granular, exportable audit logs for every portal event, including quote views, invoice downloads and address modifications, with webhook support to feed these events into our Power BI sales reporting. I would also like finer-grained portal permission presets built for B2B consulting, so I can separate billing access from service order visibility. Finally, deeper native parity with Prophet-CRM’s Outlook-native activity logging would let reps log custom sales activities directly in their inbox without switching over to the Odoo web interface. Review collected by and hosted on G2.com.
What I dislike most about Odoo is the gap between its Outlook add-in functionality and the inbox-native CRM workflow we rely on, paired with inflexible customer portal permission controls and incomplete granular audit trails. As the sales ops and CRM platform manager for our Austin B2B consulting firm, our sales team lives entirely inside Microsoft 365 Outlook, and we benchmark against Prophet-CRM which natively supports rich, customizable activity logging right in the inbox. Odoo’s plugin only supports basic actions like opportunity creation, and it cannot log custom sales touchpoints such as discovery calls, proposal reviews or follow-up check-ins without switching into the Odoo backend. This forces reps to split their workflow between Outlook and the ERP dashboard, hurting user adoption and introducing gaps in our pipeline records, which creates extra cleanup work every time I run our weekly forecast reviews.
The customer portal permission model is another major pain point. The My Account portal tiles are static; I cannot build granular access sets that separate quote visibility, invoice access and service order access for individual B2B clients. For example, some of our clients only need to view consulting invoices but do not need visibility into active statement-of-work orders, while other long-term accounts need both. Odoo’s portal access is all-or-nothing for the available modules, so I either expose unnecessary client PII and engagement data or withhold required records. This creates risk under CCPA because I cannot scope data exposure cleanly, and I have to manually validate every portal user’s access scope during our quarterly privacy audits. Unlike Prophet-CRM, where I can define field-level permissions for each contact record, Odoo’s portal access controls are broad and lack fine tuning.
The activity and portal audit logging also lacks the detail we need for compliance. Odoo logs high-level events like portal sign-ins, but it does not reliably log discrete actions such as invoice downloads, quote views, address edits or security setting changes. When a consulting client submits a CCPA request to see who accessed their data and when, I cannot pull a machine-readable, timestamped audit report directly from the platform. I have to cross-reference portal timestamps, email records and manual rep notes, piecing together an audit trail that is not airtight for regulators. Last quarter’s privacy review took five extra hours just to reconstruct these missing logs, and that delay put our response timeline at risk.
I also struggle with inconsistent two-way Outlook contact and calendar sync. Private Outlook meeting entries sometimes sync into Odoo CRM unintentionally, and occasional lag means activity logged in the add-in does not populate the pipeline dashboard for hours. Our sales leads rely on real-time pipeline visibility, and delayed sync skews our forecast numbers. There is no native toggle to filter which Outlook calendar events sync over, so I have to rely on third-party community modules that are not officially supported, which adds maintenance overhead.
Suggestions: First, expand the Outlook add-in to support fully customizable sales activity logging, matching the inbox-native experience we get from Prophet-CRM. Second, introduce modular, tile-level portal permissions so I can toggle invoices, orders and address access independently for each customer contact. Third, add detailed, exportable audit logs for every portal interaction with webhook feeds into our Power BI reporting stack. Finally, add native calendar sync filters so we can exclude private Outlook events and prevent unintended PII import into the CRM. Review collected by and hosted on G2.com.
