Marketplace ops
AuraScore 79/100

Brand Catalog Compliance Onboarding Feedback

Produce a catalog onboarding rejection and remediation email for brand partners.

Use this template when a retail brand partner submits product feeds with invalid taxonomy, missing attributes, or image errors. It provides precise technical guidance on how to fix and resubmit the listing catalog.

Template

Role: Principal Marketplace Catalog Operations Lead specializing in retail product taxonomy and multi-attribute data compliance.

Context

  • Brand Partner: {{brand_partner}}
  • Catalog Batch ID: {{catalog_batch_id}}
  • Blocked SKU Count: {{failed_sku_count}}
  • Primary Data Error: {{primary_error_category}}
  • Target Category Taxonomy: {{taxonomy_node}}
  • Resubmission Cutoff: {{resubmission_cutoff}}

Task

Write a structured technical onboarding audit email to a brand's e-commerce operations team, detailing data ingestion errors across their catalog batch and providing explicit steps to reformat attributes for listing activation.

Method

  1. Review the catalog ingestion log for batch {{catalog_batch_id}} submitted by {{brand_partner}}.
  2. Isolate the {{failed_sku_count}} suppressed items and classify them within the {{taxonomy_node}} hierarchy.
  3. Draft a precise subject line including the batch identifier, brand name, and catalog status.
  4. Summarize total ingested items versus rejected listings to highlight overall batch pass rate.
  5. Break down the specific root causes of {{primary_error_category}} (e.g., invalid GTINs, missing mandatory facets, unapproved image ratios).
  6. Provide concrete attribute correction examples showing invalid values alongside approved data schema requirements.
  7. Detail the required upload protocol, file template version, and feed ingestion path.
  8. Establish {{resubmission_cutoff}} as the hard operational cutoff for inclusion in the upcoming catalog publishing cycle.

Constraints

  • MUST cite the exact batch ID {{catalog_batch_id}} and blocked SKU count {{failed_sku_count}}.
  • MUST NOT grant provisional listing activation before data feed validation passes.
  • MUST provide clear schema examples (e.g., Incorrect Input vs. Required Format).
  • Limit email length to 350 words to maintain high operational utility.

Output format

  • Subject: [Catalog Ingestion Feedback] Batch {{catalog_batch_id}} - {{brand_partner}}
  • Ingestion Audit Summary (processed count, blocked count, pass percentage)
  • Technical Defect Analysis (taxonomy, missing mandatory fields, formatting errors)
  • Corrective Action Instructions (3-step remediation guide with syntax examples)
  • Resubmission Timeline & Operational Support Link

Self-review

  1. Did I provide clear, reproducible schema examples rather than vague data guidance?
  2. Are the batch ID and failed item counts consistent throughout the memo?
  3. Is the cutoff deadline clearly highlighted so the partner understands the launch impact?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ecommerce-retail
ecom-operations
retail-consumer-goods
marketplace ops
catalog ingestion
product data