catalog-audit

Validate Adobe Commerce product data against Catalog Service GraphQL API and AEM Edge Delivery storefront.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill catalog-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catalog-audit
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/catalog-audit
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill catalog-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of incorrect or stale product data showing on an AEM Edge Delivery Services storefront after changes in Adobe Commerce, by validating end-to-end product rendering against the Catalog Service API.

Core Features & Use Cases

  • Catalog Service connectivity validation: Confirms the Catalog Service GraphQL API is reachable and returning expected product data fields.
  • API-to-storefront data integrity checks: Compares product name, price (regular/final, currency, tax handling), descriptions, availability, and category/breadcrumb behavior between API responses and rendered PDP/PLP content.
  • Product images and Live Search verification: Checks image loading, image correctness, and validates Live Search result accuracy and relevance for sampled products.

Quick Start

Use catalog-audit to run a data integrity audit between Adobe Commerce and your EDS storefront after a catalog update or when customers report incorrect product data.

Frequently Asked Questions about catalog-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Adobe Commerce product data on an AEM Edge Delivery Services storefront?

Verify Adobe Commerce product data on AEM Edge Delivery Services by running a data integrity audit that samples the Catalog Service GraphQL API and compares API values field-by-field against rendered PDP and PLP storefront pages. It generates a discrepancy report with severity scoring and remediation guidance.

Why does my storefront show stale pricing or incorrect product images after a catalog update?

Storefront stale pricing or incorrect product images after a catalog update occur due to commerce-to-storefront sync drift. An API-to-storefront data integrity check identifies mismatches by comparing rendered storefront content against Catalog Service API responses for pricing, availability, and image loading.

Can I test Live Search accuracy and category navigation against the Catalog Service API?

Yes, you can test Live Search accuracy and category navigation by validating the Catalog Service GraphQL API connectivity and checking that rendered category breadcrumbs and search results match expected API product data fields, ensuring relevance and correct storefront behavior.

What is the best way to audit data discrepancies between Adobe Commerce and a storefront?

The best way to audit data discrepancies between Adobe Commerce and a storefront is to perform an end-to-end validation that fetches rendered pages, samples API responses, executes field-by-field comparisons with severity scoring, and outputs a comprehensive discrepancy report with actionable remediation guidance.

Does catalog-audit work without external dependencies or components?

Yes, catalog-audit operates without external dependencies or components. It internally manages connection testing to the Catalog Service API, fetches rendered storefront pages, and executes field-by-field comparisons to produce a discrepancy report directly.