Category scope
Category positioning and audience notes
Describe what the WooCommerce category covers, who typically buys from it, and any relevant market or product-range notes that should shape generation for products in that section.
AI Prompt Layers
Give the AI context about the category a product belongs to
Category Context is a per-category prompt layer that tells MerchantDrafts what a WooCommerce category covers — its positioning, typical buyer, and any relevant category-level notes. When a product in that category is generated, this context is included in the prompt so the output reflects the category's scope rather than producing generic copy that could belong to any section of the catalogue. It sits above product-level context and below Business Context in the prompt stack.
01
Write context for each category
In MerchantDrafts Settings, add a short description for each WooCommerce category — what it covers, who it's for, and any relevant positioning notes.
02
Generation reads it per product
When generating a product, MerchantDrafts looks up that product's category and includes the matching Category Context in the prompt automatically.
03
Output reflects the category
Copy for a product in a specialised category sounds like it belongs there — not like a generic product description that could have been written for anything in the catalogue.
On this page
What it shapes
Category-aware output without per-product configuration
Category Context is set once per WooCommerce category in Settings. When a product in that category is generated, MerchantDrafts resolves the category and includes the matching context in the prompt automatically — so operators do not need to explain what the category is about for every individual product run.
Automatic resolution
Resolved per product at generation time
MerchantDrafts looks up the product's WooCommerce category and includes the matching Category Context in the prompt without any per-product manual setup from the operator.
Prompt layer position
Between Business Context and product-level context
Category Context adds specificity between the store-wide baseline (Business Context) and the product-specific layer (Emphasis, Manufacturer Description), keeping output appropriately scoped to its section of the catalogue.
What to include
A brief description of the category's product range, the type of customer it serves, and any relevant market position or price-range notes that should inform copy for products in that section.
Set per WooCommerce category
Each WooCommerce category in your store can have its own Context entry in MerchantDrafts Settings. Categories with no entry fall back to Business Context alone.
Works in batch runs too
When running bulk generation in Products Workspace, Category Context is resolved for each product individually — so a mixed-category batch still gets the right context per item.
Also used in Categories Workspace
When generating category description pages directly in Categories Workspace, the same Category Context entry feeds into that generation as well.
Before
Category context added manually or skipped
- Re-explain what a category is about inside each individual AI prompt, or skip it and accept generic output.
- Products from specialist categories get the same generic language as products from general ones.
- Category notes are inconsistently applied because they depend on the operator remembering to include them per run.
- Batch generation across multiple categories produces uniform-sounding copy that ignores category distinctions.
After
Category Context stored in MerchantDrafts Settings
- Write Category Context once per WooCommerce category in Settings — it is included in every product generation for that category automatically.
- Products in specialist categories get copy shaped by that category's context without any per-product instructions from the operator.
- Mixed-category batch runs in Products Workspace resolve the correct Category Context per product individually.
- The same Category Context entry also feeds into Categories Workspace when generating the category description page itself.
Category Context is optional per category — categories without it fall back to Business Context.
You do not need to fill in Category Context for every category before generating. Any category without an entry uses Business Context and Writing Pattern as the baseline.
Core benefits
Category-level specificity without per-product configuration
Category Context gives every product in a specialist category a contextual edge in generation without requiring operators to explain the category for each individual run.
01
Set once per category
Write Category Context once in Settings per WooCommerce category. Every product generation in that category includes it automatically — no per-run input needed.
02
Copy that reflects the category
Products in specialist categories get output shaped by that category's context rather than generic copy that could belong to any section of the store.
03
Works in mixed-category batch runs
When running bulk generation across a filtered product list, each product resolves its own Category Context individually — so output stays category-appropriate across the whole batch.
04
Also used in Categories Workspace
The same Category Context entry feeds directly into Categories Workspace when generating the WooCommerce category description page itself — one setup, used in both places.
05
Optional per category
Categories without a Context entry fall back to Business Context as the baseline. You can fill in Category Context progressively — starting with the sections of the catalogue where the distinction matters most.
06
Review remains separate from generation
Category Context improves the quality of the generated draft — but it does not change the review-before-writeback model. Operators still approve output before anything touches live WooCommerce content.
Related workflows
Explore the rest of the product content workflow stack
Content Generation is one part of the MerchantDrafts workflow. These adjacent surfaces cover the jobs operators usually handle next, from promotional content and image workflows to the controls that shape output before generation.
Content
Marketing Material
Generate platform-ready promotional copy from product context instead of rewriting the same offer for each channel.
Content
Lifestyle Images
Add scene generation and product-visual workflows to the same operator process instead of handling image direction elsewhere.
Content
Generation Controls
Use What to Emphasize, Tone, Description Length, Business Context, Category Context, Manufacturer Description, and Writing Pattern to shape output before you generate.
Intelligence
Brand and prompt controls
See how Business Context, Writing Pattern, and related control layers shape output across the site.