E-commerce
Target
Target product, price and availability data
Retail catalogue records with promotions, fulfilment and store-aware stock.
What we can collect
What data can be collected from Target?
The exact schema follows your brief, but a typical Targetdataset can include the following record groups when they are publicly exposed and permitted for the intended use.
- Products by category, keyword or SKU list
- Online and promotional pricing
- Pickup, delivery and shipping availability
- Variants, specifications and review aggregates
Practical field breakdown
tcinThe source identifier used to match this record across repeat collections.skuThe source identifier used to match this record across repeat collections.product_urlThe published Target location or destination associated with the record.titleThe public-facing title exactly as observed at collection time.brandThe organisation or account attributed to the record by Target.categoryThe published classification used for filtering, grouping and market comparisons.priceThe observed commercial value and its context; never silently converted or inferred.list_priceThe observed commercial value and its context; never silently converted or inferred.discountThe observed commercial value and its context; never silently converted or inferred.availabilityThe availability or fulfilment state shown for the relevant location and query context.image_urlsThe published Target location or destination associated with the record.ratingA platform-published reputation or engagement signal, stored with the observation date.review_countA platform-published reputation or engagement signal, stored with the observation date.specificationsA structured characteristic used to distinguish, match or compare records.sellerThe organisation or account attributed to the record by Target.store_idThe source identifier used to match this record across repeat collections.page_numberThe listing or search context needed to explain where this record appeared, including pagination or rank when available.search_positionThe listing or search context needed to explain where this record appeared, including pagination or rank when available.captured_atA source timestamp or Scrapebuddy observation time used to build an auditable history.
Fields are representative rather than fixed. We show null when a value is not published; we do not quietly guess missing prices, identifiers, availability or review data.
What stands in the way
Actively defends against automated access. Feasibility is confirmed per project before anything is promised.
- Location-aware inventory
- Traffic and session validation
- JavaScript-rendered catalogue surfaces
Token estimate
~6tokens per record
An estimate for planning, not a quote. The final rate follows the real volume and the state of the source when we scope it.
Delivered through the Pricing & Repricing APICommon use cases
Where Target data becomes useful
Compare like-for-like product prices and stock by retailer
Enrich an internal product catalogue with public attributes
Track promotions, range changes and local availability over time
Delivery options
Delivered into your workflow
These are delivery formats we can arrange for a scoped project, not claims of a pre-authorised integration with Target.
Managed API
A documented endpoint shaped around the schema and query pattern agreed for your project.
Scheduled files
CSV, JSON or JSONL delivered on an agreed cadence for analysis or batch import.
Cloud or database delivery
A managed drop into your storage or database when direct delivery is the cleaner fit.
Worth knowing up front
Local availability requires an agreed set of stores or postcodes. A national snapshot cannot accurately represent store-level inventory.
We work within what each source permits and within applicable law. Where a source cannot be collected properly, we say so at feasibility stage rather than after you have paid.
Questions before you scope it
Target data FAQ
Can Scrapebuddy collect fields not shown on this page?
Usually, if Target publishes them and the intended use is permitted. Send the fields and representative URLs; feasibility is checked against the real surface before anything is promised.
How frequently can Target data be refreshed?
Cadence is agreed around how quickly the values change and the cost of each query. Every delivery includes observation timestamps so snapshots and changes remain distinguishable.
What happens when the source changes?
Managed projects are monitored and repaired as source behaviour changes. A layout or request change is handled as maintenance rather than handed back as a broken script.
Can the data be used in a customer-facing product?
That depends on the source, fields, jurisdiction and intended use. We confirm collection feasibility, but you remain responsible for rights to store, publish or redistribute third-party data.
Request a read on Target
Tell us exactly which pages and fields you need. We'll confirm what is reachable, return sample records where the source allows, and give you a token estimate for your volume — or tell you plainly if we don't think it can be done well.
- Written feasibility read before any commitment
- Sample records where the source permits
- An honest no if that is the answer
Prefer email? sales@scrapingbuddy.com
No spam. A real person will review your request and reply.