Home > > > Retail Data API Saudi Arabia: Arabic-English Feeds (2026)

Retail Data API Saudi Arabia: Arabic-English Feeds (2026)

Author : Actowiz Solution | Published On : 02 Nov 2026

Introduction

Saudi Arabia is one of the most data-hungry retail markets in the Gulf. The Ministry of Commerce counted 43,854 e-commerce commercial registrations at the end of Q4 2025, up from 40,041 a year earlier, with Riyadh, Makkah and Eastern provinces leading (Sharikat Mubasher, citing MoC). More online sellers mean more prices, more promotions and more catalogue changes to track every day.

What is a retail data API for Saudi Arabia? A retail data API for Saudi Arabia is a managed feed that collects public product, price, promotion, stock and seller data from KSA marketplaces and retailer websites, matches Arabic and English listings to one product record, normalises prices in SAR (including 15% VAT), and delivers it on a fixed schedule through REST API, S3, Snowflake or BigQuery.

This guide is for data and analytics heads, e-commerce directors and pricing teams at brands, retailers and distributors selling in KSA. It focuses on the engineering and governance side: which sources matter, how bilingual matching works, what a realistic SLA looks like, what the Saudi PDPL means for a public-data feed, and what to put in your RFP.

Why do enterprises in Saudi Arabia need a retail data API?

 

Spreadsheets and one-off scrapes break down quickly in KSA. Listings appear in Arabic and English, the same product carries different titles on each platform, and prices change several times a day around Ramadan, White Friday and payday weekends. A retail data API turns this into a stable, documented feed that your BI, pricing engine or data warehouse can rely on.

  • Pricing teams use daily or intraday SAR prices to check price index, MAP / MRP compliance and promotion depth versus key competitors.

  • E-commerce and category directors track assortment gaps, new launches, out-of-stocks and search visibility by city.

  • Brands and distributors monitor authorised and unauthorised sellers, content compliance and Buy Box ownership on marketplaces.

  • Data and analytics heads need one clean schema, change logs and QA reports – not ten different scraper outputs.

Which Saudi platforms and retailers should a retail data API cover?

Coverage should follow where your category actually sells. The table below shows the main public online channels in KSA and what each one typically adds to a feed. Exact coverage, fields and refresh are confirmed during scoping, and only publicly visible data is collected.

 

  • Marketplaces: Amazon.sa, Noon — What it adds to the feed: Multi-seller prices, Buy Box / featured offer, ratings, delivery promises — Data notes: Many sellers per product; Arabic and English page versions

  • Fashion & lifestyle: Namshi, brand stores of global fashion retailers — What it adds to the feed: Sizes, colours, size availability, sale prices — Data notes: Large, fast-changing catalogues; frequent markdowns

  • Electronics & office: Jarir, eXtra — What it adds to the feed: Model-level prices, bundles, instalment offers, stock by store/city where shown — Data notes: Model numbers help matching; promotions tied to bank cards

  • Grocery & pharmacy: Tamimi Markets Online, Nahdi; other chains with public online stores — What it adds to the feed: Pack-size prices, multi-buy promotions, availability by city — Data notes: City or store selection changes price and stock

  • D2C brand stores: Stores built on Salla or Zid — What it adds to the feed: Brand-direct prices, launches, bundles — Data notes: Many small stores; consistent templates help scale

In-body image 1: ksa-bilingual-product-matching-flow.png | Alt: 'Arabic and English product titles matched to one canonical SKU'

What data fields should a Saudi retail data feed include?

A good schema is agreed before the first crawl. These are the field groups most enterprise buyers in KSA ask for:

  • Identity: platform, product ID / ASIN / SKU, product URL, brand, model number, GTIN where publicly shown, canonical match ID.

  • Bilingual content: title_en, title_ar, description_en, description_ar, category path in both languages, attributes (size, colour, volume, pack count).

  • Price in SAR: list price, sale price, unit price, currency, VAT-inclusive flag. Consumer prices in KSA are normally shown including VAT, which has been 15% since 1 July 2020 (ZATCA).

  • Promotions: discount %, coupon text, bank-card or BNPL offer text, bundle and multi-buy rules, event tag (Ramadan, White Friday, 11.11).

  • Availability: in stock / out of stock, size-level availability, delivery promise, and city context (Riyadh, Jeddah, Dammam) where the site prices or stocks by location.

  • Sellers: seller name and seller ID as publicly shown for businesses, number of offers, fulfilment type (e.g. marketplace-fulfilled vs seller-fulfilled).

  • Ratings & rank: rating, review count, search or category rank for tracked keywords.

  • Metadata: crawl timestamp (UTC and Asia/Riyadh), source language, change flags versus the previous run.

How does bilingual Arabic-English matching work?

Bilingual matching is where most KSA feeds succeed or fail. The same perfume can appear as an English title on one site, an Arabic title on another, and a mixed title on a third. A solid retail data API handles this in layers:

  • Collect both language versions of each product page where the site offers them (for example /en/ and /ar/ paths), rather than machine-translating one side.

  • Normalise text: unify Arabic letter forms (such as alef and taa marbuta variants), strip diacritics, convert Arabic-Indic digits (٠-٩) to Western digits, and standardise units (مل / ml, جم / g).

  • Use hard keys first: model numbers, GTINs where visible, brand + size + variant.

  • Then fuzzy and semantic matching across languages, with confidence scores and a human review queue for low-confidence pairs.

  • Keep a match table (canonical ID to platform IDs) that you can audit, override and version over time.

How is the feed collected, checked and delivered?

Enterprise buyers should ask for the full pipeline, not just a scraper. A typical Actowiz set-up for KSA looks like this:

 

  • Collection: Scheduled crawls of public pages per platform, city and language; respectful rate limits; no logins bypassed — What to ask a provider: Which pages, which cities, how often, and what happens when a site changes

  • Normalisation: SAR prices parsed, VAT flag set, units and sizes standardised, Arabic text normalised — What to ask a provider: Show a sample with raw vs normalised values

  • Matching: Bilingual product matching to your master list with confidence scores — What to ask a provider: Match-rate on our SKUs; how overrides work

  • QA: Schema checks, null-rate and price-jump alerts, row-count vs previous run, manual spot checks — What to ask a provider: Daily QA report; what is a breach and how fast is it fixed

  • Change monitoring: Diffs on price, stock, title, image and seller; site-layout change alerts — What to ask a provider: Change log format and alert channel

  • Delivery: REST API (JSON), CSV/JSON files to S3 / Azure / GCS, direct loads to Snowflake or BigQuery — What to ask a provider: Delivery time in Asia/Riyadh, retries, history retention

SLA: agree delivery time, freshness (for example daily by 07:00 Riyadh time, or intraday during events), completeness target per source, and response time for breakages. Avoid any provider promising '100% accuracy' – public websites change, and good providers show how they detect and repair gaps. A sample feed can usually be shared within 48 hours of a scoped request.

In-body image 2: ksa-retail-feed-delivery-architecture.png | Alt: 'Saudi retail data feed delivered via REST API, S3, Snowflake and BigQuery'

How should feed frequency change by category and season?

Refresh rate drives cost and value. Match it to how fast each category moves and to the KSA retail calendar. Ramadan and the two Eids follow the Hijri calendar and move roughly 11 days earlier each year; Saudi National Day is fixed on 23 September (Argaam); White Friday runs in late November across Saudi Arabia and the UAE (Amazon Ads); and Amazon.sa has run an 11.11 sale (Arab News, sponsored).

 

  • Consumer electronics (Jarir, eXtra, marketplaces): Normal refresh: Daily — Event refresh: 2–4x daily around White Friday, 11.11 and National Day — Key fields: Model price, bundles, card offers, stock

  • Fashion & footwear: Normal refresh: Daily — Event refresh: Daily plus markdown diffs during Ramadan/Eid and end-of-season sales — Key fields: Sale price, size availability, new arrivals

  • Grocery & FMCG: Normal refresh: Daily or weekly — Event refresh: Daily through Ramadan and pre-Eid — Key fields: Pack price, multi-buy, availability by city

  • Health & beauty / pharmacy: Normal refresh: Weekly to daily — Event refresh: Daily during White Friday and gifting seasons — Key fields: Promo depth, bundles, OOS

  • Seller / MAP monitoring: Normal refresh: Daily — Event refresh: Intraday on hero SKUs — Key fields: Seller list, lowest offer, Buy Box

In-body image 3: ksa-retail-event-calendar.png | Alt: 'Saudi retail event calendar – Ramadan, Eid, National Day, White Friday, 11.11'

Use cases for a retail data API in Saudi Arabia

  • Price index and competitive response: daily SAR price index by category against named competitors, with VAT handled consistently.

  • Promotion intelligence: depth, mechanics and timing of discounts around Ramadan, Eid, National Day and White Friday.

  • Assortment and launch tracking: new SKUs, delistings and range gaps across Amazon.sa, Noon and specialist retailers.

  • Digital shelf and content compliance: Arabic and English titles, images and attributes versus your brand guidelines.

  • Seller and channel governance: spot unauthorised sellers and below-policy offers on marketplaces.

  • City-level availability: compare stock and delivery promises in Riyadh, Jeddah and Dammam where sites expose them.

What does the Saudi PDPL mean for a retail data feed?

Saudi Arabia's Personal Data Protection Law (PDPL) is overseen by the Saudi Data and Artificial Intelligence Authority (SDAIA; see also SDAIA's PDPL guide). It entered into force on 14 September 2023, and enforcement began after a one-year grace period in September 2024 (Baker McKenzie).

In plain words: the PDPL governs data that identifies people. A retail data feed should be built around product, price, promotion, stock and business-seller data – not shoppers. Actowiz feeds exclude personal data such as reviewer names, profile links or contact details unless there is a clear lawful basis, and we do not log in to or bypass protected areas.

  • Data residency: product and price data is not personal data, but your security team may still prefer storage in a specific cloud region. Ask where the feed is processed and stored, and whether delivery to a KSA or GCC region bucket is possible.

  • Usage rights: agree in the contract how the data may be used internally and whether it can be shared with agencies or partners.

  • Site terms: a provider should respect each site's terms and robots guidance and explain its approach.

This is general information, not legal advice. Speak to your counsel about your specific use case.

Build vs buy: what should go in your RFP?

Some teams start with an in-house scraper and move to a managed feed once bilingual matching, anti-bot changes and event-season load become a full-time job. Use these points to compare options:

 

  • Source list by platform, category and city: Prices and stock can differ between Riyadh, Jeddah and Dammam

  • Arabic + English capture and matching method: Avoids duplicate products and missed competitors

  • Field dictionary with SAR / VAT rules: Keeps price indices comparable across sites

  • Refresh plan incl. event mode: Ramadan, White Friday and 11.11 need higher frequency

  • Delivery options (API, S3, Snowflake, BigQuery): Fits your existing data stack

  • SLA, QA reports and change monitoring: Defines what 'good' looks like and how breaks are fixed

  • PDPL position, data residency and security: Answers your legal and InfoSec reviews early

  • 48-hour sample on your own SKUs: Proves coverage and match quality before you sign

Frequently Asked Questions

What is a retail data API for Saudi Arabia?

It is a managed feed of public product, price, promotion, stock and seller data from KSA marketplaces and retailers, normalised in SAR, matched across Arabic and English listings and delivered by API or cloud storage on a fixed schedule.

Can you deliver both Arabic and English titles and descriptions?

Yes. Where a site offers both language versions, we collect each one and link them to the same product record, so you get title_en and title_ar side by side.

Are prices delivered including VAT?

Consumer prices in KSA are usually shown including the 15% VAT. We capture the displayed SAR price and add a VAT-inclusive flag so you can calculate net prices consistently.

How fresh is the data and how is it delivered?

Daily is the most common cadence, with intraday runs available for hero SKUs and event periods. Delivery options include REST API (JSON), CSV/JSON to S3, Azure or GCS, and loads into Snowflake or BigQuery.

Does the feed include personal data?

No. Feeds are built on product and business-seller data. Shopper or reviewer personal data is excluded, in line with the Saudi PDPL. Please check specific questions with your counsel.

How quickly can we see a sample?

After a short scoping call, a sample on your own SKUs and platforms can usually be shared within 48 hours.

 

Conclusion

You can also reach us for all your mobile app scraping, data collection, web scraping, and instant data scraper service requirements!