Retail & E-commerce

Merchandising Content Studio

Designed for Merchandiser

Give merchandisers a governed studio that drafts channel-ready product copy and campaign assets from validated attributes, brand rules, and live performance signals, with brand and legal approval before publish.

Contract RET-02 · primary aggregate ContentWorkItem · mode loading

Decision brief

Approve and schedule publish: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Brand and legal reviewer

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

Ahead of an outerwear launch a merchandiser selects 40 styles, the studio drafts marketplace and site copy from the validated PIM snapshot, flags two drafts that used an unsubstantiated waterproof claim, and legal approves the remaining 38 for a Monday publish window..

Decision to make

Give merchandisers a governed studio that drafts channel-ready product copy and campaign assets from validated attributes, brand rules, and live performance signals, with brand and legal approval before publish.

Outcome to show

Approved copy released to channel feeds gives Brand and legal reviewer the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Select style set and channel targets
  2. 2Assemble validated attributes and brand rules
  3. 3Generate channel copy variants
  4. 4Run brand, claim, and accessibility checks
  5. 5Approve and schedule publish

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Brand and legal reviewer verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ContentWorkItem evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Give merchandisers a governed studio that drafts channel-ready product copy and campaign assets from validated attributes, brand rules, and live performance signals, with brand and legal approval before publish.
Primary aggregate
ContentWorkItem
Primary container
contentWorkItems
Hierarchical key
/tenantId + /categoryId
Schema version
1

Sample scenario

Ahead of an outerwear launch a merchandiser selects 40 styles, the studio drafts marketplace and site copy from the validated PIM snapshot, flags two drafts that used an unsubstantiated waterproof claim, and legal approves the remaining 38 for a Monday publish window.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
contentWorkItems Primary /tenantId + /categoryId ContentWorkItem, ProductAttributeSet, CopyDraft, PerformanceSignal
brandGovernanceRules Reference /tenantId + /ruleDomain BrandRule

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ContentWorkItem contentWorkItems /tenantId + /categoryId workitem::{categoryId}::{styleId} None
ProductAttributeSet contentWorkItems /tenantId + /categoryId attributes::{styleId}::{pimVersion} attributeSummaryVector
BrandRule brandGovernanceRules /tenantId + /ruleDomain brandrule::{ruleDomain}::{ruleId} ruleTextVector
CopyDraft contentWorkItems /tenantId + /categoryId draft::{styleId}::{channel}::{draftVersion} copyVector
PerformanceSignal contentWorkItems /tenantId + /categoryId performance::{styleId}::{channel}::{periodStart} None

Query patterns