How to integrate your POS with your ERP: a guide for multi-branch retailers in the UAE and Oman
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
A retailer with three branches and an online store usually has three versions of the truth. The tills know what sold today. The ERP or accounting system knows what was bought and paid for. The website knows what it thinks is in stock. Every evening someone reconciles them by hand, and every sale season they disagree in front of a customer.
Integrating the POS with the ERP means the item list, prices and stock live in one place, and every sale, return and cash-up flows back into stock and the ledger without anyone retyping it. Like most integration work, it is usually a connection project, not a reason to replace the tills.
This guide is about stock and money. If what you need is one customer record and loyalty that works in every branch, that is the POS and CRM integration; if it is sales and finance talking to each other, see ERP and CRM integration. The three fit together, and most growing retailers end up doing all of them.
What goes wrong when the tills and the ERP are separate
Stock that is only right once a day. A branch sells the last unit at noon, and the online store keeps offering it until someone uploads the day’s sales that night. Transfers between branches live on paper or in WhatsApp, so the ERP never quite knows where anything is.
A cash-up that takes an accountant. The till’s end-of-day report says one thing, the card terminal settlement lands a day or two later for a slightly different amount, the delivery apps pay out net of commission once a week, and the cash goes to the bank whenever someone has time. Matching those by hand is where days of finance time go each month.
Purchasing by feel. Without sales by item and branch in the ERP, reorders are based on what the branch manager remembers selling. Fast movers run out, slow movers pile up, and the cash is tied up in the wrong shelf.
VAT from a spreadsheet. If sales reach the ledger as one typed total per day, the VAT return is built from exports and formulas, and the records behind it are hard to produce if the tax authority asks.
What should move in each direction
From the ERP to the tills: the item master. Item codes and barcodes, the Arabic and English names that print on the receipt, units of measure (piece, pack, carton), prices per branch, promotions with their start and end dates, and each item’s VAT treatment. The ERP owns all of this. If a branch can change a price on the till, decide whether that change is allowed to flow back, and who approves it.
From the tills to the ERP: every sale and return at item level, the tenders used (cash, card, gift voucher, delivery app), each shift’s cash count and the difference against expected, stock adjustments such as damages and samples, and goods received at the branch if the branch receives deliveries directly.
One decision shapes the rest: how detailed the ledger should be. Stock should move item by item, as close to real time as you can manage. The accounting entries usually should not. Posting one journal per receipt fills the ledger with thousands of lines nobody reads. Most retailers post a summary per branch, per day, per tender, with the receipt-level detail kept in the POS and linked by reference, so an auditor can drill down from the summary to the receipt. Agree this with your accountant before anything is built.
What each sale should post in the ledger
A sale is four things at once for the accounts: revenue, the VAT collected on it (5% in both the UAE and Oman), the cost of the goods leaving stock, and money that has not yet reached the bank. The integration should post all four, so the profit by branch is known the next morning rather than at month end.
The money part is where reconciliation gets easier. Instead of posting card sales straight to the bank, post them to a card clearing account; when the acquirer’s settlement arrives, net of its fees, the integration matches it against that clearing balance and the difference is the fee. Delivery-app sales go to a receivable for that app and are cleared when its payout lands, net of commission. Cash goes to a cash-in-transit account until the deposit appears on the bank statement. Whatever is left in a clearing account is the thing to investigate, and nothing else needs a second look.
Settle the rounding rule early. VAT can be calculated per line or on the receipt total, and the two can differ by a fils or a baisa. Oman prices run to three decimals. Pick one rule, make the POS and the ERP use the same one, and the monthly VAT figure stops drifting by small amounts nobody can explain.
Keep the records. UAE tax law requires businesses to keep their accounting and tax records for at least five years, and the receipt-level detail behind each daily summary is part of that. This is orientation, not tax advice; confirm the treatment with your accountant or tax agent, in Oman as well as in the UAE.
Three ways to connect them
A ready-made connector. If your POS and your ERP are both mainstream cloud products, one of them may already offer a connector for the other. It is the fastest route (often two to four weeks, most of it mapping items, branches and accounts), but you get the connector’s idea of how a sale should post, so check it against the summary-and-clearing approach above before you sign.
A custom integration service. When the connector does not exist, or posts the wrong way, a small service sits between the two systems: it receives each completed sale from the POS, updates stock in the ERP straight away, queues the ledger entries for the daily summary, and pushes item and price changes back to the tills. With APIs on both sides this is usually four to eight weeks; an older desktop POS with no API needs an agent on the shop computer and is slower.
One system with the POS built in. A retailer with several branches, an online store and its own pricing rules can move to a single platform where the POS is a module of the ERP, so there is nothing to sync. That is a new system, usually eight to sixteen weeks, and the decision belongs alongside custom vs off-the-shelf systems in the Gulf.
Offline tills and several branches: the rules that keep the numbers straight
The till must keep selling when the mall’s internet drops. A cloud POS worth buying stores the sales on the device or the shop network and sends them when the connection returns. What the integration must add is a unique ID on every receipt, so a sale that is sent twice after a reconnect is recognised and posted once. Without that, a bad afternoon’s Wi-Fi turns into duplicate revenue and missing stock.
Stock for online orders has to be reserved, not just counted. When a customer orders online for collection at a branch, the ERP should hold that quantity against the order straight away, so the branch cannot sell it at the counter in the meantime. The same reservation logic covers sale-season peaks, which getting your POS ready for the UAE sale season walks through.
Transfers are two movements, not one. Stock leaves Branch A when it is dispatched and arrives at Branch B when it is received, and in between it is in transit. Recording that properly is what lets the ERP answer “where is it?” and makes the month-end count match.
Returns follow the original sale. A return at a different branch from the one that made the sale is normal now; the integration should find the original receipt, reverse the same VAT and cost, and put the stock back where it physically is, not where it was sold.
The rollout, step by step
1. Clean the item master first. One code per item, one barcode per pack size, units of measure that convert correctly (a carton of 24 received, single pieces sold), and Arabic names short enough to fit a receipt line. Messy item data is the most common reason these projects slip, and no integration can fix it for you.
2. Map the accounts with your accountant. Which revenue, VAT, cost, clearing and cash accounts each branch and tender posts to, and the daily summary format. This is a half-day meeting that saves a month of corrections.
3. Count the opening stock. Do a full count per branch on the night before go-live, so the ERP starts from what is really on the shelves rather than from what the old system believed.
4. Pilot one branch, in parallel. Run the integration at one branch for one or two weeks while keeping the old routine, and compare the daily figures: stock, sales, VAT, cash. Test the awkward cases deliberately: an offline afternoon, a return at another branch, a promotion that ends at midnight, a receipt printer that has to print Arabic.
5. Roll out branch by branch, then switch on the online store. Train cashiers on the two habits that keep the data clean: scanning rather than typing items, and doing the cash count at every shift change.
E-invoicing in the UAE and Oman
Both countries are moving invoices between businesses onto national e-invoicing systems, with pilots in 2026 and the mandatory phases from 2027. Everyday till receipts to consumers are not the first target, but most retailers also invoice companies (wholesale customers, corporate orders, staff uniforms), and those invoices will have to go through the new systems. An ERP that already receives clean, structured sales from every branch is most of the way there.
For the UAE timeline and what an integration needs, see how to connect your systems to UAE e-invoicing. For Oman’s Fawtara, see the Oman e-invoicing guide.
How we can help
SmartTech Studio is an Abu Dhabi studio that builds and connects ERP, CRM and POS systems for retailers in the UAE and Oman, in Arabic and English from the first screen. Connecting tills you already run to an ERP you already run is usually a defined project of a few weeks, and we will tell you if that is all you need. A new unified system starts from AED 25,000 excluding VAT.
If you are still choosing the ERP itself, start with when an SME needs an ERP.
The bottom line
A POS and ERP integration works when four things are settled before any code is written: a clean item master owned by the ERP, an agreed level of detail for the ledger, clearing accounts for every tender, and a unique ID on every receipt so offline sales post once. Get those right and stock is true in every branch and online, the cash-up stops needing an accountant, and the VAT return is a report rather than a project.
To map your branches and systems and get a quote for connecting them, request a free consultation.
FAQ
Should the POS send sales to the ERP in real time or at the end of the day?
Both, for different things. Stock should update as each sale happens, so the online store and other branches see the right quantity. Accounting entries are usually better posted as a daily summary per branch and tender, with the receipt detail kept in the POS and linked, so the ledger stays readable and still auditable.
Can the tills keep selling if the internet goes down?
A good cloud POS can. It stores sales locally and sends them when the connection returns. The integration must give each receipt a unique ID so nothing posts twice, and the online store will show slightly stale stock for that branch until the queue clears.
How long does a POS and ERP integration take?
Typically two to four weeks with a ready-made connector, four to eight weeks for a custom integration between two systems with APIs, and eight to sixteen weeks if you move to one system with the POS built in. Cleaning the item master and the opening stock count usually take longer than the code.
Do we have to replace our tills, scanners and receipt printers?
Usually not. Standard barcode scanners, cash drawers and thermal receipt printers work with most POS software, and card terminals only report approved payments to the POS. Check one thing early: that your printers print Arabic correctly, joined and right to left, because older models often do not.
Can cashiers use the POS in Arabic while finance works in English?
Yes, if both systems store item names in both languages and let each user choose the interface language. Receipts can then print the Arabic and English names together. The item code, not the name, is what links the two systems, so the language each person works in does not affect the data.
Can you connect the ERP we already use?
Usually, yes. Most current ERPs and accounting systems offer an API, and that is all a custom integration needs. If yours has none, or the licence does not include API access, we will tell you at the start, along with what the alternatives cost, before you commit to anything.