checklist
What should I check before exporting a batch of product listings?
Five checks, in order: every factual claim traces to a verified source field; every image is one you have the right to use; no copy block repeats across SKUs; no claim touches a prohibited category; and the channel’s limits were checked against their current page, not last quarter’s memory. A batch that passes all five is reviewable in minutes. SkuWeave automates the detection part — missing facts, repeated copy, and rule exceptions surface as a list — and you make the calls.
Why batches need their own checklist
Single listings get read by a person before they ship; batches get exported by momentum. The failure mode is never one bad sentence — it is one bad pattern repeated across four hundred rows: a certification nobody verified, a “best-in-class” the channel prohibits, twelve SKUs sharing an identical bullet. A checklist converts that review from vibes into a fixed sequence someone signs.
Status note first. You can open these pages and sign in to the SkuWeave workspace today. That does not mean external platform accounts are connected, and it does not mean the product has formally launched. The checks below run on the records and rules you supply.
What you need for the review
The reviewed SKU record the batch was drafted from, the channel’s current listing requirements page, and your brand rules document. If the channel rules in the workspace were last touched months ago, refresh them before trusting any automated flag.
Fifteen uninterrupted minutes per hundred SKUs. The checklist is short on purpose; rushing it in fragments is how patterns slip through.
Check 1: Facts trace to the record
Sample five to ten drafts and match every factual statement — size, material, certification — to a field in the SKU record. All product facts and image rights require verification, and the sampling is what catches a batch drafted from a stale sheet.
Check 2: Images are cleared for use
Confirm each referenced image is one your team has rights to — supplier-approved, licensed, or shot in-house. Rights questions surface at the worst possible time otherwise, which is after the listing is live.
Check 3: Nothing repeats across SKUs
Scan for identical or near-identical bullets and descriptions. SkuWeave flags repeated copy automatically; your job is deciding whether the repetition is lazy drafting or a genuine shared attribute worth one honest sentence.
Check 4: Claims respect the prohibited list
Read the flagged claims first, then sample the unflagged ones. Medical, safety, and superlative claims deserve human eyes even when the rules did not catch them — the list is a floor, not a ceiling.
Check 5: Channel limits are current
Channel limits and prohibited claims need current review. Open the channel’s requirements page, compare it against the rules in the workspace, and update before exporting. Ten minutes here beats a rejected batch and a re-draft cycle.
Verification
The review counts as done when the exception list is empty or every open item carries a written decision — verified, rewritten, or deliberately held back — and when a second person could re-run the five checks and reach the same export decision. If the checklist was “mostly done,” treat the batch as not reviewed; partial review is how one bad pattern reaches four hundred listings.
Limits worth stating plainly
All product facts and image rights require verification. Channel limits and prohibited claims need current review. SkuWeave surfaces exceptions and drafts for human sign-off; it does not verify rights, certify channel acceptance, or promise any conversion outcome.
The workspace has no live connection to channel platforms, so currency of the rules depends on the person who last updated them — which is exactly why check 5 exists.
What SkuWeave does in this workflow
SkuWeave does the detection work a human is bad at across hundreds of rows: missing source fields, repeated copy blocks, claims that touch a prohibited category, drafts that exceed channel limits. It hands you that list sorted, with the offending text next to each flag.
The calls stay yours. Every check ends in a human decision the workspace records — which is what makes the export review a review rather than a rubber stamp.
FAQ
Questions this guide is for
How often should the channel rules be refreshed?
Before every export batch, however recent they feel. Channel limits and prohibited claims need current review, and platforms change requirements without announcing it to you.
Can I export with open exceptions if the deadline is tonight?
Only with a written reason per open item and a decision about what ships anyway. An exception cleared by silence is not cleared — it is undocumented.
What if the same fact is missing across a whole group of SKUs?
It surfaces once as a repeated exception naming the field and the affected SKUs, instead of hiding inside ten separate drafts. Fix the source record once and rerun the batch — repeated copy across drafts gets flagged the same way.
Start in the workspace
Review your next batch here
Sign in or create an account and you land on the SkuWeave desk. Bring a drafted batch and its SKU record, and the workspace will surface the exceptions while you run the five checks.