Brand voice
Positioning, tone baseline, and audience
Describe who your store is, who it sells to, and how it should sound. This feeds into the prompt as the primary brand voice instruction for every generation run.
AI Prompt Layers
The baseline layer that shapes every generation run
Business Context is where you tell MerchantDrafts what your store is, who it sells to, and how it should sound. It is the dominant prompt layer — set once in Settings and applied automatically to every product, category, and manufacturer generation without any per-run configuration. Writing Pattern, Tone, and product-level context layers refine the output further, but Business Context provides the baseline that keeps copy consistent across the entire catalogue.
01
Write your Business Context
Open MerchantDrafts Settings and write a short description of your brand — what you sell, who you sell to, and what your positioning is.
02
Generation applies it automatically
Every generation run — products, categories, manufacturers — reads Business Context without requiring per-run setup. No re-entering context each time.
03
Refine other layers on top
Writing Pattern, Tone, Category Context, and Manufacturer Description add specificity. Business Context stays as the dominant baseline throughout.
On this page
What it shapes
One context entry shapes every output across the entire catalogue
Business Context is not a per-product field. You write it once in MerchantDrafts Settings and it feeds into every generation run — product copy, category descriptions, manufacturer pages, and marketing material — without any manual repetition. The other context layers (Writing Pattern, Tone, Category Context, Manufacturer Description) add specificity on top of Business Context, not instead of it.
Catalogue-wide application
Applied across products, categories, and manufacturers
Business Context is not scoped to one workspace. It applies automatically to product copy, category descriptions, manufacturer pages, and marketing material generation.
Set once
Stored in Settings, not repeated per run
Write it once in MerchantDrafts Settings and every subsequent generation run inherits it automatically. No per-product or per-batch configuration needed.
What to include
Your brand name, the store's market position, the primary customer type, and any broad tone or register instructions the model should follow by default.
Dominant layer
When Business Context and a product-level layer appear together in a prompt, Business Context acts as the wider frame. Product-level context narrows within it, not over it.
Keeps output consistent
Because every run reads the same Business Context, product copy written today sounds like product copy written next month without extra effort.
Update when the brand changes
If your positioning shifts or you launch a new line with a different audience, update Business Context in Settings and all future generation runs pick up the change.
Before
Re-explaining the brand every time
- Paste brand information into each AI prompt manually, hoping the output stays on-brand.
- Fix tone drift product by product because context is not stored and reused automatically.
- New team members and new sessions lose the accumulated context from previous runs.
- Copy from different runs sounds inconsistent because the model received different instructions each time.
After
Business Context stored in MerchantDrafts Settings
- Write Business Context once in Settings — every generation run reads it automatically with no per-run input.
- Product copy, category descriptions, and manufacturer pages all draw from the same baseline, so output stays consistent across workspaces.
- When Writing Pattern, Tone, or Category Context add specificity, they layer on top of Business Context rather than replacing it.
- Update Business Context in Settings when the brand evolves and all future runs pick up the change immediately.
Business Context is the frame. Other layers narrow within it.
Writing Pattern, Tone, Category Context, and Manufacturer Description refine output further — but Business Context sets the brand baseline that all of them operate inside.
Core benefits
One setup, consistent output across the whole catalogue
Business Context removes the manual step of re-entering brand information each time you generate. Set it once and it carries across every workspace and every run.
01
Set once, applied everywhere
Write Business Context once in Settings and every generation run across products, categories, and manufacturers inherits it automatically without any per-run input.
02
Consistent voice across the catalogue
Because every run reads the same context, copy generated today and copy generated next month use the same brand baseline — no drift, no re-alignment needed.
03
Works across every workspace
Products, Categories, Manufacturers, and Marketing Material all draw from Business Context. One update in Settings flows to all of them.
04
Dominant layer in the prompt stack
Product-level context (Category Context, Manufacturer Description, Emphasis) adds specificity within the frame Business Context sets — not instead of it.
05
No per-run brand setup
Operators do not need to re-enter positioning or audience instructions each time. Business Context is already in the prompt before generation starts.
06
Update it when the brand evolves
When positioning shifts or a new product line has a different audience, update Business Context once and all future runs pick up the change immediately.
Related workflows
Related prompt layers and generation surfaces
Business Context is the base layer. These are the surfaces that build on top of it or use it directly during generation.
Intelligence
AI Writing Patterns
Set sentence rhythm, vocabulary register, and structure rules that layer on top of Business Context to define the store writing style.
Content
Generation Controls
The left-side panel where Business Context, Writing Pattern, Tone, and product-specific layers are combined before generation runs.
Content
Content Generation
The product content workflow where Business Context is applied to generate titles, descriptions, metadata, and tags.
Operate
Products Workspace
The workspace where Business Context scales across the full catalogue in batch generation runs with review before writeback.