Core services
Enterprise Data Extraction

Scalable web, app and AI-powered collection across 40+ countries.

All 58 services →
New 2026
AI Training Data

Corpus building with provenance and opt-out compliance.

Learn more →
Free pilot
24-hour sample

We run collection on your own sources before you commit.

Get a sample →
58Services
40+Countries
DEVELOPER

Ready-Made Scrapers

Pre-built for top platforms. Self-serve, no setup.

View All →
TRY FREE

API Playground

Test endpoints instantly. No credit card.

Start Free →
28Tools
2SDKs
icons Delivery & SDKs
Streaming Crawl API Scheduler Realtime Alerts Webhook Delivery 🐍 Python SDK 💚 Node.js SDK
Need it managed instead?

Fixed monthly retainer, named engineer, no per-request metering.

Managed Data API →
HOT

Case Studies

How brands use Actowiz, with named outcomes.

Read →
FREE

Sample Datasets

Real output, no signup.

Download →
NEW

ROI Calculator

Model the return on a data engagement.

Calculate →
Data type · Catalog & assortment

Catalog & Assortment Data Services

Range breadth, newness and what quietly disappeared.

Catalog and assortment data is the structured record of what a retailer actually ranges: SKU counts by category and price band, newness introduction and cadence, delisting events, assortment overlap against competitors, category taxonomy structure and range gaps — tracked over time so range strategy becomes observable rather than inferred.

Pricing tells you how a retailer competes. Assortment tells you what they have decided to compete on. The second changes less often and matters more, and almost nobody tracks it systematically.

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

Range breadth over time Delisting detection Free pilot sample in 48 hours
assortment_snapshot_2026-08-05.jsonl LIVE FEED
{"retailer":"example-retail.com", "category_norm":"home/kitchen/cookware", "category_published":"Pots & Pans", "period":"2026-W31", "sku_count":418, "sku_count_prev":392, "new_skus_30d":44, "delisted_skus_30d":18, "newness_share_pct":10.5, "own_label_share_pct":31.8, "price_bands":{"under_20":112, "20_50":186,"50_100":88, "over_100":32}, "brand_count":37, "top_brand_share_pct":14.2} {"comparison":"overlap", "retailer_a":"example-retail.com", "retailer_b":"competitor-retail.com", "shared_skus":164, "exclusive_to_a":254, "exclusive_to_b":198, "overlap_pct":39.2}
2 of 1,142,800 category-retailer-period rows · run 2026-08-05taxonomy mapped 96.9% · schema v4.8
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

Key facts at a glance

What it is
Managed tracking of what retailers range: SKU counts, newness, delistings, overlap and category structure
Range breadth
SKU counts by normalised category, price band and brand, tracked period over period
Newness
New SKU introduction with dates, newness share and introduction cadence
Delisting
SKUs disappearing from range, distinguished from stock-outs where evidence allows
Overlap
Shared and exclusive SKU counts between retailers, so assortment differentiation is measurable
Taxonomy
Published categories mapped to a normalised structure so cross-retailer comparison works
Refresh
Weekly standard; daily for newness and delisting alerting on tracked categories
Who it's for
Buying and merchandising, brand distribution, category and strategy teams, plus investors
96.9%taxonomy mapping ratecross-retailer comparable
Newnesswith introduction datesnot just a badge
Delistingdetected as eventsdistinguished from OOS
Overlapshared vs exclusive SKUsdifferentiation measured

Key takeaways

  • What it is: Managed tracking of what retailers range: SKU counts, newness, delistings, overlap and category structure
  • Range breadth: SKU counts by normalised category, price band and brand, tracked period over period
  • Newness: New SKU introduction with dates, newness share and introduction cadence
  • Delisting: SKUs disappearing from range, distinguished from stock-outs where evidence allows
  • Overlap: Shared and exclusive SKU counts between retailers, so assortment differentiation is measurable
  • Taxonomy: Published categories mapped to a normalised structure so cross-retailer comparison works

Last verified 5 August 2026 by the Actowiz Solutions Data Engineering team.

Definition

What is catalog and assortment data, and why is taxonomy mapping the prerequisite?

Catalog and assortment data describes range rather than price: how many SKUs a retailer carries in a category, at what price bands, from which brands, how much of it is own-label, what is newly introduced, what has been dropped, and how much overlaps with competitors.

Every one of those questions requires that categories mean the same thing across retailers, which they do not. Taxonomy mapping is therefore the prerequisite rather than a refinement.

Why published categories cannot be compared directly

  • Different depth. One retailer has three category levels where another has five, so a level-two category is not comparable to a level-two category.
  • Different boundaries. Products one retailer places in Kitchen another places in Dining, and both are defensible.
  • Different naming. The same category called Cookware, Pots & Pans and Pans across three retailers.
  • Multi-placement. The same SKU appearing in several categories, which double-counts if not handled.
  • Seasonal categories. Categories that appear and disappear, inflating or deflating counts artificially.

We map published categories to a normalised structure with a confidence score, retain the published path alongside, and deduplicate multi-placed SKUs so counts are counts rather than placements.

Why delisting is the most valuable and most ambiguous signal

A SKU disappearing from range is a commercial decision, and commercially it is often more informative than any price change. But disappearance is ambiguous: it can mean delisted, out of stock and hidden, seasonally withdrawn, or recategorised.

We require continued absence across multiple runs plus disappearance from category listings before classifying a delisting, and we flag the ambiguous cases rather than resolving them. A stock-out recorded as a delist corrupts range analysis; a delist recorded as a stock-out sends supply chain after a decision that has already been made.

What we cannot see

Sales, margin, or why a decision was made. Assortment data tells you what was decided, not the reasoning or the result.

What we collect

Six categories of assortment data

Range breadth and delisting are the core. Overlap analysis is what strategy teams build on.

Range breadth

How wide the assortment actually is.

  • SKU counts by normalised category
  • Counts by price band
  • Brand count and concentration
  • Own-label share of range
  • Period-over-period change

Newness & introduction

What is being added, and how fast.

  • New SKU detection with first-seen dates
  • Newness share of range
  • Introduction cadence by category
  • New brand entry detection
  • Seasonal introduction patterns

Delisting & withdrawal

What quietly disappeared.

  • Delisting events with dates
  • Distinction from stock-outs where evidence allows
  • Ambiguous cases flagged
  • Brand exit detection
  • Category contraction signals

Assortment overlap

How differentiated retailers really are.

  • Shared SKU counts between retailers
  • Exclusive SKU counts per retailer
  • Overlap percentage by category
  • Overlap trend over time
  • Exclusive-line identification

Category structure

The taxonomy itself as data.

  • Published category paths
  • Normalised category mapping with confidence
  • Category depth and breadth
  • New and removed categories
  • Multi-placement handling

Range gaps

Where you are absent and competitors are not.

  • Categories where competitors range and you do not
  • Price band gaps in your range
  • Brand coverage gaps
  • Attribute-level gaps where published
  • Gap trend over time
Service scope

What the ecommerce data scraping service includes

A managed engagement, not a tool licence. We own the pipeline and everything that breaks in it.

✓ Included in every engagement

  • Full category enumeration rather than tracking a supplied SKU list
  • SKU counts deduplicated for multi-placement across categories
  • Taxonomy mapping with published category paths retained for audit
  • Taxonomy restructure detection so range change is not confused with site redesign
  • Delisting classification requiring continued absence, with ambiguity flagged
  • Source discovery, scoping and a written collection plan
  • Free pilot on your own sources before any commitment
  • Full pipeline build, hosting and proxy infrastructure
  • Schema design, validation and sampled human QA on every run
  • Ongoing maintenance when source layouts change — our cost, not yours
  • Delivery to your warehouse, bucket, SFTP or API endpoint
  • Documented methodology and compliance notes for your legal review

× Not included — stated upfront

  • Sales, margin or the reasoning behind a range decision
  • Retailer systems, supplier portals or authenticated catalogues
  • Range counts presented as complete where pagination limits enumeration
  • A single variant definition imposed across all categories
  • Anything behind a login, paywall or credentialed session
  • Personal data beyond a documented lawful basis
  • Licensed third-party datasets we do not hold rights to
  • Guarantees about fields a source simply does not publish
Schema

Assortment data fields you receive

Every engagement delivers a documented schema. These are the core fields; the full dictionary runs to 100+ and is agreed during scoping.

Deliverable schema — v4.8 core fields (full dictionary: 100+ fields)
Field Type What it captures Refresh
retailer / period string Retailer and the period the snapshot covers, so change is measurable Per period
category_published / category_norm / map_confidence string / decimal Published path, normalised category and mapping confidence Per period
sku_count / sku_count_prev int SKU count this period and last, deduplicated for multi-placement Per period
new_skus_30d / delisted_skus_30d int Introductions and delistings over a trailing window Per period
newness_share_pct decimal Proportion of range introduced recently, as a range-refresh signal Per period
own_label_share_pct decimal Own-label proportion of the category range Per period
price_bands object SKU counts by configurable price band, showing where range is concentrated Per period
brand_count / top_brand_share_pct int / decimal Brand breadth and concentration within the category Per period
shared_skus / exclusive_to_a / overlap_pct int / decimal Assortment overlap fields for retailer pair comparison Per period
delist_event / delist_confidence object / decimal Delisting events with dates and confidence in the classification Daily tier
gap_categories array Categories where competitors range and you do not Per period

SKU counts are deduplicated for multi-placement. A retailer listing the same product in four categories has one SKU, not four, and counting placements instead of products inflates range breadth by a variable and misleading amount.

Coverage

Retailers and categories we cover

Assortment work needs full category crawls rather than SKU lists, which makes category selection the main scoping decision.

MarketplacesGrocery chainsFashion retailersElectronics retailersDIY and homePharmacy and healthBeauty specialistsPet and babySports and outdoorToys and gamesOffice and stationeryAutomotive partsQuick commerce platformsBrand D2C sitesWholesale and B2B cataloguesRegional and independent retailers

Assortment analysis requires crawling entire categories rather than tracking a known SKU list, which is a different collection shape and cost profile from price monitoring. We scope categories deliberately for that reason. Request a source we don't list →

Markets served

Countries and markets where this service is in highest demand

We deliver into 40+ countries. These are the markets where this particular service is requested most, and the reason demand concentrates there.

Highest-demand markets for this service, and why demand concentrates there
Market Why demand concentrates here
United Kingdom & Germany Deep online assortments with clear category structures, which makes taxonomy mapping and overlap measurement most reliable.
United States Enormous marketplace catalogues where range breadth and own-label expansion are the defining competitive dynamics.
India & Southeast Asia Rapid assortment expansion and high listing churn, making newness and delisting detection unusually valuable.
France, Spain & Italy Strong specialist retail with distinct range strategies, widely used for competitive differentiation analysis.

North America

United StatesCanadaMexico

United Kingdom & Ireland

United KingdomIreland

Western Europe

GermanyFranceNetherlandsBelgiumSpainItalySwitzerlandAustria

Nordics

SwedenNorwayDenmarkFinland

Middle East

United Arab EmiratesSaudi ArabiaQatarKuwaitIsrael

Asia Pacific

SingaporeAustraliaNew ZealandJapanSouth KoreaMalaysiaIndonesiaThailandVietnamPhilippines

South Asia

IndiaBangladeshSri LankaPakistan

LATAM

BrazilArgentinaChileColombia

Africa

South AfricaNigeriaKenyaEgypt

We run production collection across 40+ countries. Coverage depth varies by market and by source, so we confirm what is actually available for your specific markets during scoping rather than claiming uniform global coverage. Ask about a market we don't list →

Who buys this data

Which teams buy assortment data

Buying and merchandising dominate, with brand distribution and strategy teams close behind.

Buying / Merchandising Director

Retailers
The problem

Range decisions need to know what competitors carry, at what price bands, and what they have recently added or dropped.

What we deliver

Category range breadth by price band and brand with newness and delisting events, tracked period over period.

Metric that moves

Range productivity

Head of Distribution

Brands
The problem

You cannot see which retailers range your products, which ranged them and stopped, or where competitors have listings you do not.

What we deliver

Listing presence across retailers with delisting detection, plus competitor range coverage in the same categories.

Metric that moves

Distribution coverage %

Category Manager

Retailers and marketplaces
The problem

Assortment overlap with competitors is unknown, so differentiation is asserted rather than measured.

What we deliver

Shared and exclusive SKU counts by category against named competitors, with overlap trend over time.

Metric that moves

Category differentiation

Strategy / Insight Lead

Retailers and brands
The problem

Competitor range strategy shifts are visible in assortment months before they show in market share.

What we deliver

Category breadth, price band mix, own-label share and brand concentration tracked over time by retailer.

Metric that moves

Strategic lead time

Own Label Development Lead

Retailers
The problem

Own-label range decisions need to know competitor own-label breadth and where branded lines dominate.

What we deliver

Own-label share by category across retailers with new own-label introduction detection.

Metric that moves

Own label penetration

Investment Analyst

Consumer and retail funds
The problem

Range breadth and newness cadence are observable operational signals ahead of reported performance.

What we deliver

Longitudinal range breadth, newness and own-label share panels by retailer and category.

Metric that moves

Signal lead time

Use cases

How assortment data gets used in practice

Four patterns, with the outcome each is judged on.

Range gap identification against competitors

Full category crawls across your competitive set are normalised to a shared taxonomy, producing categories, price bands and brands where competitors range and you do not.

Outcome: Range expansion decisions driven by measured gaps rather than by supplier proposals.

Delisting detection for brand distribution

SKU disappearance is tracked with continued-absence confirmation, so retailers that have dropped your lines are identified as events rather than discovered during a quarterly review.

Outcome: Delistings caught within a collection cycle instead of at the next range review.

Assortment overlap and differentiation measurement

Shared and exclusive SKU counts are computed between retailer pairs by category, showing how differentiated a range actually is and how that is changing.

Outcome: Differentiation claims replaced with measured overlap percentages.

Newness cadence benchmarking

New SKU introductions are detected with dates, producing newness share and introduction cadence by category and retailer over time.

Outcome: Range refresh planned against observed competitor cadence rather than an internal calendar.

Engagement examples

Two engagements, anonymised

Clients rarely permit naming. These are real engagement shapes with identifying detail removed, so you can judge whether the work resembles your situation.

Brand · Multi-market

Retailer delistings were discovered at quarterly range reviews

Situation

The distribution team learned about dropped lines from sales reports or account conversations, typically a full quarter after the decision.

What we ran

Full category enumeration with delisting detection requiring continued absence confirmation, distinguished from stock-outs and flagged where ambiguous.

Result

Delistings surfaced within a collection cycle, with dates, ahead of the account conversation.

Retailer · UK

A competitor range expansion was actually a taxonomy restructure

Situation

Weekly SKU counts showed a competitor apparently adding hundreds of lines in one category, prompting a range response.

What we ran

Taxonomy restructure detection with published category paths retained alongside normalised categories.

Result

The apparent expansion proved to be one category split into three, and the planned response was cancelled.

Examples are anonymised at client request. Named references are available on request under NDA. See published case studies →

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

Before you commit to anything, we run this service against your own sources and send you the output. If the coverage isn't there, the sample will show you that too — which is the point. We would rather lose the deal at the pilot than at month three.

  • Real extraction from your actual sources
  • Returned inside two business days
  • 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 for this work

Same collection pipeline and same 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.

Build vs buy

Should you build assortment tracking in-house or hire it as a service?

Full category crawling plus taxonomy mapping is a different and heavier problem than tracking a known SKU list.

In-house build vs self-serve tool vs Actowiz managed service
Consideration In-house scraping team Generic proxy / DIY tool Actowiz managed feed
Time to first usable data 6–12 weeks of engineering before anything is trustworthy Days, but output needs manual cleanup before use Free pilot in 48 hours, production in 5–10 business days
Who fixes it when a source changes Your engineers, at the cost of their roadmap You do — tools report failures, they don't resolve them We do, same business day, inside the retainer
Data quality assurance Whatever your team has time to build None beyond HTTP success Schema validation plus sampled human QA on every run
Compliance documentation Rarely produced, then requested urgently by legal Not provided; terms risk sits with you Sources, method and lawful basis documented for review
Accountability Distributed across a team with other priorities A support ticket queue A named engineer and an account owner
True annual cost Engineer salaries, proxies, hosting, ongoing maintenance Low licence fee plus significant hidden analyst time One fixed monthly retainer, quoted after scoping

Why assortment collection is a different shape of problem from price monitoring

Teams that already buy price monitoring often assume assortment is a small extension of it. It is not, and the difference explains why assortment data is comparatively rare.

The structural difference

  • Price monitoring tracks a known list. You supply SKUs; collection checks them. Volume is bounded by your list.
  • Assortment requires discovery. You cannot count what a retailer ranges by checking products you already know about. The entire category has to be enumerated, including products you have never seen.
  • Category crawls are unbounded. A category with 400 SKUs today may have 600 next month, and pagination, filters and sort orders all have to be handled to enumerate completely.
  • Completeness matters more than freshness. A price feed that misses 2% of SKUs is slightly incomplete. An assortment count that misses 2% is a wrong number, and the error compounds across period comparisons.
  • Multi-placement has to be resolved. The same product in four categories must count once, which requires product identity rather than page counting.

What this means for scoping

Assortment engagements are scoped by category rather than by SKU count, and weekly is usually the right cadence rather than daily — range changes on a weekly to monthly rhythm, and daily full-category crawls cost far more for little additional signal.

We do run daily on a narrower basis where newness or delisting alerting matters, monitoring category listings for additions and removals rather than re-enumerating everything. That hybrid is usually the right configuration: weekly full counts, daily change detection.

Taxonomy mapping, and why we keep the published path

Normalising categories is what makes cross-retailer assortment comparison possible. Keeping the original is what makes it auditable, and both matter.

How mapping works

Published category paths are mapped to a normalised taxonomy using path structure, product attribute profiles and the products themselves — because a category is defined by its contents more reliably than by its name. Each mapping carries a confidence score.

Why the published path stays

  • Auditability. When a count looks wrong, the first question is which published categories fed it. Without the original path that question is unanswerable.
  • Retailer conversations. Discussing range with a retailer requires their category language, not yours.
  • Mapping disagreements. Your internal taxonomy may differ from ours. With published paths retained, you can remap without recollecting.
  • Structure changes. Retailers reorganise categories, which can look like a range change if only normalised categories are stored. Keeping both makes reorganisations identifiable as reorganisations.

That last point causes more false alarms than any other issue in assortment data. A retailer splitting one category into three produces an apparent range expansion that never happened. We detect taxonomy restructures explicitly and flag them, so period-over-period comparisons are not silently broken by someone else's site redesign.

For SKU-level pricing on the products discovered, this joins directly to pricing and product data on the same product keys.

How it works

How an assortment engagement goes live in 5 to 10 business days

Categories and competitor set are scoped first, since assortment work is priced by category crawl scope rather than SKU count.

Scope the sources and fields

You send us target sites, regions, SKUs or keywords. We return a field-level schema proposal, coverage estimate and refresh recommendation — usually within two working days.

Pilot sample, free

We extract a real sample from your actual targets so you can inspect field fill rates, edge cases and match quality before any commitment.

Production build and QA harness

Our engineers build extractors, then wire validation rules: type checks, range checks, duplicate detection and golden-record comparison against a manually verified subset.

Scheduled delivery into your stack

Feeds run at your chosen cadence and land in the warehouse or bucket you already use. Schema changes are versioned and announced before they ship.

Ongoing monitoring and SLA support

We watch coverage drift, fill rates and source changes daily. A named engineer owns your account, and layout breaks are fixed by us — not queued for you.

Formats & destinations

JSON, JSONL, CSV, Parquet or XLSX, delivered to Amazon S3, Google Cloud Storage, Azure Blob, SFTP, Snowflake, BigQuery, Databricks or a REST/GraphQL endpoint. Webhooks fire on completion, and every batch ships with a manifest containing row counts, schema version and QA results so your pipeline can fail loudly instead of silently ingesting a bad file.

Compliance & data ethics

We collect publicly accessible category, search and product pages. Category enumeration respects pagination and rate limits, and collection rates are set to be low-impact. We do not access retailer systems, supplier portals or any authenticated catalogue.

Service commitments

What we commit to, in writing

These are contractual, not marketing copy. They appear in the engagement document.

Service level commitments written into every managed engagement
Commitment What we hold ourselves to
Pilot turnaround A real sample from your own sources within 48 hours of scoping, at no cost.
Go-live Production collection running within 5–10 business days of sign-off.
Delivery punctuality 99.5% on-schedule delivery, measured monthly and reported to you.
Breakage response Source layout changes triaged same business day; critical sources inside 4 hours.
Data quality Schema validation on every run plus sampled human QA before any delivery leaves us.
Escalation A named engineer and an account owner, not a shared ticket queue.
Change requests Field additions and source changes handled inside the retainer, not re-quoted.
Exit Your historical data exported in full on request. No lock-in, no export fee.

Why teams pick Actowiz for this work

  • Engineers, not a dashboard. You get people who fix breakages, not a self-serve tool you maintain yourself.
  • We tell you what we can't do. Scope limits and coverage gaps are stated before you sign, not discovered in month three.
  • QA is part of the service. Schema validation and sampled human review run before delivery, every run.
  • Compliance is documented. Sources, method and lawful basis written down so your legal team can review them.
  • Fixed monthly cost. No per-request metering, no surprise overage on a month when a competitor adds SKUs.
  • Six years, 40+ countries. Long-running production pipelines across retail, travel, mobility and finance.
Definitions

Terms used on this page

Plain definitions of the terms used on this page, so procurement and legal reviewers are working from the same vocabulary as your data team.

Range breadth
The number of distinct SKUs a retailer ranges in a category, deduplicated for multi-placement. Counting placements rather than products inflates breadth by a variable amount.
Taxonomy restructure
A retailer reorganising its category structure. It produces apparent range changes that never happened, and is the largest source of false alarms in assortment data.
Assortment overlap
The proportion of SKUs two retailers share in a category. Differentiation is usually asserted internally and rarely measured, and measured overlap is often higher than expected.
FAQ

Catalog and assortment data: frequently asked questions

What buying, distribution and strategy teams ask during evaluation.

Price monitoring tracks a list you supply. Assortment requires discovery — you cannot count what a retailer ranges by checking products you already know about, so entire categories have to be enumerated including products you have never seen.

That makes completeness matter more than freshness. A price feed missing 2% of SKUs is slightly incomplete; an assortment count missing 2% is a wrong number, and the error compounds across period comparisons. It is a heavier collection problem with a different cost profile.

By mapping published category paths to a normalised taxonomy using path structure, product attribute profiles and the actual products in the category — a category is defined by its contents more reliably than by its name. Mapping confidence is delivered per record.

We retain the published path alongside, so counts are auditable, you can remap to your own taxonomy without recollecting, and retailer conversations can use their category language rather than ours.

Usually, and we flag the cases where we cannot. Classification requires continued absence across multiple runs plus disappearance from category listings, not just an unavailable product page.

The distinction matters in both directions: a stock-out recorded as a delist corrupts range analysis, and a delist recorded as a stock-out sends supply chain chasing a decision that has already been made. Ambiguous cases carry a confidence score rather than a determination.

Weekly for full category counts, since range changes on a weekly to monthly rhythm and daily full crawls cost far more for little additional signal. Daily is worth it for change detection — monitoring category listings for additions and removals rather than re-enumerating everything.

That hybrid is the usual configuration: weekly full counts for breadth analysis, daily change detection for newness and delisting alerting.

We detect it and flag it, because it is the largest source of false alarms in assortment data. A retailer splitting one category into three produces an apparent range expansion that never happened.

Because we retain published paths alongside normalised categories, restructures are identifiable as restructures rather than being silently absorbed into period-over-period comparisons. Flagged periods can then be excluded or adjusted rather than misread.

Yes — shared SKU counts, exclusive counts per retailer and overlap percentage by category, tracked over time. It requires product identity matching across retailers, which is delivered with confidence scores.

Overlap is one of the more strategically useful outputs, because differentiation is usually asserted internally rather than measured. Retailers are frequently surprised by how high overlap actually is in categories they consider distinctive.

SKUs, deduplicated for multi-placement. A retailer listing the same product in four categories has one SKU, not four, and counting placements inflates range breadth by a variable and misleading amount.

Variants are handled per your definition — whether a colour or size counts as a separate SKU differs by category and by how you plan internally, so we agree it during scoping rather than imposing one rule across everything.

Yes, using retailer-specific own-label brand mappings rather than name matching, since many retailer brands do not carry the retailer's name and some are exclusive third-party brands.

Own-label share by category, and new own-label introduction detection, are among the most requested fields here — particularly in grocery and general merchandise where own-label expansion is the defining competitive dynamic.

We quote individually, and here the driver is category crawl scope rather than SKU count — because the SKU count is an output, not an input. Retailer count and category breadth determine the work.

A defined category set across a few competitors at weekly cadence sits at the lighter end. Full-catalogue enumeration across many retailers with daily change detection sits considerably higher. One scoping call, a free pilot on your own categories within 48 hours, then a fixed monthly quote. Request a quote.

See real assortment data for your own categories

Send us categories and competitors. We return range breadth, newness, delistings and overlap within 48 hours.

Free pilot, no card, no obligation. We'll show you the taxonomy mapping so you can check it.
Social Proof That Converts

Trusted by Global Leaders Across Q-Commerce, Travel, Retail, and FoodTech

Our web scraping expertise is relied on by 4,000+ global enterprises including Zomato, Tata Consumer, Subway, and Expedia — helping them turn web data into growth.

4,000+ Enterprises Worldwide
50+ Countries Served
20+ Industries
Join 4,000+ companies growing with Actowiz →
Real Results from Real Clients

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!"
TG
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."
II
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."
FC
Febbin Chacko
-Fin, Small Business Owner
icons 4.8/5 Average Rating
icons 50+ Video Testimonials
icons 92% Client Retention
icons 50+ Countries Served

Join 4,000+ Companies Growing with Actowiz

From Zomato to Expedia — see why global leaders trust us with their data.

Why Global Leaders Trust Actowiz

Backed by automation, data volume, and enterprise-grade scale — we help businesses from startups to Fortune 500s extract competitive insights across the USA, UK, UAE, and beyond.

icons
7+
Years of Experience
Proven track record delivering enterprise-grade web scraping and data intelligence solutions.
icons
4,000+
Projects Delivered
Serving startups to Fortune 500 companies across 50+ countries worldwide.
icons
200+
In-House Experts
Dedicated engineers across scrapers, AI/ML models, APIs, and data quality assurance.
icons
9.2M
Automated Workflows
Running weekly across eCommerce, Quick Commerce, Travel, Real Estate, and Food industries.
icons
270+ TB
Data Transferred
Real-time and batch data scraping at massive scale, across industries globally.
icons
380M+
Pages Crawled Weekly
Scaled infrastructure for comprehensive global data coverage with 99% accuracy.

AI Solutions Engineered
for Your Needs

LLM-Powered Attribute Extraction: High-precision product matching using large language models for accurate data classification.
Advanced Computer Vision: Fine-grained object detection for precise product classification using text and image embeddings.
GPT-Based Analytics Layer: Natural language query-based reporting and visualization for business intelligence.
Human-in-the-Loop AI: Continuous feedback loop to improve AI model accuracy over time.
icons Product Matching icons Attribute Tagging icons Content Optimization icons Sentiment Analysis icons Prompt-Based Reporting

Connect the Dots Across
Your Retail Ecosystem

We partner with agencies, system integrators, and technology platforms to deliver end-to-end solutions across the retail and digital shelf ecosystem.

icons
Analytics Services
icons
Ad Tech
icons
Price Optimization
icons
Business Consulting
icons
System Integration
icons
Market Research
Become a Partner →

Popular Datasets — Ready to Download

Browse All Datasets →
icons
Amazon
eCommerce
Free 100 rows
icons
Zillow
Real Estate
Free 100 rows
icons
DoorDash
Food Delivery
Free 100 rows
icons
Walmart
Retail
Free 100 rows
icons
Booking.com
Travel
Free 100 rows
icons
Indeed
Jobs
Free 100 rows

Latest Insights & Resources

View All Resources →
thumb
Blog

How Sobeys Grocery Product Data API Helps Brands Solve Pricing, Assortment, and Competitor Tracking Challenges

Sobeys Grocery Product Data API helps brands track product prices, availability, assortment, and competitor activity for smarter grocery market decisions.

thumb
Case Study

How We Helped a Brand Leverage Boots.com Review Data Collection for Additional 6.6M Reviews & Sentiment Analysis

Boots.com Review Data Collection helps brands analyze product reviews, ratings, sentiment, customer feedback, and an additional 6.6M reviews at scale.

thumb
Report

Amazon Zipcode-Level Product Data Report 2026 - Hyperlocal Pricing Intelligence USA to Track Local Product Prices and Availability

Amazon Zipcode-Level Product Data Report 2026 explores Hyperlocal Pricing Intelligence USA for tracking local prices, availability, and product trends.

Start Where It Makes Sense for You

Whether you're a startup or a Fortune 500 — we have the right plan for your data needs.

icons
Enterprise
Book a Strategy Call
Custom solutions, dedicated support, volume pricing for large-scale needs.
icons
Growing Brand
Get Free Sample Data
Try before you buy — 500 rows of real data, delivered in 2 hours. No strings.
icons
Just Exploring
View Plans & Pricing
Transparent plans from $500/mo. Find the right fit for your budget and scale.
Get in Touch
Let's Talk About
Your Data Needs
Tell us what data you need — we'll scope it for free and share a sample within hours.
  • icons
    Free Sample in 2 HoursShare your requirement, get 500 rows of real data — no commitment.
  • icons
    Plans from $500/monthFlexible pricing for startups, growing brands, and enterprises.
  • icons
    US-Based SupportOffices in New York & California. Aligned with your timezone.
  • icons
    ISO 9001 & 27001 CertifiedEnterprise-grade security and quality standards.
Request Free Sample Data
Fill the form below — our team will reach out within 2 hours.
+1
Free 500-row sample · No credit card · Response within 2 hours

Request Free Sample Data

Our team will reach out within 2 hours with 500 rows of real data — no credit card required.

+1
Free 500-row sample · No credit card · Response within 2 hours