Begin with the source package
A listing review should start before anyone opens the storefront editor. Gather the approved product record, image folder, variant map, channel template, and the name of the person who can resolve conflicts. Mark the version or effective date. A neat page built from an old spreadsheet is still wrong.
Treat missing information as a visible queue. If dimensions, materials, compatibility, warnings, or usage rights are absent, do not fill the gap from a similar item. Record the missing field, source checked, and owner needed. This keeps preparation separate from product and compliance judgment.
Check identity before copy
Confirm the SKU, parent-child relationship, option values, and channel identifier before polishing titles or descriptions. Variant errors often look small in a content review but can connect a customer to the wrong item, image, or warehouse record.
Use exact matches for durable identifiers and a documented normalization rule for display names. If a retired alias still appears in open orders or returns, preserve that relationship until the catalog owner approves the merge or retirement.
Review claims and customer-facing detail
Compare every factual statement with an approved source. Product benefits, safety language, environmental claims, warranties, certifications, and comparative statements need substantiation owned by the business. A support role can place approved language but should not create evidence by rewriting it.
Read the page as a customer would. Confirm that the title, key attributes, variant label, image sequence, delivery context, and return-related details describe the same product. Flag ambiguity instead of smoothing it over.
Make visual and accessibility checks specific
Verify that images belong to the selected variant, follow the approved order, and do not contain obsolete overlays or cropped instructions. Alternative text should identify useful product information without repeating nearby copy or stuffing keywords.
Test the listing at mobile and desktop widths. Look for clipped option labels, controls that cannot be reached by keyboard, weak focus indicators, and information that appears only on hover. Record the page and viewport with each issue.
Close with a change record
A completed QA record should show the item reviewed, source version, fields changed, unresolved exceptions, reviewer, and publication state. For bulk work, retain a sample that includes new items, changed variants, and known difficult categories.
After publication, reopen the customer-facing page and compare it with the approved record. Imports and channel transformations can introduce defects after the draft looked correct. The final check should verify what customers can actually see.
Common questions
Can an assistant approve product claims?
No. The assistant can verify placement against approved source material; substantiation and approval stay with the accountable business owner.
Should every listing receive the same review?
Use a common baseline, then add controls for categories with safety, regulatory, compatibility, or high-return risks.
What is the smallest useful record?
SKU, source version, fields checked, exceptions, reviewer, and publication status.
Source note
This guide uses public guidance as a boundary and review reference; it does not report a proprietary performance study or replace professional advice.