Which step is NOT typically involved in integrating third-party services in SFCC?

Integrating third-party services in Salesforce Commerce Cloud (SFCC) generally involves specific technical and configuration steps to ensure successful communication and data exchange between the SFCC platform and external systems. Among these steps, redesigning the entire storefront is not commonly required.

Creating a custom cartridge is essential because it allows developers to write specific code that interacts with the third-party service, encapsulating functionality in a reusable manner. This custom cartridge can handle the nuances of the integration, such as adapting data formats and managing requests and responses.

Setting up API keys is another critical step to ensure secure communication with third-party services. API keys authenticate the requests and allow SFCC to interact with external APIs safely.

Using HTTP client libraries for communication is also a necessary part of the process. These libraries facilitate the sending and receiving of HTTP requests to and from the third-party service, enabling SFCC to make API calls effectively.

In contrast, redesigning the entire storefront is not typical for third-party integrations. Most integrations focus on specific functionalities, such as payment processing, shipping, or inventory management, without requiring a complete overhaul of the existing storefront. This approach allows developers to add or modify specific components while keeping the overall design and user experience intact.