Is JSON-LD enough for product scraping?

It is a useful first source, but validate completeness against the page and your required product fields.

How should I track price changes?

Store currency, region, observation time, canonical URL, SKU, and parser version with each observation.

Can I scrape checkout or customer data?

Only with explicit authorization and a lawful data process; this guide focuses on public product information.

Why did stock change without a page change?

Availability can vary by API response, region, session, or fulfillment location even when the page template remains unchanged.

Extract Product Data From E-commerce Sites at Scale

TL;DR

E-commerce product scraping is difficult because price, stock, variants, shipping, and availability can change independently.
Prefer public structured endpoints or embedded product data when available; use rendered pages only for fields that require it.
Store observations with URL, SKU, currency, timestamp, region, and content hash so price changes are distinguishable from parser errors.
Nstdata Crawl fits bounded catalog collection and rendered product pages; your application still owns schema validation and business rules.

Why product pages need more than a title and price

Use Nstdata Crawl when catalog discovery and rendered artifacts are the repeated burden.

An e-commerce page can expose a list price, sale price, variant price, seller price, or a region-specific price. Stock can be represented as quantity, a boolean, a shipping promise, or a disabled purchase control. A scraper that stores only visible text creates ambiguous records. Start with Nstdata Crawl when catalog scope, rendering, and repeatable artifacts are part of the problem.

The Schema.org Product vocabulary gives a useful common language for offers, SKU, brand, and availability. It is a schema aid, not proof that a target page’s data is complete or current.