App Store Approval Requirements

The Apps Marketplace team reviews all app submissions and tests apps to verify they meet Marketplace listing standards. Verify your app meets the requirements below before submitting it for approval.

General requirements

  • Make support resources available throughout the app, during onboarding, and on the app’s dashboard.
  • Follow branding guidelines when referencing BigCommerce (see our Media Kit for more information).
  • Don’t reference competitor platforms in the app’s listing information or dashboard.
  • Use the same app name in app submission and in app content such as logos and descriptions.
  • Keep app titles concise. Avoid using extra taglines or descriptors; include those in the app summary, if necessary.
  • Include the name of both your brand and any connected third-party platforms in the title (For example: “Marketplace by BigCommerce” or “Search by BigCommerce”).
  • Develop app client-side code to be compatible with all BigCommerce supported browsers.


  • Approval for the Marketplace requires all fields listed in the “Publishing Apps” section (Case Studies and Videos are optional).
  • Listings should be well worded, cleanly formatted, and follow wording and image specifications.
  • App listing name should be restricted to only branding and not include taglines.


  • Apps must work as intended and can not conflict with BigCommerce functionality.
  • Apps must use V3 endpoints in favor of V2 endpoints when feature parity exists.
  • Apps must serve all callback URLs over HTTPS.
  • Apps in the Marketplace must be multi-user enabled.
  • Apps that process transactions or handle credit card data must pass a PCI Compliance review by BigCommerce’s security team.
  • Apps that add another marketplace or sales channel to a store must make use of the Channels API and follow Channel App Requirements.


  • Apps should be single-click and use OAuth flow to authenticate1.
  • Apps must respond to install callback with styled HTML for the control panel iFrame; this content cannot be blank and must follow our user-interface constraints.
  • Apps must store user tokens against the store hash, not the user’s email address, to avoid problems with ownership changes and multiple user support.
  • Apps need to include options for new user registration as well as existing users.


  1. If your app cannot meet this requirement, email to discuss the potential for a connector app listing.

Next steps


Sample apps


Blog posts