Use Product Feed Audit Checklist when a store decision needs a clear next step instead of a vague note.
Ecommerce template
Product Feed Audit Checklist
Audit identifiers, titles, images, price, availability, shipping, and landing-page consistency.
Quick answer
This template turns feed review into an owner-assigned checklist across identifiers, titles, images, offer data, policy details, landing pages, and review evidence.
Topic, affected product or campaign, current issue, and the decision the team needs to make
A clearer explanation, reusable decision frame, and links to related tools or templates.
Why this matters in a real store
Product Feed Audit Checklist matters because ecommerce growth work usually breaks down in the handoff between a number, a platform warning, a campaign idea, and the person who has to make the next decision. A store team may know something is wrong, but still lose time because the issue is not written in a way that connects the symptom to a next action.
Use this page as a practical translation layer. The goal is to slow down the first reaction, name the business risk, and give the team enough context to decide whether the next move is a calculation, a feed change, a campaign QA step, or a page update. The tables and checklists are there to make the work repeatable, but the judgment comes from understanding why the issue appears in the first place.
Checklist sections
- Identifiers: GTIN, brand, MPN, identifier_exists
- Titles: brand, product type, attributes, variant details
- Images: resolution, variant match, blocked URLs, overlays
- Offer data: price, sale price, availability, currency, tax
- Policies: shipping, returns, contact, checkout trust
- Landing pages: matching product data and visible purchase path
What to record
For each issue, record the SKU, field, current value, proposed value, owner, due date, and review result. A checklist without ownership becomes a reading exercise, not a fix process.
Audit scoring
| Score | Meaning | Action |
|---|---|---|
| Pass | Data is correct and consistent across feed and page. | Leave it alone and record the check date. |
| Fix soon | Data is not ideal but is not blocking revenue today. | Batch into the next feed cleanup sprint. |
| Fix now | Data can cause warnings, wasted spend, or shopper confusion. | Assign an owner and test the fix on a small sample. |
| Needs source | The team cannot verify the correct value. | Ask supplier, manufacturer, warehouse, or catalog owner before editing. |
Copyable audit rows
| SKU/group | Area | Issue | Severity | Owner | Review result |
|---|---|---|---|---|---|
| TOP-SELLERS | Price | Feed and page price differ during sale | Fix now | Paid media lead | Pending |
| BRAND-A | Identifiers | Missing GTIN for known branded items | Fix soon | Merchandising | Not started |
| BOOTS | Images | Variant image does not match color | Fix soon | Catalog manager | Sample fixed |
Methodology and limits
Copy the table into a spreadsheet or project board. Add one row per issue, not one row per vague workstream.
The template does not replace channel policy review. It organizes the store team's evidence and cleanup work.
Reusable download
Use the related CSV as a working file for the calculation, checklist, or planning step covered on this page.
Common questions
Should the checklist be SKU-level?
Use SKU-level rows for specific errors and product-family rows for rules that affect many items.
What should severity mean?
Severity should reflect revenue risk, disapproval risk, wasted spend, and shopper confusion.
When is an audit complete?
When high-risk rows have evidence, owner, fix date, and review result.