Odoo Point of Sale: sessions, payment methods and cash closing

What Odoo Point of Sale 20 covers, how it is configured and what to check: sessions, payments, employees, loyalty, restaurants and when custom development is needed.

ProductOdooPOSretailERP19 November 2026 · 18 min read

Odoo Point of Sale (POS) is a sales interface optimised for tablets and touch screens, which works both online (connected to Odoo) and offline (local session with synchronisation when the connection returns). It integrates with Inventory (real-time stock deduction), Accounting (session closing entries), CRM (customer identification and loyalty) and HR (authentication of employees on shift). This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise.

When an implementation is healthy

A point of sale implementation works when five conditions hold:

  • sessions are opened and closed every day, with complete accounting reconciliation;
  • the POS catalogue and prices are the same as in the Odoo back end, with no separate price lists;
  • payment methods match the physical payment terminals, with no manual reconciliation;
  • the restaurants' floor plans reflect the physical layout and tables are managed in Odoo;
  • loyalty programmes are active and linked to CRM contacts.

The module covers seven areas: session management (opening, closing, shift change), the product catalogue (categories, variants, price lists), payment methods (cash, card, integrated terminals), employee management (multi-cashier, PIN access), loyalty programmes (points, discounts, gift cards), restaurant functions (floor plans, kitchen display, order management) and reporting (Z report, sales analysis).

The two interfaces and offline mode

The POS has two interfaces: the back end (configuration and reporting) and the POS interface proper, the sales screen.

InterfaceUse
POS session (front end)The touch sales screen: the cashier's view
POS, Dashboard (back end)Overview of all configured POS and session history
POS, Orders (back end)All past orders: search, return, receipt reprint
POS, Reporting (back end)Sales by product, payment method, employee, session
POS, ConfigurationProducts, payment methods, price lists, loyalty programmes

The POS also works without a connection. Transactions are stored locally and synchronised with Odoo when the connection returns. This means that a network outage does not stop sales, but that synchronisation errors must be monitored after reconnection, and that integration with the fiscal printer (in countries that require a fiscal receipt) may require connectivity.

The session life cycle is the accounting control point

Each session represents a financial period that must be opened and closed correctly. On opening you use Open session and enter the opening cash float, that is the physical cash counted in the drawer. During the session sales are recorded, payments collected and receipts printed; returns are processed by refunding the payment; cash movements in and out (tips, float corrections) are recorded by hand.

On closing you use Close session: the cash in the drawer is counted and the counted amount entered, and Odoo shows expected against counted, flagging the difference. On confirmation the accounting entry is created: debit to the cash account (cash sales), debit to the bank or cards account (card sales), credit to the revenue accounts (by product category). The session is archived and cannot be reopened. The Z report is the end-of-session summary: total sales by payment method and by product category.

A session left open overnight or for several days is a breakdown of accounting control: cash movements from different sales periods get mixed.

The product must be configured for the POS

Not all back-end products are automatically available in the POS. The product form requires: the Available in POS tick (so it shows in the search), the POS category (organises the products on the screen with a button per category), the price (the standard sales price, with the price list if configured), taxes (the default customer tax, of a type compatible with the POS), variants (colour or size variants create a selector on the screen) and images (the product image appears on the screen, to recognise it at a glance).

POS categories form a hierarchy: the category Drinks with the sub-categories Hot, Cold, Alcoholic; the category Food with Starters, Main courses, Desserts. The cashier touches the category button and the filtered grid of products appears. Products not configured for the POS simply do not show up: there is no warning, they are silently absent from the list.

Payment methods reflect the physical reality

Each POS payment method must correspond to a real payment instrument and an accounting account. Cash has the cash register as its account; the opening and closing floats are counted by hand, and the difference between expected and counted is the cash discrepancy, recorded automatically. The integrated payment terminal (Stripe, Adyen, Worldline & Axepta BNP Paribas and others) is connected through an IoT Box or a direct IP connection: the request starts from the POS, the customer taps or inserts the card and the confirmation comes back to the system. The card amount is not typed by hand, so typing errors disappear; the account is a bank register separate from the cash one. The manual card, without terminal integration: the cashier chooses "Card" and enters the amount by hand, with no hardware link. The risk is the typing error and the absence of automatic reconciliation with the terminal's report. Bank transfer, voucher and gift card are custom methods and each requires its own accounting account.

The principle is one payment method for each physical instrument. Mixing cash and card in a single method makes bank reconciliation impossible.

Multi-employee mode

Without multi-employee mode all the sales of a session are attributed to whoever opened it. It is enabled in POS, Configuration, Connected devices, Employee access (PIN or badge). Each employee has a four-digit PIN, set in the employee form in HR, HR Settings tab. The cashier chooses their name (or swipes the badge), enters the PIN and starts their shift inside the session.

The advantages are individual reports per cashier, security (the cashier can lock the screen on leaving the till) and the attribution of tips to the cashier. A session can cover several employees' shifts, and several employees can work on the same session: a shift change does not require closing it.

In Odoo 20 the permission levels are documented: an employee without a database user or with a light user, manager and so on, with a table of permissions by employee category (cash management, sales transactions, prices and discounts, bookings). A Price control setting and employee access rights complete the picture.

The floor plan is the table management interface

For restaurants and bars the floor plan replaces the POS home screen. It is configured with the floor plan editor, from the till: a plan is created (for example "Main room", "Terrace", "Bar"), tables are added with number, shape (square, rectangular, round, oval), seats and position, then decorations, walls, texts and background images; several plans are used for different areas. In Odoo 20 the editor is used directly from the cash register, with layers and duplication of plans.

The order flow in the restaurant: the waiter opens the POS and sees the plan; touches a free table and the order screen for that table opens; adds the items and sends them to the kitchen display (KDS) or prints the kitchen ticket; the items are prepared and served; when the bill is requested Close is used, then the payment screen, the receipt, and the table is freed. The table status colours: green free, red occupied (open order), orange order sent to the kitchen but not yet counted. The kitchen display is a separate screen that shows incoming orders in real time; the kitchen marks the items as ready, the waiter is notified and no paper tickets are needed.

Courses (starters, main courses, desserts) are managed in two ways. By hand: with the Course button in the cash register the course is created and then the products are added. Automatically (new in Odoo 20): from Settings, Preparation, Automatic course assignment, each POS product category is tied to a course. With Send the first course is prepared, the others appear as On hold in the preparation display until Fire is used on the next one. Items can be moved from one course to another.

Configuration

A checklist for the basic setup: the POS name (for example "Till 1", "Bar", "Table service"); the register, with the cash register assigned and the cards one if cards are accepted; the payment methods (cash and at least one card method); the receipt (company name, VAT number, address, footer message, gift receipt and early printing if needed); the printers (Point of Sale, Configuration, Printers, with paper format and detection through local network access); the scale (USB or IoT for products sold by weight, and the Reference price if the price per kilo must be shown); the fiscal configuration (VAT on receipts); the products (all the sellable ones with the Available in POS tick and a category); the price list if there are several price bands (personal discount, happy hour).

For the advanced setup: multi-employee with PINs assigned to all cashiers; the loyalty programme with point rules and reward thresholds; gift cards with denomination and validity; the fiscal printer connected through an IoT Box (in Italy the RT printer, in France the certified POS); the integrated payment terminal connected and tried with a real transaction.

Loyalty programmes have five types: points (N points per euro spent, to be redeemed for discounts or free products); discount (spending X euro on a visit gives Y per cent off the current or a future order); gift cards (cards of fixed denomination are sold and redeemed); eWallet (the customer loads a credit that is deducted at the till); free product (buy N items and receive one free). They are configured in POS, Configuration, Loyalty programmes, New, defining the accrual rules (euro spent, points) and the reward ones (points, euro of discount). The programme is tied to the identified customer, who must be selected at the POS; there is also anonymous loyalty, with points tracked by phone number without a full customer record.

For supermarkets and shops discount labels with a barcode can be created (for example "discount -10 per cent"): the cashier scans the code and the discount is applied to the last item or to the whole order. Typical uses are discounts for damaged goods, for staff and manager authorisation.

The flows

Daily session in retail. In the morning the manager opens the session, counts the float, enters the amount and the session is open; cashiers log in with the PIN. During the day every sale follows select products, payment, receipt. A return is done from POS, Orders, finding the order and using Return, partial or total. Cash withdrawals to the safe are recorded as "Cash Out" in the session. In the evening the last cashier completes the last sale, the manager counts the drawer and enters the count; Odoo shows expected, counted and difference. If the difference exceeds the tolerance it is investigated before closing. With Close session the entries are posted and the session is archived; the Z report is printed or saved for accounting.

Restaurant shift. At opening the plan is reviewed, all tables must be green, and the kitchen display is active. During service the waiter takes the order on the tablet at the table, the order goes to the kitchen (display or ticket), courses are fired in sequence, items can be moved between courses. Once the items are delivered the customer asks for the bill (an early bill can be printed with the early printing of the receipt). Close on the table opens payment in cash or by card, the receipt is printed and the table goes green again on the plan. To split the bill there is Split bill: items are assigned to each customer and separate payments made. To move a table there is Transfer: the destination table is chosen, all the items move and the origin table is freed. At the end of service all tables are closed, the session is closed and there is the shift handover or the end-of-day closing. In the Odoo 20 restaurant the plan, orders, preparation printer, bill splitting and tips are reorganised; presets have a service fee and a date selector, plus self-ordering options.

What changes with Odoo 20

Odoo 20 Enterprise is the reference. Before classifying a need as development (Studio or custom), it pays to test it against these functions.

  • Restaurant courses: besides manual assignment, automatic assignment by POS product category; courses on hold are labelled On hold on the preparation display until they are fired; items are transferred between courses.
  • Floor plan editor directly from the till: table shapes, seats, decorations, walls, texts, background images, layers, duplication of plans.
  • Receipts: Gift receipt (without prices), Early receipt printing (the bill before payment), choice between full or simplified receipt on reprint, Customise information (phone, email, website, address and logo specific to the point of sale).
  • Reference price: the price per unit of measure (for example per kilo) shown beside the sales price on the product form and on printed labels.
  • Suspended products (temporarily unavailable, also in self-ordering) and combos that can be broken into their components (Break the combo).
  • USB scale connected directly to the device running Odoo, without an IoT system.
  • Debit notes issued from a POS invoice.
  • Printers managed in Point of Sale, Configuration, Printers, with Paper format and detection through local network access.
  • Payment terminals: Worldline is now Worldline & Axepta BNP Paribas.
  • Access rights documented (see above) and the Price control setting.
  • Restaurants: Google Reserve information, GoFood delivery integration (APAC), presets with service fee and date selector.
  • Miscellaneous: Download invoice setting, notes on Bancontact Pay and receipt printers, updated IoT connection page, a note on offline mode.

The functions already present in Odoo 19 remain valid: the renewed POS front end, cash differences always tracked, products that can be created and edited from the POS, customer display on remote devices without an IoT Box; improved payment (change of method before printing, one-click validation, QR code payments from a bank app, a series of preset POS settings, adjustment on the selected account); restaurants with preset internal notes, quick table merging, allergen management, organisation by courses and reports on preparation times; primary and secondary grouping of products and categories, product information with long press; employee profiles with minimal rights for cash-only operations and ZPL formats for receipts and labels.

For development requests the guidance is this: custom till screens, course layouts in the restaurant, early bill printing, gift receipts, labels with the price per kilo, manual registers of cash differences and external customer displays are tested first against the standard and the configuration of Odoo 20 POS and against hardware constraints.

The justifications you hear

In the company they sayIn reality
"We close the POS session every week, not every day"A week of sales, returns and cash movements in a single session. Cash discrepancies are impossible to trace and the Z report means nothing.
"We use 'Manual card' because we don't have an integrated terminal"Manual entry has no hardware check and typing errors are invisible. It is worth integrating an inexpensive terminal (Stripe, Adyen reader).
"We don't use POS categories because we have too many products"Without categories the cashier searches for each product by name. Category buttons reduce each sale to two or three touches instead of typing.
"Loyalty programmes are too complicated to explain to cashiers"A programme explained in one sentence ("one point per euro, 10 per cent off at 100 points") can be explained in ten seconds. The complexity is in the setup, not in the use.
"We write orders on paper and enter them in the POS afterwards"Paper orders are not in Odoo until they are entered, communication with the kitchen is verbal and errors are not tracked. It defeats the purpose of a POS.
"Odoo's floor plan does not match our dining room"It is configurable. The drag-and-drop editor takes thirty minutes. A plan that does not match makes waiters serve the wrong table at every service.

Warning signs

  • Sessions not closed every day: several days of transactions in one session, cash reconciliation impossible.
  • Opening cash float never entered: the expected cash balance is wrong from the start of every session.
  • Products not assigned to POS categories: cashiers search for each product by name, with slow service.
  • No integrated payment terminal: cards typed in by hand, no payment confirmation at hardware level.
  • Multi-employee mode not enabled: all sales attributed to a single cashier, no individual tracking.
  • Restaurant floor plan not matching the physical layout: confused waiters, wrong table assignments.
  • Kitchen display not configured: verbal or paper communication, prone to errors.
  • Loyalty programme exists but the customer is never identified at the POS: points do not accumulate, the programme is invisible.
  • Gift cards sold without validity: they never expire and the liability is not recognised.
  • Fiscal printer not connected in jurisdictions that require it (Italy, France): legal non-compliance.
  • Returns processed as new discounts instead of with the Return function: wrong accounting entries.
  • Z report not generated when the session is closed: the end-of-day accounting reconciliation document is missing.

How to check a configuration

After configuring or assessing the POS, the check goes through these controls:

  • there is at least one POS configured for each physical point of sale;
  • the cash register and the card register are correctly assigned for each payment method;
  • the integrated payment terminal is connected and tried end to end with a real transaction;
  • all sellable products have the Available in POS tick and a POS category;
  • the POS categories are organised as a tree that matches the physical layout or the menu;
  • multi-employee mode is enabled and every active cashier has a PIN;
  • the session opening and closing flow is established: daily closing, counted float, Z report saved;
  • the tolerance on cash differences is set and differences are investigated before closing;
  • for restaurants: the floor plan is configured like the physical layout and all tables are named;
  • the kitchen display or the kitchen printer is configured (restaurants);
  • the loyalty programme is configured and customer identification at the POS is tried;
  • gift cards: denomination, validity and redemption are tried;
  • the fiscal printer is connected and certified, if required by local law (Italy, France and so on);
  • offline mode is tried: the network is disconnected mid-session, sales are recorded, it is reconnected and the synchronisation is verified;
  • POS reporting is reviewed: Z report, sales by product, by payment method, by cashier.

Standard, configuration, integration or custom development

To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: POS with several tills and several shops and offline mode; reading products by barcode and QR code; several payment methods (cash, card, vouchers, split payments, loyalty points); customer identification and loyalty programmes at the till; real-time stock synchronisation at every sale; the kitchen display (KDS) for restaurants; the daily session closing with Z report and cash reconciliation; the integration with Accounting (daily sales entry) and with Inventory (stock movements).

Five questions help classify every gap before asking for a development:

  1. Which POS system is used today? A dedicated system for shops or restaurants, a tablet app, or manual? How many transactions a day? An existing POS with deep integrations requires an integration assessment. A simple POS is standard.
  2. Which payment methods must be accepted? Cash, POS terminal (from which provider?), contactless, gift cards, loyalty points? Standard payments are configuration. A provider not natively supported is an integration.
  3. How is end-of-day closing handled? Who counts the cash, how is the Z report reconciled, how does the entry reach accounting? Manual reconciliation is standard plus a process change. A complex closing across several tills is configuration.
  4. Is there a loyalty programme? How does it work, which customers are enrolled, is it multichannel? An existing programme is configuration (Odoo's Loyalty module). Loyalty across channels with e-commerce is configuration.
  5. How is stock tracked at the point of sale? Real-time synchronisation with the central warehouse, in periodic batches or not at all? If it is not tracked, it is a configuration gap solved by synchronisation between POS and Inventory.

The typical classification of the most common cases is this:

Frequent gapTypical pathSigns that push towards custom
Existing POS with deep integrationsIntegration (assess) or standard (replace)A fiscal printer with a proprietary protocol not supported by Odoo
Unsupported payment providerIntegrationNone
Manual end-of-day accounting entryStandard and process changeNone
Loyalty programme across several channelsConfigurationA complex points engine with an external loyalty platform
This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

odoo-posA guide to designing and checking the Odoo 20 Enterprise Point of Sale (POS) module: sessions and cash closing, product catalogue, payment methods and integrated terminals, multi-employee access with PIN, loyalty programmes and gift cards, restaurant functions (floor plans, kitchen display, courses). It contains the warning signs, the justifications heard in companies and the questions for deciding between standard, configuration, integration and custom development. It is needed when setting up or checking the point of sale in Odoo, with or without interviews with store and dining room managers.