Platform · Ounass

Ounass Data Scraping

The same designer piece, priced for the Gulf. Whether and by how much that differs from Europe is a measurement — if it is made properly.

Ounass data scraping collects luxury product listings, prices and availability for GCC markets. The question clients most often bring is the regional price gap: is the same designer piece priced differently in the Gulf than in Europe? That is answerable, but only from paired records — same style and colourway, observed on a shared schedule, with both currencies and both tax bases recorded. Asserted regional premiums are the most repeated and least checked figure in luxury retail.

Everyone has a view on how much more luxury costs in a given region. Very few of those views came from paired records.

Get a free sample See sample data

Free pilot on your own Ounass list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

ounass.jsonl LIVE FEED

{"retailer":"ounass","country":"AE", "brand_style_code":"as published","colourway_code":"as published", "price":9450.00,"currency_displayed":"AED", "panel_schedule_id":"gcc-eu-luxury-sync"} {"comparator_retailer":"eu-stockist","comparator_market":"FR", "comparator_price":2200.00,"comparator_vat_basis":"inclusive", "regional_gap_pct":7.8,"gap_basis":"both tax-inclusive as displayed"} {"regional_gap_pct":"null", "gap_null_reason":"comparator_in_markdown_window"}

3 of 404,110 product rows · GCC vs EUa premium is measured, never asserted · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Ounass or its owners. Ounass and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Ounass at a glance

How we handle Ounass specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Retailer: Ounass — GCC luxury
The question: Regional price gap against Europe
Answerable: Only from paired records
Pairing needs: Style code, colourway, shared schedule
And: Both currencies and both tax bases
So: regional_gap_pct computed, never asserted
Markets: Several GCC countries
Refresh: Daily where the gap is the question

Platform specifics

Measuring a regional premium properly

These are the reasons a Ounass dataset needs its own handling rather than a shared retail schema.

Four things a regional gap needs

A regional premium is a comparison of two prices for one product in two places. Each part can go wrong.

Same product — style code and colourway code, both. A similar bag is not the same bag.
Same time — a shared schedule, because markdown timing differs by region and a gap measured across a markdown boundary is a timing artefact.
Tax basis — European prices are typically VAT-inclusive at European rates; GCC prices carry a different basis, and some markets have none.
Currency — FX stamped at both observations, local currencies retained as primary.

We deliver regional_gap_pct only where all four hold, with the European comparator named and gap_basis stating whether the comparison is tax-inclusive on both sides. Where they do not hold, the field is null with a reason.

And the gap moves

Because markdowns start at different times, the gap is a series rather than a number. We deliver it over time rather than as a single figure.

Markets, calendar and scope

Several GCC markets

country and vat_basis on every price, as on our Namshi page.

Calendar

Regional sale events and Ramadan shift the timing of markdowns relative to Europe, which is part of why the gap moves. days_from_ramadan_start travels with every record.

European comparators

Typically a European luxury retailer or the brand's own European site, collected on the same schedule — see our Farfetch page for delivery-market handling.

What we do not collect

Customer data, stock quantities, or a regional premium asserted without paired records.

Scope

What we collect on Ounass, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

regional_gap_pct only where product, time, tax basis and currency all hold
The European comparator named on every gap
gap_basis stating the tax treatment on both sides
Gap delivered as a series over time
Style code and colourway code required to pair
Shared schedule across regions
country and vat_basis on every price
days_from_ramadan_start on every record
FX stamped per observation, local currencies primary

❌ What we do not, and why

A regional premium asserted without paired records
A gap measured across a markdown boundary
A gap with different tax bases unstated
A similar product paired as the same product
Customer data or stock quantities

Core Ounass fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
retailer / country / vat_basis	The GCC market and its tax basis
brand_style_code / colourway_code	Both required to pair
price / currency_displayed / fx_observed_at	As displayed, stamped
comparator_retailer / comparator_market	The European side, named
comparator_price / comparator_vat_basis	Its price and basis
regional_gap_pct / gap_basis	Computed only where all four hold
gap_null_reason	Where they do not
markdown_started_at	Per region
days_from_ramadan_start	Calendar alignment
panel_schedule_id	Shared across regions
observed_at	Timestamp

Use cases

What teams do with Ounass data

Regional luxury price gap

Paired records across the GCC and Europe with tax basis and currency stated, delivered as a series rather than an asserted premium.

Markdown timing by region

When markdowns start in the Gulf against Europe, which is part of why the gap moves.

GCC luxury range

Which designers and styles are carried for the region.

Per-market GCC pricing

Country and tax basis on every price across the region's markets.

The 24-hour sample — run on your sources, not ours

Send us a Ounass item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Ounass is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Ounass data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what fashion & apparel data covers, and a Ounass-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Ounass data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

That is measurable, product by product, but only from paired records — same style and colourway, same schedule, with both currencies and both tax bases recorded. We deliver the gap where those hold and decline it where they do not.

Because European prices are typically VAT-inclusive at European rates while GCC prices carry a different basis, and some markets have none. A gap that ignores this partly measures tax.

Because markdowns start at different times in different regions, so the gap moves through a season. A single figure depends on when it was taken.

Typically a European luxury retailer or the brand's own European site, named on every gap and collected on the same schedule.

No. A similar product is not the same product, and the gap would describe the difference between two items.

We quote individually. Gap work includes the European comparator panel, which roughly doubles collection and is where the value is.

One scoping call, a free pilot within 24 hours including sample paired gaps, then a fixed monthly quote. Request a quote.

See real Ounass data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner