Shopify Product Data Quality & SKU Collision Audit

Deterministic product-data findings with severity, rule ID, affected variants and supporting values. Cross-product SKU collisions are checked only across the supplied successfully fetched products; useful for preparing data cleanup work.

Quick start

Supply1-10 canonical public Shopify product URLs. The prefilled example processes one product. No Shopify login, API key, browser, proxy or AI service is needed.

Example input:

{"productUrls":["https://www.deathwishcoffee.com/products/2026-death-wish-coffee-mug"]}

Results

One dataset row per successfully processed product; nested arrays stay structured in JSON. Use Apify dataset exports for JSON/CSV/Excel. Common fields: stableKey, productId as string, productUrl, sourceUrl, productTitle, checkedAt. Specific fields: issueCount, findings, notExposedFields, auditScope. OUTPUT reports per-product source errors, stored report count, charged count and budget truncation.

Pricing

Pay per event USD0.003 per saved product report (USD3 per1,000 reports). This is per product report, not per asset, finding, review or variant. Failed/unsupported sources and diagnostics are free. A valid report with zero findings, zero reviews or zero media can be chargeable because the requested check succeeded. Platform usage charges may also apply. Every report is stored before its event is charged. Storage and billing are separate services; interruption between them is not an atomic transaction. A billing/storage failure stops processing rather than silently continuing.

Scope and limitations

Public field checks only; no Shopify Admin data, checkout, feed ingestion, Google Merchant Center validation, SEO rank or legal/accessibility certification. Missing fields are issues only when the public API field exists and is blank; absent fields are NOT_EXPOSED, not proved merchant omissions. Blank SKUs may be intentional. Prices use raw Ajax numeric representation and are checked for finite nonnegative integers only; no currency/FX or discount-validity claim. SKU collisions are case-sensitive and scoped to one store and the supplied successfully fetched products, not a complete catalog. Findings are advisory, not a claim that a store is broken.

Each run reads at most10 selected products, 10 primary HTTP requests, at most3 same-origin redirects per request,4MiB per response and120 seconds of source work. No unbounded pagination or retries. Headless/password-protected stores may be unsupported; public source formats may change. All unsupported/failing inputs fail the run when no supported report can be produced; partial success is explicit in OUTPUT. Default QA input is small and intended to finish under5 minutes. Product IDs and handle/source URL are verified; unsafe numeric IDs are rejected rather than rounded.

Security and privacy

Read-only public HTTPS with DNS/IP validation and pinning, TLS hostname verification, same-origin redirects, hard caps and no arbitrary scripts, cookies, login or private network access. Product metadata may contain merchant-provided content; no customer/reviewer personal information is intentionally exported. No Admin API or cart writes. Not affiliated with Shopify or Judge.me. Respect content rights and target terms.

Development

Run npm ci, npm test and apify validate-schema. See TEST_PLAN.md and BUILD_PUBLISH_CHECKLIST.md for acceptance. Pricing is configured only for this new Actor; no changes to existing public Actor prices.