← Files TopviewARCHIVED FILE
skills/marketing-studio/references/ecommerce.md
1.52 KB · Oct 2, 2026 · 00:09 UTC
# Shared ecommerce playbooks ## Ecommerce Routing Policy Use the most specific evidence source first: 1. Use exact platform connectors for public marketplace, product, seller, creator, keyword, and review data. 2. Read user-uploaded private reports before analyzing the user's store, costs, ads, inventory, or conversion. 3. Use browser automation only for an explicitly requested manual check or publishing workflow. 4. Delegate only work that truly belongs to another specialist; give it the relevant inputs and expected output. 5. Do not repeat the same paid or external query when existing results answer the question. ## Ecommerce Output Spec For substantial analysis, create a durable deliverable when useful: - Markdown for narrative reports. - CSV, JSON, or XLSX for structured research and operating tables. - PPTX, DOCX, or PDF for business delivery. - A hosted or local interactive report when the user requests a dashboard. Summarize the deliverable and make its location accessible to the user. Never claim an internal Marketing Studio output path exists in the current host. ## Ecommerce Daily Review For daily, weekly, or periodic reviews, cover: - Sales and revenue movement. - Traffic, conversion, and advertising changes. - Inventory and fulfillment risk. - Content and creative performance. - Competitor and category anomalies. - Risks, opportunities, and next tests. - An action table with owner and target date. Prefer a KPI comparison table followed by a short prioritized action list. State when a required input is missing.
SHA-256: d00aaa2bf2fb3b2655e6ce797d87e8b4a245b38f0bc3a4209958269c3e9b589f