BOTSOURCE | PRODUCT CATALOG QA TEMPLATE

Use the same source and category rules with an employee, a BPO or an AI bot.
Worked example: https://www.botsource.ai/resources/product-catalog-qa
No signup. This is a blank template, not a supplier or live product record.

CATEGORY AND SOURCE RULES

Category / schema version: [Name / version]
Required attributes: [Field, unit and allowed values]
Optional attributes: [Fields that can be omitted]
SKU and parent source: [Approved master / exact matching rule]
Specification source: [Approved model-specific document / revision]
Variant naming rules: [Source values and approved store mappings]
Authorized image source: [Manifest / SKU match]
Price source and authority: [Separate authorized workflow]
Inventory source and authority: [Separate authorized workflow]
Description rules: [Approved facts and brand style]
Conflict rule: [When precedence resolves a field; when to hold]
Publication permissions: [Routine actions and exception owner]
Recovery method: [Prior version and restore process]

PRODUCT AND VARIANT QA RECORD

Batch / record / schema version: [Identifiers]
Parent / variant SKU: [Exact identifiers]
Source pack: [Document or URL, revision and checked date]

Repeat the following for each changed attribute:
  Field: [Attribute]
  Source value: [Original value]
  Evidence location: [Source ID, row/page/section]
  Normalized value: [Proposed store value]
  Rule applied: [Formatting, mapping or approved factual update]
  Result: [Pass, missing or conflict]

Required-field result: [Complete or exact missing fields]
Variant and image result: [Match, mismatch or unresolved]
Conflict: [Competing exact values and sources]
Decision owner: [Who can resolve this specific exception]
Question: [Precise missing information or conflict to resolve]
Release condition: [Evidence or correction needed]
Staging validation: [Import mapping and variant behavior results]
Publication result: [Ready, held, or published with exact receipt]
Change and recovery record: [Previous version, changes and restore method]

READY / HOLD HANDOFF

Ready under agreed authority: [Exact SKUs and checks passed]
Held: [Exact SKUs or fields and reasons]
Sibling variant behavior: [Selector remains valid; shared claims checked]
Other work can continue: [Unaffected products or fields]
Publication receipt: [Destination, version, time, confirmed result; only after write]

Never infer a missing fact from a sibling variant. Price changes, purchases,
payments and money movement need their separate authorized workflows.

QUALITY REVIEW

Sample and date: [Representative products reviewed]
Factual accuracy: [Method and results]
Variant/image matches: [Correct and incorrect counts]
Required-field completeness: [Counts and missing source facts]
Corrections per reviewed batch: [Count and reasons]
Exception resolution time: [Observed time and method]

https://www.botsource.ai/roles/product-catalog-specialist