Noon.com E-Commerce Scraper: 1,079 of 1,098 Runs Succeeded (2026)

Extracting retail catalog data from Noon across UAE, Saudi Arabia, and Egypt yields 15 output fields per product, including SKU, selling price, discounts, customer ratings, and promotional tags. Running on Apify's free plan costs $5.00 per 1,000 results, while higher paid tiers offer reduced rates. You can test inputs with the included monthly platform credit without a credit card. This tool suits merchandise teams and competitive intelligence analysts monitoring MENA retail pricing. It is not for anyone who needs merchant seller contact details, which the listing cards do not include.

Try it before you read further. Apify's free plan includes $5.00 of usage every month with no credit card, enough for up to 1,000 results at $0.005 each before platform usage. Open Noon.com E-Commerce Scraper on Apify and run the prefilled example.

How reliable is Noon.com E-Commerce Scraper in production?

Across the last 30 days of public runs on the Apify platform, Noon.com E-Commerce Scraper recorded 1,098 runs with the following outcomes.

Outcome	Runs	Share
Succeeded	1,079	98.3%
Failed	19	1.7%
Aborted by the user	0	0.0%
Timed out	0	0.0%
Total	1,098	100.0%

In scheduled production pipelines, expect about 2 in a hundred runs to fail or time out based on the 1.7% failure rate. Set automated retries for production jobs and build alerts around consecutive failures. Running smaller item caps helps isolate transient issues without sacrificing broader catalog coverage.

What does it cost to run Noon.com E-Commerce Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

Apify plan	Per result	Per 1,000 results
FREE	$0.005	$5.00
BRONZE	$0.00433	$4.33
SILVER	$0.00367	$3.67
GOLD	$0.003	$3.00
PLATINUM	$0.003	$3.00
DIAMOND	$0.003	$3.00

Worked example: collecting 10,000 results costs $50.00 in result charges before run-start fees and platform usage. With 1.7% of runs failing or timing out in the last 30 days, budget for re-running a portion of those batches rather than assuming every run completes.

The maxItems parameter drives your total cost by capping dataset volume directly. When using mode set to search, broad search queries can quickly exhaust capacity up to the 1000 item limit. The cheapest test approach is keeping maxItems at the default 50, which caps result charges at $0.25 on the free plan.

How do you run Noon.com E-Commerce Scraper from the API?

The schema marks 1 of its 8 controls as required: mode. The payload below uses the schema's own prefilled values, so it runs as written once you substitute your API token.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~noon-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","market":"uae","searchQuery":"moisturizer","startUrls":[],"sortBy":"popularity","maxItems":50}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search",
  "market": "uae",
  "searchQuery": "moisturizer",
  "startUrls": [],
  "sortBy": "popularity",
  "maxItems": 50
}

run = client.actor("crawlerbros~noon-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search",
  "market": "uae",
  "searchQuery": "moisturizer",
  "startUrls": [],
  "sortBy": "popularity",
  "maxItems": 50
}

const run = await client.actor('crawlerbros~noon-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

The synchronous endpoint holds the connection open until the run finishes, which is convenient for small batches and wrong for large ones. For anything long running, start the run asynchronously and poll, or attach a webhook, so a dropped connection does not cost you the results.

Which Noon.com E-Commerce Scraper inputs matter, and which can you skip?

The input schema exposes 8 controls, with mode being the only required setting. Switching between search, byCategory, and byUrl controls how pages are discovered, while market dictates the target country. Most users should leave minRating and sortBy untouched on initial test runs.

mode (string): What to fetch from Noon. Default: "search".
market (string): Noon regional website to scrape. Default: "uae".
searchQuery (string): Keyword to search for (mode=search). Default: "moisturizer".
categoryPath (string): Noon category URL path segment, e.g. beauty-personal-care, electronics, home-kitchen. From the URL after /uae-en/.
startUrls (array): Noon search or category URLs. E.g. https://www.noon.com/uae-en/search?q=serum Default: [].
sortBy (string): Product sort order. Default: "popularity".
minRating (number): Only emit products with rating >= this value (0-5).
maxItems (integer): Hard cap on emitted records. Default: 50.

Fixed-choice controls: mode accepts search (Search products by keyword), bycategory (Browse products by category URL path), byurl (Fetch from Noon search or category URL(s)); market accepts uae (noon.com/uae-en), saudi (Saudi Arabia (noon.com/saudi-en)), egypt (noon.com/egypt-en); sortBy accepts popularity, price_asc (Price: Low to High), price_desc (Price: High to Low), discount (Biggest Discount), new_arrivals (New Arrivals).

What does Noon.com E-Commerce Scraper return?

The dataset delivers structured product listings with clean numeric values for price, originalPrice, and discountPercent alongside regional currency codes. It does not provide historical price tracking, seller business registrations, or full user review texts.

name - full product name
sku - Noon product identifier (e.g. N70154922V)
url - direct link to the Noon product page
price - current selling price (numeric)
originalPrice - pre-discount price (numeric, when discounted)
discountPercent - percentage saved (numeric, when discounted)
currency - ISO currency code (AED, SAR, EGP)
rating - average star rating (0-5 scale)
reviewCount - number of customer reviews
brand - brand name (when shown on listing card)
imageUrl - primary product image URL from Noon CDN
promotionTags - active tags, e.g. ["Noon Express", "Free Delivery"]
stockWarning - low-stock message when shown (e.g. Only 2 left)
market - market code: uae, saudi, or egypt
scrapedAt - ISO 8601 timestamp of the scrape

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Noon.com E-Commerce Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

Select mode as search and specify market as uae to test a basic keyword run.
Enter a representative keyword into searchQuery and set maxItems to 10 to limit initial credit consumption.
Run the Actor once and inspect the dataset to verify that numeric price, sku, and currency match the expected marketplace locale.
Switch mode to byCategory or byUrl if you need systematic directory extraction, supplying a valid path like beauty-personal-care in categoryPath or a direct link in startUrls.
Set sortBy to discount, price_asc, or popularity depending on whether your pipeline indexes bargains or core catalog entries.
Apply minRating only if your pipeline requires pre-filtered quality thresholds, keeping in mind it will drop unrated and low-rated products.
Raise maxItems up to 1000 for your production run once record structures and downstream parsing scripts pass inspection.

How do you apply it? Three worked playbooks

These are Noon.com E-Commerce Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Price comparison

Outcome: Track Noon prices against other MENA e-commerce platforms

Configure: Set mode to "search", market to "uae", searchQuery to target matching SKUs or exact product names, and maxItems to 50.

Working method: Start from a single high-priority SKU, verify the returned price and currency against external retailer data, and widen queries across your cross-platform product catalog.

Deliverable: A matched pricing table linking Noon SKU, current price, and competitor identifiers.

Stop condition: Stop if the returned currency fails to match the regional market or if selling prices parse as zero.

Use case 2: Brand presence analysis

Outcome: Measure brand reach and product count across Noon's categories

Configure: Set mode to "byCategory", market to "saudi", categoryPath to "beauty-personal-care", sortBy to "popularity", and maxItems to 500.

Working method: Execute scheduled extractions across top category paths, group returned items by the brand field, and compute catalog share against total listings over time.

Deliverable: A category distribution matrix showing product counts, average ratings, and review volumes per brand.

Stop condition: Halt if more than half of the category records omit the brand property entirely.

Use case 3: Market research

Outcome: Compare product availability and pricing between UAE, Saudi Arabia, and Egypt

Configure: Run three separate jobs with identical searchQuery, setting market respectively to "uae", "saudi", and "egypt", capped at maxItems 100.

Working method: Trigger parallel runs across all three regional markets, normalize prices to a single baseline currency, and compare SKU availability and active promotionTags across borders.

Deliverable: A regional price-variance report highlighting cross-market margins, local stock warnings, and regional discount spreads.

Stop condition: Abort when search queries yield zero results in two or more target markets consecutively.

What breaks, and how do you design around it?

Over the last 30 days, 1.7% of public runs failed and 0.0% timed out. Build retries and alerting around those rates rather than assuming every run completes.

Noon hard caps individual scrape runs at 1000 items, requiring divided query batches for deeper departmental monitoring. Because optional fields like brand and stockWarning omit keys entirely when absent, downstream consumers must use defensive schema parsing. Regional sites maintain separate catalogs, so cross-border comparisons require separate invocations per country.

When should you not use Noon.com E-Commerce Scraper?

Do not use this Actor if you require luxury fashion catalog depth with multi-angle editorial images and designer curation; use Ounass Scraper instead for specialized GCC luxury apparel. If your monitoring scope centers on North American or global cross-border deals rather than regional Middle Eastern retail, Amazon Deals Scraper provides native marketplace department filters across international portals. Furthermore, avoid this Actor if your integration requires an official write-enabled inventory API or real-time webhooks on price shifts, as this extracts static search and category snapshots on demand.

What should you check before trusting the output?

Verify sku exists and follows Noon's alphanumeric format on every record.
Check that price is a positive floating-point number and currency matches the requested market code (AED, SAR, or EGP).
Confirm that discountPercent is null or omitted whenever originalPrice equals price or originalPrice is absent.
Alert if url does not contain the selected regional Noon domain prefix.
Halt downstream ingestion if a completed run emits zero records despite a broad searchQuery or valid categoryPath.

None of this proves a record is correct. It gives a scheduled Noon.com E-Commerce Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What is the run success rate and failure frequency for this Actor?

Out of 1,098 public runs in the last 30 days, 1,079 succeeded, delivering a 98.3% success rate. Exactly 19 runs failed (1.7%), with 0 aborted and 0 timeouts. Practitioners should plan for about 2 runs in a hundred failing and implement standard job retries.

How much does a production scrape cost on Apify's free plan?

The free-plan price is $5.00 per 1,000 results ($0.005 per item), plus platform usage and a run-start fee per execution. Apify's free plan includes $5.00 of monthly usage, which allows you to extract up to 1,000 results each month without paying out of pocket.

Which regional Noon websites are supported?

The market input parameter supports three distinct regions: UAE (noon.com/uae-en), Saudi Arabia (noon.com/saudi-en), and Egypt (noon.com/egypt-en). The scraper automatically pulls localized pricing in AED, SAR, or EGP depending on which market you configure.

What categoryPath format should I supply for byCategory mode?

Supply the URL path segment found directly after the regional path segment (/uae-en/). For example, use electronics, beauty-personal-care, or home-kitchen. Do not paste the entire website URL into categoryPath; complete URLs belong in startUrls under byUrl mode.

Why do some dataset records lack brand or stockWarning fields?

The scraper omits empty fields entirely rather than outputting null values. When a product listing on Noon does not show a brand tag or low-inventory notice, those specific keys are excluded from that record's JSON object.

Where to go next

When you are ready to run it, open Noon.com E-Commerce Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the Noon.com E-Commerce Scraper Actor page for the current input schema, pricing tier, and run history.

If you are comparing approaches rather than committing to one Actor, these category pages list every option we publish:

Review scrapers covers 193 Actors in this family.

Readers running Noon.com E-Commerce Scraper commonly pair it with:

Property Finder Scraper: Scrape property listings from Property Finder (UAE, Saudi Arabia, Qatar, Bahrain, Egypt).
Cartlow Scraper: Scrape Cartlow - Middle East's digital marketplace for gift cards, gaming credits, and entertainment vouchers.
Ounass Scraper: Scrape Ounass (ounass.ae) - luxury fashion e-commerce for the UAE and GCC.
Ozon Scraper - Products, Categories & Search: Scrape Ozon.ru, Russia's largest e-commerce marketplace.
Tiki Product Scraper: Scrape Tiki.vn - Vietnam's leading e-commerce marketplace.
Amazon Deals Scraper: Scrape Amazon's Today's Deals grid (/deals) - discounted products with deal price, list price, savings amount/percent, deal type, brand and department IDs.
Zalora Fashion Scraper: Scrape Zalora with Southeast Asia's leading fashion and lifestyle marketplace.
iHerb Scraper - Vitamins, Supplements & Health Products: Scrape iHerb.com product listings and details.

Related guides:

Resources

Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-24.
Actor last updated by its maintainers on 2026-05-27.
Run outcome figures cover the 30 day public window ending 2026-09-24.
Noon.com E-Commerce Scraper on Apify