Odoo Point of Sale: Shops, Sessions, and Receipts

Introduction

Odoo Point of Sale gives growing companies a dedicated place to run a slice of their business inside the same database as sales, inventory, finance, and HR.

Disconnected tools create duplicate entry, conflicting numbers, and slow decisions, especially when teams scale past a single location or product line.

Standard Point of Sale flows are designed to be configurable before you customize code, which keeps upgrade paths manageable for lean IT teams.

Business owners, functional leads, and project sponsors reading this guide want to understand real-world usage before they scope an implementation.

Point of Sale is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Point of Sale: Shops, Sessions, and Receipts states the storyline for stakeholders.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Point of Sale.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Point of Sale is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Leadership opens a beautiful dashboard, then asks why the cash number does not match accounting. Someone built a view on incomplete data, and now every meeting starts with trust issues, not decisions.

Leaders want insight and tailored processes, but data and customization sprawl without governance. Dashboards and Studio changes only help when they sit on reliable transactional data.

Sound familiar? Teams usually hit these walls:

• KPIs that do not match operational reality
• Customization without sandbox discipline
• Integrations that break silently after upgrades

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Point of Sale, and measure what changes.

Top 10 Point of Sale Use Cases

10 use cases for Odoo Point of Sale, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Open your first POS session and ring up a clean sale Level 1 — Easy

Level 1 is the simplest possible Point of Sale action: one cashier, one register, one customer. No loyalty, no multi-shop, just a session opened, a cart filled and a payment validated.

Here's how you'd do it in Odoo:

1. Go to Point of Sale, Dashboard, click New Session on the main shop and type the cash drawer opening amount.
2. In the POS interface, tap a product tile or scan its barcode to add the line to the running order.
3. Click Payment, pick Cash or Card, type the amount tendered and click Validate to close the order.
4. Pick Print Receipt or Email Receipt so the customer leaves with a proof of purchase.
5. At the end of the shift, click Close Session, count the cash drawer and confirm the Z-report posts to Accounting.

What you get: One clean shift, daily close in five minutes, and every order linked to the right journal without any spreadsheet on the side.

2. Identify the customer at checkout to tie every sale to a record Level 2 — Easy

Level 2 stays on a single cashier but adds the customer file. Every sale now lands on a real Contact instead of an anonymous walk-in line, so marketing, finance and CRM share the same picture.

Here's how you'd do it in Odoo:

1. In the POS interface, click the Customer button at the top of the cart to open the contact search.
2. Search by name or phone; click Create to add a new Contact directly from the POS if the buyer is not in the file.
3. Select the contact so the receipt shows the name and the order is linked to that record in Contacts.
4. Validate the payment and email the receipt; the order appears under Sales History on the customer card.
5. Open the contact in Contacts to see all past POS orders, average basket and last visit date in one place.

What you get: Walk-in revenue stops being anonymous; every receipt feeds the customer database that CRM and Marketing use the next morning.

3. Process a refund and customize the receipt header Level 3 — Easy

Level 3 covers the daily after-sales reflex: a returned item and a clean receipt. Still one cashier, but the operation now handles refunds and a receipt that carries your shop branding.

Here's how you'd do it in Odoo:

1. In the POS, click the Orders button, search the original order by date or customer and open it.
2. Click Refund, pick the lines to return, adjust the quantity if it is a partial refund and validate.
3. Pick the same payment method as the original sale and click Validate to issue the cash or card refund.
4. Go to Point of Sale, Configuration, Point of Sale, open the shop and edit the Receipt Header and Footer with your shop name and return policy.
5. Switch Receipt Printout to Email by Default for customers who prefer a digital copy and save the configuration.

What you get: Returns are traced to the original order in seconds and every receipt carries the shop brand without any external print tool.

4. Launch a loyalty program with points and rewards Level 4 — Medium

Level 4 turns POS into a retention engine. The Loyalty layer awards points on every receipt and lets returning customers redeem rewards directly from the cashier screen with no manual stamp card.

Here's how you'd do it in Odoo:

1. Go to Sales, Configuration, Loyalty Programs, click New and name the program POS Loyalty.
2. Set an earn rule: one point per euro spent on selected categories, with optional bonus points on special weekends.
3. Add reward rules: one hundred points equals five euros off, two hundred and fifty points equals one free item from a chosen list.
4. Open Point of Sale, Configuration, Point of Sale, enable Loyalty Program on the shop and pick the program you just created.
5. At checkout, the cashier identifies the customer and the available rewards appear on the cart for one-click application.

What you get: Repeat visit rate becomes a measurable KPI instead of a hunch, and the cost of each reward is tracked line by line in Accounting.

5. Roll POS out to several shops with a shared catalog and pricelists Level 5 — Medium

Level 5 turns on multi-shop. One product master, one customer file, and a dedicated cash journal per location, so a chain runs on one database instead of one Excel per store.

Here's how you'd do it in Odoo:

1. Go to Point of Sale, Configuration, Point of Sale and create one POS record per physical shop.
2. On each shop, set the Stock Location, the Cash Journal and the receipt printer so accounting stays clean per location.
3. Open Sales, Configuration, Pricelists and assign a pricelist per shop to handle local price differences.
4. Share the Loyalty Program across the shops so points earned in one store can be redeemed in another.
5. Open Point of Sale, Reporting, Sales Details and group by Shop to compare revenue, basket size and top SKUs.

What you get: Chain-level visibility on revenue and stock is back without a Monday-morning consolidation of CSV exports.

6. Switch POS into restaurant mode with floors, tables and a kitchen screen Level 6 — Medium

Level 6 unlocks Restaurant Mode. The same engine becomes a front-of-house system with table plans, courses fired to the kitchen and split bills, without buying a separate restaurant tool.

Here's how you'd do it in Odoo:

1. Open Point of Sale, Configuration, Point of Sale, edit the shop and enable Restaurant Mode under the Features section.
2. Go to Point of Sale, Configuration, Floors and Tables, draw the floor plan and place the tables that match the dining room.
3. Tag products by course (Starter, Main, Dessert, Drinks) under Point of Sale, Products so each line is fired to the right station.
4. Connect a kitchen display through an IoT box so confirmed courses appear instantly on the screen in the back.
5. At checkout, tap Split to distribute lines per guest and print one ticket per person at the press of a button.

What you get: Service speeds up, kitchen errors drop and table turnover becomes a measurable number every dinner shift.

7. Connect POS live to Inventory with reordering rules on top sellers Level 7 — Hard

Level 7 wires POS into the warehouse. Every sale decrements stock in real time, and Odoo proposes a purchase order before any bestseller goes empty on the shelf.

Here's how you'd do it in Odoo:

1. On each shop product, set the Product Type to Goods and enable Track Inventory under the Inventory tab.
2. Open the product and add a Reordering Rule with Min Quantity, Max Quantity, Preferred Vendor and Lead Time.
3. Repeat the rule on the top twenty SKUs identified from Point of Sale, Reporting, Best Sellers.
4. Run Inventory, Operations, Run Scheduler daily so Odoo creates the proposed Requests for Quotation automatically.
5. Open Point of Sale, Reporting, Inventory Movement to confirm POS sales now drive replenishment proposals end to end.

What you get: Bestseller stockouts drop measurably and the shelf reality stops drifting from the system after every busy weekend.

8. Run promotions, coupons and gift cards for seasonal pushes Level 8 — Hard

Level 8 turns POS into a marketing-ready engine. The Promotions and Coupons layer ships discounts, codes and gift cards that cashiers do not need to remember.

Here's how you'd do it in Odoo:

1. Go to Sales, Configuration, Discounts, Loyalty and Gift Card, click New and pick the Promotions program type.
2. Define the rule: ten percent off on a category between two dates, or buy two get the third one free on selected SKUs.
3. Create a second program of type Coupons; bulk-generate codes and print them on shop receipts to bring buyers back.
4. Create a third program of type Gift Card sold as a product; the customer redeems the code at any shop on the chain.
5. Enable the three programs on the POS configuration; the discount, coupon and gift card buttons appear on the cart at checkout.
6. Open Sales, Reporting, Discount and Loyalty Programs to track redemption rate, revenue lift and margin impact per campaign.

What you get: Marketing experiments run cleanly at the register, cashiers stop computing discounts by hand, and the margin impact is visible per program.

9. Unify web, shop and CRM with shared loyalty and cross-channel returns Level 9 — Hard

Level 9 is the omnichannel setup. The same customer record powers eCommerce, POS and CRM, with one loyalty balance and a return-in-store policy on web orders that just works.

Here's how you'd do it in Odoo:

1. Install Website and eCommerce; open a product and confirm the same Contact is used for online signup and POS checkout.
2. Share the Loyalty Program between Website Sales Settings and the POS configuration so points earn and redeem on any channel.
3. On the shop POS, click Orders, search a web order by reference and click Refund to handle a web-bought return at the register.
4. In CRM, enable the Auto-create Lead rule on customers whose lifetime value crosses an internal threshold for outreach by the account team.
5. Build a Spreadsheet view 'Lifetime Value per Customer' combining eCommerce orders, POS receipts and loyalty balance in one dashboard.
6. Use Studio Automation to flag any omni-customer above the lifetime value target for a personal manager follow-up.

What you get: Customer experience finally matches modern expectations, returns no longer break finance, and retention becomes a controllable lever.

Wiring shared loyalty, cross-channel returns and lifetime value reporting between POS, eCommerce, CRM and Spreadsheet is the kind of retail engagement Dasolo runs as a partner-led project from day one.

10. Run an AI-powered POS with vision, demand forecast, payment APIs and live dashboards Level 10 — Expert

Level 10 is the full operating system. Computer vision speeds checkout, AI tunes the catalog, payment terminals and EDI talk to suppliers, and live dashboards let leadership see every register from one screen.

Here's how you'd do it in Odoo:

1. Connect approved payment terminals (Adyen, Stripe Terminal, Worldline) through Point of Sale, Configuration, Payment Methods so the amount auto-syncs from the cart.
2. Train an Odoo AI Demand Forecast on twenty-four months of POS sales so the system adjusts Min and Max on Reordering Rules every Monday.
3. Add a self-checkout flow with computer vision item recognition through an IoT box camera that scans baskets faster than barcode scanning.
4. Wire EDI feeds with the top vendors so RFQs proposed by the scheduler, vendor confirmations and bills travel without anyone typing a line.
5. Map dynamic pricing rules in Pricelists (time of day, weather, stock pressure) and let Studio Automation apply them on selected SKUs.
6. Build a Spreadsheet dashboard 'Retail Live' tracking sales per register, conversion rate, average basket and stock alerts, refreshed in real time.
7. Push the dashboard to leadership by webhook and to the floor managers through a TV display in the back office of each shop.

What you get: Each register acts as a sensor of the whole retail operation, exceptions surface in minutes and the team focuses on customer experience, not on data entry.

Designing the payment terminal integration, the AI feedback loop, the EDI mapping and the live retail dashboard is the architecture Dasolo assembles in a partner-led Point of Sale program. Most teams need an outside team to wire these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Point of Sale, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Point of Sale includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo