Zid Store Catalog & Price Scraper

Products, prices, discounts and stock from any Zid store — the Saudi e-commerce platform behind thousands of shops in Saudi Arabia, Kuwait and the Gulf.

Give it a store link. No API key, no login, no browser, no proxy.

oav.zid.store
https://h3jssz.zid.store/
yourstore.com            (a Zid store on its own domain)

---

What you get

One row per product, 23 fields, every one always present — missing values come back as null, never dropped.

Field	Example
name	ديلينا دي مارلي
price	5.756
regularPrice	11.511
salePrice	5.756
currency	KWD
isOnSale / discountPct	true / 50.0
availability / isAvailable	InStock / true
rating / ratingCount	5.0 / 1
lastModified	2026-09-01T...
changeType / previousPrice	UPDATED / 7.328 (only with Only new or changed products)

Plus store, productUrl, sku, condition, category, imageUrl, imageCount, description, scrapedAt.

Exact prices. Kuwaiti and Bahraini dinars have three decimals. The price is taken from the store's Open Graph tags, which keep all three — not the search-engine block, which rounds 4.111 down to 4.11.

A real discount, not a claimed one. isOnSale is true only when the sale price is genuinely below the regular price.

lastModified is the date the store's sitemap reports for the product.

---

Input

Input	Default	What it does
stores	["oav.zid.store"]	Store links or domains. The same store given twice is read once.
maxProductsPerStore	1000	Stop after delivering this many products from a store. Pages without product data and products left out by onlyOnSale do not count, and no page past the cap is opened. With onlyChanges it counts products checked.
onlyOnSale	false	Only products with a real discount.
onlyChanges	false	Monitoring mode — see below.
skipUnchangedPages	false	With onlyChanges: do not open a product page whose sitemap lastmod is the same as last run. Off by default — see below.
fullRefreshHours	24	With skipUnchangedPages: at least this often, open every page regardless of lastmod — see below.
stateStoreName	zid-catalog-state	Named key-value store that keeps the snapshot between runs. Use one name per independent monitor.

---

Monitoring: only new or changed products

Turn on onlyChanges and schedule the Actor. Each run compares every product with the last run and delivers only:

• NEW — a product not seen before (the first run delivers every product as NEW), or
• UPDATED — its price, regularPrice, salePrice or availability changed; previousPrice holds the price from the last run, changedFields names the fields that moved and previousValues holds all four from the last run (both null on NEW rows).

By default every product page is opened and compared, so no change is missed. Turn on skipUnchangedPages to skip pages whose sitemap lastmod date has not changed since they were last read — a quiet store then costs almost nothing to watch. Measured 15 Sep 2026 on oav.zid.store (62 products): with skipping on, the second run opened no product pages and finished in 0.5 s.

Honest limits of monitoring:

• Skipping relies on the store updating lastmod when a product changes. We have not confirmed that Zid does this for price or stock changes, which is why skipUnchangedPages is off by default.
• To bound that risk, a skipping monitor still does a full refresh — every page opened, lastmod ignored — whenever the last full refresh is fullRefreshHours (default 24) old. A full refresh is recorded only when it read every sitemap and every page: a failed or unreadable sitemap, a failed or blocked page, maxProductsPerStore leaving pages unread, or the spending limit all mean it is not recorded, and the next run tries again. A snapshot saved by an older build has no recorded full refresh, so its first run after the upgrade opens every page. The run report shows fullRefresh and fullRefreshRecorded per store. A store whose sitemaps keep failing is therefore read in full on every run — slower, but nothing is skipped on the strength of a list that may be incomplete.
• Skipped products do not count toward maxProductsPerStore. With a cap smaller than the catalog, each run checks the next products whose pages changed or were never read.
• The snapshot is saved only when a store was read to the end (or to the cap). A store cut off by your spending limit keeps its old snapshot, so nothing is missed next run.

---

Use it for

• Competitor price monitoring — onlyChanges on a schedule
• Discount tracking — turn on onlyOnSale, sort by discountPct
• Stock-out alerts — watch availability change to OutOfStock
• Catalog and market research across Saudi and Gulf stores

---

How it works

1. Reads the sitemaps named in the store's robots.txt, then sitemap.xml and its product sitemap — the list of every product the store publishes for search engines.
2. Opens the product pages several at a time, retrying a page that fails.
3. Reads the structured product data on each page (JSON-LD, including @graph blocks, plus Open Graph).

Measured 15 Sep 2026 on a home connection (speed on Apify's servers will differ):

Run	Products	Time
h3jssz.zid.store, whole catalog	143	34.7 s
oav.zid.store + h3jssz.zid.store, 20 each	40	14.7 s
oav.zid.store, onlyChanges + skipUnchangedPages, second run, nothing changed	0 (62 skipped)	0.5 s

Zero failed pages in all three.

---

Honest notes

robots.txt is respected. Zid disallows its /api/ path, so this Actor does not touch it — it reads only the product pages the store allows.

Only published products. A product the store left out of its sitemap is not found. Hidden and draft products are never collected.

Only public stores. Links to IP addresses, ports, user:password@ links and names that point to private or internal addresses are refused, and every request — including redirects — is checked before it is sent.

No personal data. Reviews' authors are not collected; only the rating and the number of ratings.

A store that yields nothing is named in the run's status message and under notReached in the run report. A store the run never got to because your spending limit was reached is listed separately, under notReachedSpendingLimit.

Every run publishes a report to the key-value store under RUN_REPORT. For each store: pages in its sitemap, products delivered and checked, pages skipped as unchanged, pages without product data, failed pages, and a summary of what was read — products, how many on sale, how many out of stock, and the minimum, median and maximum price. The summary comes from the pages already read, with no extra requests.

---

Questions, or a store that returns nothing?

Open an issue with the store link.