Shirley XueAll work
ablefyTwo-sided marketplaceShipped2023–2024

Marketplace mechanics, decided in the open

Problem
Affiliates could only join a seller's program by invitation. Sellers had no discovery channel, and thousands of registered affiliates sat idle with nothing to promote.
Solution
An open marketplace: sellers publish programs with commission terms; affiliates browse, join and promote. Tracking and attribution rules were decided explicitly, and a KPI tree was defined before launch.
Result
Both sides shipped to production, and the marketplace is still live two years later.

Role & team

Design lead for the feature, 0→1

  • Owned the design end, from the first surveys to the in-product launch system.
  • Worked with product management and engineering; ran the pre-launch usability program.

Duration & scope

Six months, discovery to production

  • Launched mid-2024.
  • Both sides: seller programs and terms, affiliate marketplace, statistics, onboarding.
  • Two in-product surveys, a five-incumbent teardown, 30 testers, ~60 unique issues.

Key metrics

Measured from launch day, in both directions

  • The KPI tree became the feature's dashboard, built before launch; 51 metrics are tracked today.
  • The guided-tour onboarding built for launch still runs.
  • It stayed a niche revenue channel, and the numbers showed that early.
Context

At ablefy, a creator-commerce platform, a seller had to know an affiliate personally to invite them into a program. It looked like a missing feature; underneath, it was a matching problem.

What made it hard:

  1. Two sides with different questions: sellers ask “who will promote my product and what will it cost me”, affiliates ask “what can I earn and can I trust this offer”.
  2. Marketplace rules are platform rules. They affect money, so every choice had to be explicit, not inherited.
  3. A two-sided product starts empty, so both sides needed onboarding. Launch was a flow, not a date.
Research

Two sides, researched separately

One in-product survey per side, because the unknowns differed. Sellers needed control: which products, what commission, who gets in. Affiliates needed discovery and proof of earnings.

Alongside the surveys: a teardown of affiliate-network incumbents, personas for both sides, and a customer journey with seller and affiliate as two actors in one funnel.

Metrics

Metrics before high-fidelity design

The northstar was revenue flowing through marketplace-created links. A KPI tree broke it down into both funnels: sellers publishing programs, and affiliates from visit to sign-in to promote to first sale.

When the marketplace later stayed a niche channel, the same instrumentation made that visible instead of arguable.

The affiliate-side statistics page — per-seller and per-product rows with clicks, views, leads, sales, conversion rate, revenue, commission and earnings-per-click columnsView full size
Affiliate-side statistics (test data) · the KPI-tree funnel as a page
Mechanics

The decisions that make a marketplace

Commission base, tracking window, attribution, and who a program actually covers: each was argued in the open, with use cases and edge cases, before anything was built.

Some decisions never became a control: a bonus on the customer's first order, to make subscription products worth promoting, and the edge cases sellers would really hit, such as the same product in two programs, or a program changing its terms after affiliates had joined.

The live program creation form — commission for all or selected products, a multilevel program toggle, commission from gross amount, cookie duration and commission percentage, plus affiliate landing pagesView full size
The shipped program creation form

Every control is a decision

Five controls, and the argument each one settles:

  1. Close-up of the checkbox labelled: affiliate commission from gross amount?

    “Affiliate commission from gross amount?”

    The commission base: gross or net. Aligned across the whole marketplace rather than left to each seller, so two offers side by side mean the same thing to the affiliate comparing them.

  2. Close-up of the commission section header with radio buttons: all products or selected products

    All products, or selected products

    Whether a program pays on the seller's whole catalog or only on the products it lists. Research found sellers who assumed the narrow reading and had no idea their entire catalog was exposed, so the mapping between program and offer was made explicit, both public and private.

  3. Close-up of the cookies expire field, set to fifteen

    Cookies expire — a number, per program

    The tracking window: how long after a click a sale still counts as the affiliate's. Set per program and written down with the attribution rule (first touch, last touch or shared), rather than inherited from whatever the tracking code happened to do.

  4. Close-up of the commission duration dropdown, set to cookie duration

    Commission duration, kept separate from the cookie

    How long an affiliate keeps earning on a customer they brought is a different question from how long the click is tracked. Once subscriptions are in the catalog, one number for both gives the wrong answer.

  5. Close-up of the multilevel program toggle, switched off

    Multilevel program — the one we left out

    Affiliates recruiting affiliates: analysed with full pros and cons, then cut from the MVP as complexity without proven demand. The toggle in this 2026 capture came later.

Close-ups from the live product (test environment)

Testing

Usability testing before launch

16 colleagues tested in the affiliate role and 14 as sellers, each in a 30-minute session with written instructions, on staging and production.

The findings split by role and set the launch plan: core concepts needed explaining (offers versus programs, estimated earnings), the statistics page confused people, moving between the account and the marketplace wasn't obvious, and existing sellers struggled to become affiliates at all. Fixes went into must-fix sprints, help texts and, for the conceptual gaps, education built into onboarding rather than more UI.

The live marketplace from the seller's side — offer cards with estimated earnings, commission, cookie duration and program size, category filters on the leftView full size
The marketplace, seller view · estimated earnings answer the testers' first question
Launch

Launch as a system

The launch was designed in the platform's in-product guidance layer, which I also ran: guided tours for both roles, onboarding flows for joining a program and creating the first link, beta-tester recruiting banners, and staged soft-launch waves before the public launch.

The marketplace shipped on time, still runs, and stayed a niche revenue channel — visible early, because the KPI tree existed before launch.

The affiliate's home dashboard in the live product — total commission, transfers, clicks, sales and leads cards, with program cards to promote belowView full size
The affiliate's home (test data) · earnings first, the overview testers asked for
The live marketplace from the affiliate's side — the same offer cards with a Promote action on eachView full size
The affiliate view of the same marketplace · one click from browsing to promoting