Connecting your online store to your POS in the UAE: one stock count, one price list, one customer
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
Many UAE retailers start with a physical shop and a POS that runs the till, then add an online store on Shopify, WooCommerce, Salla or Zid. For the first few weeks it works: orders are few, and someone adjusts quantities by hand every evening. Then the store grows, a sale season arrives, the website sells an item the branch sold an hour ago, a customer finds an online price that differs from the shelf price, and a cashier cannot find the online order the customer wants to return.
All of these problems have one cause: two systems, each holding its own version of the truth. Connecting the online store to the POS means giving them one version: one product catalogue, stock counted per location and visible to both, one price list, and one customer record wherever that customer buys.
This guide explains what has to sync between the store and the POS, which system should own each kind of data, when you need real-time sync, how to handle click-and-collect and ship-from-store, how to avoid overselling on peak days, and how all of this relates to VAT and the coming UAE e-invoicing system. It is written for store owners and operations managers, not developers.
What this integration is, and what it is not
There are three common integrations around a POS, and they solve different problems. This article covers the first one only: the online store and the shop POS sharing products, stock, prices, orders and customers so that the business sells as one shop with several doors.
The second is POS to accounting or ERP: sales, payments, VAT and cost of goods flowing into the books, and purchasing and stock valuation flowing back. We cover that in our guide to integrating your POS with your ERP. The third is POS to CRM: purchase history feeding customer profiles, segments and campaigns, covered in POS and CRM integration.
In a growing business you usually need all three in time, and the order matters. If the store and the POS disagree about stock, connecting either of them to the ERP simply copies the disagreement into your accounts. Fixing the store-to-POS link first gives every later integration a clean base.
What has to sync between the online store and the POS
Before choosing a connector or writing any code, list every kind of data the two systems share and decide three things for each: which system owns it, which way it flows, and how quickly. The table below is the starting point we use with retailers; your answers may differ, but every row needs an answer before go-live.
| Data | Usual owner | Direction | How often |
|---|---|---|---|
| Products, SKUs and barcodes | POS or ERP | To the store | On change |
| Descriptions, photos, SEO text | Online store | Stays in the store | Not synced |
| Stock per location | POS (with the warehouse) | Both ways | Real time or near it |
| Prices and promotions | One system, chosen once | To the other system | On change, before the sale starts |
| Online orders | Online store | To the POS | Real time |
| Returns and refunds | Where the return happens | Both ways | Real time |
| Customers and loyalty points | One system, chosen once | Both ways | Real time for points |
Two rows cause most of the trouble. Stock, because it changes every minute in two places at once. And prices, because a promotion set up in one system and forgotten in the other produces exactly the shelf-versus-website complaint that customers screenshot and share.
Which system should be the source of truth?
Every piece of shared data needs exactly one owner. If both systems are allowed to create and edit products, you will end up with duplicates, two barcodes for the same item, or a price change that one system overwrites with an older value at the next sync. The rule is simple to state and easy to break: edit data only in the system that owns it, and let the integration copy it everywhere else.
For most UAE retailers with physical branches, the POS (or the ERP behind it) should own the product master: SKUs, barcodes, variants such as size and colour, cost and the base price. The shop is where goods are received, counted and sold in the largest numbers, and barcodes must scan correctly at the till. The online store then owns what only it needs: long descriptions in Arabic and English, photos, collections and search text.
The exception is the business that started online and opened a shop later. If your catalogue was built in Shopify or Salla and the branch carries a subset of it, it can make sense for the store to own the product master and push items to the POS. Either answer works. What does not work is leaving the question open.
Customers deserve the same decision. If the shop collects phone numbers at the till and the website collects email addresses at checkout, decide which identifier joins them (in the UAE it is usually the mobile number) and which system holds the master record. Your data protection obligations also depend on knowing where customer data lives.
Real-time or scheduled sync?
Not everything needs to move instantly, and treating everything as urgent makes integrations fragile and expensive. A practical split:
Real time, or within a minute or two: stock levels, new online orders, cancellations, returns, refunds and loyalty point balances. These are the events where a delay causes a wrong sale, a missed order or an unhappy customer at the till.
On change, but a few minutes is fine: new products, price changes and promotions, as long as the change is pushed before the promotion starts rather than at the moment it starts.
Scheduled, such as nightly: reconciliation reports, sales summaries and any full re-count that checks the two systems still agree. A nightly reconciliation is cheap insurance; it catches the order that failed to sync at 3 p.m. before it becomes a complaint.
Technically, real-time sync usually means webhooks (the store notifies the integration the moment an order is placed) and event-driven updates from the POS. Scheduled sync means the integration polls each system for changes. Many POS systems in use across the Gulf do not offer webhooks at all, so part of the scoping is simply finding out what each side can do.
Stock per branch, click-and-collect and ship-from-store
A single total stock figure is the most common shortcut and the most expensive one. If the website shows “10 in stock” because there are four pieces in Dubai Mall, five in Abu Dhabi and one in the warehouse, it will happily sell a customer in Sharjah an item that has to cross the country, or promise next-day delivery from a location that cannot ship.
Count stock per location in both systems. The store can then decide, location by location, what is available to sell online. Most retailers do not expose every branch: a flagship may keep its display stock off the website, while the warehouse and one or two large branches fulfil online orders.
Click-and-collect (order online, pick up in a branch) needs the customer to see stock at the branch they choose, and needs the branch POS to receive the order, reserve the item and mark it collected when the customer arrives. Without that reservation, a walk-in customer can buy the last piece while the online customer is driving over.
Ship-from-store (the branch packs and ships an online order) needs order routing rules: which location fulfils which order, and what happens when the first choice is out of stock. Start with simple rules, such as nearest location with stock, then the warehouse, and only add complexity once you have real order data. For retailers with several branches across the emirates, this is often where the integration pays for itself, because stock that would sit unsold in one branch can be sold online and shipped from where it is.
Sale days: how to stop overselling
The UAE retail calendar has a handful of days that test every integration: White Friday, the Dubai Shopping Festival, Ramadan and the Eid weekends, back-to-school. On those days the store and the branches sell the same fast-moving items at the same time, and a sync that is perfectly adequate on a quiet Tuesday falls behind. Our article on preparing your POS for the shopping season covers the till side; here is the integration side.
Hold a safety buffer. Publish online slightly less than you have, for example keeping the last one or two units of each item for the shop, so that a delay of a minute or two does not turn into an order you cannot fulfil. Raise the buffer on fast movers during a sale and lower it afterwards.
Reserve on order, not on payment. Stock should be deducted the moment an online order is placed, and released if payment fails or the order is cancelled, so the branch does not sell the same piece in the gap.
Load the promotion before it starts. Push sale prices to both systems the evening before, with a start time, rather than editing prices live at midnight. Then check a sample of items in both systems before doors open.
Watch the queue. An integration that falls behind should alert someone, not fail silently. A simple dashboard showing the number of unsynced orders and the time of the last successful stock update is worth more on a sale day than any feature.
Shopify, WooCommerce, Salla, Zid, Magento: connector or custom middleware?
The platforms common in the UAE all have APIs and app marketplaces, and most popular POS systems list ready-made connectors for at least some of them. Shopify also sells its own POS, and some platforms offer their own in-store option. If your POS and your store already have a maintained connector between them, and it handles stock per location, returns and your promotion types, use it. It will be cheaper and faster than anything built from scratch.
A ready-made connector stops being enough when the business does not fit its assumptions. The usual signs are: several branches with their own stock but the connector only syncs one total; bundles, gift sets or items sold by weight that the connector cannot map; a local POS with no connector at all; prices that vary by branch or customer group; or a store, POS and ERP that all need to agree, so that a two-way connector between two of them is not enough.
In those cases the answer is a small middleware service that sits between the systems. It receives events from the store, calls the POS, keeps a log of every message, retries anything that fails, and gives you one place to see what synced and what did not. It is the approach we take in our internal systems work, and it also leaves room to add the ERP or the e-invoicing provider later without rebuilding the store or the POS.
Whichever route you take, ask three questions before committing: does it handle stock per location, what happens when one side is offline, and who will you call when it stops at 9 p.m. on a sale day?
Returns, refunds, customers and loyalty
Customers expect to return an online purchase in any branch. That is only possible if the branch POS can find the online order, see what was paid and how, and issue the refund in a way both systems record. If the refund goes back to a card, the payment usually has to be reversed through the online payment gateway, not the shop terminal, so decide the procedure with your finance team before launch.
Returned stock also has to go somewhere. An item returned in a branch should normally go back into that branch’s stock, not the warehouse it was shipped from, and the integration must update both systems accordingly.
Loyalty programmes are where a single customer record pays off. Points earned online should be redeemable at the till the same day, and the other way round. That means one balance, held in one system, updated in real time. Two separate programmes that “sync overnight” invite customers to spend the same points twice.
VAT and the coming UAE e-invoicing system
Whichever system issues the invoice for an online order, the store or the POS, must produce a valid VAT invoice, and the other system must not issue a second one for the same sale. Agree which system numbers and issues invoices for each channel, and make sure refunds produce credit notes that reference the original invoice.
E-invoicing adds a deadline to this decision. Under the UAE Electronic Invoicing System, businesses with revenue of AED 50 million or more must issue e-invoices from 1 January 2027, and the rest of the businesses in scope from 1 July 2027. Sales to consumers are outside the system in its first phases, but many retailers also sell to businesses: corporate gifting, trade accounts, office orders placed through the website. Those invoices are in scope, and they must come from a system that can send structured data to your Accredited Service Provider.
If you are connecting your store and POS now, design the integration so that invoices for business customers end up in one place, usually the ERP or accounting system, from which the e-invoicing provider can collect them. Our guide to e-invoicing integration in the UAE explains the model, and the e-invoicing deadline and penalty calculator shows which date applies to you. This is general information, not tax advice; confirm the details with your tax adviser.
Testing and go-live checklist
Clean the catalogue first. Every product needs one SKU and one barcode, matched across both systems. Most failed integrations fail here, on duplicates and missing codes, not on code.
Count stock before switching on. Do a physical count, or at least a count of the items you will publish online, and load those numbers as the starting point in both systems on the same day.
Test the unhappy paths. A normal sale always works in a demo. Test a failed card payment, a cancelled order, a partial return in a branch, an exchange for a different size, an order for the last unit placed at the same moment as a shop sale, and a sync while the POS is offline.
Run in parallel for a week. Keep the old manual process alongside the integration, compare stock in both systems every day, and fix every difference before you trust it.
Go live on a quiet day. Never in the week before a sale. Choose a weekday morning with your team and your developer available.
Name an owner. Someone in operations should check the sync dashboard daily and know whom to call when it shows a problem.
What it costs and what drives the price
If a maintained connector already exists between your store and your POS and it fits your business, the cost is mostly its subscription and a few days of setup and catalogue clean-up. That is always worth checking first.
A custom integration is a different project. At SmartTech Studio, custom ERP, CRM and POS work, including integrations of this kind, starts from AED 25,000 excluding VAT. What moves the figure is the number of systems involved, the number of branches with their own stock, whether the POS has a usable API, the promotion and pricing rules you need, and whether the ERP and e-invoicing are part of the same project. We quote after a short mapping exercise, using the table earlier in this article, so that the price reflects your data rather than a guess.
If you are still choosing the store itself, our guide to e-commerce website costs in the UAE covers the build side, and our web development service lists the e-commerce package.
FAQ
Can I connect Salla or Zid to a POS in the UAE?
Yes. Both platforms have APIs and app marketplaces. First check whether your POS already has a maintained connector that handles stock per branch and returns. If it does not, a small custom middleware service can connect them and log every sync.
Does stock need to sync in real time?
Stock, orders, cancellations, returns and loyalty points should sync in real time or within a minute or two. Product and price changes can take a few minutes if they are pushed before a promotion starts. Reconciliation reports can run nightly.
Which system should own products and prices?
For most retailers with branches, the POS or the ERP behind it owns SKUs, barcodes, cost and base prices, while the online store owns descriptions and photos. A business that started online may do the reverse. What matters is that each piece of data is edited in one system only.
How do I avoid selling the same item twice on White Friday?
Count stock per location, keep a safety buffer of the last one or two units for the shop, deduct stock when the online order is placed rather than when it is paid, load sale prices the evening before, and watch a dashboard of unsynced orders during the sale.
Does UAE e-invoicing apply to my online store?
Sales to consumers are outside the system in its first phases. Invoices to business customers are in scope from your mandatory date: 1 January 2027 for revenue of AED 50 million or more, and 1 July 2027 for the rest. Confirm your position with your tax adviser.
How much does it cost to connect an online store to a POS?
If a maintained connector fits your business, the cost is mostly its subscription and a few days of setup. A custom integration at SmartTech Studio starts from AED 25,000 excluding VAT, depending on the number of systems and branches and whether the POS has a usable API.