Odoo POS · intro · 8 min read
What Is Odoo POS?
A practical definition of Odoo Point of Sale for retail operations: sessions, orders, payments, inventory updates, multi-store design, and how POS connects to ecommerce and warehouse execution.
Last reviewed 2026-07-30 · Estimated effort: 1–2 weeks typical discovery
Table of contents
Odoo Point of Sale is the cashier-facing application that turns store visits into confirmed orders, payments, and stock moves — sharing products, prices, customers, and inventory with Sales, Inventory, and ecommerce channels in one database.
Core capabilities span POS configuration per store, session open and close, payment methods, receipt and fiscal handoff concepts, returns, pricelists, and real-time or batched inventory updates depending on architecture.
This pillar covers multi-store design, inventory integration, barcode, payments and fiscal considerations, hardware concepts, offline resilience, loyalty, KPIs, mistakes, and project planning. Retail, Logistics, Shopify, Performance, and Migration guides cover specialized depth.
Store managers often ask whether Odoo POS can replace a dedicated register system when they have only seen back-office demos. Without a shared definition of in-store selling in Odoo, projects stall on whether POS is a lightweight add-on or a strategic retail channel.
This article sets boundaries for the Odoo POS pillar. Later articles cover multi-store deployment, inventory sync, barcode, payments, hardware, offline mode, loyalty, reporting, mistakes, and project planning.
Odoo POS is the application that cashiers use to scan or select products, apply discounts, collect payment, and print or email receipts — while creating sales orders or POS orders that update stock and accounting according to your configuration.
Each store typically has a POS configuration tied to a warehouse or stock location, payment methods, pricelists, and optional fiscal or hardware middleware. Sessions track who opened the register, what was sold, and how cash was reconciled.
- ▸Sessions: open, sell, close, cash control
- ▸Orders: lines, taxes, discounts, returns
- ▸Payments: cash, card, split, customer account
- ▸Stock: real-time deduction or picking from store location
It is not an isolated cash register that ignores inventory. POS can run without deep warehouse integration, but you lose accurate ATP for ecommerce and replenishment when store sales do not update the same quants.
It is also not a fiscal compliance engine by default. Payment and receipt rules vary by jurisdiction. Odoo provides hooks and community or custom bridges — project teams must scope fiscal constraints early, not treat compliance as a post-go-live patch.
Retail and Shopify channels share catalog and pricing with POS. When a product sells in store, availability for online shoppers should reflect the same stock record where architecture allows.
Logistics handles replenishment to store backrooms and barcode receiving. Performance matters when many registers hit the server during peak hours. Migration preserves POS configs through version upgrades.
Single-site operators may run one POS config with a simple stock location. Multi-store chains need per-location configs, centralized product masters, and clear rules for transfers and pricing.
Franchise or multi-company models add company boundaries, reporting consolidation, and sometimes separate fiscal identities per entity. The architecture and multi-store articles walk decision paths before enabling configs at every site.
- ✓Name Odoo as the system of record for in-store sales before connecting ecommerce channels.
- ✓Map each physical store to a warehouse or stock location before go-live.
- ✓Pilot one store with full session open-to-close before rolling out the chain.
- ✓Cross-link the Retail guide when omnichannel pricing and promotions matter.
- ✓Cross-link Logistics when store replenishment depends on DC pick accuracy.
- ✓Define who owns POS config versus who runs daily cash reconciliation.
- !Treating POS as a demo add-on while inventory truth lives in spreadsheets.
- !Enabling every payment method before fiscal and acquirer contracts are signed.
- !Assuming one POS config fits all stores with different layouts or tax rules.
- !Skipping session close procedures until month-end exposes cash variances.
- !Copying demo products and pricelists that do not match live catalog structure.
- !Running POS in Odoo while ecommerce inventory is updated manually elsewhere.
Odoo POS is in-store selling wired to the same catalog, customers, and stock as the rest of Odoo — configurable from a single register to a multi-store chain.
Next, validate store-to-location mapping and master one session lifecycle before scaling configs across sites.
Open session
Cashier starts till.
Sell
Scan / select products.
Pay
Tender and receipt.
Close session
Reconcile cash and sales.
Client / Channel
Users & devices
Odoo Application
Business logic
PostgreSQL
System of record
Workers / Cron
Async work
- clientapp(HTTP)
- appdb(ORM)
- appjobs(queue)
Frequently asked questions
Can Odoo POS replace our current register system?
Odoo POS handles scanning, payments, receipts, and inventory updates for many retail models. Evaluate fiscal requirements, hardware middleware, offline needs, and peak traffic before assuming a dedicated POS vendor is required.
How is POS different from Odoo Sales?
Sales targets order entry and quotations. POS targets fast cashier workflows, session control, register hardware, and store-optimized UX with immediate payment capture.
Does Odoo support multiple stores?
Yes. Each store can have its own POS config, stock location, and payment setup while sharing product and customer masters. The multi-store deployment article covers rollout patterns.
Should we connect inventory on day one?
Define locations and products first. Sequence inventory integration by whichever channel creates the most oversell risk, but keep one stock model from the start.
Related articles
Planning a Multi-Store POS Deployment
Roll out Odoo POS across multiple stores: phased versus big-bang, config templates, location mapping, training, hypercare, and governance for pricing and promotions at scale.
View →Integrating POS with Inventory
Connect Odoo POS to inventory truth: stock locations, real-time deduction, picking policies, replenishment, omnichannel ATP, and avoiding oversell across stores and ecommerce.
View →Choosing the Right POS Architecture
Choose Odoo POS architecture: hosting model, store-to-warehouse mapping, single versus multi-company, online-first versus offline tolerance, ecommerce allocation, and scaling registers.
View →Planning an Odoo POS Project
Structure an Odoo POS implementation: stakeholders, phases, requirements, pilot criteria, UAT, training, hypercare, cutover, and success metrics for retail go-live.
View →Scoping Odoo POS for your store estate?
Share your store count, fiscal constraints, and channel mix — we will outline a POS footprint that fits.
