A point of sale system records what happens when a customer buys something. For the business owner, the more important questions extend beyond the receipt. What stock remains? Which products generate margin? Were payments collected correctly? What should be reordered? Can the business recognise the customer when they return?
Odoo POS brings checkout into a wider business platform. Alongside point of sale, Odoo provides applications for inventory, purchasing, accounting, online sales and customer communication. The opportunity is to manage these activities together, with clearer information and fewer disconnected records.
That is particularly relevant to businesses combining different ways of selling. A bookshop with a coffee shop, a food store with a restaurant, or a takeaway café selling packaged products needs to coordinate several workflows within one operation.
For South African businesses, the practical decision also includes local payments, suitable hardware, connectivity and the cost of implementation. Understanding how these parts work together is the basis for choosing an effective Odoo POS system.
What does Odoo POS do?
Odoo Point of Sale is designed for shops and restaurants. Its checkout workflow supports selecting or scanning products, applying prices, associating customers with transactions, recording payments and issuing receipts. It also provides workflows for refunds, cashier operations and closing the register. Odoo 19.0 documentation
The wider platform matters because a checkout transaction affects other parts of the business. Selling a stocked product creates a stock consequence. Recording payment creates a financial consequence. Identifying the customer creates an opportunity to connect the purchase with future service.
A typical retail setup therefore needs more than a screen containing product buttons. It needs reliable product records, payment methods, stock locations, accounting arrangements and defined employee responsibilities.
For example, a customer buying a book and a packaged food item should receive the correct prices and receipt. Behind the counter, management needs the sale reflected against the right products and stock, with the payment available for reconciliation.
Odoo’s value is the connection between those activities. The implementation must establish how the business will use that connection in daily trading.
How do POS payments work in South Africa?
For card payments, two arrangements deserve separate consideration: an independent card machine and an integrated payment terminal.
With an independent machine, the cashier enters the amount on the terminal, checks that payment succeeded and records the card payment against the Odoo sale. This arrangement allows the business to use its chosen payment service, but staff must control the handover between the two systems.
Suppose the Odoo basket totals R185. The cashier enters R185 on the card machine and waits for approval before validating the sale as paid. Entering R158 by mistake creates a difference that must be identified and resolved.
With a supported integrated terminal, the POS sends the payment request through the terminal connection. Compatibility must be established for the actual provider, terminal, merchant account and Odoo version being proposed. A terminal appearing on an international feature list does not establish that a South African merchant can use that arrangement. www.odoo.com
Online payment gateways are a separate consideration. A provider used for website checkout does not automatically provide an integrated countertop terminal.
Cash, card and any other accepted methods need their own procedures. At closing, staff should compare recorded payments with cash counts and terminal records. Finance must then reconcile provider settlements, fees and timing differences.
Managing a shop and café within one business
South African customers are familiar with businesses combining retail and hospitality. Fresh Earth provides a recognisable food-store-and-café example. Vida e caffè illustrates coffee service alongside products customers can take home. Bookshops with coffee shops provide another familiar format. Fresh Earth
These names illustrate the business models; the following Odoo example is hypothetical.
Consider a food store with a café, retail shelves and a shared storeroom. A retail cashier scans packaged products, while café staff take orders for prepared food and drinks. The two activities need different checkout layouts and preparation processes, but management needs a consolidated view of the business.
Odoo supports both shop and restaurant operations within its POS offering. A proposed implementation can use distinct POS configurations for the retail counter and café while coordinating the underlying business records. Odoo 19.0 documentation
The management questions remain concrete. Which suppliers serve both activities? What stock is held centrally? How is it transferred to the café? Can management distinguish café revenue from retail revenue while reviewing the overall business?
A unified platform should preserve the operational differences that matter. Staff need interfaces suited to their work, while management needs consistent product, purchasing and financial information.
Shared inventory and the difference between products and ingredients
Shared inventory means the business can coordinate stock through a common inventory system, with locations representing the storeroom, shop and café. It does not mean every stock item must sit in one undifferentiated quantity. Odoo Inventory provides warehouses and locations to organise stock across physical sites and areas. GitHub
If a supplier delivers bottled juice, the goods can be received into the storeroom and allocated to the appropriate selling locations. Selling a bottle is a straightforward sale of that stocked product. Moving bottles from the storeroom to the café is an internal transfer.
Prepared food and drinks introduce a different requirement. Selling a cappuccino records the sale of the drink; accounting for the beans and milk requires an ingredient-consumption process.
A practical implementation might begin with recorded transfers to the café, stock counts and documented wastage. If the business needs recipe-level consumption and costing, the scope must include the appropriate production or ingredient-management workflow and demonstrate its connection to sales.
This distinction matters for purchasing and profitability. A standard recipe represents expected consumption; actual usage may differ because of portion sizes, preparation losses and waste.
Management needs a process for investigating those differences. Shared records provide the foundation, while clear stock movements and consumption procedures make the information dependable.
Returns and refunds: from the original sale back to stock
Odoo provides a POS refund workflow. Staff can locate the original order, select the products and quantities being returned, and complete the refund transaction. The physical goods also need the correct inventory treatment. Odoo 19.0 documentation
Consider a customer returning an unused mug bought from the retail section. Staff identify the original sale and confirm the item and quantity. They inspect the mug, process the agreed refund and ensure that the return is reflected in stock.
If the mug is undamaged and ready for resale, it can rejoin saleable inventory. If it is cracked, recording its physical return should not make it available to another customer.
For damaged goods, the operating procedure needs a defined inspection or damaged-stock location and the appropriate transfer or disposal process. A standard refund should not be assumed to make that condition decision automatically.
The payment procedure also matters. With an independent card machine, processing the Odoo refund and executing the provider refund are separate actions that must agree. With an integrated arrangement, the refund capabilities of that particular connection must be verified.
Testing should therefore follow both the money and the goods. The refund record, actual repayment, returned quantity and final stock disposition must all tell a consistent story.
Customer management, loyalty and ongoing communication
A customer record becomes useful when it connects purchases with subsequent interactions. Odoo POS allows staff to associate a customer with an order, supporting functions such as invoicing, customer pricing and loyalty. www.odoo.com
For a combined shop and café, this creates opportunities beyond an anonymous receipt. A recognised customer might buy groceries, visit the café and later place an online order. The business can plan how those activities contribute to its customer relationship.
Odoo’s discount and loyalty applications support programmes across POS, Sales and eCommerce. The business must define where each programme applies, what earns rewards and how those rewards can be used. www.odoo.com
The wider Odoo platform can also support website presence, online shopping and planned customer communications through the relevant applications. Those capabilities extend the POS rather than all belonging to the checkout application itself.
A useful approach is to define the purpose of each communication: a transaction message, help with a purchase, a reward notification or a promotional campaign. Customer identification and permission for marketing should be handled as separate requirements.
The commercial objective is better service and more relevant engagement. Customer records should help staff understand and support the relationship over time.
Accounting and management reporting
Sales reporting tells management what customers bought. Business management also requires an understanding of costs, cash, stock and the resources used to generate those sales.
The accounting setup must define how POS sales, taxes, discounts, payments and refunds reach the financial records. Finance should review a sample sale and refund through to their accounting treatment before launch.
In the combined food-store-and-café example, management may want separate sales reporting for packaged goods, prepared meals and drinks. Product categories and reporting arrangements should support those distinctions.
Profitability needs more care. The margin on a stocked retail item and the margin on a prepared meal rely on different cost information. Reliable ingredient costs, consumption records and waste information are needed before a café’s gross margin can be assessed confidently.
Management should select a small number of useful measures: sales by activity, product performance, discount levels, payment discrepancies, stock losses and purchasing requirements.
A report is valuable when someone uses it to make a decision. The implementation should establish who reviews each measure and what action follows an exception.
Hardware and operation during connectivity interruptions
Odoo POS uses a browser-based interface and supports several types of connected hardware. Scanners, receipt printers, cash drawers, customer displays, scales and payment terminals must be checked against the proposed connection method. www.odoo.com
Buy hardware against a verified equipment list. Some peripherals connect directly, while others require an additional IoT arrangement or network setup. An existing printer or scale should be tested before it is included in the launch plan. www.odoo.com
Odoo documents temporary offline operation for POS. This helps an already-loaded register continue with supported POS activities when its server connection is interrupted. It should not be presented as unrestricted offline access to the entire business platform.
Connected payment terminals still require an active internet connection. A separate card machine may use its own mobile connection, but payment availability remains subject to that device and provider.
While transactions await synchronisation, management and other counters may not have their latest information. Staff should preserve the open browser and its local data until the POS reconnects and synchronises. Odoo 19.0 documentation
The interruption test should cover the complete checkout: screen, power, scanner, printer, payment device and recovery procedure. Battery power for one component does not establish that the complete arrangement will remain operational.
Costs, implementation and essential testing
The cost of Odoo POS includes the software arrangement and the work needed to make it operational. The scope may include Inventory, Accounting, Website, eCommerce and other applications alongside POS.
Subscription, hosting and integration requirements should be quoted for the actual proposed system. Add hardware, payment charges, data preparation, configuration, training and ongoing support to understand the full investment.
The launch scope should define products, barcodes, units, prices, taxes, stock locations, payment methods, customer rules and staff permissions. It should also identify who owns each process after launch.
For a combined shop and café, testing should include a retail sale, a café order, a stock transfer, an unsuccessful payment, a refund and a closing reconciliation. If ingredient consumption is included, demonstrate how a sale affects component quantities and costs.
Test a connectivity interruption and the subsequent synchronisation. Where online sales are included, follow an order through payment, fulfilment and a customer enquiry.
A phased rollout can keep the work manageable, provided each phase delivers a complete usable workflow. Management should know which functions are ready at launch and which are scheduled for later.
When is Odoo POS a suitable choice?
Odoo POS deserves consideration when the business needs checkout to work closely with stock, purchasing, accounting, online sales and customer management.
That can suit a retailer expanding into e-commerce, a food store with a café, a bookshop with hospitality activity, or a business coordinating several counters and locations.
A simpler arrangement may be sufficient where the principal requirement is straightforward selling and payment collection. The additional value of Odoo should be assessed against the operational problems it will address and the resources needed to implement it.
For a mixed retail and hospitality business, the important opportunity is coordinated management: shared purchasing, controlled stock movements, distinct selling workflows, customer relationships and financial visibility within a connected platform.
Hatton Locks works with South African businesses to define these requirements and translate them into practical systems and working processes. We help establish priorities, assess payment and hardware arrangements, plan implementation and prepare employees for daily operation.
The work starts with how the business needs to perform and continues through the information, controls and responsibilities that support that performance.