Product Price Availability

Product Price & Availability Snapshot

One small job: Read a single public HTTPS product page and output one price/availability snapshot from schema.org Product JSON-LD or from standard public product:* meta tags on the same HTML page. No crawling, browser, login, Amazon or eBay.

For: Merchants, analysts, and product-feed builders who need a bounded, structured snapshot from a URL they supply.

First-run example (real public product)

The Console prefill is:

{"product_url":"https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/"}

On 2026-11-01, this live product page was accessible and public head metadata included product:price:amount=351.66, product:price:currency=CAD, and product:availability=instock. The Actor reads those meta tags if JSON-LD lacks a usable offer. The store's prices and stock can change at any moment. A successful network fetch of the original HTML by the Actor has not been tested in the local container or on Apify; the live target was separately checked using a public webpage retrieval service. If the third-party store changes its markup or access rules, replace it with a suitable public product URL.

Example output (illustrative date, based on verified public meta fields):

{"url":"https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/","price":"351.66","currency":"CAD","availability":"InStock","checked_at":"2026-11-01T00:00:00Z"}

Output fields: url (supplied URL), price (decimal string or null), currency (ISO currency or null), availability (schema.org normalized term or null), checked_at (UTC ISO 8601 run time). One object per run, never a historical database. A null indicates unknown, not zero or out-of-stock. JSON-LD is preferred; supported values include InStock, OutOfStock, PreOrder, BackOrder, Discontinued, etc. With AggregateOffer, lowPrice is used as the price snapshot when an exact offer price is absent, so it may not represent every variant.

Run locally (no SDK)

$ACTOR_INPUT_JSON='{"product_url":"https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/"}' python src/main.py

Or create storage/key_value_stores/default/INPUT.json. Results are written to storage/datasets/default/000000001.json etc. On Apify, the runtime reads the INPUT record and writes the dataset through the Apify REST API, not the SDK.

Limits and data policy

• One user-supplied public product HTML page; one GET, response up to 2 MB, 15-second timeout. No other host, no redirects, no retry, no JavaScript rendering, no pagination. Public HTTPS and DNS validation; no private/local IPs.
• Reads application/ld+json scripts for Product offers.price, offers.lowPrice, priceSpecification.price, priceCurrency and availability, including @graph, plus public HTML meta properties product:price:amount, product:price:currency, product:availability as fallback. Does not guess from visible price text or dollar symbols.
• Dynamic JavaScript-only product offers, Shopify variant JSON, currency changes by location, store taxes, shipping, logged-in discounts, and stale structured data are outside scope. A result is page markup, not checkout-confirmed inventory or a verified transaction price.
• Errors are simple and no record is invented. Respect store policies. The example is a third-party live URL, not an owned or guaranteed stable demo.
• Includes runnable offline unit tests and an actual script-mode subprocess smoke test with a mocked HTTP product page. The fixture is labeled simulated; it is not a verified live Apify run.

Store categories and pricing (proposal only)

• Apify Store categories (declare on Store listing): ECOMMERCE, SCRAPING.
• Suggested pricing: $3 per 1,000 emitted result items ($0.003/item). Pricing is only a suggestion; nothing is published or billed.

Verification

From the Actor folder: python -m unittest discover -s tests -v and python tests/smoke.py. The latter directly invokes python src/main.py, checks the JSON file, and prints the exact terminal result. See Batch 2's root VERIFICATION.md.