VTEX Sales App Extensibility is in beta, and we're working to improve it. If you have any questions, please contact our Support.

After creating extensions for your Sales App, publish them during deployment to make them publicly available.

A deployment starts when you push a commit to the configured production branch, typically main. If WebOps detects changes in the sales-app module, it automatically builds and deploys the extension to VTEX. No separate manual build step is required. In about 10 minutes, the changes are usually applied to your store.

Since sales App extensions support only production deployments, to revert a change, create a new commit that reverses the previous one, then push it to the same branch.

Make sure you have installed the FastStore WebOps. For detailed instructions, see the guide Installing WebOps for Sales App extensions.

Deploying Sales App extensions with WebOps doesn't require the discovery module. The storefront can use another technology, as long as the account is configured to use the sales-app module.

If the build fails, the issue is usually in your extension code or configuration. Common causes include type-checking errors and typos.

FastStore WebOps shows when a build fails, but Sales App build logs aren't available there. To inspect the logs, check the GitHub Checks for the failed commit:

You can also run the following command. Remember to replace {account-name} with the name of your account.

This command builds the VTEX Sales App extension for the specified account and displays any local build errors. If the command succeeds locally, check your GitHub repository for issues in the build workflow.