---
title: Enable Commerce Search v3 in production
slug: commerce-composable-modules/search-v3/enable-commerce-search-v3-in-production
docTags: 
createdAt: 2026-08-05T19:35:40.106Z
---

After you successfully test the Commerce Search v3 functionality in your Optimizely Configured Commerce sandbox environment, follow these steps to upgrade production.

## Prerequisites

Follow the steps given in [Commerce Search v3 prerequisites](docId\:NBnEv0gSpVeqoJ2qQmI4z).

### Shadow mode

Optimizely recommends running Commerce Search v3 in shadow mode before you switch your storefront to it. In shadow mode, the v3 jobs run in the background while Commerce Search v2 remains the active search provider.

Set **Search Indexer Name** to Commerce Search v3 and configure the ODP user events sync job. Leave **Search Provider Name** on Commerce Search v2. Indexing and event sync then run without affecting the live search experience for your shoppers.

Shadow mode lets user event data accumulate before you switch providers, giving the Vertex AI model a head start. Behavior-based relevance improvements, dynamic facets, and autocomplete suggestions depend on sufficient event data and model processing. Validate these features before you switch providers rather than assuming they are ready.

After enough user event data accumulates, follow [Production steps](docId\:DS5VzU1Fd9TiG8TLG0SGU). Keep **Search Provider Name** on Commerce Search v2 until you complete the index rebuilds, validation, and waiting period in step four.

## Production steps

Perform the following steps in production:

1. [Review custom extensions.](docId\:hsPpUqQYUDL3v-lcq_eOS)
2. [Integrate with Optimizely Data Platform (ODP).](docId:6yYvpN2alK2UU7P4uwlVI)
3. [Create integration jobs to sync user events and historical orders.](docId:0xyBsenmyBbSBRcwldDhz)
4. Update the search configuration:
   1. Set the **Search Indexer Name** to **Commerce Search v3**. Do not yet update the **Search Provider Name** to Commerce Search v3; use the current Search Provider.

      ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/O7VgyOUlZP2g8huHQgJwp-20260720-144512.png)
   2. Perform a full index rebuild and confirm it completes successfully.
      - If the rebuild fails or logs show errors or warnings, troubleshoot the issues or contact Optimizely Commerce Support.
      - If unresolved, revert the Search Indexer to the previously used version (v1 or v2) and do not proceed to the next step until the issues are resolved.
      - If the rebuild is successful, run a few additional rebuilds to ensure stability, and wait at least 12 hours before proceeding to the next step.
   3. Ensure the Search Provider Name is correctly set to Commerce Search v3.

      ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/WYTNgUq4_atqPF46Dccnh-20260720-144511.png)
   4. Verify that the **Autocomplete** setting is enabled in the updated Search Provider configuration.
   5. Replicate any other settings and search parameters that were validated in Sandbox and are required in the Production environment.
5. If you encounter issues in production, set **Search Provider Name** and **Search Indexer Name** back to the previous version.
6. Investigate and resolve the problems, or contact [Optimizely Support](mailto\:support@optimizely.com).
7. After you resolve the issue, set both settings back to Commerce Search v3.

### Monitor search after you go live

Check your search-related logs regularly after you switch to Commerce Search v3. If you see errors or unexpected behavior, correct the issue or contact [Optimizely Support](mailto\:support@optimizely.com).

If a critical search issue occurs, roll back to Commerce Search v2 while Optimizely reviews the issue. Your site continues to function normally while you investigate.

## Known issues

:::ExpandableHeading
### Catalog branch switching and search errors

Optimizely has identified a known issue with catalog branch switching when you index products to a new branch. Shortly after a full index rebuild, searches on the newly indexed catalog branch may temporarily fail due to unsynchronized attributes. This results in temporary downtime for storefront product searches and browsing, which can impact the storefront searches.

You should take the following actions to mitigate this issue:

1. Disable the **Catalog Branch Switching** setting until the issue is resolved. This is currently under investigation with Google.
   While disabled, products are indexed and served from the same default branch, ensuring consistent search behavior.
2. Archive or deactivate products rather than delete them. Permanently deleted products that were previously indexed remain as stale entries on the default branch and may still display in search results. If products are sourced from an ERP system, you may need to update the refresh jobs to deactivate products that have been deleted in the ERP.
3. Avoid changing product types (such as from **Primary** to **Variant**), as these changes prevent products from being indexed correctly.
4. Work with [Optimizely Support](https://support.optimizely.com/hc/en-us) to eliminate stale products with a branch switch and catalog reingestion. This involves a few manual steps to ensure a smooth transition without production downtime.
:::