WooCommerce Public Catalog — Prices & Stock

Enter a WooCommerce store URL with an accessible public Store API; no merchant API key is needed.
Download product names, prices, currency, stock status, categories and image URLs as JSON, CSV or Excel.

Catalog summary and completeness

RUN_REPORT.sources contains a summary for every attempted store: delivered/fetched product counts, in-stock/out-of-stock/unknown counts, sale counts, and average/total prices separately for each currency. Missing or invalid prices are counted separately. Summary values cover only delivered products and add no billable dataset rows.

RUN_REPORT.snapshotComplete is true only when pagination finishes for every requested store without source errors or output/request limits. Page-cap exhaustion and a truncated first-run example are incomplete. snapshotScope, sourceDatasetId, sourceRunId, and sourceActorId bind the report to its source. The run report can feed this author's Dataset Change Detector together with the source dataset; use product keys ["storeUrl", "id"] and reuse one named baseline store. Launch the comparison only after the source run finishes successfully.

This release does not add per-variation rows or private stock quantities. Existing product output and pricing remain unchanged.

Batch delivery and store links

Results are saved in batches of up to 100 and reports count only the delivered prefix when a spending limit cuts a batch. A conventional /shop/ link is normalized to the store root (or the parent WordPress installation directory). The 5,000-result setting is a cap, not a guarantee: response sizes, robots, requests and the 240-second processing deadline still apply.

Real output example

Captured on 2026-09-14 from run 7WaNm6Ql94zwh0jf6 using the input below. Selected fields are shown; long values are shortened with an ellipsis. Live source data can change.

name	price	currency	inStock
Help Scout Connector	59	USD	true
Bulk Search & Replace	49	USD	true
Product Dependencies	29	USD	true

The first-run example intentionally stops at 3 results. LIMIT_REACHED is expected and does not mean the complete store, board or feed was collected.

Quick start

1. Leave the prefilled example in place and click Start for a small first run. Replace it with your own source when ready.
2. Set Maximum delivered results and Apify's Maximum cost per run.
3. Run the Actor. Export the dataset as JSON, CSV or Excel. Open Run report for errors, skipped items and limits.

{
  "storeUrls": [
    "https://woo.com"
  ],
  "maxResults": 3
}

What it supports

Uses the public Store API products route /wp-json/wc/store/v1/products, falling back to ?rest_route= for plain permalinks and to the site root when the given directory has no Store API. One row per publicly listed product, not per variation. Variable products may expose the public price range/default price rather than every variant. Supports WordPress installed in a subdirectory by including that path. Currency minor units are converted (including three-decimal currencies). No login, private inventory quantities, orders or customer data. Up to 10 stores, 50 pages per store and 5,000 results per run. A disabled Store API or robots restriction is reported, not bypassed.

Price

$0.0020 per product ($2 per 1,000), plus $0.001 per run start at the supported 512 MB–1 GB memory sizes. The custom result event is charged only for a delivered dataset row. There is no separate automatic dataset-row fee. A run that returns zero rows still incurs the start fee. Your account's displayed pricing and platform terms apply. Actor authors pay their own platform resource costs during development and testing.

Set the maximum cost in Apify to cap spending. maxResults also limits output. A limit may truncate a catalog or comparison; inspect RUN_REPORT rather than assuming completeness.

Output and reliability

Main fields: name, sku, price, currency, inStock, url. Each row includes observedAt. Nested values remain JSON; choose JSON export to preserve all detail.

RUN_REPORT contains result count, HTTP request/download totals, source errors, skipped unchanged items and final status. PARTIAL means at least one source failed while other rows were delivered. FAILED means no successful result and at least one error. Successful empty feeds or no-change comparisons can legitimately return zero rows. A 240-second processing deadline and Apify's run timeout bound execution. Downloads are limited to 40 MB per run, with smaller per-response caps; robots checks count as requests. No proxy or external AI API subscription is required.

Only public pages and documented public APIs are supported. Access restrictions are reported. The crawler does not send your Apify token to target websites or connect to private network addresses. Use sources you are entitled to access. Static HTML tools do not execute website JavaScript.

Repeated runs

For Actors with stateStoreName, use a distinct name for each collection and keep the same name for later runs. Apify creates that store in your account; storage retention and access follow your account settings. Do not start overlapping runs that share a store. onlyChanges emits new/updated items and retains at most 10,000 recent fingerprints. It does not infer removed pages/jobs. Other Actors are stateless: supply fresh inputs, or feed their datasets into the Dataset Change Detector.

Apify tasks, schedules and integrations can reuse this input. No recurring schedule or customer notification is created automatically.

عربي

أداة جاهزة للتشغيل من واجهة Apify أو API. أدخل الروابط أو البيانات، وحدد عدد النتائج والحد الأعلى للتكلفة. النتائج بصيغ JSON وCSV وExcel، والتفاصيل والأخطاء في RUN_REPORT. البيانات العامة فقط؛ الحقول غير المتوفرة تبقى فارغة. راجع حدود الأداة أعلاه قبل اعتماد النتائج.