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 · Stock & availability

Stock & Availability Data Services

With stock-out duration measured, not just a flag on a run.

Stock and availability data is the structured record of whether a product can actually be bought: in-stock state, out-of-stock start time and duration, quantity limits, low-stock signals, fulfilment options, pre-order state and replenishment events — captured at the granularity a retailer exposes, from national online down to individual store.

A flag saying out of stock today tells you almost nothing. A stock-out that started at 06:40, lasted four hours, showed a substitute and was replenished by lunchtime tells you what it cost and whether anyone noticed. The second dataset requires collecting the transitions, not the states.

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

Duration, not just a flag Replenishment detection Free pilot sample in 48 hours
stock_availability_2026-08-05.jsonl LIVE FEED
{"sku_key":"aw-sku-4471028", "retailer":"example-retail.com", "location_scope":"store", "store_ref":"3312-cheadle", "listed":true, "in_stock":false, "oos_since":"2026-08-05T06:40Z", "oos_minutes_running":142, "oos_events_30d":6, "oos_minutes_30d":1884, "availability_30d_pct":95.6, "substitute_shown":true, "substitute_is_own_label":true, "qty_limit":2, "fulfilment":["delivery","click_collect"], "observed_at":"2026-08-05T09:02:11Z"} {"sku_key":"aw-sku-4471028", "store_ref":"3312-cheadle", "event":"replenished", "event_at":"2026-08-05T12:18Z", "oos_duration_minutes":338}
2 of 9,204,700 sku-location rows · run 2026-08-05T09:00Ztransition capture 98.7% · schema v5.0
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 monitoring of whether products can actually be purchased, with transitions captured rather than states sampled
Duration
Out-of-stock start times, running duration, event counts and trailing availability percentages
Listed vs in stock
Two separate fields, so never-ranged products are excluded from availability metrics
Replenishment
Restock events with the duration of the gap they closed
Granularity
National online, fulfilment area, delivery zone or individual store, per what a retailer exposes
Substitutes
Whether an alternative was offered, and whether it was own-label
Refresh
Hourly on priority sets; several times daily as standard
Who it's for
Supply chain, availability, ecommerce, category and trade teams, plus investors
Durationmeasured in minutesnot a daily flag
98.7%transition capture rateon hourly tier
Listed vs in-stockseparate fieldsmetrics mean what they say
Replenishmentdetected as eventswith gap duration

Key takeaways

  • What it is: Managed monitoring of whether products can actually be purchased, with transitions captured rather than states sampled
  • Duration: Out-of-stock start times, running duration, event counts and trailing availability percentages
  • Listed vs in stock: Two separate fields, so never-ranged products are excluded from availability metrics
  • Replenishment: Restock events with the duration of the gap they closed
  • Granularity: National online, fulfilment area, delivery zone or individual store, per what a retailer exposes
  • Substitutes: Whether an alternative was offered, and whether it was own-label

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

Definition

What is stock and availability data, and why do daily snapshots understate the problem?

Stock and availability data records whether a product is purchasable: in-stock state, out-of-stock timing and duration, per-order quantity limits, low-stock hints, fulfilment options offered, pre-order and discontinued states, and replenishment events.

Almost every availability dataset samples states. The useful dataset captures transitions, and the difference is not cosmetic.

What daily sampling misses

  • Short stock-outs disappear entirely. A four-hour gap between two daily readings is invisible. In fast-moving categories most stock-outs are short, so daily collection systematically understates the problem.
  • Duration cannot be computed. Two products both flagged out of stock today may have been out for one hour and eleven days. Those are different problems with different owners.
  • Replenishment is invisible. A product that went out and came back looks identical to one that never went out.
  • Time-of-day patterns vanish. Stock-outs concentrating in evenings indicate a replenishment cadence problem rather than a forecasting one.
  • Lost-sales windows cannot be sized. Without duration, the commercial cost is unquantifiable.

Why listed and in-stock must stay separate

This is the field design decision that matters most. listed records whether a product exists in that retailer's or location's range at all. in_stock records buyability where it is listed.

Merging them turns a commercial range gap into an apparent supply failure. We have watched brands escalate a 40% "unavailability" figure to supply chain and spend weeks discovering most of the gap was locations where the SKU was never ranged. Availability metrics are computed only across the listed population, so an on-shelf availability figure means what the phrase actually means.

What we cannot see

Inventory depth, units on hand and allocation. A product being purchasable does not reveal how many units remain. Where a retailer displays a low-stock hint we capture it as displayed; we never estimate quantity.

What we collect

Six categories of availability data

Duration measurement is the core. Store-level and substitute capture are what supply teams build on.

Availability state

The base signal, per location scope.

  • In-stock, out-of-stock, pre-order, discontinued
  • Listed versus never-ranged as separate fields
  • Low-stock hints as displayed
  • Per-order quantity limits
  • Backorder and lead time where shown

Duration & events

Where the commercial value sits.

  • Out-of-stock start timestamps
  • Running and completed durations
  • Event counts over trailing windows
  • Trailing availability percentages
  • Time-of-day and day-of-week patterns

Replenishment

The other half of the story.

  • Restock events with timestamps
  • Duration of the gap closed
  • Replenishment cadence per SKU and location
  • Repeat stock-out detection
  • Recovery time distribution

Substitutes & alternatives

What the shopper was offered instead.

  • Whether a substitute was shown
  • Substitute product identity
  • Own-label substitution flag
  • Substitute price versus original
  • Substitution frequency by category

Fulfilment options

How it can actually be received.

  • Delivery, click-and-collect, in-store
  • Delivery slot availability where shown
  • Same-day and express eligibility
  • Store pickup availability
  • Fulfilment method changes over time

Location granularity

As fine as the retailer exposes.

  • National online availability
  • Fulfilment area or postcode district
  • Delivery zone or pincode
  • Individual store stock where published
  • Granularity level recorded per record
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

  • Transition capture with stock-out start times and completed durations
  • Listed and in-stock as separate fields, with availability computed on the listed population only
  • Replenishment events recorded with the duration of the gap closed
  • Substitute capture including own-label substitution flags
  • location_scope on every record so granularity is never ambiguous
  • 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

  • Inventory depth, units on hand or allocation data
  • Adding items to baskets or creating accounts to reveal hidden availability
  • Treating displayed low-stock hints as verified quantities
  • Deciding between long stock-out and delisting where evidence is ambiguous
  • 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

Availability data fields you receive

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

Deliverable schema — v5.0 core fields (full dictionary: 90+ fields)
Field Type What it captures Refresh
sku_key / retailer string Product identity and retailer, joinable to pricing and content records Every run
location_scope / store_ref enum / string Whether the record is national, area, zone or store level, and which location Every run
listed boolean Whether the product is ranged here at all, separate from whether it is buyable Every run
in_stock / stock_state boolean / enum Buyability plus a state enum covering pre-order and discontinued Per cadence
oos_since / oos_minutes_running timestamp / int When the current stock-out began and how long it has run Hourly tier
oos_events_30d / oos_minutes_30d int Event count and cumulative out-of-stock minutes over a trailing window Daily
availability_30d_pct decimal Trailing availability computed across the listed population only Daily
substitute_shown / substitute_is_own_label boolean Whether an alternative was offered and whether it was own-label Per cadence
qty_limit / low_stock_hint int / string Per-order caps and displayed low-stock text, captured as shown Per cadence
fulfilment array Fulfilment methods offered at capture time Per cadence
event / event_at enum / timestamp Transition records for stock-out and replenishment events Hourly tier

Availability percentages are computed only across the listed population. Including never-ranged locations in the denominator produces a figure that looks like a supply chain problem and is actually a range decision.

Coverage

Retailers and granularity we cover

Availability exposure varies enormously by retailer. We confirm what each one publishes before build rather than assuming.

Grocery chains (store-level where exposed)MarketplacesQuick commerce platformsPharmacy retailElectronics retailFashion retail (size level)DIY and homePet and baby specialistsConvenience formatsWholesale and cash-and-carryBrand D2C sitesDelivery platform store listsClick-and-collect availability checkersStore stock checkers where publishedDelivery slot availability where exposed

Some retailers expose availability only inside an add-to-basket flow. We do not add items to baskets or create accounts, so where availability is not publicly exposed we say so rather than substituting a national figure. 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 Grocery retailers expose store-level and click-and-collect availability more openly than most markets, which makes store-level analysis genuinely viable.
United States Large store estates with widespread store stock checkers, and heavy demand from field sales teams prioritising visits.
India & GCC Quick commerce dark stores where availability changes hourly and stock-outs are short, so duration capture matters most.
Germany & Netherlands Strong online grocery with detailed fulfilment options exposed, supporting slot and method-level 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 availability data

Supply chain and availability leads dominate, with ecommerce and trade teams close behind.

Availability / Supply Chain Lead

Brands and manufacturers
The problem

Stock-outs at retailer level are invisible until sales dip, and by then the cause is unrecoverable and unattributable.

What we deliver

Hourly availability with stock-out start times, duration, replenishment events and trailing availability across your SKU and location set.

Metric that moves

Lost sales from OOS

Ecommerce Manager

Brands
The problem

Your listings can be unbuyable at a retailer for hours without anyone noticing, while paid traffic keeps arriving.

What we deliver

Availability monitoring aligned to your trading hours with alerting, so spend is not driven to unbuyable listings.

Metric that moves

Wasted media spend

Trade / Field Sales Lead

FMCG
The problem

Field visits are prioritised by intuition rather than by which stores actually have gaps.

What we deliver

Store-level availability where exposed, with repeat stock-out detection so visits target persistent problems.

Metric that moves

On-shelf availability %

Category Manager

Retailers
The problem

Supplier fill rate claims are hard to verify, and substitution is quietly moving volume to own-label.

What we deliver

Availability by SKU and store with substitution capture including own-label substitution flags.

Metric that moves

Category availability

Demand Planner

Brands and retailers
The problem

Forecasts are fitted to sales data that was suppressed by stock-outs nobody recorded.

What we deliver

Trailing out-of-stock minutes per SKU and location, so demand history can be corrected for suppressed availability.

Metric that moves

Forecast accuracy

Investment Analyst

Consumer funds
The problem

Availability is an observable operational quality signal ahead of reported performance.

What we deliver

Longitudinal availability panels by retailer, category and brand, computed on a consistent listed-population basis.

Metric that moves

Signal lead time

Use cases

How availability data gets used in practice

Four patterns, with the outcome each is judged on.

Quantifying lost-sales windows

Stock-out start times and durations are captured per SKU and location, producing cumulative out-of-stock minutes over trailing windows so the commercial cost can be sized rather than estimated.

Outcome: Lost-sales exposure quantified in minutes rather than described as a flag count.

Separating range gaps from supply failures

Listed and in-stock are separate fields, and availability is computed only across the listed population, so never-ranged locations surface as a distinct range-gap metric.

Outcome: Supply chain effort directed at real stock-outs, with range gaps routed to a category conversation instead.

Substitution and own-label leakage tracking

Where a retailer offers an alternative on an out-of-stock listing, the substitute is captured including whether it is own-label, with substitution frequency tracked by category.

Outcome: Volume leakage to own-label during stock-outs measured rather than suspected.

Media spend protection

Availability is monitored at the cadence your paid traffic runs, so campaigns driving to unbuyable listings can be paused within the hour rather than the week.

Outcome: Paid spend stopped while listings are unbuyable instead of after the reporting cycle.

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.

FMCG brand · UK

Daily availability reporting was missing most stock-outs entirely

Situation

Availability was checked once daily, so short gaps between readings never appeared, and the reported availability figure was consistently better than field observations suggested.

What we ran

Hourly collection with stock-out start timestamps, completed durations and replenishment events, plus availability computed across the listed population only.

Result

Cumulative out-of-stock minutes revealed materially more exposure than the daily flag count had shown.

Retailer · EU

Own-label substitution during stock-outs was invisible

Situation

The category team knew branded stock-outs occurred but had no view of what shoppers were offered instead or how often it was own-label.

What we ran

Substitute capture on out-of-stock listings including own-label substitution flags, with substitution frequency tracked by category.

Result

Substitution patterns became measurable, informing both range and replenishment priorities.

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 availability monitoring in-house or hire it as a service?

Transition capture requires continuous polling, which is where in-house availability projects quietly become daily snapshots.

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 replenishment detection is worth as much as stock-out detection

Availability programmes focus almost entirely on detecting stock-outs. The restock event is equally informative and almost never captured, because capturing it requires continuous observation rather than periodic sampling.

What replenishment tells you

  • Recovery time distribution. A retailer that restocks within four hours has a different operational problem from one taking four days, even with identical stock-out counts.
  • Replenishment cadence. Restocks clustering at particular times reveals delivery and shelf-filling schedules, which explains why stock-outs concentrate where they do.
  • Repeat offenders. A SKU that goes out and returns six times in a month has a forecasting or ordering problem, not a one-off event. Six separate stock-out flags look like bad luck; six events with durations look like a pattern.
  • Whether anyone noticed. A long gap suggests nobody was monitoring. A short one suggests they were.
  • Range decisions in progress. A SKU that goes out and never returns is usually a delist, not a stock-out — and confusing the two corrupts both metrics.

How we capture it

Availability is polled continuously on the hourly tier, and transitions are written as event records with timestamps and the duration of the gap they closed. That last point matters: without it, you have two unlinked observations rather than one measured event.

The distinction between a long stock-out and a delisting is resolved by continued observation rather than assumed. Where a SKU has been unavailable long enough that a delist is plausible, we flag the ambiguity rather than deciding for you. This pairs naturally with catalog and assortment data, where delisting is the primary signal rather than an edge case.

Store-level availability: valuable, uneven, and worth scoping honestly

Store-level availability is the most requested and least uniformly available field in this category. Retailers differ enormously in what they publish, and a vendor promising uniform store coverage is not describing reality.

The exposure patterns

  • Full store stock checker. Some retailers publish per-store availability on the product page. Excellent, and collectable.
  • Click-and-collect availability. A proxy for store stock, sometimes accurate and sometimes reflecting a fulfilment decision rather than shelf stock.
  • Fulfilment area only. Availability by postcode district or delivery area, which is finer than national but coarser than store.
  • Basket-flow only. Availability revealed only after adding to a basket and selecting a store. We do not do this — it means creating sessions and adding items, which we consider out of bounds.
  • National online only. No sub-national signal at all, whatever the store estate looks like.

How we scope it

We confirm per retailer which pattern applies before build, and record location_scope on every record so you always know what granularity a figure describes. Mixing store-level and national records in one analysis without that field produces conclusions that hold in neither.

Store-level collection also multiplies volume by store count, so we scope store sets deliberately — a representative sample across formats and regions usually answers the question that full-estate collection would answer at many times the cost.

How it works

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

Retailers, SKU set, location granularity and refresh cadence are scoped first, since store and zone counts drive volume.

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 displayed availability information. We do not add items to baskets, create customer accounts, use customer credentials or place orders to reveal availability that is not publicly exposed. Where availability is not public for a retailer, we state that rather than substituting a coarser figure.

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.

Out-of-stock duration
The elapsed time a product was unavailable, measured from a captured start timestamp. Duration is what makes lost-sales exposure quantifiable; a daily flag cannot produce it.
Listed population
The set of products actually ranged at a retailer or location. Availability percentages must be computed across it, or never-ranged products depress the figure and disguise a range decision as a supply failure.
Replenishment event
A restock transition recorded with a timestamp and the duration of the gap it closed. Capturing it requires continuous observation rather than periodic sampling.
FAQ

Stock and availability data: frequently asked questions

What supply chain, ecommerce and category teams ask during evaluation.

Because most stock-outs in fast-moving categories are short, so daily sampling misses them entirely and systematically understates the problem. It also cannot compute duration — two products flagged out of stock today may have been out for one hour and eleven days.

We capture transitions rather than states: stock-out start timestamps, running duration, event counts and cumulative out-of-stock minutes over trailing windows. That is what lets you size the commercial cost instead of counting flags.

Two separate fields, and it is the most consequential design decision here. listed says whether the product is ranged at that retailer or location at all; in_stock says whether it is buyable where it is listed.

Availability percentages are computed only across the listed population. Merging the fields turns a range gap into an apparent supply failure — we have seen brands escalate a 40% unavailability figure to supply chain and spend weeks discovering most of it was never-ranged locations.

Yes, as event records with timestamps and the duration of the gap they closed. Replenishment is as informative as the stock-out: recovery time distribution, replenishment cadence and repeat-offender patterns all come from it.

It requires continuous polling rather than sampling, which is why most availability datasets do not have it. On the hourly tier it is standard.

Where a retailer publishes it, yes — typically via a store stock checker or click-and-collect availability on the product page. Coverage varies enormously by retailer and we confirm the pattern per retailer before build.

Where availability is revealed only inside a basket flow, we do not collect it, because that means creating sessions and adding items. Every record carries location_scope so you always know whether a figure is store, area or national level.

No, and nobody scraping public pages does. Inventory depth, units on hand and allocation are internal retailer data.

Where a retailer displays a low-stock hint — "only 3 left" — we capture it exactly as displayed, as text or a number, without treating it as a verified quantity. Those hints are often thresholds rather than counts, and presenting them as inventory levels would be misleading.

We distinguish them where the evidence supports it, and flag the ambiguity where it does not. A product unavailable long enough that a delist is plausible carries a flag rather than a determination.

Continued observation resolves most cases: a delisted product typically disappears from the category listing entirely, while a stock-out usually remains listed as unavailable. For range analysis specifically, catalog and assortment data treats delisting as the primary signal.

Hourly where availability is the primary use case, several times daily otherwise. Daily is close to useless for transition capture — you will see that a product went out without seeing when, for how long, or whether it came back.

We scope which SKUs and locations justify hourly rather than applying it universally, since hourly collection across a full estate multiplies cost substantially for SKUs that rarely go out.

It can often explain them, and it is one of the more satisfying uses. Joining out-of-stock minutes per SKU and location to your own sales data usually accounts for a meaningful share of unexplained variance.

It also improves forecasting, because demand history suppressed by stock-outs is otherwise fitted as genuine low demand. Correcting for out-of-stock minutes is a straightforward adjustment once the duration data exists.

We quote individually. The dominant driver is locations multiplied by SKUs multiplied by frequency — store-level hourly collection is the most expensive configuration in our catalogue, and often unnecessary at full scope.

A defined SKU set at national online level with several-times-daily refresh sits at the lighter end. Store-level hourly across a large estate sits considerably higher. We design the location sample with you before quoting. One scoping call, a free pilot on your own SKUs within 48 hours, then a fixed monthly quote. Request a quote.

See real availability data for your own SKUs

Send us a SKU list and retailers. We return availability with stock-out timing, duration and replenishment events within 48 hours.

Free pilot, no card, no obligation. We'll confirm which retailers expose store-level availability publicly.
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

Your National Price Report Is Hiding Your Worst Markets

A national price average is the arithmetic mean of your best and worst markets. Why geo-resolved price collection changes the numbers, and how to do it correctly.

thumb
Case Study

Building a 50,000-Product Retail Catalogue With Nutrition Data: Wegmans US

A one-time extraction of up to 50,000 Wegmans products with pricing and nutrition attributes. Why single-location scoping and attribute completeness decide whether a bulk catalogue is usable.

thumb
Report

Brazil Car Rental Pricing Intelligence Report 2026

Brazil Car Rental Pricing Intelligence Report 2026 reveals rental price trends, market shifts, competitor rates, and opportunities for smarter pricing.

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