---
title: "eBay listing data: listing IDs, offers & sold history"
url: https://www.datawebot.com/blog/ebay
description: "Map eBay listings, selected variations, seller offers, auctions and sold history. Separate active offers from Product Research sales evidence."
updated: 2026-10-18
author: datawebot team
---

Independent source guide

# eBay listing data: IDs, variations and sold-price research

Map eBay listings, selected variations, seller offers, auctions and sold history. Separate active offers from Product Research sales evidence.

Updated October 18, 2026 · datawebot team

## Keep eBay listing, variation and catalog product separate

A listing, an individual purchasable variation within it, and an eBay catalog product are different records. Keep each value with its source so a parent listing is not mistaken for one option.

| Identifier | What it refers to | How to preserve it |
| --- | --- | --- |
| Listing | One seller's listing at its source URL. A multi-variation listing groups several options, such as different colors or sizes, under one parent listing. | Record the listing URL as the parent listing. Join a specific option only when the selected variation is captured. |
| Selected variation | The exact size, color, model or edition chosen within a multi-variation listing. | Store the selected option with the listing record; the parent listing alone does not identify one option. |
| ePID | An eBay catalog product ID identifies an associated catalog product; a listing may not have one. | Keep it as an optional catalog match, separate from listing and seller-offer records. |

[Structured e-commerce data fields ↗](https://www.datawebot.com/docs/data) · [Build a product price-history database ↗](https://www.datawebot.com/blog/build-product-price-history-database)

## Compare the complete eBay offer context

A displayed amount only compares like with like when the listing format, marketplace, selected option, condition and delivery basis are preserved with it. Keep seller and shipping terms as separate visible fields; omit buyer account details and member personal information.

| Context | What to record | Comparison rule |
| --- | --- | --- |
| Marketplace and currency | The eBay site/marketplace, displayed currency, and destination context when known. | Do not combine prices from different markets or convert currency without recording the rate and time. |
| Selling format | Fixed price, auction, or another displayed buying option; for an auction, the current bid and observation time. | A fixed price is an asking offer. An auction bid is not the final sale price. |
| Selected variation and condition | Exact size, color, model or edition and the stated item condition. | A different option, bundle or condition is not a like-for-like offer. |
| Seller and delivery terms | Only the seller/delivery details presented for the selected listing, item price, shipping charge and delivery basis when visible. | Keep shipping separate from item price and avoid collecting user information without consent. |
| Listing state and time | Source URL, active or ended state, and observation timestamp. | A later page may be a revised, unavailable or ended offer rather than the same listing. |

[Price monitoring across repeated offer observations ↗](https://www.datawebot.com/blog/price-monitoring-guide-for-ecommerce)

## Separate active offers from eBay sold-history evidence

An active item page shows a seller's current offer or auction state; it does not reveal the price a buyer paid. eBay's seller research tools answer historical-sale questions with a separate dataset and stated time range.

| Evidence source | What it can answer | Limit to preserve |
| --- | --- | --- |
| Active item page | The buyer-facing price or bid, condition, selected variation, seller/delivery terms and state visible at capture time. | This is an offer observation, not a completed transaction or sales trend. |
| Completed-listing results | eBay help describes sold listings that ended within the previous 90 days. | Treat it as a recent window, not a multi-year sales history. |
| Product Research in Seller Hub | For sellers with access, eBay reports up to three years of sales data across eBay marketplaces, with price ranges/averages, shipping metrics and selling formats; results include actual sale price when a Best Offer was accepted. | Search terms and filters matter; do not infer an accepted offer price from the original listing price or compare loosely related results as identical products. |
| Your dated offer captures | How an asking price or current auction bid changed across observations you actually recorded. | A self-built offer history cannot reconstruct a sale or earlier price that was never captured. |

[eBay Product Research time range, filters and Best Offer results ↗](https://www.ebay.com/help/selling/selling-tools/terapeak-research-and-SEO?id=4853) · [Build a product price-history database ↗](https://www.datawebot.com/blog/build-product-price-history-database)

## Keep eBay terms separate from crawler directives

The current eBay.com User Agreement and the eBay.com robots file are different sources with different scopes. Record their checked date and exact version or user-agent group; robots rules alone do not establish permission for a particular data-collection use.

| Source | Checked statement | Boundary |
| --- | --- | --- |
| eBay.com User Agreement, section 3 | Checked October 4, 2026. The posted version is effective June 28, 2026 for users who agreed to a prior version and upon acceptance for new users; it names eBay Inc. for U.S. residents. Section 3 names robots, scrapers, data mining and data-gathering/extraction automation, except with eBay's prior express permission; it separately addresses technical circumvention, unreasonable load and collection/use of user information without consent. | Attribute this to the reviewed eBay.com agreement. Do not make a legal determination about an individual workflow or generalize to every local eBay site's agreement. |
| eBay.com robots.txt | Checked October 4, 2026; the file showed no last-updated date. GPTBot is in a group with Disallow: / and enumerated allowed paths. OAI-SearchBot and ChatGPT-User are in a separate group with path/query-specific rules and exceptions. | Different user-agent groups do not share one blanket rule; robots directives are crawler instructions, separate from contractual permissions. |

[eBay.com User Agreement ↗](https://www.ebay.com/help/policies/member-behavior-policies/user-agreement?id=4259) · [eBay.com robots.txt ↗](https://www.ebay.com/robots.txt) · [Robots.txt and access-policy concepts ↗](https://www.datawebot.com/blog/robots-txt-legal-considerations-web-scraping) · [Dynamic pricing use case ↗](https://www.datawebot.com/solutions/dynamic-pricing-optimization)

Content reviewed 2026-10-18.