An e-commerce site connected to an ERP through a connector has a basic flaw: when the synchronisation goes wrong, it does so silently. Prices that diverge, stock that is not updated, orders that never arrive. Odoo Website and eCommerce start from a different idea: the site is a view of the system, not a copy of it.
Five principles
1. The site catalogue is the warehouse catalogue. The products are the same. A duplicated catalogue (one in Odoo, one on the site) sees prices diverge regularly. Price lists, stock and variants follow the same single-source rule.
2. Payment providers are tested before launch. A configuration error blocks all online revenue: it must be checked with a real purchase all the way to collection. Providers left in test mode on the public site do not allow any real order; no provider configured means handling every order by hand.
3. SEO is configuration, not just content. Odoo offers the tools, but they must be switched on page by page: title, description, keywords, readable URLs. Without configuration, search engines struggle to index the site. Connecting Google Search Console gives visibility on indexing errors and search performance.
4. B2B and B2C are different configuration modes. In B2B, prices often must not be visible to anonymous visitors (otherwise you expose the price list to competitors) and access is for registered customers. In B2C the checkout can allow guests, but a guest-only checkout creates no account and no purchase history.
5. Live chat is a conversion and support tool. It integrates with the CRM (lead creation) and with Helpdesk (ticket creation). A widget installed with no operators or chatbot configured shows up and nobody answers, which is worse than not having it.
Warning signs
- A site on an external CMS (WordPress, Shopify) connected to Odoo by a connector: silent synchronisation errors.
- A duplicated catalogue with diverging prices.
- A payment provider in test mode on the public site, or no provider at all.
- SEO not configured on any page; Search Console not connected.
- B2B prices visible to anonymous visitors.
- Guest-only checkout.
- Live chat with no operators or chatbot.
- Several websites in Odoo but products not assigned to the right site: wrong products are shown.
- Automatic invoicing not enabled: e-commerce orders confirmed but never invoiced.
Discovery questions
Where does the site live today? Who updates prices and stock? How do you collect payment? Do you sell to businesses, to consumers or to both? How do you answer visitors? The path: a site with a connector to an external CMS is assessed against the standard, because Website often replaces it; highly customised storefront needs or external marketplaces require integration or development, to be assessed after the standard.
An example
A company sells spare parts with a site on an external CMS. When a price changes in Odoo, the site is updated the following night, if the synchronisation succeeds; one evening it does not, and for two days parts are sold at the old price. With a single catalogue, the price the customer sees is the price the warehouse sees, at the same moment.
The skill at the end carries these rules in a form an agent can use to configure or check the site.
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-websiteKnowledge to configure or assess Odoo Enterprise Website, eCommerce and Live Chat: shared catalogue, payment providers, SEO per page, B2B and B2C, automatic invoicing. Use it when the user asks to set up or check the website and online sales in Odoo, with or without interviews.