Review Product Audits
Use the product audit stream to understand catalog and inventory-related changes.
Product audits show catalog activity and help you understand what changed, when it changed, and who made the change when that information is available.
Use audits before changing a product that affects invoices, storefronts, checkout links, or reports.
Audits are especially useful when a customer-facing price, image, description, or active status looks different from what the team expected.
Open Audits
- Open Products > Audits.
- Review the Activity stream.
- Use the product selector to filter the stream to one product.
What Audits Show
Audit rows include the action, description, subject product, user, and date. Use this when a product price, status, description, or related inventory context needs review.
An audit row is evidence of activity, not always the full business reason. If a change affects a customer-facing price or invoice, check the related order, checkout link, or teammate notes too.
Filter by Product
Use the All products selector to focus on one product. This is the fastest way to answer questions such as who changed a product, when a status changed, or which record produced an unexpected checkout value.
Start with the product that appears wrong in the customer-facing flow, then compare the audit timeline with the invoice, order, storefront, or checkout link where the issue was noticed.
Compare Audit And Current Product
An audit entry tells you what changed, but the product page tells you what is true now. Open the product after reviewing the audit so you can compare current price, status, category, tags, images, and commerce usage before making another change.
If the product was copied into an invoice, estimate, or checkout link before the latest catalog change, the copied record may still show older details. Update the customer-facing record directly when needed.
When to Review Audits
- A checkout page shows an unexpected price.
- A product appears inactive or missing.
- A finance line item does not match the expected catalog data.
- A team member needs context before editing an item.
- You are cleaning up old products, categories, or tags.
Follow Up From An Audit
After finding the relevant audit entry, open the product and review current price, status, category, tags, description, tax behavior, and commerce usage. Then check any affected storefronts, checkout links, or invoice drafts before making another change.
Review Workflow
- Filter the audit stream to the product.
- Find the latest relevant price, status, category, tag, or description change.
- Open the product and confirm current values.
- Check live commerce and finance records that may have copied old values.
- Add a note in your internal process if a cleanup decision was made.
Use Audits Before Cleanup
Before archiving, deleting, or renaming products in bulk, review audits for recent activity. A product that looks old may still be used by a current checkout link, storefront, recurring invoice, or teammate process.
If an audit shows recent customer-facing use, archive cautiously and check the live flow before making the product inactive.
Troubleshooting
If the audit does not explain the business reason, ask the user who made the change or review related tasks, orders, or finance records.
If a public page still shows old product data, check whether the product details were copied into a storefront, checkout link, invoice, or estimate before the catalog change.