Uninstall the Marketplace from B2B Demo Marketplace

This document describes how to uninstall marketplace features from the B2B Demo Marketplace to transform it into a standard B2B Demo Shop.

Overview

The B2B Demo Marketplace comes with all marketplace-specific features pre-installed, including the Merchant Portal, marketplace product management, and merchant-related functionality. If you want to use the B2B Demo Marketplace as a starting point for a standard B2B project without marketplace features, you can use the provided uninstallation scripts to remove all marketplace-specific features.

The uninstallation process consists of two main scripts:

Prerequisites

Before you begin the uninstallation process, make sure you have the following:

• A latest working version of B2B Demo Marketplace installation based: on https://github.com/spryker-shop/b2b-demo-marketplace
• Docker SDK installed and configured
• Python 3 installed on your system
• Node.js and npm installed
• Sufficient disk space for rebuilding the application

Uninstall marketplace features

1. Locate the uninstallation scripts

The uninstallation scripts are included in the B2B Demo Marketplace repository. After cloning the repository, you can find them in the root directory:

• uninstall-marketplace-modules.sh - Backend uninstallation script
• uninstall-marketplace-config.json - Configuration file for the backend script
• uninstall-frontend-marketplace.sh - Frontend uninstallation script

2. Make the scripts executable

Run the following commands to make the scripts executable:

chmod +x uninstall-marketplace-modules.sh
chmod +x uninstall-frontend-marketplace.sh

3. Run the backend uninstallation script

Execute the backend uninstallation script to remove all marketplace-specific backend features:

./uninstall-marketplace-modules.sh

This script performs the following operations:

1. Removes Marketplace Features: Uninstalls all spryker-feature/marketplace-* Composer packages
2. Removes Marketplace Core Modules: Uninstalls individual spryker/* marketplace modules
3. Cleans PHP Dependency Providers: Removes marketplace-specific plugins, event subscribers, and configurations from dependency provider files
4. Updates Configuration Files: Removes marketplace-related settings from configuration files
5. Removes Marketplace Directories: Deletes marketplace-specific module directories from src/Pyz/
6. Updates Data Import Configuration: Removes marketplace data import entities from YAML import files
7. Updates Docker Configuration: Removes Merchant Portal commands from Docker installation files
8. Updates Deploy Files: Removes Merchant Portal application definitions from deploy files
9. Processes XML and Test Files: Updates OMS configurations and test files as needed

The script displays progress messages for each step. Review the output to make sure all operations complete successfully.

4. Run the frontend uninstallation script

After the backend uninstallation completes, execute the frontend uninstallation script:

./uninstall-frontend-marketplace.sh

This script performs the following operations:

1. Removes Frontend Configuration Files: Deletes tsconfig.mp.json, .stylelintrc.mp.js, and angular.json
2. Removes Frontend Directories: Deletes the frontend/merchant-portal directory
3. Cleans ESLint Configuration: Removes Merchant Portal configuration blocks from eslint.config.mjs
4. Cleans package.json: Removes mp:* scripts and Angular-related dependencies
5. Updates npm Dependencies: Runs npm install to update the dependency tree
6. Installs Required Packages: Installs @babel/core and @babel/runtime packages
7. Cleans npm Cache: Removes the node_modules/.cache directory

5. Rebuild the application

After both scripts complete, rebuild your application to apply the changes:

docker/sdk clean && docker/sdk boot deploy.dev.yml && docker/sdk up

6. Verify the uninstallation

To verify that the marketplace features have been successfully removed:

1. Check that the Merchant Portal is no longer accessible
2. Verify that marketplace-specific database tables are not being used
3. Check that no marketplace-related errors appear in the application logs
4. Test the B2B storefront functionality to ensure it works correctly

7. Remove the uninstallation scripts

After successfully uninstalling the marketplace features, remove the uninstallation scripts from your project:

rm uninstall-marketplace-modules.sh
rm uninstall-marketplace-config.json
rm uninstall-frontend-marketplace.sh

What gets removed

The uninstallation scripts remove the following features:

Troubleshooting

Script fails with “Configuration file not found” error

Make sure the uninstall-marketplace-config.json file is placed in the same directory as the uninstall-marketplace-modules.sh script.

Composer removal fails

If Composer fails to remove packages, try running the removal command manually with additional flags:

composer remove --ignore-platform-req=ext-grpc --ignore-platform-req=ext-redis PACKAGE_NAME

Application fails to build after uninstallation

1. Clear all caches:

docker/sdk cli console cache:empty-all

2. Regenerate transfer objects:

docker/sdk cli console transfer:generate

3. Run a full rebuild:

docker/sdk prune && docker/sdk boot deploy.dev.yml && docker/sdk up

Database errors after uninstallation

If you encounter database-related errors, you may need to drop and recreate your database:

docker/sdk cli console propel:install

Customizing the uninstallation

The uninstallation behavior is controlled by the uninstall-marketplace-config.json configuration file. You can modify this file to:

• Add or remove packages from the uninstallation list
• Adjust which files and directories are processed
• Customize the cleanup operations for specific files

For detailed information about the configuration file structure and available operations, see the UNINSTALL_MAINTENANCE_GUIDE.md file.