How Odoo eCommerce Works When It Shares One Database With Inventory and Accounting

Most online stores bolt a storefront onto an ERP through connectors that sync every few minutes, and stock lags, prices disagree, and tax totals drift apart. Odoo eCommerce takes a different route, because the storefront, the inventory, and the accounting all run on one database. This guide explains how that shared database design works in practice for an Indian business, and where it still falls short of a dedicated storefront platform.

📋 Key Takeaways

  • Odoo eCommerce reads from the same product, stock, and pricing records as Inventory, Sales, and Accounting, so there is no connector and no sync lag.
  • When a customer orders online, stock is reserved instantly, the sales order is created, and the accounting entry posts on confirmation.
  • GST applies automatically at checkout using the same fiscal positions set for offline sales, and HSN codes carry through to the invoice.
  • For pure storefront polish, a dedicated platform still leads. The Odoo eCommerce advantage is operational, with no integration layer between selling and fulfilling.
  • Choose Odoo eCommerce when integration simplicity matters more than storefront sophistication.

Why a Separate Store and ERP Create Problems

Before looking at how Odoo eCommerce works, it helps to see the setup it replaces. When your storefront and ERP are separate systems joined by a connector, small timing gaps turn into real customer problems. Teams evaluating the best ERP for eCommerce usually hit these four issues first.

What breaks when the store and ERP are joined by a connector

  • Stock sync delay. The store shows five units. The warehouse shipped three to an offline buyer minutes ago. The connector has not synced. An online customer orders four. You oversell.
  • Price mismatch. A promotion updates in the ERP, but the connector pushes prices on a schedule. For that window, the store keeps showing the old price.
  • Tax disagreement. The ERP calculates GST one way and the storefront plugin another. The invoice total does not match what the customer paid at checkout, and disputes follow.
  • Order duplication. A connector error can write the same order twice, so the buyer receives double and returns follow.

How Odoo eCommerce Works on One Shared Database

Odoo eCommerce removes the connector entirely. The storefront is a view onto the same records the rest of the business already uses,, the same idea behind Odoo inventory integration.

The architecture difference in plain terms

  • One product record. The product on the storefront is the same record Inventory, Sales, and Accounting use. Change the price in the product form and the website updates at once.
  • One stock record. The quantity shown to the online buyer is the quantity the warehouse sees. A delivery to an offline customer lowers the number everywhere at the same moment.
  • One customer record. A buyer who shops online and offline is a single record with one order history and one credit term.
  • One tax engine. The fiscal position that sets GST for offline invoices sets it for online orders too. Same calculation, same rates, same HSN codes.

Catalogue, Variants, and Pricing Rules

The catalogue you sell from is the product master the whole company shares. If you also plan to design the pages yourself, the Odoo website builder handles layout without a separate theme engine.

  • Product catalogue. Products marked as published appear on the storefront. Unpublished ones stay in the back office. Publication is a toggle, not a second catalogue to maintain.
  • Variants. Size, colour, material, or any attribute. Each variant carries its own SKU, price, stock level, and barcode, and the storefront builds the selectors.
  • Pricelists. Separate price lists for retail, wholesale, and VIP buyers. The storefront applies the right one based on the logged in customer category, with discounts and date ranges configurable.
  • Images and descriptions. Rich descriptions, several images per product, and zoom. Less theme flexible than a dedicated platform, but solid for standard pages.

Live Stock Straight From Inventory

Because the storefront reads the real stock table, the number a shopper sees is the number the warehouse holds, with no cached copy waiting on a sync window.

  • Live stock levels. When the warehouse confirms a receipt of fifty units, the storefront shows fifty available within seconds. No scheduled job runs in between.
  • Multi warehouse visibility. If configured, the store shows stock per location or a total across warehouses.
  • Out of stock behaviour. When a product hits zero it can be hidden, marked unavailable, or opened for backorder.
  • Reserved stock. Items are soft held at checkout and hard allocated on confirmation, stopping overselling at peak.

Checkout, Payment, and Tax

Checkout is where the shared database pays off most for Indian sellers, because the tax logic is identical to your back office. That consistency is grounded in Odoo accounting for compliance, so what the customer pays is what the invoice shows.

What the checkout flow does

  • Cart review. Product, quantity, unit price, and tax are shown, with shipping added by delivery method and destination.
  • Address collection. Billing and shipping details, plus a GSTIN field for B2B invoicing.
  • Tax calculation. Fiscal positions set CGST and SGST or IGST automatically from the shipping state against the company state, matching offline invoices exactly.
  • Payment gateways. Razorpay, PayU, Cashfree, and CCAvenue for domestic, plus Stripe and PayPal for international. Confirmation updates the order and starts fulfilment.

Order to Delivery Without Retyping Anything

Once a shopper clicks place order, the whole chain fires from that single action. The invoice stage reuses the same Odoo invoicing workflow your finance team already runs for offline sales.

What happens after place order

  • Sales order created. The same sales order object as an offline order, sitting in the Sales module and linked to the customer record.
  • Delivery order generated. A picking list appears in the warehouse queue automatically.
  • Invoice generated. On confirmation, on delivery, or on manual trigger, with GST, HSN, and payment terms applied for you.
  • Accounting entry posted. Revenue is recognised and tax payable recorded. If payment was captured at checkout, the receivable clears at once.

Customer Accounts and Portal

Every shopper account maps to a contact in Odoo, so the portal shows a real, connected view of that customer rather than a separate storefront profile.

  • Registration. Customers create accounts at checkout or on their own, each mapped to an Odoo contact.
  • Order history. Logged in customers see past orders, download invoices, and track delivery from one dashboard.
  • Reorder. Repeat an earlier order in a click, which suits B2B buyers.
  • B2B portal. Wholesale buyers see their own pricelists, payment terms, and credit limits.

Marketing and CRM Connection

Because everything lives in one system, your marketing and sales teams work from the same customer data. Website enquiries flow straight into the Odoo CRM module alongside every online purchase.

  • Abandoned cart recovery. Odoo tracks carts that reach checkout but do not finish, then emails a reminder.
  • Email marketing. Segment buyers by history, category, or order value and send campaigns from the same platform.
  • CRM link. Website forms create leads, and online purchases attach to the customer record, so sales sees online and offline activity together.
  • Promotions. Percentage or fixed discounts, minimum order thresholds, validity dates, and coupon codes.

When to Integrate Shopify or WooCommerce Instead

Odoo eCommerce is not always the right pick. When the storefront itself is the competitive edge, a dedicated platform can earn its integration cost. Weigh the two honestly against your business model.

Use Odoo eCommerce when

  • Your priority is operational, meaning stock accuracy, GST compliance, and order to delivery without an integration layer.
  • The storefront is one channel among several. You also sell offline, through distributors, or by B2B quotation.
  • You want one system for the whole business, and adding a separate store would recreate the sync problems above.
  • Your catalogue is moderate and your storefront design needs are standard.

Integrate Shopify or WooCommerce when

  • The storefront is the business, and marketing, conversion, and design are your edge.
  • You need a deep app ecosystem for reviews, loyalty, subscriptions, and marketplace connectors.
  • Your catalogue is very large with heavy filtering and merchandising needs.
  • You accept the ongoing connector cost of monitoring and updates.

What to Validate Before Migrating a Store

A calm migration is a tested one. Run this checklist before you point your domain at the new store.

Pre migration checklist

  • Product catalogue imported, with all variants, images, descriptions, and pricing verified.
  • Stock levels accurate, matching the current platform and a physical count.
  • Payment gateway tested, with at least one successful transaction through your chosen provider.
  • GST configuration validated for both intra state and inter state orders at checkout.
  • Shipping methods configured, with costs correct by weight, region, or flat rate.
  • Email templates ready, covering order confirmation, shipping notice, and cart recovery.
  • SEO redirects planned, so old URLs point to the new store and rankings hold.
  • Mobile rendering and load capacity tested against expected traffic.
💡Run the new store in parallel for a week or two before switching your domain. Process test orders and verify the full chain from order to delivery to invoice to accounting entry, so issues surface before customers find them.
Odoo eCommerce

Want an Online Store That Shares One Database With Your Inventory and Accounting?

Tatvamasi Labs configures Odoo eCommerce with live stock, GST ready checkout, and order to delivery automation. One system, zero sync problems.

Set Up Your Online Store

Frequently Asked Questions

It runs on the same database, so stock levels on the storefront reflect actual warehouse quantities in real time. There is no connector and no sync delay. A delivery to an offline customer reduces online availability instantly.
Yes. Fiscal positions apply the correct GST rate automatically based on customer location, and HSN codes carry through from product to invoice. The tax setup used for offline sales applies to online orders too.
For a business that needs the store tied to inventory, accounting, and CRM on one database, it removes the sync problems a Shopify plus ERP setup creates. For pure storefront marketing and app depth, Shopify still leads.
Razorpay, PayU, Cashfree, and CCAvenue cover domestic payments, while Stripe and PayPal handle international ones. Payment confirmation updates the sales order and triggers fulfilment automatically.
Yes. The portal can show customer specific pricelists, payment terms, and credit limits, so the same wholesale buyer who orders online can also be invoiced on thirty day terms.
It comfortably handles catalogues into the low thousands of SKUs with variants. Very large catalogues above ten thousand SKUs with heavy merchandising needs may be better served by a dedicated platform.
Yes. An online order creates the same sales order object as an offline one, so fulfilment, invoicing, and accounting follow one workflow no matter where the order started.