How to Verify If Your Odoo Version Supports SeaText: A Readiness Checklist
SeaText integrates with Odoo through an Embed Code module in the Website editor, but the public documentation does not list specific supported Odoo versions. To verify compatibility, check the SeaText Odoo integration page or...
SeaText connects to Odoo by placing a JavaScript snippet into an Embed Code block inside the Website module. The published integration guide walks through the installation steps but does not state which Odoo versions are officially supported. The reliable way to confirm compatibility is to consult the SeaText Odoo integration page or the Odoo App Store listing for a supported version range (for example, Odoo 15, 16, 17) and match that against the version running on your instance.
Understanding the SeaText-Odoo Integration Method
SeaText does not install as a native Odoo module from the Odoo App Store. Instead, you add the SeaText JavaScript code through the standard Website builder. The process uses the Embed Code block under Dynamic Content, then hides the block on desktop so the script runs without displaying a visible element. Because the integration relies only on the Website module and the ability to paste JavaScript, it works on any Odoo version that includes the Website module with the Embed Code block and visibility controls.
This approach is deliberately lightweight. It avoids database schema changes, custom Python modules, or server-side dependencies. That means the integration is less likely to break during Odoo upgrades, but it also means the compatibility surface is defined by the Website builder features rather than by a formal module version.
The key technical requirement is that your Odoo version must include the Website module with the Embed Code block. This block has been present since Odoo 14 in most standard builds. However, some older versions or heavily customized instances may not expose it. The visibility controls, specifically the "Hide on Desktop" option, are also standard in recent versions.
How to Check Your Current Odoo Version
- Log in to your Odoo database as an administrator.
- Open the Settings app (gear icon).
- Scroll to the bottom of the Settings page and click "About" or look for the version line at the very bottom of the left-hand menu.
- Note the major version number (for example, 15.0, 16.0, 17.0).
If you cannot see the version in Settings, you can also open the developer tools (activate developer mode, then use the bug icon > View Metadata) or check the database list on your Odoo.sh or on-premise server.
For Odoo Online (SaaS), the version is usually displayed in the top-right corner of the backend. For Odoo.sh, you can see the version in the project settings. For on-premise installations, the version is often visible in the database list or in the server logs.
Knowing your exact version matters because the Embed Code block and visibility controls have evolved. For example, older versions may require a different block name or may not support the "Hide on Desktop" option. If you are on Odoo 14 or earlier, you should test the block availability before assuming compatibility.
Where to Find SeaText's Official Version Requirements
The SeaText Odoo integration page (seatext.com/odoo-integration) is the primary source for compatibility information. If the page does not list a version range, check the Odoo App Store for a SeaText listing — some third-party connectors are published there with explicit version badges. When neither source publishes a range, assume the integration works on any currently supported Odoo version that includes the Website module with Embed Code and visibility options, but verify with SeaText support before deploying to production.
The SeaText integration page provides step-by-step instructions but does not explicitly state a supported version range. This is a common pattern for lightweight JavaScript integrations. The absence of a version list does not mean the integration is broken; it means the compatibility is defined by the Website builder features rather than by a formal module version.
If you are using Odoo Enterprise, the Website module is included in the standard subscription. If you are using Odoo Community, the Website module is also available, but some advanced features may differ. The Embed Code block is available in both editions, so the integration should work in either case.
Compatibility Readiness Checklist
| Check | How to Verify | Pass Criteria |
|---|---|---|
| Odoo major version | Settings > About | Version is within the range published by SeaText (e.g., 15, 16, 17) |
| Website module installed | Apps > search "Website" > Installed | Website module shows "Installed" |
| Embed Code block available | Website > Edit page > Blocks > Dynamic Content | "Embed Code" appears in the block list |
| Visibility controls present | Edit Embed Code block > Visibility section | "Hide on Desktop" option exists |
| JavaScript execution allowed | Security settings / Content Security Policy | No CSP rule blocks inline scripts from seatext.com |
| Valid domain for SeaText account | SeaText dashboard > Domains | Your Odoo website domain matches a registered SeaText domain (localhost not allowed) |
This checklist is a practical heuristic. It covers the most common failure points. If you pass all six checks, the integration is very likely to work. If you fail any check, you have a specific issue to resolve before proceeding.
Key Facts from SeaText Documentation
| Fact | Detail | Source |
|---|---|---|
| Integration method | Embed Code block in Website module, paste SeaText JavaScript snippet | S1 |
| Block location | Dynamic Content section of Blocks panel | S1 |
| Visibility setting | Select "Hide on Desktop" in Visibility section after pasting code | S1 |
| Domain restriction | Each SeaText account links to one primary URL; localhost and dynamic dev domains are restricted | S1 |
| Multi-site usage | Separate SeaText account required for each website/domain | S1 |
| Account prerequisite | SeaText AI account must exist before installing the script | S1 |
These facts come directly from the SeaText Odoo integration guide. They define the operational constraints. The most important one is the domain restriction: you cannot use localhost or dynamic development domains. This is a security measure to prevent abuse and to ensure that traffic is correctly attributed to your account.
The multi-site requirement is also critical. If you run multiple websites from different Odoo databases, you need a separate SeaText account for each domain. The script is not shared across databases. This is a common point of confusion for users with multi-tenant setups.
Common Compatibility Issues and Workarounds
Missing Embed Code Block
Older Odoo versions (pre-14) or customized Website modules may not include the Embed Code block under Dynamic Content. Workaround: use a custom HTML block or ask your developer to inject the script via a QWeb template override.
If you are on Odoo 13 or earlier, the Embed Code block may not exist. In that case, you can use a custom HTML block, but you will need to manually add the script tag. This is more fragile and may not support the "Hide on Desktop" option. A QWeb template override is a more robust solution, but it requires developer involvement.
Content Security Policy Blocks Script
If your Odoo instance or reverse proxy sets a strict CSP, the SeaText script may be blocked. Add https://seatext.com and the SeaText CDN domain to the script-src directive.
CSP is a common issue in enterprise environments. If you see a console error about "Content Security Policy" or "Refused to execute inline script", you need to update your CSP configuration. This is a server-side change, not an Odoo setting.
Localhost or Staging Domains
SeaText restricts localhost and dynamic development domains. For staging, use a real domain (e.g., staging.yourdomain.com) and register it in your SeaText account.
This restriction is intentional. SeaText needs to associate traffic with your account reliably. Dynamic domains like *.ngrok.io or *.herokuapp.com may not work because the domain changes frequently. Use a stable subdomain for staging.
Multi-Database Odoo Instances
Each Odoo database that serves a distinct website needs its own SeaText account and script. The script is not shared across databases.
If you have a single Odoo instance with multiple databases, you must create a separate SeaText account for each database. This is a common requirement for agencies managing multiple clients.
Limitations of Current Documentation
- No explicit supported Odoo version list is published on the SeaText integration page.
- No Odoo App Store listing for SeaText was found in the source pack; the integration is documented as a manual JavaScript embed.
- No guidance on Odoo Enterprise vs. Community differences for the Website module.
- No information on Odoo.sh or Odoo Online specific constraints.
Because of these gaps, treat the checklist above as a practical heuristic. Confirm with SeaText support if you run an older LTS version (14 or earlier) or a heavily customized Odoo build.
The documentation is focused on the installation steps, not on compatibility. This is typical for a lightweight integration. However, it means you need to do some verification yourself. The checklist above is designed to fill that gap.
If you are on a version that is not explicitly supported, you have two options: upgrade Odoo to a supported version, or contact SeaText support for a custom integration review. The latter is safer if you cannot upgrade immediately.
Frequently Asked Questions
Does SeaText work on Odoo Community Edition?
Yes, if the Community Edition includes the Website module with the Embed Code block and visibility controls. The integration does not require Enterprise-only features.
Can I install SeaText on Odoo 14 or 13?
The source pack does not confirm support for versions older than 15. Check the Embed Code block availability in your version; if present, the script will likely run, but SeaText has not published a guarantee.
Do I need a separate SeaText account for each Odoo database?
Yes. Each SeaText account is linked to a single primary URL. If you serve multiple websites from different databases, create one account per domain.
Will SeaText work behind a VPN or on a private network?
SeaText requires a valid, publicly resolvable domain. Private IPs, localhost, and dynamic development domains are restricted for security reasons.
What happens if my Odoo version is not supported?
The script may still execute, but SeaText cannot guarantee functionality or provide support. Upgrade Odoo or contact SeaText for a custom integration review.
Where do I get the SeaText JavaScript snippet?
Log in to your SeaText dashboard; the code appears in the integration section. Copy it and paste into the Embed Code block as described in the integration guide.
Can I use SeaText with Odoo's multi-website feature?
Yes, but each website domain needs its own SeaText account and script. Configure the Embed Code block on each website separately.
How do I test if the script is running?
After saving the Embed Code block, visit your website and open the browser developer tools. Look for network requests to seatext.com. If you see them, the script is loading.
What if the script loads but SeaText does not appear?
Check that your domain is registered in the SeaText dashboard. Also verify that you have an active SeaText account. The script will not function without a valid account.
Does SeaText work with Odoo's website builder in edit mode?
Yes, the Embed Code block is available in the editor. However, the script may not execute in edit mode. Test on a live page to confirm functionality.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.