Odoo POS: The In-Store Point of Sale Module

What Is Odoo POS?

Odoo Point of Sale is the in-store and in-restaurant terminal module built into the Odoo ERP suite. It is designed for managing shops and restaurants, runs in a standard web browser on virtually any device, and is engineered to keep working through temporary network outages.

Unlike a standalone POS terminal that syncs to a separate retail system, Odoo POS sits inside the same Odoo database as your inventory, accounting, sales, and eCommerce apps. Every transaction posts directly to the linked warehouse and ledger, so there is no retail middleware to maintain and no nightly batch reconciliation between systems.

Beyond traditional counter sales, the module also supports a self-ordering feature that lets customers place orders and pay at a dedicated kiosk or from their own mobile device, all powered by the same backend.

• →Web-browser-based — runs on any device with a browser, no dedicated OS required
• →Two operation modes — Shop (retail) and Restaurant (tables, floors, tips)
• →Built-in offline mode — cashiers keep selling during outages; data auto-syncs
• →Native inventory sync — every sale decrements stock in the linked warehouse
• →One Odoo database can host many POS configurations, each tied to its own shop

Shop Mode vs. Restaurant Mode

Odoo POS is configured per-terminal in Configuration -> Settings, where you choose between two primary operation modes depending on the kind of business you run.

Shop mode is built for retail: it adds quotations, sales-order import, a Ship Later flow for out-of-stock items, and barcode plus discount-tag support for fast scanning at the counter.

Restaurant mode is built for hospitality. The POS interface exposes three main buttons for navigating between Tables, the register, and orders, and it supports floor plans, table management, course-by-course ordering, tips, and online delivery integrations.

Each physical location typically gets its own POS configuration set to the mode that matches its workflow — a retail store uses Shop mode, a cafe or full-service restaurant uses Restaurant mode, and a hybrid venue can run both from the same Odoo database.

Offline Mode and Automatic Sync

A defining feature of Odoo POS is its built-in offline mode. If the network drops mid-service, the cashier frontend keeps processing transactions normally — orders and payments are stored locally in the browser rather than blocked.

Once connectivity returns, the locally stored data is automatically synced back to the Odoo server. Cashiers do not need to re-key anything, and back-office inventory, accounting, and reporting update as if the outage never happened.

This matters most in hospitality and busy retail environments where a stalled terminal means a lost sale or a long queue. Because offline storage is browser-local and the switchover is automatic, the feature requires no extra licensing or separate offline database server.

• →Cashiers continue ringing sales during a network outage
• →Orders are stored in the browser and auto-sync on reconnect
• →No re-keying or duplicate entries after recovery
• →Works for both Shop and Restaurant modes

Payments, Receipts, and Hardware

Odoo POS supports a wide range of payment methods out of the box. Beyond cash, it integrates directly with card payment terminals including Adyen, Ingenico, Stripe, Mollie, Mercado Pago, Razorpay, Pine Labs, SIX, Tyro, Viva.com, Worldline, DPO Pay, and QFPay.

For non-card tender, the module supports QR code payments, customer account payments, and connected cash machines from vendors like Cashdro, Cashmatic, and Glory.

Receipts and invoices generate from the register and print via receipt printers. Peripherals — receipt printers, customer displays, scales, and electronic shelf labels — are commonly connected through the Odoo IoT box, which bridges the browser-based POS to physical hardware on the counter.

• →Integrated card terminals: Adyen, Ingenico, Stripe, Mollie, Mercado Pago, Razorpay, Pine Labs, SIX, Tyro, Viva.com, Worldline, DPO Pay, QFPay
• →QR code payments and customer account payments
• →Cash machines: Cashdro, Cashmatic, Glory
• →Receipt printers, customer displays, scales, and electronic shelf labels via the Odoo IoT box

Inventory Awareness and Multi-Shop Deployments

Because Odoo POS is part of the ERP, inventory is native, not bolted on. Every sale decrements stock in the warehouse linked to that POS, so on-hand quantities stay accurate in real time across the whole company.

The Ship Later feature is a good example of that integration: when a customer buys an item that is not in the store, the POS creates a delivery order directly from the warehouse to the shipping address, all without leaving the register.

Multi-shop deployments follow the same pattern. Each POS is configured separately and linked to a specific shop and warehouse, so a chain of stores can ring sales against the right stock location. Inter-site replenishment uses Odoo's standard routes and reordering rules, and multi-company setups assign each company its own POS and warehouse.

• →Each POS ties to a specific warehouse — stock depletes against the correct location
• →Ship Later creates a delivery order from the warehouse to the customer
• →One POS configuration per physical store, each linked to its own shop
• →Multi-company setups give each company its own POS and warehouse
• →Inter-store replenishment via Odoo routes and reordering rules

The Dynamics 365 Equivalent: Store Commerce

The Microsoft Dynamics 365 analogue is the Store Commerce app — the next-generation POS for Dynamics 365 Commerce. It unifies the older Modern POS (MPOS) and Cloud POS (CPOS, now Store Commerce for web) into a single application available on Windows, Android, and iOS.

Microsoft deprecated MPOS and the Retail hybrid apps in October 2023 and recommends Store Commerce or Store Commerce for web for all new deployments, with existing MPOS customers directed to migrate. Store Commerce supports cash-and-carry, shift management, clienteling, endless-aisle ordering, order fulfillment, inventory, and reporting for first-line store workers.

Two deployment topologies are available. In-app keeps all components local, supports a local hardware station, and enables offline mode via a dedicated SQL Server offline database installed with the --installoffline parameter. Hybrid renders Cloud POS from the Commerce Scale Unit and does not support offline. Payments run through the Adyen Payment Gateway with PayPal for order fulfillment, plus a Payments SDK for ISV connectors; Dynamics 365, SVS, and Givex gift cards and digital wallets are supported.

When Each Fits an SME

For an SME choosing between the two, the decision usually comes down to scale, integration depth, and total cost of ownership rather than raw feature counts.

Odoo POS fits SME retailers, cafes, restaurants, and multi-location hospitality operators who want a single Odoo instance covering POS, inventory, accounting, and eCommerce without separate retail middleware. Licensing is comparatively low and the module is included with the Odoo Enterprise apps, so a growing chain can add terminals without re-architecting.

Dynamics 365 Commerce Store Commerce fits mid-to-enterprise retail and hospitality chains that need deep omni-channel capability, enterprise compliance, ISV payment connectors, and centralized control from a commerce headquarters. It is the natural path when an Odoo POS prospect outgrows SME retail and needs enterprise-scale channel management.

Because Flectic implements both platforms, we are genuinely platform-neutral on which one is right for a given operation — the right answer depends on your transaction volume, number of locations, compliance requirements, and existing Microsoft or Odoo investment.

1. 01
   Start with your locations and volume

   One to a handful of stores with simple inventory needs tends to land on Odoo POS; dozens of locations with complex fulfillment lean toward Store Commerce.

2. 02
   Evaluate integration depth

   If you want POS, inventory, accounting, and eCommerce in one database at low licensing cost, Odoo POS is usually the cleaner fit. If you need central headquarters control and ISV payment connectors, Store Commerce pulls ahead.

3. 03
   Factor in compliance and payments

   Enterprise compliance, gift-card ecosystems (SVS, Givex), and regulated payment flows are well-trodden paths in Dynamics 365; Odoo POS covers mainstream terminals and cash machines for typical SME retail.

4. 04
   Plan the implementation

   Either way, the project is an ERP implementation, not a POS install. Scope the warehouse structure, chart of accounts, and integration points before configuring a single terminal.