Shopping Feed Leak Watch — Shopify & WooCommerce
Pricing
$2.00 / 1,000 audited variants
Shopping Feed Leak Watch — Shopify & WooCommerce
Shopify feed price mismatch monitor: compare Shopify, WooCommerce or feed variants with live pages; track price, stock, GTIN and image exceptions.
Pricing
$2.00 / 1,000 audited variants
Rating
0.0
(0)
Developer
Jean Swiegers
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Features
Share
What does Shopping Feed Revenue-Leak Watch do?
Shopify feed price mismatch monitor for evidence-backed, stateful exception lists. Compare a public product feed or Shopify / WooCommerce catalog with the corresponding product page. Track NEW, CHANGED and RESOLVED findings instead of repeatedly exporting the same audit.
This is a private technical proof of concept, not a validated revenue-loss predictor. Customer pilots and willingness-to-pay validation have not passed. No daily schedule or messages are created automatically.
Why use a feed/page drift API?
Paid-shopping agencies can review products whose public feed price, offer stock, currency, GTIN or image disagree with the exact variant's structured page evidence. Unknown fields are reported separately. A blocked page or missing GTIN never silently becomes a clean bill of health. Previously active issues remain active until the same check produces comparable matching evidence.
Use your actual merchant feed for an independent comparison. Public Shopify products.json and WooCommerce Store API mode are convenient catalog consistency tests, not access to Merchant Center diagnostics. They can share an upstream backend with the landing page, so agreement is not independent proof of advertising eligibility.
What data is returned?
| Field | Meaning |
|---|---|
| kind / event | exception versus diagnostic; NEW, CHANGED, RESOLVED, optionally PERSISTENT |
| title / sku / variantId | Product identity where available |
| field | currency, structured_price, visible_price, availability, gtin, image or variant |
| expected / actual | Feed value and observed page value |
| firstSeen / lastSeen | Observation timestamps; not when Google first disapproved a product |
| evidenceUrl | Exact variant landing page |
| reviewRequired | Image differences require human review |
The default dataset contains change events and coverage diagnostics. The default key-value store's SNAPSHOT contains all checked variants/checks; SUMMARY records request/coverage counts. Download the dataset as JSON, HTML, CSV or Excel or use Apify's API tab.
How to run a Shopify or WooCommerce feed mismatch check
- Enter up to five public
storesobjects withurl,platformand a knowncurrency, or supply HTTPSfeedUrls. - For a feed-only run set
stores: []. Supported feed formats are Google-style XML/RSS, CSV and a JSON item array. Fields: id, link, price, currency, availability, variant_id, sku, gtin, image_link. A price such as29.00 USDcarries its currency. - Start small with
maxItems: 5,maxRequests: 20. - Reuse the same
monitorIdon later runs for diffs; use a new ID for a different market, currency or configuration. Do not run the same monitor concurrently. - Inspect UNKNOWN checks and diagnostics as carefully as exceptions.
Example public demo input:
{"stores":[{"url":"https://theme-dawn-demo.myshopify.com","currency":"CAD"}],"maxItems":1,"maxRequests":6,"monitorId":"dawn-cad"}
Illustrative output, not a finding about that demo store:
{"kind":"exception","event":"NEW","field":"structured_price","expected":29,"actual":19,"evidenceUrl":"https://example.com/product?variant=123"}
Cost and proposed pricing
Private prototype only: Apify compute/storage/transfer applies; no monetization has been configured. Fetching is bounded and uses no proxy by default. Publication proposal, subject to Jean's approval and measured margins: US$0.002 per successfully audited variant event (US$2/1,000), not per alert. Charging only anomalies cannot cover audits that find no problems. Diagnostics/individual field findings would not be additional charges. The audited-variant hook bills at most once per completed exact-identity audit with at least one comparable non-identity field. UNKNOWN-only/error rows, diagnostics and extra field findings do not add charges. The run charge cap is respected; no fees are activated while the Actor remains unpriced.
Limits, safety and support
This is a static HTML/JSON-LD checker, not a browser-rendered checkout audit. Static displayed-price checks require one unambiguous recognized current amount. WooCommerce sale prices prefer the active ins amount over del regular prices, including accessibility-hidden duplicate markup. UnitPriceSpecification arrays distinguish current versus ListPrice values; European decimal/currency-suffix amounts are supported. This is not a browser-computed visibility or checkout test, and ambiguous/JS-only amounts remain UNKNOWN. Exact variant/SKU selection is mandatory. Missing variants are unknown, not proven mismatches. Missing Shopify barcodes can be enriched through the documented public Ajax Product API, matching the exact variant ID; this adds at most one cached request per product. GTIN comparisons require independently supplied feed/catalog and page values, valid check digits, and normalized UPC/EAN padding. A SKU-like barcode is not treated as a GTIN. Identifiers omitted by WooCommerce or either page remain UNKNOWN with a coverage reason. Image URLs are normalized for common Shopify CDN aliases and sizes, not visually compared. No image bytes are fetched. WooCommerce uses the public, unauthenticated Store API type=simple, preserving installation subdirectories. WooCommerce catalog mode covers simple products; variable products need explicit variant feed links and may remain unknown.
Only public HTTPS destinations are accepted; credentials/custom ports/private/reserved IPs and DNS addresses are rejected. Robots policies, byte caps, timeout and total-request limits are enforced. No retries, login bypass, admin changes, checkout, feed corrections or alerts are performed. Use sources you may lawfully access, respect licensing/terms, and do not include personal data or secrets in feeds. Private named state persists between runs; the per-run default store is not the history store. Keep monitor IDs separated. Raise implementation issues through the Actor's Issues tab when access is available.
WooCommerce example and coverage
{"stores":[{"url":"https://demo.woostify.com","platform":"woocommerce"},{"url":"https://websitedemos.net/brandstore-02","platform":"woocommerce"}],"maxItems":2,"maxRequests":8,"monitorId":"woo-two-demo-stores"}
No WooCommerce admin keys are requested. The public catalog's minor currency units are normalized. Summary checkCoverage separates MATCH, MISMATCH and UNKNOWN for every field. An empty exception dataset does not prove all fields were audited; always inspect SUMMARY and SNAPSHOT. Public demo stores are technical fixtures, not customer pilots. No Merchant Center account, refund, lost-sales estimate or automatic correction is involved.