Odoo eCommerce: Your Online Store, Built Inside Your ERP

What Odoo eCommerce Actually Is

Odoo eCommerce is the open-source e-commerce module that lives inside the broader Odoo Website app. When you install it, your Odoo instance gains a customer-facing online store: you configure products, customize design with a drag-and-drop builder, manage ordering and checkout, set delivery methods, handle orders end-to-end, and analyze store performance—all without leaving Odoo.

Crucially, Odoo eCommerce is not a bolted-on storefront. It extends the same Sales, Inventory, and Accounting apps you already run. A product you publish online is the same product record used in your warehouse, your quotes, and your invoices. That single-source design is what separates Odoo eCommerce (often called Odoo Commerce in search) from standalone shopping-cart platforms that only talk to the ERP through connectors.

The underlying Website builder is a no-code, drag-and-drop tool with live WYSIWYG editing, an AI-assisted site configurator, responsive-by-default layouts, and multi-website / multi-language support. Free themes ship out of the box, and you can switch themes anytime without losing content. In Odoo 19, AI-assisted fields also help generate and translate product and page copy inside the same editor.

Go-Live Setup Path: Website → Products → Payments → Delivery

A practical ecommerce-in-Odoo rollout follows one sequence. First install Website and eCommerce (and Inventory if you ship goods). Confirm company address, fiscal localization, and multi-website if you need separate B2B and B2C domains. Publish a minimal shop page with theme colors and fonts so product URLs and SEO settings have a home before you import the full catalog.

Second, model products the warehouse and finance teams will trust: product templates and variants with SKUs/barcodes, eCommerce categories, taxes, pricelists, and inventory defaults under Website → Configuration → Settings (stock display, out-of-stock behavior, warehouse used for web routes). Optional products and accessories belong on the product form so upsells reuse the same Sales rules as quotes.

Third, configure Payment Providers under Website → Configuration → Payment Providers (shared with portal invoices). Publish only tested live providers—Stripe, PayPal, Adyen, Mollie, Authorize.Net, Razorpay, regional gateways, bank transfer, or Cash on Delivery as markets require—and map journals so captures hit Accounting cleanly.

Fourth, set delivery methods: fixed or rule-based rates, Click & Collect with pickup warehouses, and carrier APIs (DHL, FedEx, UPS, USPS, Sendcloud, Shiprocket, and others documented by Odoo) for live rates and labels. Run end-to-end test orders for guest and signed-in paths, tax-included vs tax-excluded display, multi-warehouse availability, and refund flows before marketing traffic hits the site.

How Orders Flow Through Inventory and Accounting

The practical value of ecommerce in Odoo is the order pipeline. When a shopper adds items to the cart, Odoo creates or updates a Quotation—literally a draft sale order in the Sales app. Checkout steps (address/delivery, review, payment) stay on that same record. On confirmation, the sale order drives Inventory (delivery orders, stock moves, multi-warehouse routes) and Accounting (customer invoice, payment journal entry, tax lines) without re-keying SKUs or prices.

Inventory synchronizes with confirmed eCommerce orders. Website availability can reflect real-time stock; when a sale posts, Odoo creates a delivery order and updates quantities across warehouses. Routes such as dropshipping or cross-docking reuse the same inventory rules you use for offline sales, so web demand does not live in a second stock truth. Multi-warehouse and multi-location setups stay centralized: you fulfill from the right warehouse instead of reconciling nightly CSV exports from a pure storefront.

Accounting records payments and invoices created by online sales. Confirmed orders generate customer invoices from the sales order; taxes follow fiscal positions and product tax configuration; card and wallet captures from payment providers land in the correct journals with currency and fee tracking. Month-end does not depend on a fragile Shopify → connector → QuickBooks chain. If you already sell on marketplaces or a third-party storefront, partner or API connectors can still push those orders into the same Sales → Inventory → Accounting path so Odoo remains the operational core.

That architecture is why practitioners on X and partner blogs frame Odoo as “one connected business platform” for retailers who already struggle with inventory, POS, CRM, and accounting in separate tools—while pure marketing-led brands often still prefer a specialist storefront for launch speed.

Omnichannel: eCommerce, POS, and Click & Collect

The unified inventory/POS/eCommerce story is Odoo’s strongest pitch for retailers who already run stores and a website. Website and Point of Sale sell the same product variants from the same Inventory ledger. A unit reserved by a confirmed online order is not still “available” for the next POS ticket, and loyalty points, coupons, gift cards, and eWallets configured under Sales apply on both channels without a third-party sync app.

Click & Collect (Pick up in store) bridges the two: customers buy on the website and choose a pickup warehouse configured as a delivery method with the in-store pickup provider. Warehouse teams fulfill from real locations; POS can complete in-store handoff when you run both apps on the same database. Odoo Experience sessions and partner retail guides highlight this path for ship-from-store and multi-location availability—exactly where disconnected storefronts oversell.

Practitioners and partners on X and retail blogs repeat the same operational lesson: separate POS, spreadsheet stock, and marketplace listings create waste and cancellations; one ERP ledger cuts overselling and reconciliation time. If your growth is limited by clipboards and dual stock counts—not by storefront themes—native Odoo eCommerce plus POS is usually a cleaner architecture than stacking more Shopify apps.

Designing the Storefront: Themes and Building Blocks

Odoo eCommerce design starts with the Website editor. The Theme tab controls global styling: a primary color palette with light and dark variants, fonts (Google Fonts or custom uploads), page layout, and button styles (Fill, Outline, or Flat). These choices apply across every page of your store.

Page content is assembled from Building Blocks, the drag-and-drop snippets Odoo ships. Structure blocks (Intro, Columns, Content, Images, Catalog) act as containers; you drop Inner Content blocks (text, images, buttons, videos, embed code) inside them. Each block has its own Style tab for fine-grained tuning.

eCommerce-specific design targets three surfaces: the overall store, the catalog/shop page, and the individual product page. Blocks can be scoped to apply across all pages or only to specific products, which is useful for landing pages and seasonal campaigns. Design trade-off to plan for: Odoo’s builder is strong for ERP-native stores, but brand-heavy DTC teams sometimes still prefer Shopify’s theme ecosystem and agency playbooks—then connect Odoo for stock and finance instead of replacing the storefront day one.

Catalog, Products, and Variants

In Odoo, a product is a template. Variants are the combinations generated from attributes, for example Color x Size. Each variant carries its own inventory, barcode or SKU, and price. A Variants smart button on the product lists every generated combination so you can manage stock at the variant level.

eCommerce Categories and Variants are configured under the Website app. Attribute Display Types include Pills, Color (circles or patterns), Radio, Select, Image, and Multi-checkbox. Variant Creation can be set to Instantly, Dynamically, or Never, depending on whether you want Odoo to pre-generate every combination or create variants on demand.

The shop/catalog page itself supports filters: a price-range slider, tags, and attribute filters (auto-shown when variants exist; up to four expanded, more than four collapse). You can configure columns, items per page, manual re-ordering, and per-product ribbons and badges to highlight bestsellers, new arrivals, or sale items.

The product page supports carousel or grid image layouts, Regular or Full-width layout, and an Attributes/Specification section (None, Bottom, or In accordion). Purchase-style toggles, Buy Now, wishlist, compare, reviews from logged-in users, and stock/out-of-stock messages all live here, alongside top and bottom building blocks for cross-sells and trust signals.

Checkout, Payments, Shipping, and Tax Setup

Adding a product to the cart creates or updates a Quotation (draft sale order). The cart is session-based for guests or tied to a customer account for logged-in shoppers. Checkout proceeds through sequential steps: Address/Delivery, Review, and Payment—so shipping method, fiscal address, and payment capture stay on one document.

Payment providers are configured under Website > Configuration > Payment Providers (also reachable from Accounting or Sales). Odoo shares one provider model across eCommerce, the customer portal, and online invoices. Documented providers include Stripe, PayPal, Adyen, Mollie, Razorpay, Authorize.Net, Worldline, Amazon Payment Services, AsiaPay, Buckaroo, Flutterwave, Mercado Pago, Nuvei, Paymob, PayU, Redsys, Toss Payments, Xendit, and others, plus bank transfer and Cash on Delivery for markets where cards are not universal. Publish only providers you have tested; keep test-mode providers unpublished so they never appear at checkout.

Delivery methods cover fixed/rule-based shipping, Click & Collect (Pick up in store) with pickup warehouses configured as a delivery method, and third-party carriers. Odoo documents carrier integrations including DHL, FedEx, UPS, USPS, bpost, EasyPost, Sendcloud, Shiprocket, Starshipit, and Envia.com for live rates, labels, and multi-package shipments. Carrier API calls initiated from Odoo are part of the standard product model (not “External API” licensing).

Taxes should be set before go-live, not patched after the first invoice. Configure company tax options, activate localization taxes, assign default taxes on products, and use fiscal positions to map rates by customer country or type (for example export 0% VAT). B2B tax-excluded versus B2C tax-included display is a website-level setting; fiscal positions and EU intra-community distance-selling features handle cross-border mapping. Wrong fiscal positions create the tax inconsistencies that multi-tool stacks often hit when storefront, ERP, and accounting each compute rates differently.

B2B vs B2C Capabilities

B2B versus B2C is set per website under Website > Configuration > Settings. The eCommerce Display Product Prices toggle controls whether prices are tax excluded (typical B2B) or tax included (typical B2C). A dedicated B2B shop can hide prices entirely, show a Contact us prompt instead, require sign-in, and expose B2B fields such as company and VAT number in the delivery step.

You can run B2B and B2C as separate websites on the same Odoo database, or tune one site carefully when audiences share a catalog. Either way, cart lines still become sales orders with the same pricelists, discounts, and inventory rules used by your sales team offline. After checkout, customers reach orders and invoices through the customer portal under Your Orders and Your Invoices—portal and public shoppers do not consume paid internal-user seats under Odoo’s published user model.

For wholesalers and manufacturers, the B2B path is usually the differentiator versus a pure Shopify theme: pricelists by customer, tax-excluded quotes that convert online, sign-in gates, and ERP-grade stock reservation. For consumer DTC, B2C tax-included pricing, guest checkout, abandoned-cart email, and Merchant Center feeds matter more. Many SMEs run both: a public B2C site and a signed-in B2B site on multi-website.

Sales Tools: Loyalty, Abandoned Carts, and Marketplaces

Odoo's loyalty programs, coupons, and promotions are shared across eCommerce, Sales, and Point of Sale. Once Discounts, Loyalty & Gift Card is enabled, you create rules under Sales > Products > Discount & Loyalty and they apply everywhere you sell. Gift cards and eWallets can be purchased and redeemed as a payment method in both eCommerce and PoS, which keeps online and in-store incentives consistent.

Abandoned carts in Odoo are simply draft Quotations. Under Website > eCommerce > Orders, remove the Confirmed filter and apply the Abandoned filter to surface them. A Follow up abandoned carts feature can be enabled in eCommerce settings with a configurable delay, so Odoo can automatically email shoppers who left without paying. Marketing Automation and Email/SMS apps can layer longer sequences on the same customer records.

For retailers combining online and physical retail, Click & Collect is enabled under Website > Configuration > Settings > eCommerce, with pickup warehouses configured as a delivery method using the Pick up in store provider. Wishlist is enabled by default on product pages and the catalog, and product reviews allow logged-in portal users to submit star ratings and comments.

Marketplace connectors keep social and marketplace demand on the same stock ledger. Odoo’s Amazon Connector synchronizes confirmed Amazon orders (FBA and FBM) into Odoo; built-in product push from Odoo to Amazon is limited—plan catalog ownership carefully. Odoo 19 also documents a native TikTok Shop Connector that streamlines social commerce by synchronizing orders, products, and inventory between TikTok Shop and Odoo, reducing manual entry and cancellations that damage shop ratings when listings oversell. A Shopee Connector (available from Odoo 18.0, documented for 19.0) pulls confirmed Shopee orders into Odoo and can push available quantities for FBM-style fulfillment. Partner or API connectors remain common for Shopify-fronted hybrids and other channels—the design goal is always the same: one Sales → Inventory → Accounting path.

Recurring revenue can sell through the same shop: Odoo Subscriptions supports subscription products in the eCommerce storefront so customers start recurring plans at checkout. Confirmed subscription sales use the Subscriptions app for renewals and automatic payments; note that delivery orders are not generated for pure service or subscription product lines the way they are for storable goods—plan fulfillment rules accordingly when you mix physical kits with recurring services.

SEO and Store Performance

Odoo generates /sitemap.xml automatically. It is cached, updated every 12 hours, and auto-chunked into roughly 45,000-URL files for large catalogs so you stay within search-engine limits. The /robots.txt file is editable under Website > Configuration > Settings > SEO, and every page has an Indexed toggle that controls noindex status and sitemap inclusion.

Per-page SEO is edited via Website > Site > Optimize SEO. You get title tag, description, meta keywords, a SERP preview card, and an AI Fill with AI suggestion tool. A single H1 per page and in-text keywords drive relevance, and Odoo implements schema.org microdata (HTML5) so eCommerce products can show price, availability, and rating rich snippets in search results.

URL Redirect Mapping supports 301, 302, 308, and 404 redirects on a per-website basis (including external URLs) and is managed under Website > Configuration > Redirects in developer mode. Renaming a product or page auto-creates a 301 redirect when the Redirect Old URL option is enabled, protecting your SEO equity when you restructure the catalog.

For paid and social channels, the Google Merchant Center integration generates a dynamic /gmc.xml product feed, and the same feed URL can be reused for TikTok, Facebook, and Instagram catalogs. Google Search Console verification is configured under Website > Configuration > Settings > SEO via HTML file upload, HTML meta tag, DNS record, Google Analytics, or Google Tag Manager.

Odoo eCommerce vs Shopify vs Dynamics 365 Commerce

Three common patterns compete in 2026: (1) Odoo eCommerce as the native storefront on the ERP, (2) Shopify (or similar) as the storefront with Odoo as inventory/accounting via connector, and (3) Microsoft Dynamics 365 Commerce for enterprises already on the Dynamics stack. The right answer depends on whether eCommerce is the whole business or one channel inside manufacturing, wholesale, or multi-warehouse retail.

Shopify wins on pure DTC launch speed, theme/app marketplace depth, and “it just works” perception among brand operators. The trade-off is operational: multi-location stock, manufacturing BOMs, B2B tax-excluded pricing, and GL-level accounting usually need extra tools or an ERP connector. Partner content and practitioner discussion both describe a common hybrid—Shopify sells online; Odoo manages backend inventory, warehouses, invoices, and reports—with explicit multi-location sync to stop overselling.

Microsoft Dynamics 365 Commerce is the enterprise omnichannel counterpart. It uses a hub-and-spoke architecture: Commerce headquarters acts as the back-office hub, with Commerce Scale Units hosting a headless commerce engine for in-store POS, online, and call-center channels. Online storefronts use Commerce site builder (React-based) or headless frontends on Retail Server APIs. Per Microsoft's public pricing page, D365 Commerce is listed at $210 per user per month (paid yearly) for core Commerce capabilities, plus an e-Commerce add-on listed at $4,000 per user per month (paid yearly); attach discounts and tiered commercial pricing vary by segment.

Odoo pricing is per paid internal user; external users (website visitors placing eCommerce orders, portal customers, and suppliers) are free and unlimited on the published model. Standard and Custom plans include all apps for a single fee—including eCommerce, Website, Sales, Inventory, Accounting, and POS—with regional rates that change over time, so always confirm on odoo.com/pricing for your country. Choose Odoo eCommerce when one product/order model across warehouse and finance matters more than the largest theme store. Choose Shopify + Odoo when marketing velocity and agency ecosystem matter first and you will invest in a solid connector. Choose D365 Commerce when you already run Dynamics 365 Finance & Operations at enterprise omnichannel scale.

Total cost of ownership matters as catalogs and channels grow. A mid-market Shopify stack often adds a separate ERP connector, loyalty app, tax engine, shipping tool, B2B app, and email platform on top of the storefront plan—partner analyses in 2025–2026 frequently cite multi-thousand-dollar monthly SaaS stacks before custom work. Odoo Standard/Custom plans include eCommerce with Inventory, Accounting, CRM, loyalty, and multi-carrier shipping under one per-internal-user model (external shoppers and portal users remain free on Odoo’s published pricing). Confirm current regional rates on odoo.com/pricing; do not treat third-party listicles as the source of truth for your country.

Implementing Odoo eCommerce with Flectic

Flectic is an AI-driven ERP and CRM implementation partner for SMEs on both Microsoft Dynamics 365 and Odoo. We are platform-neutral: we implement both, and we recommend the one that fits your business, not the one we happen to sell. For online-store projects, that means we help you weigh native Odoo eCommerce against Dynamics 365 Commerce—and against a Shopify-fronted Odoo backend—on catalog complexity, B2B/B2C mix, channel coverage, warehouse design, and licensing budget.

Our AI-Accelerated Delivery approach is designed to deliver up to 3x faster than a traditional implementation, without skipping the configuration that makes an eCommerce site trustworthy: correctly scoped variants, working payment providers, B2B tax display, abandoned-cart recovery, carrier methods, fiscal positions, and SEO fundamentals like sitemaps, schema, and redirects. We serve Canada first, then the UK, then the USA.

Whether you are launching your first online store or replacing a storefront that has outgrown its platform, the first step is an ERP Readiness Call. We will map your product catalog, channels, checkout requirements, and inventory model to the right module set on the right platform—and call out when a hybrid storefront-plus-ERP pattern is the safer path than a full replatform.

Frequently asked questions