Marketplace Listing

Origin & evolution

The enterprise app marketplace begins with the Salesforce AppExchange, launched at Dreamforce in 2005, two to three years before Apple's consumer App Store. Marc Benioff reportedly took the ecosystem idea from advice by Steve Jobs🔨JobUserJob To Be Done: what the user is trying to accomplishView reference →, and later gifted the "App Store" trademark to Apple. AppExchange created something new: a place to distribute software built on someone else's platform, letting small ISVs reach enterprise buyers without an enterprise salesforce. By December 2025 it carried over 6,000 apps from roughly 3,600 developers.

The consumer and SMB web followed. Shopify opened its App Store in June 2009, inviting developers to build for its merchants. The platform cut became the defining variable. Shopify dropped its commission to 0% on a developer's first $1M in revenue in 2021, down from 20%, charging 15% only above that line, then later narrowed the exemption to lifetime rather than annual revenue. Those numbers move real businesses, which is why the platform tax sits at the centre of every listing decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference →.

How it works in practice

A two-person team builds an inventory sync app and lists it on the Shopify App Store. The listing page carries screenshots, a pricing plan, and the review score that decides install rate. In month one, 80% of installs come through Shopify search, traffic the team never paid for. Under the first-$1M exemption, Shopify takes nothing yet; once the app crosses that threshold, 15% of marginal revenue goes to the platform. The team weighs that tax against the alternative of standing up its own billing, acquisition, and trust signals from scratch, and the listing wins on reach despite the cut.

Marketplace listing vs. its neighbours

• API ecosystem🕸️API EcosystemPartners & EcosystemAn API ecosystemView reference → is the platform's whole programme of third-party extensibility; the listing is one entry within the catalogue it publishes, related by api_ecosystem_lists_marketplace_listingAPI EcosystemlistsMarketplace Listinghierarchy.
• Integration partner🗿Integration PartnerPartners & EcosystemAn integration partnerView reference → is the company behind the listing. The partner is the legal and commercial entity; the listing is its storefront tile, the install surface customers see.
• Feature⭐FeatureProduct SpecificationA product capability or featureView reference → is the capability💪CapabilityStrategyAn ability that enables value deliveryView reference → the listing delivers to the host product. A listing exists to extend the platform, captured by marketplace_listing_extends_featureMarketplace ListingextendsFeaturecross-domain, so the line runs from storefront to the function it adds.

In the graph

In the Unified Product Graph, a marketplace listing sits in the ecosystem region, enumerated by the platform through api_ecosystem_lists_marketplace_listingAPI EcosystemlistsMarketplace Listinghierarchy. Two edges give it meaning: marketplace_listing_extends_featureMarketplace ListingextendsFeaturecross-domain records what the listing adds to the host product, and marketplace_listing_references_help_videoMarketplace ListingreferencesHelp Videocross-domain links the support content that drives successful installs. Modelling the listing as distinct from the partner behind it lets the graph track a distribution channel on its own terms, its review score, its platform cut, its reach, separate from the company that ships it.