Marketplace ops
AuraScore 81/100

Multi-Tier Marketplace Seller Commission and Incentive Architecture

Design a tiered seller take-rate and fee-rebate framework to accelerate GMV growth while protecting marketplace unit economics.

Deploy this framework when restructuring platform take-rates across heterogeneous merchant tiers. It balances platform profitability with competitive merchant retention and volume incentives.

Template

Role: Principal Marketplace Strategist and Partner Operations Lead

Context

  • Marketplace Platform: {{marketplace_name}}
  • Core Seller Categories: {{seller_categories}}
  • GMV Volume Bands: {{gmv_volume_bands}}
  • Competitor Take Rates: {{competitor_take_rates}}
  • Key Operational Metrics: {{service_level_metrics}}
  • Strategic Annual Targets: {{growth_targets}}

Task

Develop a comprehensive marketplace commission structure, fee incentive matrix, and merchant governance framework that aligns {{marketplace_name}} profit margins with partner merchant retention across {{seller_categories}}.

Method

  1. Establish baseline take-rate benchmarks for each category in {{seller_categories}} against {{competitor_take_rates}} to identify margin headroom and churn vulnerabilities.
  2. Segment merchant volume thresholds across {{gmv_volume_bands}} to create clear, progressive commission discount brackets.
  3. Model variable fee rebates tied directly to fulfillment and customer experience performance across {{service_level_metrics}}.
  4. Design co-investment mechanics where seller fee discounts require matching commitments toward advertising or buyer discounting to support {{growth_targets}}.
  5. Map out category-specific margin floors and exemption criteria to prevent predatory pricing and bottom-line erosion.
  6. Formulate operational audit cadences and automated reconciliation workflows for monthly tier adjustments.
  7. Structure a migration risk framework detailing grace periods, churn prevention strategies, and targeted seller communications.

Constraints

  • Base commission calculations MUST maintain aggregate net take-rate targets without violating {{growth_targets}}.
  • Rebate qualification MUST depend strictly on verified targets within {{service_level_metrics}}.
  • MUST NOT create tier gaps that incentivize artificial order throttling near {{gmv_volume_bands}} transitions.
  • All fee schedules MUST include distinct formulas for standard listing fees, fulfillment surcharges, and category premiums.

Output format

Present the framework in four distinct sections:

  1. Commission & Take-Rate Matrix (Markdown table detailing Category, Volume Band, Base Fee, Rebate Floor, Effective Rate)
  2. Performance-Linked Incentive Mechanics (Operational criteria, SLA formulas, and clawback triggers)
  3. Margin Governance & Risk Controls (Floors, exemption rules, and automated audit rules)
  4. Merchant Migration & Rollout Timeline (Phase-by-phase operational schedule across 4 quarters)

Self-review

  • Ensure every volume band in {{gmv_volume_bands}} has a mathematically viable progression.
  • Verify all operational criteria map directly to {{service_level_metrics}}.
  • Check that margin safeguards protect net platform take-rate against aggressive seller tiering.
AuraScore breakdown
81/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 engineering12/12 · Strong

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
business-strategy-marketing-sales
marketplace
take-rate
business-strategy