+91 98414 81435Free diagnosis
OdooBots
Loading
Module · Point of Sale

Odoo Point of Sale

A point of sale has one requirement that outranks every feature list: it must keep billing when the internet does not. A queue at a counter does not care about an elegant interface.

Odoo POS runs offline and synchronises when the connection returns, and it reduces the same stock the rest of the ERP reads. This page is about the application; selling in a retail business is covered on Odoo ERP for retail.

Arun KumarOdoo Functional Consultant, 8+ years| Reviewed by Karthik Raj| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
Book a free Odoo diagnosis +91 98414 81435
0Odoo projects delivered
0Consultants & developers
OfflineBilling continues without internet
ChennaiAmbattur, Tamil Nadu

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo POS?

Odoo POS bills at the counter, keeps working offline, and reduces the same stock the rest of Odoo reads. Sessions open and close with a cash count, products are found by search or barcode, payments split across cash, card and digital methods, restaurant mode adds tables, courses and kitchen printing, and every sale consumes stock from the outlet it was sold at.

Session closing is the control that makes a POS trustworthy. If nobody counts the drawer and signs the variance each night, the figures are a record of what the till was told rather than what happened.

Session
One shift at one counter, opened and closed with a cash count. The unit of accountability.
Offline mode
Billing continuing without a connection, syncing when it returns. Non-negotiable at a counter.
Kitchen printing
Order tickets sent to the preparation point. Restaurant mode, not standard retail.
Variance
The difference between counted cash and expected cash. Recorded and explained, never absorbed.
Capabilities

What Odoo POS does

Six parts make up the point of sale, and its advantage over a standalone till is everything behind the counter.

Counter billing

Fast product search, barcode scanning, quantity and discount entry, customer attachment where you want it, and receipt or GST invoice printing.

BarcodeDiscountsGST invoice

Offline operation

Billing and payment continuing without a connection and synchronising when it returns, which matters more at a counter than any other feature.

No internetSyncQueue safe

Payments

Cash, card, UPI and other digital methods on one bill, with split payment, change handling and a per-method breakdown at session close.

SplitUPIBreakdown

Restaurant mode

Floor plans and tables, course sequencing, order transfer between tables, bill splitting and kitchen or bar ticket printing.

TablesCoursesKOT

Multi-store

Several outlets and counters under one database, each reducing its own stock, with outlet-wise sales and margin reporting.

OutletsOwn stockPer-outlet P&L

Sessions and closing

A shift opened and closed with a counted drawer, expected versus actual cash, and a variance that is recorded and explained rather than absorbed.

Cash countVarianceSign off
Connected

How Odoo POS works with the rest of Odoo

A sale at the counter reduces stock at that outlet, so the replenishment suggestion for tomorrow is based on what actually sold today. The accounting entry posts with the session. If a central kitchen or warehouse supplies the outlet, the transfer is an internal move rather than a sale, so group stock stays correct.

A standalone till records takings. A POS inside an ERP records takings, stock, margin and replenishment from the same transaction.

  • Each sale reducing stock at the outlet it happened in
  • Replenishment driven by actual consumption rather than an estimate
  • Accounting entries posted per session, with cash variance visible
  • Outlet-wise margin from the same records, not a monthly assembly
  • Central kitchen or warehouse supply handled as an internal transfer
Odoo POS connected to the other Odoo applications in one database
One database — how point of sale shares records with the rest of Odoo instead of exporting to it.
Expertise · how we work

What we settle in week one of an Odoo point of sale implementation

These are the configuration decisions that are cheap to make now and structural to change once transactions exist. We walk through each one before a single record is migrated.

  1. Hardware list

    Printers, scanners, cash drawer, card terminal and the machine running the till, confirmed as compatible before anything is bought.

  2. What happens offline

    How long you can run disconnected, what is unavailable, and who re-syncs. Tested deliberately rather than discovered on a busy evening.

  3. Invoice versus receipt

    When a GST invoice is raised rather than a simple receipt, and how a customer is attached mid-sale without slowing the queue.

  4. Discount authority

    Who can discount at the counter and by how much, enforced in configuration rather than negotiated at the till.

  5. Session closing rules

    Who counts, what variance is acceptable, and who signs it. The control that decides whether the numbers mean anything.

  6. Stock source per outlet

    Which location a counter sells from, and how it is replenished from a warehouse or central kitchen.

  7. Product and barcode data

    Clean barcodes and prices before go-live, because a counter is the worst place to discover a missing product.

Community or Enterprise

What Odoo POS includes, and what needs Enterprise

Odoo moves features between Community and Enterprise from one version to the next, so the list below is what holds today and is confirmed against your own version during the diagnosis rather than taken as permanent.

Community includes the till itself: sessions, offline billing, barcode, payments, discounts, receipts and multi-outlet operation with stock behind it.

Enterprise adds the service and loyalty layers, and the restaurant features are the ones most often worth the charge for a food business.

  • Restaurant features — floor plans, courses and kitchen printing. Enterprise.
  • Loyalty and gift cards — points, rewards and vouchers at the till. Enterprise.
  • IoT box — certain printers, scales and payment terminals. Enterprise plus hardware.
  • Subscriptions — memberships sold at the counter and billed recurring. Enterprise.
  • Studio — extra fields and screens without code. Enterprise.
  • Community is enough for straightforward retail counters with stock and GST invoicing.
Odoo POS reporting view used to compare Community and Enterprise features
Editions — the features that decide whether Enterprise is worth its per-user charge.
Trust · honest advice

Where Odoo POS needs work

We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a bolt-on, or tell you another tool is the better answer.

Very long offline periods

Offline mode covers an outage, not a day. A site with no reliable connection at all needs its architecture discussed first.

Payment terminal integration

Which card terminals integrate directly depends on the provider and region, and it is confirmed before purchase rather than assumed.

Complex promotions

Layered offers, mix-and-match and conditional bundles go beyond standard pricelists and often need development.

Weighing scale integration

Scales usually need the IoT box or a scoped integration, which matters for grocery and food counters.

Franchise reporting

Royalty calculation and franchisee-level reporting across outlets is a reporting build on top of the data.

Queue-busting hardware

Handheld ordering, self-checkout and kiosk flows are separate products connected to Odoo rather than POS features.

Our services

Our Odoo point of sale implementation process

Implementing Odoo POS needs more than installing the application. It should reflect how your business already works, and change only what is worth changing.

  1. What you do today

    Understand how many outlets and counters you run, what hardware exists, how reliable the connection is, and whether restaurant features are needed.

  2. Configuration decisions

    Settle the hardware list, offline expectations, invoice rules, discount authority and session closing process before go-live.

  3. Configure, not customise

    Set Odoo POS up around how you work rather than installing it at its defaults, and build only what configuration genuinely cannot reach. See Odoo customization.

  4. Data migration

    Masters, open items and opening balances prepared and loaded. Data cleaning is scoped explicitly, because it is usually the largest single task. See Odoo migration.

  5. Testing with your own records

    Your team runs real transactions in a test database before go-live, including the awkward cases that never appear in a demonstration.

  6. Training and go-live

    Role-based training for the people who key transactions daily, then cutover, hypercare and ongoing support and AMC.

Trust · what it costs

What an Odoo Point of Sale implementation costs

We do not publish one price, because the same application costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Number of outlets and tillsEach counter is configuration, hardware and training.
  • Restaurant featuresFloor plans and kitchen printing need Enterprise and setup.
  • Hardware compatibilityTerminals and scales may need an IoT box or an integration.
  • Product data qualityBarcodes and prices must be clean before a counter goes live.
  • Promotion complexityLayered offers often need development beyond pricelists.
  • Staff turnoverCounter staff change often, so training is recurring.
Why us

Why choose OdooBots to implement Odoo Point of Sale

We test your offline behaviour on purpose before go-live — pull the connection during a mock session and watch what happens. Finding out on a Saturday evening with a queue is the alternative, and it costs more than the test.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo POS: frequently asked questions

What is Odoo POS?
The point of sale application: sessions opened and closed with a cash count, fast billing by search or barcode, split payments across cash, card and UPI, GST invoices where needed, restaurant mode with tables and kitchen printing, and every sale reducing stock at the outlet it happened in.
Does Odoo POS work without internet?
Yes. Billing and payment continue offline and synchronise when the connection returns, which matters more at a counter than any other feature. It covers an outage rather than a permanently disconnected site, so a location with no reliable connection needs its setup discussed first.
How is this different from the retail industry page?
This page covers the application. Odoo ERP for retail covers running a retail business on Odoo — buying, pricing, outlets, stock discipline and the decisions specific to that trade.
Can Odoo POS run several outlets?
Yes, with each outlet and counter under one database, selling from its own stock location and reporting its own sales and margin. Supply from a central warehouse or kitchen is handled as an internal transfer rather than a sale, so group stock stays correct.
Do we need Enterprise for Odoo POS?
Not for a standard retail counter — sessions, offline billing, barcode, payments, discounts and receipts are in Community. Restaurant features, loyalty and gift cards, and the IoT box for certain hardware are Enterprise, and restaurant mode usually justifies it for a food business.
Can Odoo POS print kitchen tickets?
Yes, in restaurant mode, along with floor plans, table management, course sequencing and bill splitting. Full kitchen display systems with order timing go beyond ticket printing and usually need additional work.
Does a POS sale reduce stock?
Yes, at the outlet it was sold from, which is the main advantage over a standalone till. Tomorrow’s replenishment suggestion is then based on what actually sold today rather than on an estimate someone made at the end of the week.
Why does session closing matter so much?
Because it is the control that makes the figures real. A counted drawer, an expected-versus-actual comparison and a signed variance each night is the difference between a record of what happened and a record of what the till was told.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The configuration advice, edition notes and limitations come from our own implementations.

Ready to put Odoo POS to work?

Tell us how many counters you run and whether you need restaurant features. Those two answers shape the configuration, and the diagnosis call is free.

Book a free Odoo diagnosis Talk to us +91 98414 81435