+91 98414 81435Free diagnosis
OdooBots
Loading
Module · Website

Odoo Website

The argument for Odoo Website is not that it builds the prettiest site. It is that the shop reads live stock, the form creates a real lead, and the customer portal shows real invoices — with no integration in between.

The argument against it is search. If organic traffic is how your business is found, Odoo Website is workable rather than strong, and we would rather say so than have you discover it six months after launch.

Arun KumarOdoo Functional Consultant, 8+ years| Reviewed by Karthik Raj| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
Book a free Odoo diagnosis +91 98414 81435
0Odoo projects delivered
0Consultants & developers
Live stockThe shop reads the real figure
ChennaiAmbattur, Tamil Nadu
Odoo Website — a website builder connected to products, stock and CRM in Odoo
630
630+ projectsdelivered on Odoo

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo Website?

Odoo Website builds pages and an online shop that read directly from the same database as your stock, prices and customers. Pages are assembled from blocks without code, products and live availability come from inventory, orders become sales orders with no connector, contact forms create CRM leads with their source, a customer portal shows real orders and invoices, and several sites and languages can run from one database.

On search, be realistic. Odoo covers the basics — titles, descriptions, sitemap, redirects — but it is behind a dedicated stack on structured data, page speed control and content tooling. If ranking is the main job of the site, that trade-off is worth deciding deliberately.

Building block
A drag-and-drop section. Fast to assemble, and markup you do not fully control.
Live availability
Stock shown on the shop coming from the same figure the warehouse maintains.
Portal user
A customer with limited access to their own orders, invoices and tickets.
Multi-website
Several sites from one database, with their own domain, language and pricing.
Capabilities

What Odoo Website does

Six parts make up the website applications, and every one of them reads from the same database as the back office.

Page building

Drag-and-drop blocks, themes, a mobile-responsive layout and editing in place, so marketing can change a page without raising a ticket.

BlocksThemesIn-place edit

eCommerce

Products, variants and prices straight from the catalogue, live availability from inventory, checkout, payment providers and delivery options.

Live stockVariantsCheckout

Lead capture

Forms creating CRM leads with the page, campaign and referrer attached, routed by assignment rule rather than landing in a shared inbox.

Forms to CRMSourceRouting

Customer portal

Customers signing in to see their own quotations, orders, invoices, delivery status and support tickets without anyone sending a PDF.

OrdersInvoicesTickets

Content and engagement

Blog, live chat with operators, forum and eLearning, all tied to the same contact records as the rest of the system.

BlogLive chateLearning

Multi-site and language

Several websites with their own domains, languages, pricelists and product selections from one database and one back office.

DomainsLanguagesPricelists
Connected

How Odoo Website works with the rest of Odoo

A visitor sees a product with the quantity the warehouse actually has, orders it, and that order appears as a sales order ready to pick — no connector, no sync delay, no overselling because two systems disagree. A visitor who does not buy fills in a form that becomes a lead with its campaign attached, assigned to a salesperson by rule.

That is the honest case for this application: not design, but the absence of an integration layer and everything that usually goes wrong inside one.

  • Shop availability reading the same stock figure as the warehouse
  • Online orders arriving as sales orders with nothing to synchronise
  • Forms creating leads with page, campaign and referrer recorded
  • Customer portal showing real orders and invoices, not copies
  • Several sites and languages served from one back office
Odoo Website connected to the other Odoo applications in one database
One database — how website shares records with the rest of Odoo instead of exporting to it.
Expertise · how we work

What we settle in week one of an Odoo website implementation

These are the configuration decisions that are cheap to make now and structural to change once transactions exist. We walk through each one before a single record is migrated.

  1. Whether Odoo should host the site at all

    If organic search is the main channel, a dedicated stack with an Odoo integration may serve you better. This is decided first, not after launch.

  2. What stock figure the shop shows

    Forecast available rather than on hand, with an optional buffer, which is what prevents the site selling what is already reserved.

  3. URL structure and redirects

    If you are replacing a site, every existing URL needs a destination. Skipping this is the fastest way to lose rankings you already had.

  4. Form to lead mapping

    Which fields become which lead fields, how duplicates are matched and who each form is routed to.

  5. Portal scope

    Exactly what a logged-in customer can see. A permission decision rather than a display one.

  6. Multi-website rules

    Which products, prices and languages belong to which site, agreed before the second site is created.

  7. Who edits, and what they may break

    Edit rights on pages, because in-place editing is a strength until someone changes a checkout page on a Friday.

Community or Enterprise

What Odoo Website includes, and what needs Enterprise

Odoo moves features between Community and Enterprise from one version to the next, so the list below is what holds today and is confirmed against your own version during the diagnosis rather than taken as permanent.

Community includes the website builder, blog, forms and eCommerce with live stock and checkout. A working shop can be built on it.

Enterprise additions here are mostly about marketing and service rather than the site itself, so the question is whether you will genuinely use them.

  • Marketing Automation — multi-step campaigns from site behaviour. Enterprise.
  • Helpdesk — support tickets raised from the site with SLA. Enterprise.
  • Studio — custom fields and screens without code. Enterprise.
  • Subscriptions — recurring products sold online. Enterprise.
  • Live chat and Blog — available in Community, which surprises people.
  • Community is enough for a brochure site, a lead-capture site or a straightforward shop.
Odoo Website reporting view used to compare Community and Enterprise features
Editions — the features that decide whether Enterprise is worth its per-user charge.
Trust · honest advice

Where Odoo Website needs work

We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a bolt-on, or tell you another tool is the better answer.

Search engine optimisation

Titles, descriptions, sitemap and redirects are covered. Structured data, page speed control and content tooling are behind a dedicated stack, and that matters if ranking is the goal.

Markup control

Building blocks generate their own HTML. You do not control it the way you would in a hand-built front end, which constrains technical SEO work.

Design ceiling

Themes and blocks reach a point where further change becomes development. A heavily designed brand site is usually built elsewhere.

Page speed

Performance is acceptable rather than exceptional, and tuning options are narrower than on a dedicated front end.

Content workflows

Editorial approval, scheduling and versioning are thin compared with a real content management system.

Headless use

Running a separate front end against Odoo as a back end is a legitimate architecture and it is a development project, not a setting.

Our services

Our Odoo website implementation process

Implementing Odoo Website needs more than installing the application. It should reflect how your business already works, and change only what is worth changing.

  1. What you do today

    Understand what the site is for, where your traffic comes from today, whether you sell online, and what exists at your current URLs.

  2. Configuration decisions

    Settle whether Odoo hosts the site, the stock figure shown, the redirect map and the form-to-lead mapping before anything is built.

  3. Configure, not customise

    Set Odoo Website up around how you work rather than installing it at its defaults, and build only what configuration genuinely cannot reach. See Odoo customization.

  4. Data migration

    Masters, open items and opening balances prepared and loaded. Data cleaning is scoped explicitly, because it is usually the largest single task. See Odoo migration.

  5. Testing with your own records

    Your team runs real transactions in a test database before go-live, including the awkward cases that never appear in a demonstration.

  6. Training and go-live

    Role-based training for the people who key transactions daily, then cutover, hypercare and ongoing support and AMC.

Trust · what it costs

What an Odoo Website implementation costs

We do not publish one price, because the same application costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Design ambitionBlocks are fast; a bespoke design becomes front-end development.
  • Catalogue sizeLarge product sets need data preparation and category structure.
  • Migration of an existing siteContent and a complete redirect map are real work and not optional.
  • Number of websitesEach site has its own rules, products and languages.
  • LanguagesTranslation is content effort more than configuration.
  • Payment and delivery optionsEach provider connected is its own configuration and testing.
Why us

Why choose OdooBots to implement Odoo Website

We will tell you when not to use Odoo Website. If organic search is how you are found, a dedicated front end with an Odoo back office is usually the better buy — and that is the advice we gave on our own site.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo Website: frequently asked questions

What is Odoo Website?
A website and eCommerce builder that reads from the same database as the rest of Odoo: pages assembled from drag-and-drop blocks, a shop showing live stock and real prices, forms that create CRM leads, a customer portal with genuine orders and invoices, and multi-site and multi-language support from one back office.
Is Odoo Website good for SEO?
It is workable rather than strong. Titles, descriptions, sitemap and redirects are covered, but structured data, markup control, page speed tuning and content tooling are behind a dedicated stack. If organic search is your main channel, that trade-off deserves a decision before launch rather than after.
Does the shop show real stock?
Yes, from the same inventory the warehouse maintains. What should be published is forecast available rather than on hand, optionally with a small buffer, so the site does not sell units already reserved against other orders.
Do online orders need an integration?
No, and that is the main argument for this application. An order placed on the site is a sales order in the same database, ready to pick, with nothing to synchronise and no connector to fail quietly in the middle of the night.
Can website forms create CRM leads?
Yes, with the page, campaign and referrer attached, matched against existing contacts so repeat enquirers are not duplicated, and routed by assignment rule. That turns a shared inbox into a pipeline you can actually measure.
Can we run several websites from one Odoo?
Yes, each with its own domain, language, pricelist and product selection, served from one back office. Which products and prices belong to which site is agreed before the second site exists, because retrofitting that split is awkward.
What happens to our existing URLs if we move to Odoo Website?
Every one of them needs a destination, mapped before launch. Skipping the redirect map is the fastest way to lose rankings you already had, and it is the part of a site migration most often left until after go-live, when the traffic has already gone.
Can we use a separate front end with Odoo behind it?
Yes, running a custom front end against Odoo through its API is a legitimate architecture and often the right one where design or search performance matters most. It is a development project rather than a configuration choice, and it is scoped as one.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The configuration advice, edition notes and limitations come from our own implementations.

Ready to put Odoo Website to work?

Tell us whether the site is mainly for search traffic or mainly for selling to people who already know you. That answer decides the approach, and the diagnosis call is free.

Book a free Odoo diagnosis Talk to us +91 98414 81435