Catalog Audit: How to Find and Fix Product Data Problems
A catalog audit is a structured review of your product data to find what’s missing, wrong, inconsistent or out of date. It checks every product for complete attributes, accurate prices and stock, consistent variant names, usable images, duplicate content and the fields that sales channels and ad platforms require.
Product data drifts over time as supplier files, bulk imports, migrations and quick manual edits pile up. A regular audit catches those problems before they show up as broken filters, rejected ads or customers leaving product pages without the information they need.
What a Catalog Audit Checks
A thorough catalog audit looks at both the completeness and the quality of each product record. The table covers the main areas and the kinds of problems each one turns up.
| Area | What to look for | Why it matters |
|---|---|---|
| Completeness | Blank required fields, such as brand, product type, category, SKU, barcode or key attributes | Gaps break filters, search, feeds and comparison shopping |
| Descriptions | Empty, very short or copied descriptions shared across many products | Thin content leaves shoppers without answers and weakens product pages |
| Images | Products with no image, too few images, inconsistent backgrounds or sizes, missing alt text | Images drive buying decisions and are required by most channels |
| Variants and options | The same option spelled several ways, variants without their own price, SKU, stock or image | Inconsistent options create messy filters and wrong orders |
| Accuracy | Wrong prices, outdated stock, incorrect dimensions or specifications | Errors cause returns, complaints and channel disapprovals |
| Duplicates | Repeated products, titles or handles | Duplicates confuse shoppers, split reviews and clutter search results |
| Organization | Products missing from collections or categories, inconsistent tags, wrong product types | Poor organization hides products from navigation and filters |
| Availability | Published products that are out of stock with no restock plan, or drafts that should be live | Unbuyable products waste traffic and ad spend |
| Channel readiness | Missing fields that feeds require, category mapping gaps, price or stock mismatches between feeds and your site | Feed errors lead to disapproved or limited listings |
A catalog audit is different from an SEO audit. An SEO audit looks at pages, links and rankings, while a catalog audit looks at the product data underneath, which feeds your storefront, filters, marketplaces, ads and AI shopping tools alike.
How to Run a Catalog Audit
The most reliable audits work from a full export rather than clicking through products one by one. A spreadsheet lets you count problems across the whole catalog, sort them and turn them into a clear list of fixes.
1. Set the scope and standards
Decide what a complete, correct product looks like before you start counting. Write down the required fields for each product type, your naming rules for options such as sizes and colors, and the minimum content you expect, such as a set number of images or a description length.
If you sell through Google Shopping, marketplaces or other channels, add their required fields to your standard. Google, for example, expects an ID, title, description, link, image, price and availability for each product, plus brand and GTIN where they apply.
2. Export the full catalog
Export every product and variant with all the fields you plan to check, including metafields or custom attributes where your platform allows. Check that the export is complete by comparing the product count with what your admin shows, since a truncated file gives misleading results.
Add sales data if you can. A column with each product’s revenue or units sold over the last year lets you rank problems by impact later.
3. Organize the data for review
Most exports list each variant on its own row, which inflates counts for product-level problems such as missing descriptions. Create one view at the product level and another at the variant level, so you count each issue where it belongs.
Freeze the header row, turn on filters and keep an untouched copy of the original export. That way you can always check a finding against the source data.
4. Run the checks
Work through your standard one field at a time. Simple spreadsheet tools handle most of the counting:
- Blank fields. Filter each required column for blanks, or use COUNTBLANK to total empty cells per column.
- Thin descriptions. Add a word count column, then filter for descriptions below your minimum.
- Duplicates. Use COUNTIF on titles, SKUs, barcodes and descriptions to flag any value that appears more than once.
- Inconsistent values. Build a pivot table or unique list of option values, vendors, product types and tags to spot variations such as “Grey,” “Gray” and “gray.”
- Images. Count image URLs per product and flag products below your minimum, then check a sample of your best sellers visually for consistency.
- Availability. Filter for published products with zero stock and for products outside any collection.
Record the count for each issue, overall and by category. Those numbers show where problems cluster and give you a baseline to measure progress against next time.
5. Prioritize and fix
Sort the findings by impact rather than fixing them in the order you found them. The next section covers how to rank them, and the fixes themselves usually work best in bulk: correct the spreadsheet, then import only the changed columns back into your store.
When the same fix applies to hundreds of products, a bulk tool saves hours of manual editing. Bulkflow supports exporting selected store data and updating existing records in bulk with field mapping for Shopify, WooCommerce and Wix, which fits the export, fix and re-import cycle of a catalog audit.
6. Re-check and record the results
After the fixes go live, export the catalog again and rerun the same checks. Compare the new counts with your baseline, and note which issues came back, since recurring problems usually point to a process that needs changing.
Catalog Audit Checklist
Use this checklist as a starting point and adapt it to your product types and channels. Each item should have a clear pass or fail rule in your standard.
| Check | Pass when |
|---|---|
| Titles | Every product has a clear, unique title following your naming pattern |
| Descriptions | No empty descriptions, none below your minimum length and no copy shared across unrelated products |
| Required attributes | Brand, product type, category and key specifications are filled for every product |
| Identifiers | Each variant has a unique SKU, and barcodes or GTINs are present where products have them |
| Prices | Prices and compare-at prices are correct, with no zero or placeholder values |
| Stock | Inventory matches your warehouse or supplier data |
| Variants | Option names and values follow one spelling, and each variant has its own price, SKU and stock |
| Images | Every product meets your minimum image count, with consistent style and size on best sellers |
| Alt text | Product images have descriptive alt text |
| SEO fields | Products have meta titles and descriptions, or your platform’s defaults produce sensible ones |
| Organization | Every active product belongs to at least one collection or category, with consistent tags |
| Duplicates | No duplicate products, titles, handles or SKUs |
| Status | Published products are buyable, and drafts or archived products are intentional |
| Channel feeds | Feed diagnostics show no missing required attributes or price and stock mismatches |
How to Prioritize What You Find
A first audit often finds more issues than you can fix at once. Ranking them keeps the work focused on what affects sales.
Start with revenue. Problems on your best-selling products and most visited categories matter far more than the same problems on items that rarely sell, so sort each issue list by sales before deciding what to fix first.
Then weigh severity. Issues that stop a product from selling or being listed, such as missing prices, broken images or disapproved feed items, come before issues that weaken it, such as short descriptions or inconsistent tags.
Finally, sort each finding into one of three groups. Fix small, high-impact issues right away, plan larger work such as rewriting descriptions as a project, and automate fixes for problems that keep coming back, such as stock or price updates from supplier files.
How Often to Audit Your Catalog
For stores that add or change products regularly, a full audit every quarter is a practical rhythm. Smaller, stable catalogs can audit less often, while fast-moving catalogs benefit from lighter monthly checks on key fields.
Some events call for an audit whatever your schedule. Run one after a store migration, a large bulk import or a new supplier feed, and before peak seasons or major ad campaigns, when data errors cost the most.
Keep Your Catalog Clean Between Audits
Audits work best when fewer problems get in to begin with. A few habits keep product data in shape between reviews:
- Document your standards. Share required fields, naming rules and image guidelines with everyone who adds or edits products.
- Validate imports. Check supplier files and bulk imports against your standard before they reach your live store.
- Use controlled values. Pick option names, product types and tags from a fixed list rather than typing them freely.
- Automate recurring updates. Scheduled imports for prices and stock prevent the slow drift that manual updates cause.
- Watch channel diagnostics. Review feed errors in tools such as Google Merchant Center as they appear, rather than waiting for the next audit.
Conclusion
A catalog audit turns scattered product data problems into a clear, prioritized list of fixes, from missing attributes and thin descriptions to duplicates and feed errors. Running it regularly, and after big changes such as imports or migrations, keeps your product information reliable for shoppers and every channel you sell on. We hope this guide helps you plan and run your next catalog audit. If you need to export and update product data in bulk, you can explore Bulkflow.
