Merchant Center May Now Disapprove Products Whose Price Changes More Than Once a Day: A White Friday Price-Markup Audit of Arab Online Stores

Google now warns that fast-changing prices can get Shopping products disapproved. Its Merchant Center help page, revised on 27 September 2026, says automatic item updates “may not work” when a price changes more than once a day. On 11 October 2026 we read 40 product pages from Arab online stores. Of the 24 that showed a discount, none carried sale dates in readable price markup.

That gap matters most in White Friday week, when flash sales can move a price several times in one day. Below are Google’s exact words and what 40 Salla, Zid, Shopify and WooCommerce pages in Saudi Arabia, the UAE and Egypt put in their price tags. Then come the Saudi Ministry of Commerce rule on showing both prices and a checklist for the weeks before the sale.

What did Google change on the Merchant Center automations page?

Google added a warning to its page on automatic item updates. Automations, it now says, “may not work for products with frequent price or availability value changes (for example more than once per day). The product may be disapproved instead of updated if we detect a mismatch.” A second sentence adds that updates can stop once mismatches pile up.

Automations are on by default. They read the price, availability and condition on your product page and correct Merchant Center when your feed disagrees. Google’s own example is a feed that says $4 while the page says $3, so the ad shows $3. The current help page narrows that safety net: “We may also stop updates if the total number of detected mismatches becomes too large.” It describes automations as a fix for “sporadic problems” affecting “a small percentage of your products”. Stores whose prices change frequently, it says, “should use the Merchant API”.

PPC News Feed dates the revision to 27 September 2026, and Search Engine Roundtable reported it on 8 October. One detail shows how far the advice moved. On 11 October we fetched the same URL without its English language parameter, and Google served an older version. Its best-practice list said that when most prices update “multiple times per day, then automations can help you avoid errors”. The current English page no longer carries that line.

Google’s note names a trigger, and it is narrower than some headlines suggest. A price change alone does not disapprove anything. The disapproval follows a mismatch that Google detects between the page and your product data. A fast flash sale creates exactly that.

Why do White Friday flash sales collide with this rule?

Automations compare two snapshots taken at different times: the price Google crawls on your product page and the price in your feed. A flash sale that moves the page price twice in one afternoon opens two windows in which the feed and the page disagree. Each window is now a chance for a disapproval rather than an automatic fix.

White Friday 2026 is expected to run from 27 to 30 November, as our Snapchat catalogue rules for Arab stores worked out from Amazon Ads’ guidance. That leaves 47 days from our 11 October audit. A flash deal is built to change price during the day, which is the pattern Google’s note describes, whether the store sells in Saudi Arabia, the UAE or Egypt.

Google’s page names the fixes it expects. For sale prices, it asks that “the time period in which the sale is active is specified correctly” with the sale price effective date attribute. It also asks that “the timezone is correct”. Any strikethrough price on the page must match the regular price attribute when a sale price is also provided. If a page shows more than one strikethrough price, Google says: “You shouldn’t enable automatic updates for price in this case.”

Speed is the risk, and the markup decides whether a fast change reads as an error.

How we checked 40 Arab product pages

We fetched 40 public product pages on 11 October 2026: 10 stores each on Salla, Zid, Shopify and WooCommerce. Twenty-six are Saudi stores, 7 sell in the UAE and 7 in Egypt. On each store we took the first discounted product on the homepage, or the first product link when none showed a discount, and read that page once.

The plan was to compare each visible price with the page’s Product JSON-LD. Our fetch tool turns pages into text and drops script blocks and microdata attributes, so on all 40 pages the JSON-LD was not visible to us. We did not guess. We switched to the price meta tags the fetch does show: product:price:amount, product:sale_price:amount, og:price:amount, their currency fields and product:availability.

That layer is a second machine-readable price on the same page, not the schema.org markup Google’s automations page documents. Read our counts as a check of what each store’s template writes into price fields. Our Salla and Zid store audit from 2 October, which read raw HTML, found Product JSON-LD with price and availability on 19 of 20 product pages. So a missing script in our fetch says something about the tool and nothing about the store.

What the price markup on 40 pages showed

The basics held. Every readable price tag carried Western digits and a three-letter ISO currency code, and none disagreed with the price on screen when we fetched it. The gaps sat in sales: 24 pages showed a discount, only 12 of them put the original price in their markup, and none said when the sale ends.

The platforms split cleanly. Salla and Zid templates wrote both a regular price and a sale price into their tags on every page. That is why all 12 discounted pages on those two platforms carried the original price. Eight of 10 Shopify pages wrote one value, the current price, and 2 wrote none; 6 of 10 WooCommerce pages wrote no price tag at all.

Which of these gaps can trip Merchant Center automations?

Four of our findings match warnings on Google’s page: no sale end time in the markup, strikethrough prices the markup never mentions, stray second prices and thousands separators. A fifth, prices served in another currency depending on where the visitor sits, is a crawler risk worth testing on your own store before the sale.

• None of the 24 discounted pages declared when the sale ends in its readable markup. If your feed carries sale dates and the page does not, the two sources can disagree at the minute a flash deal starts or stops. You control both sides.
• On 12 of 24 discounted pages the markup held only the current price, or nothing, while the page showed a crossed-out price. Google asks that the strikethrough match the price attribute you submit.
• Seven pages carried a second value that was not a real reduction. It was a 0 in the sale slot, a 0.00 promotion card or a crossed-out price equal to the current one. A text fetch cannot tell whether these are hidden on screen, but an extractor reading the page can meet them.
• Two Shopify pages wrote prices such as 3,799 into the og:price:amount tag. Google’s format for the schema.org price is a number with no separators, so check that your JSON-LD does not copy the same formatting.
• Four Saudi store pages served our fetch in US dollars, with matching USD tags. Google says the currency should meet the requirements of your target country, so confirm what a crawler outside Saudi Arabia receives. Your Saudi shoppers never see the dollar version. A crawler from elsewhere can.

Availability was cleaner. One pre-order page was tagged in stock, and Google’s relaxed matching treats preorder as compatible with in stock, so that case does not cause a mismatch. Six Zid pages had an out-of-stock string in their page text next to an in-stock tag. It looks like a hidden template block, and we were unable to confirm what shoppers see, so we did not count them.

Advertising on Google Shopping this November? Check my Shopping feed and price markup before White Friday.

What does Saudi Arabia’s discount rule add for online stores?

It makes the second price mandatory for Saudi stores. The Ministry of Commerce’s nine rules for businesses and e-stores (26 September 2022) require a permit before a price reduction is announced. Rule five reads: “Discounted products must have a tag showing the original price and the discounted price.” For Google, that original price is the strikethrough automations read.

The ministry enforces the display side. Around National Day 2025 it ran 14,164 field visits, checked price tags or electronic price readers “showing the price before and after the discount”, and issued 348 instant violations. The same rules say advertising in electronic stores must follow the ministry’s advertising rules, and misleading discounts fall under the Anti-Commercial Fraud Law.

So a Saudi store cannot solve the strikethrough problem by hiding the old price. The fix runs the other way: show exactly one original price, the licensed one, and put the same value in the feed’s price attribute and in the page markup. We did not verify equivalent rules for the UAE or Egypt on official pages for this piece, so stores there should check with their own regulator. This is not legal advice.

A price checklist for the weeks before White Friday

Fix the markup in October, rehearse one price change in early November, and plan every sale-week price change as a scheduled update rather than a manual edit. The order below puts the cheapest checks first and the API work last.

1. Open one discounted product per template in Google’s Rich Results Test and read the price, priceCurrency and availability it finds. Our fetch was unable to see JSON-LD, so this step is yours.
2. Keep price values as plain numbers with a full stop for decimals, such as 1299.00, and the currency as SAR, AED or EGP. Remove thousands separators from every price tag.
3. Show one strikethrough price per product and delete theme leftovers such as a 0 in the sale slot or a crossed-out price equal to the current one.
4. Send sale_price with sale_price_effective_date in the feed, with the UTC offset of the market you sell in, for every White Friday deal.
5. List the products whose price will change more than once a day. For those, schedule feed refreshes or Merchant API updates at each change instead of relying on automations to catch up.
6. Check what a visitor from outside your country receives. If a Saudi page switches to dollars, confirm the landing page Google crawls shows the currency in your feed.
7. For Saudi stores, match the strikethrough to the licensed original price and keep the Ministry of Commerce permit details to hand before the sale is announced.

The same clean price data serves other channels. Our ChatGPT shopping ads plan for White Friday uses the same sale_price discipline. Our structured data review of Arabic websites shows the plain-digit price format in code.

Our read

For most Arab stores the September note changes the sale-week plan and leaves the store itself alone. Every readable price in our sample matched the page, so ordinary days look fine. The White Friday risk is a discount that the page announces and the markup never explains.

Your slow sellers are not the problem. We would treat automations as a backstop for the slow-moving catalogue and take the fast movers out of their hands. Put every hourly or daily deal on a scheduled feed or API update, with dates, and keep the page’s strikethrough honest and single. For Saudi stores the ministry already requires that second price, so the work is making the feed say the same thing.

We would not rebuild themes before the sale. Shopify and WooCommerce stores have more to check than Salla and Zid stores, but most of it is template settings and feed timing.

What this audit does not show

Forty pages, one product each, read once on one afternoon, cannot show how frequently prices change on these stores or whether any product has been disapproved. A single fetch also cannot catch a lag between feed and page, because that needs two readings over time. We saw no mismatch, and that is the expected result for one snapshot.

Our fetch was unable to see JSON-LD or microdata, which is what Google’s page documents, so our counts describe price meta tags. Many fetches failed and were replaced with other stores, and we name no small store.

FAQ

My Shopping products were disapproved during a flash sale. Is the new note the cause?

It is one candidate. Google’s automations help page now says a product whose price changes more than once a day faces disapproval instead of an update when Google detects a mismatch. Check the product’s issue in Merchant Center, then compare the time of each page price change with the time your feed last refreshed.

Should I turn off Merchant Center automatic price updates for White Friday?

Not by default, because they still fix occasional mismatches. Google says to switch off price automations when your pages show more than one strikethrough price. For products that change price several times a day, Google points to the Merchant API, so plan scheduled feed or API updates for every price change.

Does Google read the price shown on my Salla or Zid product page?

Yes. Automations read structured data on the product page and, where markup is missing or wrong, use extractors on the visible page. Our 2 October audit found Product JSON-LD with price and availability on 19 of 20 Salla and Zid product pages, so most stores start with working markup.

Do I need to show the old price next to the sale price in Saudi Arabia?

Yes for discounts. The Saudi Ministry of Commerce’s nine rules for businesses and e-stores say discounted products must carry a tag with the original and the discounted price. A permit is also needed before a price reduction is announced. This is not legal advice; check the ministry’s current rules.

Can my product markup use prices like 1,299 or Arabic numerals?

No. Google’s automations page asks for price as a plain number without currency symbols, thousands separators or spaces, such as 1498.99, and for a three-letter ISO 4217 currency code. Show Arabic numerals and local currency signs to shoppers on the page, and keep the markup in plain Western digits.

The better question

Whether Google will disapprove a product for changing price is the smaller question. The one worth asking before White Friday is whether your feed and your page will say the same thing, with the same dates, at every minute of a flash sale. A price that changes on schedule, with one honest strikethrough, is a price Merchant Center can follow.

If your sale prices already go out through scheduled feed or API updates with effective dates, spend October checking templates for stray prices and separators. If they do not, set that up first and keep automations for everything else. Either way, help me plan White Friday price changes without disapprovals.