AppExchange Listing
An AppExchange Listing is the marketplace page on the Salesforce AppExchange that represents a single managed package or solution offered by a partner.
Definition
An AppExchange Listing is the marketplace page on the Salesforce AppExchange that represents a single managed package or solution offered by a partner. The listing carries the product name, tagline, screenshots, demo video, feature highlights, customer reviews, pricing model, edition compatibility, installation instructions, support contacts, and links to documentation. Listings are how Salesforce customers discover and evaluate third-party products before installing them. Each listing maps one-to-one to a managed package (or to a multi-package solution bundled together) and lives at appexchange.salesforce.com under a permanent URL.
AppExchange listings are reviewed and approved by Salesforce before going live. Partners submit the listing through the AppExchange Publishing Console, attach the package, fill out the rich content (descriptions, screenshots, supported editions), and run the package through the Salesforce Security Review. The security review is where most listings spend their longest stretch: it can take weeks to months and requires the partner to fix any flagged issues. Once approved, the listing publishes to the marketplace and customers can install with one click. The listing then becomes the partner's marketing surface, support landing page, and review aggregator all at once.
What a listing contains and how partners maintain it
Sections of a typical listing
Every listing carries Tagline, Description, Highlights, Demo Video, Screenshots, Pricing, Supported Editions, Languages, Categories, Installation Instructions, Support Info, and Reviews. The Description is long-form prose; Highlights are short bullet-style summaries. Customers skim Highlights and screenshots first; the Description and reviews drive the actual install decision.
The Security Review
Every listing-bound package passes through Salesforce Security Review. The review covers OWASP-style web vulnerabilities, FLS and CRUD enforcement, sharing model compliance, secret handling, and a number of Salesforce-specific best practices. Partners run the Checkmarx scanner during development; the formal review uses additional tooling plus a manual review by Salesforce engineers. Failures take weeks to remediate; successful reviews unlock listing publication.
Pricing models on listings
Listings can be Free, Paid (with a billing model managed outside Salesforce), or Subscription via the Checkout flow (managed by Salesforce). Subscription pricing supports per-user and tiered models. Free listings still go through Security Review; the review fee is waived but the standards are identical.
Reviews and ratings
Each listing has a star rating computed from customer reviews. Reviews require a verified install of the package. Partners can respond to reviews; they cannot delete them. Negative reviews about resolved bugs sit on the listing forever, which is one reason partners invest heavily in support and pre-release testing.
Editions, languages, and prerequisites
Listings declare which Salesforce editions are supported (Group, Professional, Enterprise, Unlimited, Performance, Developer, Essentials, Sales Cloud, Service Cloud, etc.), which languages the UI is localised into, and which prerequisite features must be enabled in the customer org (Communities, Person Accounts, FSC, etc.). Customers with mismatched editions cannot complete the install.
The Publishing Console
Partners maintain listings through the AppExchange Publishing Console. The console is where new versions of the package get attached, where listing content gets updated, and where lead capture and trial flow are configured. Most changes (new screenshots, edits to the description) go live within a day; package-version updates require a re-review for security.
Trial Org Templates and Lead Capture
Listings can offer Try It Free flows that spin up a trial org pre-installed with the package, often based on a customer-supplied template. The trial flow captures the prospect's contact info as a Lead in the partner's Salesforce instance. Trial Org Templates are how partners give buyers hands-on time without forcing them to install into a production org.
Common listing mistakes
Three mistakes are common. The first is generic descriptions that read like brochure copy; specific outcomes and use cases convert better. The second is outdated screenshots, which signal the product is abandoned. The third is ignoring negative reviews, leaving them to define the listing in search results. Each mistake is cheap to fix but easy to overlook in the first release rush.
How to publish an AppExchange Listing
Publishing a listing is a multi-month exercise dominated by Security Review. Done well, the listing becomes the partner's most durable marketing asset.
- Become an AppExchange Partner
Register through the Salesforce Partner Community. Sign the partner agreement. Obtain a Partner Business Org plus an AppExchange Publishing Organization (APO) where the package lives.
- Build and package the solution
Develop the solution in a development org. Create a managed package, version it, and prepare it for distribution.
- Run pre-review scans
Use the Checkmarx scanner and Salesforce Code Analyzer to find security and quality issues before submission. Fix everything before paying the review fee.
- Submit for Security Review
Submit through the Partner Community. Pay the review fee. Respond to Salesforce findings within the requested SLA. Re-submit until the review passes.
- Build the listing in Publishing Console
Open AppExchange Publishing Console. Fill in tagline, description, highlights, screenshots, demo video, pricing, editions, and prerequisites. Submit the listing for publication.
The packaged solution that the listing represents.
The prose that drives discovery and conversion.
Visual content; arguably the highest-leverage section for conversion.
Which Salesforce editions can install the package.
Required before publication; takes weeks to months.
- Security Review failures require remediation and re-submission. Plan for multiple cycles; first-attempt passes are rare for complex packages.
- Outdated screenshots signal an abandoned product. Refresh visuals with every major version.
- Negative reviews about long-fixed bugs stay on the listing forever. Invest in pre-release testing to avoid creating the review in the first place.
- Edition mismatches block install. Confirm the edition matrix matches what target customers actually run.
Trust & references
Cross-checked against the following references.
- Salesforce Partner CommunitySalesforce
- AppExchangeSalesforce
Straight from the source - Salesforce's reference material on AppExchange Listing.
- Publishing to AppExchangeSalesforce Developer Docs
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does an AppExchange Listing represent?
Q2. What should you check on a listing before installing a package?
Q3. Who creates and maintains AppExchange Listings?
Discussion
Loading discussion…