Skip to content
All case studies
03Supermarket group · Dubai

Four stores. One operating system.

The business had four branches. Its information architecture behaved like four separate companies.

  • Systems that Connect
  • Retail & FMCG
  • Odoo
  • Founder experience

Branches

4

Platform

Odoo

Modules

8 connected

Core symptom

Negative inventory

Reading time

2 min read

A Dubai supermarket operator ran four branches, but the point-of-sale environments and the central business systems were not properly connected.

Each branch could operate independently. Head office, however, could not see the whole business from the systems themselves. Branches sent daily operational reports covering sales, purchases, stock, waste and cash.

Inventory was losing contact with reality

The most serious symptom was negative inventory. Products continued selling through the POS while the system showed quantities below zero. Physical stock could arrive while the system position stayed inaccurate. Management could no longer rely on ERP stock figures when making purchasing decisions.

Expiry was a blind spot

For a supermarket, quantity is only half the information. The other half is how long the stock can still be sold. Without that visibility, management could not act early enough to return eligible products, move inventory, or promote items approaching expiry. By the time the problem was visible on the shelf, the commercial options had narrowed.

Purchasing was disconnected from receiving

Head office could raise and approve a purchase order. But when the supplier arrived at a branch, the manager often still had to telephone head office to ask whether it was authorised, what quantity was approved, and whether to receive the delivery. The information existed. It was not available where the decision was being made.

Head officepurchase order raised & approvedBranch 1Odoo POSBranch 2Odoo POSBranch 3Odoo POSBranch 4Odoo POSInventory · Sales · Purchases · Qualityone operational systemAccountingfollows the same transactionsreceiving checkedagainst the PO
Fig. 03, The transaction becomes the report
Scroll to see the full diagram

Connecting the transaction flow

The retail environment was brought into an Odoo architecture integrating the four points of sale with the wider business: POS, Inventory, Sales, Purchases, Accounting, Quality, Payroll and Attendance.

The important change was not another application. A sale affects stock. Receiving affects inventory. Purchasing begins with an approved order. Branches work against the same procurement information head office created. Expiry becomes data inside the same environment used to sell the product. Financial activity follows the same underlying transactions.

What changed

  • Stock became visible across all four branches from one record rather than four
  • The daily reconciliation report stopped being somebody’s job, because head office could see the branches directly
  • Receiving was checked against the approved purchase order at the branch, not by telephone to head office
  • Expiry became data inside the same system used to sell the product, early enough to act on

Instead of asking branches what happened yesterday, the business gained an architecture that could see it. The transaction itself became the report.

Technology used

Odoo POSInventorySalesPurchasesAccountingQualityPayrollAttendance

The result

Head office gained one operational system across four locations, and the transaction itself became the report.

Systems that Connect

Related work

Recognise any of this?

Start with a Health Check. AED 1,500, credited in full against your project.