Observable data collection for e-commerce

Web data collection that follows the real page journey.

Model the visible browser interactions behind dynamic product data, validate every transformation and monitor each run before the result reaches a pricing decision.

Map a collection workflow Explore a live scenario

Single pages · Lists · Search results · CSV/XML feeds

reevals.app / collection / run-40218 Illustrative workflow

01
Open product pageHTTP 200 · 420 ms
02
Select colour: blackVisible page control
03
Wait for price responseDOM · network idle
04
Capture required fieldsPrice · stock · shipping
05
Validate and storePreview before publish

store.example / outdoor-grillLive page state

Outdoor grill 60 cm €1,199.00 In stock

Raw capture"1.199,00 €"Stored value1199.00 EUR

Run activeOpening the page

Start with the source you actually have

Product pages, result lists and feeds do not behave the same way.

Each source keeps its own navigation, extraction and health logic while producing consistent downstream fields.

Single product page

Capture the definitive product state, including variants and fields revealed after interaction.

Detail verification

List and category pages

Discover product URLs, work through pagination and preserve the relationship to each listing.

URL reconciliation

Search results

Submit a query, wait for the result state and follow matching products into their detail pages.

Search workflow

CSV and XML feeds

Map source columns, preview common fields and normalize values through the same validation pipeline.

Mapped import

Browser interactions, made explicit

When a person has to work through the page, the workflow can describe that journey.

Reevals uses the visible controls and states of the configured page: click, fill, scroll, wait, branch and capture. The sequence remains inspectable instead of disappearing inside a black box.

01 / 04

The price appears only after a valid variant is selected.

Discover available colours and sizes, iterate the valid combinations and capture the resulting price and stock state for each one.

Discover control options
Loop valid combinations
Capture the resulting state

store.example / grill

Choose colour

Choose size

Visible result€1,199.00In stock

Sequencediscover → foreach → click → wait → capture5 states

02 / 04

A search result is a journey, not a single URL.

Fill the query, submit it, wait for the result DOM, collect product links and continue through pages without losing the source context.

Fill and press Enter
Wait for result DOM
Follow discovered URLs

store.example / search

outdoor grill⌕

Outdoor grill 60 cm€1,199 · in stock

Compact gas grill€899 · in stock

Grill cover€79 · accessory

Sequencefill → enter → wait DOM → foreach URL12 URLs

03 / 04

The page has loaded. The data has not.

Wait for a visible element, a URL change, a network response or a settled DOM state instead of capturing the page too early.

Wait for visibility
Observe network completion
Capture only after the condition passes

store.example / availability

Loading store availability…

Availability resolved7 stores in stock

Conditionwait: [data-stock-state] visible1.8 s

04 / 04

A cookie banner should not silently block the next step.

Identify a configured overlay, clear the visible obstruction, scroll the target into view and continue through the intended page flow.

Hide configured overlay
Scroll target into view
Record the action in the run

store.example / product

Product details are now reachable

Cookie preferences

This overlay covers the configured target.

Sequencehide obstruction → scroll → captureCleared

Build the journey from visible actions

Model the browser flow before you trust the extraction.

Combine small, reviewable actions into reusable scenarios. Branch only when the page requires it. Keep the happy path readable.

01⌨Fill inputEnter a query, SKU or postal code

02↗Click or pressUse the visible page control

03◌Wait for stateDOM · URL · network · visibility

04⑂Loop or branchVariants, elements and conditions

05□Capture evidenceFields, URL, HTML or screenshot

Bounded action timeoutsBounded loops and combinationsReviewable branch logicScreenshots available for diagnosis

Raw value to decision-ready field

See the value at every stage—not only after it is wrong.

The common-field preview uses the same normalization path as the stored value. Teams can inspect what was picked, how it was transformed and what will be published downstream.

Price and currency normalization
Availability and delivery mapping
Ratings, identifiers and product attributes

01 · Picked from page"1.199,00 €"selector: [data-price]

02 · Transformed1199.00parser: decimal_eu

03 · Final stored value1199.00 EURtype: money

Stock availability"In stock" → in_stockValidReview rating"4.8 out of 5" → 4.8ValidShipping price"—" → nullReview

Operational visibility after launch

Know whether the page responded, the workflow finished and the product was really missing.

HTTP response and processing outcome stay separate. A healthy run is confirmed only after the final callback and queue work are complete.

Current run

List · Garden category

Running

✓Crawling24 pages

✓Preparing product URLs186 URLs

Extracting142 / 186

76%

Product lifecycle evidence

Outdoor grill 60 cm

SKU 40218

EvidenceStateObserved

Category listingMissingNow

Direct product checkHTTP 20012:41

Processing outcomeProduct present12:41

Consecutive misses1 / 3Tracked

iA missing listing URL triggers direct detail verification instead of immediately marking the product unavailable.

Collected once. Kept in context.

The workflow does not end at extraction.

Validated fields retain source, freshness and run evidence as they move into the rest of the pricing system.

Collection evidence1199.00 EURProduct present · fresh 12 min

02Product matchingComparable context

03Market monitoringOffer and rank

04Pricing decisionsRules and guardrails

06AnalyticsMeasured outcome

Reliability needs an honest boundary

A durable workflow starts with the source—not with an unlimited promise.

We configure collection around the source structure, permitted access and a responsible cadence. Exact support is assessed against the real page or feed. Run state and limitations remain visible after launch.

01Source access and load constraints are part of the design.
02Failed transformations cannot silently publish a valid-looking value.
03Operational changes remain reviewable and auditable.

Before we map the source

Questions teams ask about collection workflows.

Yes, when the required path can be expressed through supported browser actions such as filling an input, clicking a visible control, scrolling and waiting for a page state. Exact support is confirmed against the configured source.

Continue the decision loop

Put validated market evidence to work.

Compare like with likeProduct matching

↗ 01

See the live marketCompetitor monitoring

↗ 03–05

Turn evidence into actionControlled repricing

↗

Start with one real source

Show us the page journey your team handles manually today.

We will map the source, required interactions, fields, validation rules and operational boundary before recommending a workflow.

Map a collection workflow Explore all solutions

Follow every pricing decision from signal to outcome.

Start with the bottleneck. Keep the wider context.

Bring evidence in. Move approved decisions out.

Technical context without the sales fog.

Web data collection that follows the real page journey.

Product pages, result lists and feeds do not behave the same way.

Single product page

List and category pages

Search results

CSV and XML feeds

When a person has to work through the page, the workflow can describe that journey.

The price appears only after a valid variant is selected.

A search result is a journey, not a single URL.

The page has loaded. The data has not.

A cookie banner should not silently block the next step.

Model the browser flow before you trust the extraction.

See the value at every stage—not only after it is wrong.

Know whether the page responded, the workflow finished and the product was really missing.

List · Garden category

Outdoor grill 60 cm

The workflow does not end at extraction.

A durable workflow starts with the source—not with an unlimited promise.

Questions teams ask about collection workflows.

Put validated market evidence to work.

Show us the page journey your team handles manually today.

Web data collection that follows the real page journey.

Product pages, result lists and feeds do not behave the same way.

Single product page

List and category pages

Search results

CSV and XML feeds

When a person has to work through the page, the workflow can describe that journey.

The price appears only after a valid variant is selected.

A search result is a journey, not a single URL.

The page has loaded. The data has not.

A cookie banner should not silently block the next step.

Model the browser flow before you trust the extraction.

See the value at every stage—not only after it is wrong.

Know whether the page responded, the workflow finished and the product was really missing.

The workflow does not end at extraction.

A durable workflow starts with the source—not with an unlimited promise.

Questions teams ask about collection workflows.

Can Reevals collect from pages that require clicks or selections?

How are dynamic product variants handled?

What happens when a product disappears from a list?

Can raw values be reviewed before they are stored?

Can collected products be matched automatically?

Put validated market evidence to work.

Show us the page journey your team handles manually today.