← Item Value Checker
Original aggregate data30 complete UTC days

What 4,642 resale price checks show about the path from photo to listing

We aggregated first-party product counters from Jun 10, 2026 through Jul 9, 2026. The result is a narrow, auditable usage report—not a claim about item values, unique people, estimate accuracy, or completed sales.

The fixed snapshot

Four counts, with their boundaries intact

4,643
valid photo checks

Images that passed validation and reached the estimator.

4,642
successful estimates

Responses that returned a price range and supporting listings.

100
listing drafts

Successful, user-requested AI listing generations.

99.98%
valid-check completion

Successful estimates divided by valid checks, not by page visits.

What the counters support

1. Once a valid photo reached the estimator, a result was highly reliable

The estimator recorded 4,643 valid checks and 4,642 successful estimates. That leaves a one-event gap across the full window. This measures the post-validation service path; it does not include visitors who never chose a photo or files rejected before estimation.

2. Listing work happened overwhelmingly inside the estimate workflow

Of 100 completed listing drafts, 97 (97%) carried the estimate-results source. That is evidence that the in-result drafting path is being used. It is not a 97% estimate-to-draft conversion rate: the counters are aggregate events, not session-linked cohorts.

3. eBay was the target for 98 of 100 completed drafts

The marketplace dimension recorded 98 eBay drafts (98%). This should not be read as an unbiased marketplace-preference survey: eBay is the product's default marketplace and the estimate results are built around eBay comps. The figure describes this workflow as configured during the report window.

Methodology

How this report was produced

  1. 1

    Fixed window: 30 completed UTC dates, 2026-06-10 through 2026-07-09. July 10 was excluded because it was still in progress when the snapshot was generated.

  2. 2

    First-party aggregates: the report generator issued GET-only reads for an allowlist of daily integer counters. It summed those days and discarded the daily rows.

  3. 3

    Server-confirmed primary events: a valid check is recorded after image validation; a successful estimate after a response is built; a listing draft only after generation succeeds.

  4. 4

    Privacy boundary: the snapshot contains no uploaded images, item titles, estimated prices, listing samples, emails, IP addresses, cookies, user IDs, or raw event logs.

Snapshot generated July 10, 2026. Source schema version 1. See the site's privacy policy for the broader product data policy.

What this dataset cannot answer

No item mix

The retained aggregates do not show categories, brands, titles, conditions, or value buckets.

No accuracy study

An estimate event says a result was delivered, not that a later sale confirmed the price.

No unique-user count

One person can generate multiple events; the report counts product actions, not people.

No market-share claim

Marketplace defaults and interface placement influence which draft option gets used.

Put the workflow behind the numbers to work

Upload a photo, review the supporting listings and range, then decide whether the item is worth listing.

Check an item free