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.