what_you_need
Prepare the inputs before opening the apps
- A clean CSV with one row per product
- Verified product facts and differentiators
- A description structure and tone
- Forbidden claims and marketplace constraints
step_by_step
The working process
-
1
Treat the CSV as the factual source
Create stable columns for product name, material, dimensions, intended use, included items, differentiators, and any mandatory wording. Leave unknown facts blank instead of asking the model to guess.
-
2
Define one reusable output structure
Set the required title, short description, benefits, specifications, care notes, or other fields in Batch Generate Text with any AI. Match the structure to where the copy will actually be used.
-
3
Set voice and claim boundaries
Use a persona or writing sample for tone, then explicitly prohibit invented certifications, guarantees, comparisons, sustainability claims, and unsupported performance statements.
-
4
Preview varied product rows
Test a simple product, a complex product, and one with sparse data. Correct the CSV or template when the sample reveals missing facts or repetitive phrasing.
-
5
Generate the complete batch
Run the approved topic list with the chosen provider and model. Save each draft locally using filenames that map back to a stable product identifier.
-
6
Verify before publishing
Compare every factual claim with the source data. Remove generic filler, check marketplace rules, and edit descriptions that sound interchangeable across products.
human_checkpoint
Review before you call it finished
- Can every factual statement be traced to the CSV or another approved source?
- Are prohibited claims absent?
- Does each file map to the correct product?
- Were generic and repetitive drafts rewritten or rejected?
honest_boundaries
Limits and privacy
Practical limitation
The model does not know whether catalogue facts are true and can invent persuasive-sounding details. This workflow creates drafts; it does not verify or publish listings.
Privacy boundary
CSV row content and prompts are sent to the AI provider you choose. Provider keys are encrypted locally and finished Markdown or text files are saved to your PC.
faq
Questions worth answering
Does the app upload descriptions to a marketplace?
No. It creates local text or Markdown drafts for review; publication remains a separate deliberate step.
Is AI usage included in the app price?
No. You bring your own compatible provider key, choose the model, and pay that provider directly.