Which Odoo Versions Work With the SeaText Integration?
SeaText supports Odoo versions 14, 15, 16, and 17. The integration uses a JavaScript embed code placed in Odoo's Website module via the Embed Code block, so any version that includes the Website module...
Quick Answer
SeaText works with Odoo 14, 15, 16, and 17. The integration does not rely on a deep backend module; it loads a JavaScript snippet through Odoo's standard "Embed Code" block inside the Website editor. If your Odoo instance has the Website module and the Dynamic Content section with an Embed Code block, you can install SeaText.
How the Integration Works
SeaText connects to Odoo by pasting a JavaScript snippet into an Embed Code block. You log in to Odoo, open the Website module, edit the target page, drag the Embed Code block from the Dynamic Content section into the page, paste the snippet, and save. The script stays inert until you activate it in your SeaText dashboard.
Why Version Compatibility Matters
Odoo releases a new major version each year. Older versions eventually lose security patches and official support. If you run an unsupported version, you risk compatibility issues with the Website module or the Embed Code block. Staying on a supported version (14–17 at the time of writing) ensures the integration surface SeaText uses remains stable.
Decision Criteria for Choosing an Odoo Version
| Criterion | What to Check | Why It Matters |
|---|---|---|
| Official Odoo support status | Check Odoo's supported versions page | Supported versions receive security fixes; unsupported versions may break the Website module |
| Website module availability | Confirm the Website app is installed | SeaText embeds only work inside the Website editor |
| Dynamic Content > Embed Code block | Open the editor and verify the block exists | This is the only supported insertion point for the SeaText snippet |
| JavaScript execution policy | Ensure no CSP or firewall blocks external scripts | The SeaText snippet loads from SeaText's CDN |
| Multi-domain setup | Each domain needs its own SeaText account | SeaText ties one account to one primary URL |
Step-by-Step Compatibility Check
- Open your Odoo database and go to Apps. Search for "Website" and confirm it is installed.
- Navigate to Website > Pages, pick any page, and click Edit.
- In the Blocks panel, scroll to Dynamic Content. Look for the Embed Code block.
- If the block is present, drag it onto the page. A popup appears — this confirms the insertion point works.
- Log in to SeaText, copy the integration snippet, paste it into the popup, and click Save.
- In the block's Visibility settings, enable "Hide on Desktop" if you only want SeaText active on mobile or vice versa.
- Return to SeaText and activate the integration. The status should change to Active within a few minutes.
How to Check Your Odoo Version
- Log in to your Odoo database as an administrator.
- Open the main menu and click on the "Settings" app.
- Scroll down to the bottom of the Settings page. The Odoo version number is displayed in the footer (e.g., "Odoo 16.0").
- Alternatively, open any backend page and look at the browser tab title; it often includes the version.
- If you use Odoo Online, the version is shown in your Odoo.com account under "My Databases".
- For Odoo.sh, check the branch name in the Odoo.sh dashboard; it includes the major version.
- For on-premise installations, run the command
odoo-bin --versionin the terminal where Odoo is installed.
Odoo Online vs Odoo.sh vs On-Premise
All three hosting models support the Website module and the Embed Code block. The SeaText JavaScript snippet works the same way because it runs in the browser. However, there are practical differences:
- Odoo Online (SaaS): You always run the latest minor release of a major version. Updates are automatic and may change the editor UI slightly. Test after each bi‑monthly update.
- Odoo.sh: You control the branch (e.g., 16.0, 17.0) and can test in staging before promoting to production. Custom modules or themes may add Content Security Policy headers that block external scripts.
- On‑Premise: You manage the server, database, and web server configuration. Ensure your reverse proxy or firewall allows outbound connections to SeaText's CDN. Also verify that the Website module is installed and not disabled by a custom configuration.
Common Scenarios and Trade-offs
Scenario A: You are on Odoo 14 or 15 (nearing end of standard support)
SeaText will work today. Plan an upgrade to 16 or 17 before the version's support window closes to avoid future breakage.
Scenario B: You are on Odoo 16 or 17 (current standard support)
This is the sweet spot. Full Odoo support, Website module stability, and SeaText compatibility are all aligned.
Scenario C: You are on Odoo 18 or newer
SeaText has not publicly confirmed support for 18+. The JavaScript embed method will likely still work, but you should contact SeaText support before relying on it in production.
Scenario D: You run Odoo.sh or On-Premise with custom code
Custom themes or CSP headers can block the SeaText script. Test in a staging environment first.
Troubleshooting: Embed Code Block Not Showing
- Confirm the Website module is installed and upgraded to the latest version for your major release.
- Clear the browser cache and reload the Website editor.
- Check that you are editing a page type that supports blocks (standard pages, not backend views).
- If you use a custom theme, switch temporarily to a standard Odoo theme (e.g., "Default") to see if the block appears.
- Inspect the browser console for JavaScript errors that might prevent the Blocks panel from loading.
- Verify that your user has "Website Manager" or "Administrator" access rights.
- If the block is still missing, contact your Odoo developer or SeaText support with a screenshot of the Blocks panel.
Limitations and When This Advice Does Not Apply
- The version list (14–17) reflects SeaText's published compatibility at the time of writing. Always verify on the SeaText Odoo integration page for updates.
- Odoo Online (SaaS) receives bi-monthly minor releases. These are generally backward-compatible, but a minor release could change the Website editor UI.
- If you use a heavily customized theme that removes the Dynamic Content section, the Embed Code block will not appear.
- Development domains (localhost, dynamic tunnels) are restricted by SeaText for security. Use a real domain for testing.
Key Terms
- Embed Code block
- An Odoo Website block type that accepts raw HTML/JavaScript. Found under Dynamic Content in the Blocks panel.
- SeaText snippet
- A short JavaScript tag unique to your SeaText account. It loads the SeaText AI agents onto your site.
- Dynamic Content
- A section of the Odoo Website Blocks panel that holds advanced blocks like Embed Code, HTML, and custom widgets.
- Primary URL
- The single domain linked to a SeaText account. Multi-domain setups require separate accounts.
Key Facts
| Fact | Detail |
|---|---|
| Supported Odoo versions | 14, 15, 16, 17 |
| Integration method | JavaScript embed via Embed Code block |
| Required Odoo module | Website |
| Insertion point | Dynamic Content > Embed Code |
| Multi-domain rule | One SeaText account per primary URL |
| Development domain restriction | localhost and dynamic tunnels blocked |
FAQ
Does SeaText work on Odoo 13 or older?
Not officially. Those versions are past end-of-life and lack security updates. The Embed Code block may exist, but SeaText does not test or support them.
Can I use one SeaText account for my staging and production Odoo sites?
No. Each domain needs its own SeaText account. Create a separate account for staging.
What if my Odoo theme hides the Dynamic Content section?
Switch to a standard Odoo theme temporarily to install the snippet, then switch back. Or ask your developer to add the Embed Code block to your custom theme.
Will a minor Odoo SaaS update break the integration?
Unlikely. Minor updates rarely remove the Embed Code block. If the block disappears, contact SeaText support.
Do I need administrator rights in Odoo to install SeaText?
You need Website Manager or Administrator access to edit pages and add blocks.
How long until SeaText shows as Active after I paste the snippet?
Usually 5–15 minutes. The dashboard polls for the script on your page.
Can I place the snippet in the header or footer instead of a page block?
The documented method uses the Embed Code block on a page. Header/footer injection is not covered by the official guide and may not work reliably.
What should I do if the SeaText script is blocked by a Content Security Policy?
Add the SeaText CDN domain to your CSP "script-src" directive. Consult your developer or hosting provider for the exact syntax.
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.