Checking one product? Use the free Product Schema Checker to review brand, GTIN/MPN, price and availability in Product JSON-LD.
What is an Adobe Commerce product data audit?
An Adobe Commerce product data audit compares product identity, selected variant, price, currency and availability across the public storefront, Product/Offer structured data and any supplied channel record. Its output should identify the affected URLs, evidence, uncertainty, repair owner and a repeatable acceptance check.
Can Lumen test size and colour selections automatically?
Yes, on supported Adobe Commerce dropdowns and swatches when the selected child SKU can be resolved. Lumen samples up to three product pages, with the default state and up to three alternative combinations per product within a shared 20-second browser budget. This is a bounded sample, not a test of every combination or all 1,000 products.
Custom controls, Ajax POST flows and missing child-SKU metadata are unsupported or inconclusive. An inconclusive result is not a pass. Private Adobe Admin settings and unpublished feeds are not accessed by the public scan.
What does the $299 assessment include?
The one-time assessment covers one storefront, discovered catalog products up to the 1,000-SKU limit, six product-intent web searches and a PDF with prioritized findings. The interactive variant sample remains limited as described above. The six searches use Tavily Search; they do not directly measure recommendations inside ChatGPT or other assistants. Implementation is separate and rankings or sales are not guaranteed.
Review scope and buy the $299 assessment · See the evidence format before buying
Need a wider variant sample or a specific store view checked? Confirm fit before purchase with your public store URL, two affected product URLs, selected options and currency. Do not send credentials or customer data.
Start with a free three-product scan. For a deeper review, the $299 assessment covers one store with up to 1,000 products and six measured queries. You receive prioritized fixes and a client-ready PDF with supporting product-page evidence.
The storefront assessment checks publicly accessible data. Reviewing private admin settings or an unpublished feed requires those records to be supplied separately. Optional monitoring is $99/month.
Scan three products free See the sample reportWhen to request an Adobe Commerce audit
A product data audit is useful when configurable products show inconsistent prices or availability, store views publish conflicting details, or a channel feed disagrees with the landing page. It also gives a catalog team a baseline before changing attribute mappings or preparing product data for AI shopping discovery.
Lumen’s assessment focuses on public product-page evidence and a bounded shopping-query sample. A broader Magento security, code, checkout or performance audit needs a separately agreed scope. The published assessment does not include private admin inspection or implementation work.
Bring a specific catalog problem
Start with your public storefront URL and two or three affected product URLs. Note the intended store view, currency, selected variant and the value you expected to see. For price or stock discrepancies, use the product feed and landing-page mismatch checklist to compare the same offer across the visible page, structured data and channel record. Keep private feeds, credentials and customer records out of the public request.
Run the free three-product scan first, then inspect the sample report to see how evidence and fixes are presented. If your question needs a wider scope, discuss your Adobe Commerce audit requirements before purchasing.
What an Adobe Commerce product data audit should cover
Adobe Commerce and Magento catalogs can use attribute sets, configurable products, store views, websites and channel exports. A useful audit follows a product’s data from admin attributes to the rendered product page and then into the feed or discovery channel that consumes it.
A practical Adobe Commerce audit checklist
For each sampled product, record the public URL, selected option, store view, currency and time checked. The following is an illustrative worksheet, not a finding about your store.
| Check | Evidence to compare | Recheck after a fix |
|---|---|---|
| Configurable product | Selected child SKU and option against the visible title, image and offer | The same selected option describes the same purchasable product |
| Price and stock | Visible price, currency and availability against Product/Offer data and any supplied feed row | The same offer agrees across the records at the time checked |
| Product attributes | Missing or generic details across representative product families | The corrected facts appear on the affected public pages |
| Store-view consistency | Equivalent products in the intended store view and currency | The correction survives the next catalog export |
Prioritize conflicts on purchasable products, then repeated template or mapping issues, then isolated content gaps. Assign each repair to a catalog, theme or feed owner and retain the same URLs for remeasurement. The free public scan does not inspect private attributes or feed exports.
Keep a reusable product-data audit worksheet. Download the free Adobe Commerce audit worksheet (CSV) to record the same product, selected option, store view, currency and check time before and after a fix.
The blank template includes checks for product identity, identifiers, price, stock and store-view consistency, plus columns for evidence, expected values, owner, priority and recheck results. It contains no customer findings and requires no email or account. Fill it in locally; include a feed value only when you have that record. Do not put credentials or customer records in the worksheet.
Worked example: a configurable product price mismatch. Fictional values below illustrate how to fill in the worksheet; they are not a customer finding.
Suppose the selected option is a blue, medium shirt with child SKU SHIRT-BLU-M. Keep the same website, store view, USD currency and check time for every comparison. A parent product's starting price is not sufficient evidence of a mismatch with a selected child.
| Record | Illustrative evidence | Next check |
|---|---|---|
| Selected storefront option | Blue / medium; USD 35; in stock | Save the URL, selected options and time checked. |
| Product/Offer structured data | USD 29; option identity not established | Identify which product or offer the markup describes before calling it a conflict. |
| Supplied feed row | SHIRT-BLU-M; USD 35; in stock; earlier export | Confirm destination, currency, export time and whether the row describes this same child. |
Interpretation: the page and supplied feed row agree on price. The markup needs investigation: a USD 29 offer for another variation is different from stale markup incorrectly describing SHIRT-BLU-M. Compare the selected child's identity first; the sample does not establish the cause.
Assign and recheck: ask the theme or structured-data owner to inspect the selected offer mapping. If a mapping error is confirmed and fixed, recheck this child and a sibling option, then the next feed export. Record the evidence and outcome in the worksheet. Do not change every feed price based on a parent-price comparison.
Adobe explains the relationship between configurable products and their child products. Google's product variant structured-data guidance helps distinguish variants and their offers. These references describe platform behavior; they do not prove how a particular store is configured.
The free scan samples public product pages. It does not inspect a private feed, authenticate into Adobe Admin or guarantee interaction with every variant. Use the worksheet to add authorized private evidence locally, and start a free public product-data scan for an initial sample.
1. Review attributes and attribute sets
Check that important product facts use appropriate attributes with consistent codes, labels, scope and value types. Confirm the right attribute set is assigned to each product family and that key customer-facing attributes are enabled for storefront display where needed. Adobe documents how to add product attributes and how attribute sets define available product fields.
2. Test configurable products and store views
For configurable products, verify that the parent and each simple child have the expected identifiers, option values, images, price and salability. Test that selecting a child updates the storefront display. Compare values across relevant store views and currencies so localized pages and feeds do not present stale or conflicting details.
3. Match the page, schema and export
Compare visible product facts against Product and Offer structured data and the channel export. Check URL, title, image, SKU or GTIN where applicable, price, currency, sale dates and stock status. Confirm that an export maps the intended source attribute and includes the correct website or store-view values. Google’s Product structured data documentation describes supported product markup; valid markup can make a page eligible for certain appearances, but does not guarantee them.
4. Check indexing and product-page quality
Confirm that the canonical product URL is accessible, indexable when intended, returns the correct status, and provides distinct useful content. Check for duplicate URLs, layered-navigation parameters, empty descriptions, missing images, and variant pages that cannot be understood without client-side interaction.
5. Prioritize fixes by scope and impact
Start with a cross-category sample. Group repeated issues by attribute, product type, store view, and feed mapping so the team can fix the source once instead of editing products one by one. Recheck representative products after deployment and monitor whether the correction survives scheduled exports.