360 Secure SkillHub
360 安全技能中心

AOV Uplift Simulator

基于用户提供的价格、成本、利润与转化假设,模拟捆绑、追加销售与购物车策略对平均订单金额的影响,输出基线视图、场景结果、利润与盈亏平衡含义、主要风险点及是否测试的建议。该 Skill 仅提供分析框架与输出模板,不含可执行代码或数据源。

leooooooow
leooooooow
热度 80.56
最近更新 2026-05-11 17:32:53
分类:营销依赖:纯提示词应用场景:市场分析 / 报告撰写 / 财务 / 推荐

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add aov-uplift-simulator
Metadata
name
aov-uplift-simulator
description
Estimate how changes in bundle uptake, upsell acceptance, or cart-building tactics could increase average order value without hiding margin tradeoffs. Use when teams want a practical view of AOV upside before changing offers.

AOV Uplift Simulator

Model how AOV could move under different bundle, upsell, and pricing assumptions before you change the live offer.

Solves

Many ecommerce teams make pricing or offer decisions with incomplete economics:

  • they see revenue upside but not margin drag;
  • they model one variable but ignore knock-on effects;
  • they test offers without clear guardrails;
  • they scale offers before checking break-even logic.

Goal: Turn offer assumptions into a clearer economic view that is easier to evaluate and act on.

Use when

  • You want to compare offer scenarios before launching
  • A discount, bundle, or upsell idea sounds good but needs economic validation
  • Growth teams need a faster way to pressure-test merchandising decisions
  • Teams want clearer go / watch / no-go logic before scale

Inputs

  • Core commercial assumptions relevant to the scenario
  • Price and cost structure
  • Margin or refund assumptions
  • Traffic / conversion or attach-rate assumptions
  • Constraints or guardrails

Workflow

  1. Clarify the baseline commercial setup.
  2. Model the scenario inputs that change order economics.
  3. Surface upside, downside, and sensitivity.
  4. Identify the biggest weak points or break-even pressure.
  5. Recommend whether to test, revise, or avoid the scenario.

Output

  1. Baseline view
  2. Scenario result
  3. Margin / break-even implications
  4. Key risks and weak points
  5. Recommendation

Quality bar

  • Output should be commercially interpretable, not just a raw formula dump.
  • Recommendations should stay grounded in ecommerce economics.
  • Weak points should be clearly separated from upside assumptions.
  • The result should help a team decide what to test next.

Resource

See references/output-template.md.