Open a Go-Live ticket to ensure your B2C Commerce realm is appropriately configured for live traffic.
After your first site has gone live as outlined below, you only need to confirm that a certificate is installed on the new site because the Go-Live process detailed below is not required for subsequent sites. Therefore, please ensure that an SSL certificate is installed per Install a SSL Certificate on B2C Commerce and optionally, the custom maintenance pages are configured. When prompted for a Support case number after following the steps in Mark a Site as Live in B2C Commerce, you can use the case number from your original go-live case or any case number you have.
A Go-Live case must be opened with Support at least 5 business days prior to launch.
The Go-Live checklist is a comprehensive checklist of readiness items that need to be completed before you launch on the B2C Commerce platform. It is intended only for each realm's first site launch. This document should be reviewed by both you and Commerce Cloud Support prior to launch and all items need to be tracked in the project plan to ensure they are completed.
Please contact Commerce Cloud Support if you have questions or comments about this checklist.
Once the checklist is completed and you are ready to launch a site on Production for the first time, you must open a Support case with Commerce Cloud B2C Support, who are then responsible for changing the site's status from Preview to Online (Protected). Commerce Cloud B2C Support does this only for the first site launched on Production. For subsequent sites, you can change the site's status yourself. Once the status has been updated to Online (Protected), you can then change the status to Live when you are ready.
Note:
000391578

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.