Catalog Health

Help / Documentation

Using Catalog Health

Catalog Health scores your BigCommerce catalog and lists what to fix. The Catalog Health app only opens inside BigCommerce after you install it. For email support, see Support.

Getting started

  1. In BigCommerce, open Apps and install Bez Leda Catalog Health.
  2. Approve the requested access so Catalog Health can read your catalog and write the fixes you confirm.
  3. BigCommerce opens the app in this window. The first catalog sync and scan start automatically.
  4. When the scan finishes, Overview shows a 0–100 score and the open issues.

Other store users can be given the app from BigCommerce. Free is included with install. You do not need a paid plan to scan a small catalog.

Overview

Overview is the home screen. It shows:

Use Scan catalog to run a full scan now. Free stores scan only when you ask. Paid stores also scan on a schedule. If the catalog is over the plan product cap, Overview says so; extra rows are kept, not deleted.

Health Score

The store score is a 0–100 number from the same rules every time. It is not an AI opinion and not a legal, SEO, or accessibility certificate.

Open a product from Catalog to see that product’s issues and whether they are open, ignored, or resolved.

Issues

Issues is the working list. Filter by severity, category, status, brand, or search. Open an issue to see why it fired and what to change.

Ignored issues do not count as open work and are not deleted. Filter the list to Ignored and use Restore to put one back. You can ignore or restore several at once. A later scan will not reopen an ignored item until you restore it.

Some fields can be changed in Bulk Fix. Others stay in the BigCommerce editor; Catalog Health links there instead of replacing your catalog screens.

Catalog

Catalog is a read-through of the products Catalog Health has synced from BigCommerce.

Catalog Health scores products with store rules. It does not invent a separate health score for each variant.

Catalog Standards

Catalog Standards sets store-wide expectations such as required fields, text length, and image counts. Paid plans include this. Free sees an upgrade prompt.

Rules can turn individual checks off for the store. Disabled checks stop creating new issues on the next scan. You can restore the default set of checks at any time.

Scan History

Scan History lists recent runs:

Each run shows open issues at that time, new issues first found on that scan, and issues resolved on that scan. If a scan fails, Overview shows the error so you can try again.

Alerts

Alerts (paid plans) emails the address you set when:

If email delivery is not ready, Catalog Health saves the alert and sends it when delivery is available. Catalog Health does not send Slack or chat messages.

Paid stores also stay current when products or categories change in BigCommerce. Diagnostics shows whether that monitoring is healthy. Close and reopen the app from BigCommerce Apps if it needs attention.

Exports

Exports (paid plans) queues a CSV of issues. You can also export the current selection from the Issues list. When the file is ready, download it from Exports.

This is an issue list for this store, not a full personal-data export and not a BigCommerce catalog backup. Files are removed when the store is later purged after uninstall.

Bulk Fix

Bulk Fix (paid plans) can write a small, explicit set of catalog fields back to BigCommerce: brand, add a category, SKU, page title, and meta description.

The flow is always preview, then confirm. Nothing is written until you confirm. Images, HTML descriptions, prices, inventory, variant options, and custom URLs stay in the BigCommerce editor. If a write fails, the preview result says so.

AI Suggestions

Paid plans include AI Suggestions . AI Suggestions uses your own AI provider account. Your provider bills you directly. Catalog Health does not include AI credits.

  1. Open AI in Settings.
  2. Paste your OpenAI API key and save. After save you only see a masked last-four.
  3. Use Test to confirm the key works. Remove deletes it from Catalog Health.
  4. Generate title, description, or meta copy for a product. Review, approve or discard, then Apply if you want it written to BigCommerce.

Catalog Health never publishes generated content until you review and apply it. You are responsible for what you apply. Do not email us the key. If it leaked, rotate it at OpenAI and save the new one here.

Store Connection

Store shows the BigCommerce store Catalog Health is linked to: name, domain, timezone, currency, installed date, and last successful sync. Those values come from BigCommerce.

The store hash and other technical details stay on Diagnostics for Support.

Subscription

Subscription shows this store’s plan (Free, Pro, Growth, Business, or complimentary access from Bez Leda Studios).

Paid plans are billed through BigCommerce. We never collect a card number. There is no self-serve free trial. Complimentary Pro, Growth, or Business is access Bez Leda Studios can grant; it does not apply a subscription charge. Your AI provider bills you directly.

Change or cancel in Subscription. Cancel is end-of-period: paid features continue until BigCommerce reports the period ended. Uninstalling the app does not cancel a paid BigCommerce subscription. After you uninstall, still cancel in BigCommerce if you want charges to stop.

If checkout is unavailable, Subscription will say so. That is on us, not your store.

Diagnostics

Diagnostics is a health check of this store’s Catalog Health connections:

Each row is Healthy, Attention, or Not configured. Last API sync, last scan, and last webhook use readable times. Email delivery ready means Catalog Health can send mail; it does not mean a token is exposed.

Open Advanced technical details if Support asks for the store hash, app version, or webhook topics. Use Copy next to the store hash. Do not copy tokens or API keys.

If monitoring needs attention, close and reopen the app from BigCommerce Apps. Start another check with Scan catalog.

Uninstall

Uninstall from BigCommerce Apps. When that happens we:

  1. Mark the store uninstalled and stop scans for it.
  2. Clear the BigCommerce access token and any stored OpenAI key immediately.
  3. Remove the catalog-update connections we created. BigCommerce also removes app connections on uninstall.
  4. Keep catalog copies, issues, scores, users, and billing copies for 30 days so a reinstall of the same store can continue instead of starting empty.
  5. After that window, the store, related records, and export files are deleted. A user account is removed only if it is not linked to another store.

We do not wipe every copy at the moment you click uninstall. Nightly backups can keep a snapshot for up to 3 days. Email cataloghealth@bezledastudios.com after uninstall if you want the remaining live copy purged sooner. Details: Privacy Policy.

Cancel paid billing separately in Subscription or on the BigCommerce invoice if you still have an active subscription.