Most UAE Merchant Center disapprovals come down to one thing: the price Google reads in your feed is not the price it finds on your product page. VAT is the usual culprit. Google compares the two automatically, and a five percent gap is enough to pull the product out of Shopping without any warning you will notice.
The short version
- Your feed price must include VAT, because the price shown to a UAE shopper on the landing page includes it. Send the pre-VAT price and you fail the price mismatch check.
- Disapprovals are silent by default. Nothing stops, nothing errors. Impressions just fall and the products quietly leave the auction.
- Price mismatch, missing GTIN and availability drift are the three that account for most of what we find in UAE accounts.
- Fix the feed before touching bids. A campaign bidding hard on a half disapproved catalogue is optimising against inventory it cannot sell.
Why does VAT cause so many disapprovals here?
The UAE applies VAT at five percent, and consumer prices are quoted inclusive of it. Your Shopify or Salla storefront shows the inclusive price to the shopper.
The feed is where it goes wrong. Depending on how your product data is exported, the price attribute can carry the net figure instead. Google then crawls your landing page, sees a different number, and treats it as a mismatch.
From the outside this looks like nothing happened. There is no failed build, no broken campaign. Impressions on the affected products drop toward zero and the account average quietly gets worse.
The rule is simple enough to check in a minute. Open the feed, open the product page, and confirm the two numbers are identical to the fils. Not close. Identical.
What are the disapprovals we actually find most often?
| Disapproval | What causes it in a UAE account | Fix |
|---|---|---|
| Price mismatch | Feed carries the pre-VAT price, landing page shows inclusive | Export the inclusive price. Confirm currency is AED on both sides. |
| Missing GTIN | Local and private label products genuinely have no barcode | Set the identifier exists attribute to no rather than leaving it blank. |
| Availability mismatch | Feed says in stock, page says sold out after a fast selling day | Increase feed fetch frequency, or use the content API for stock. |
| Image issues | Promotional overlays and watermarks on product shots | Clean product image in the feed, marketing versions in the ad creative. |
| Currency mismatch | Store shows a converted currency by IP, feed declares AED | Force AED for the UAE feed, or run a separate feed per country. |
How do you find them if nothing tells you?
Check the diagnostics tab in Merchant Center weekly, not when something looks wrong. By the time performance visibly drops you have usually been serving a reduced catalogue for a fortnight.
The number to watch is not the count of disapproved items. It is the share of your revenue those items represent. Twenty disapproved products sounds minor until you notice they are your twenty best sellers, which happens more often than chance would suggest, because best sellers are the ones whose stock and price change most.
Does any of this actually move the numbers?
It moves them more than bidding does, in the accounts we take over.
On the UAE craft supplies account we run, the last ninety days returned AED 213,502 in conversion value on AED 39,372 of spend, which is 5.1 times. That account is not winning because of a clever bidding strategy. It is winning because the feed is clean, the catalogue is fully approved, and Performance Max has the whole inventory to work with rather than the fragment that survived the last disapproval sweep.
We wrote about the structural side of this in Performance Max for UAE stores, and the feed first build in how we run Google Shopping for UAE stores.
A mistake we made: on one account we fixed a price mismatch by editing the feed rule and moved on the same afternoon. What we missed was that the store ran a scheduled promotion every Thursday, which rewrote prices on the page but not in the feed until the next fetch. So the catalogue was compliant six days a week and disapproved on the busiest one. We now check the feed against the page on a promotion day rather than a quiet one.
If your Shopping performance dropped without an obvious cause, the feed is the first place we look. Book a growth call and we will go through the diagnostics with you. Or see how we manage Google Ads and Shopping accounts.
Frequently asked questions
Yes. The price in your feed should match the price a UAE shopper sees on the landing page, which is VAT inclusive. Sending the net price creates a mismatch between the feed and the page, and Google disapproves the product for it.
Disapprovals do not stop a campaign. The affected products simply leave the auction while everything else keeps running, so you see a gradual fall in impressions rather than a failure. Check the diagnostics tab in Merchant Center rather than waiting for an alert.
Set the identifier exists attribute to no. Private label and handmade products often have no barcode, and declaring that explicitly is accepted. Leaving the field blank is what causes the disapproval, not the absence of a barcode.
Weekly, and always on a promotion day. Scheduled price changes are the most common way a compliant catalogue becomes non compliant, because the page updates before the next feed fetch does.
The feed, every time. Bidding harder on a partially disapproved catalogue spends more money against the inventory that happens to still be eligible, which is rarely the inventory you most want to sell.