---
schema_version: "1"
id: a332d8bf098e77a77dfadedb6c2e51da39ecade3e6bdf4f986b663f2f58c7dd5
title: Reinstall Commerce Apps After Upgrading to B2C Commerce Version 26.7
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_reinstall_commerce_apps.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_reinstall_commerce_apps.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: de80b0eee597ad141a175ef19041ba8b8e099262497c2cdd929b4bb1f9127ddd
description: When you upgrade to version 26.7, Commerce apps installed on B2C Commerce version 26.6 no longer appear as installed on the Commerce Apps page in Business Manager, even if you didn’t remove them.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Reinstall Commerce Apps After Upgrading to B2C Commerce Version 26.7

When you upgrade to version 26.7, Commerce apps installed on B2C Commerce version 26.6 no longer appear as installed on the Commerce Apps page in Business Manager, even if you didn’t remove them.

B2C Commerce version 26.7 introduces a new staged table called `COMMERCEFEATURESTATE2`. However, the information in the previous table doesn't migrate to the new table, so you must reinstall and reconfigure each Commerce app that you installed before version 26.7.

After you reinstall the Commerce apps on the staging instances, first publish your changes to production using code replication. Then replicate the data using the `SITE_COMMERCE_FEATURE_STATE` replication group.

During version 26.7 rollout, your original `COMMERCEFEATURESTATE` table remains in place. The COMMERCEFEATURESTATE table will be removed in a future release. If you need historical install metadata, contact Salesforce Customer Support.

| Group | Replicates | Notes |
| --- | --- | --- |
| `SITE_COMMERCE_FEATURE_STATE` | Commerce app installation and configuration state for the site, including install status, configuration status, version, timestamps, and metadata. The replication process updates the CommerceFeatureState system object type extension on the target system. | Replicate code first so that the cartridge artifacts referenced by the Commerce app's configuration tasks exist on production before the rows arrive. |

#### See Also

- [Create a Code Replication Process in B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_create_code_replication_process.htm&release=264.0.0&type=5 "Trigger a code replication process manually, schedule it to run at a specified time, or create a job to run it.")
- [Create a Data Replication Process in B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_create_data_replication_process.htm&release=264.0.0&type=5 "Trigger a data replication process manually, schedule it to run at a specified time or recur at a specified interval, or create a job to run it.")
- [Data Replication Tasks in B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_data_replication_tasks.htm&release=264.0.0&type=5 "A data replication process includes one or more configurable tasks that handle different types of data.")