Launch your new storefront and make it accessible from its official, public web address.
Before running the commands, replace any placeholders with actual values.
To perform administrative tasks, you must have one of these roles and permissions:
To make requests to the Managed Runtime API, you must include an API key in the HTTP request Authorization header with the value, Bearer $API_KEY. For all the sample requests provided, replace $API_KEY with your actual API key. To find your API key, log in to Runtime Admin and go to the Account Settings page.
Treat your API key like a password because it allows scripts to complete operations on your behalf.
Important
Alternatively, use the B2C CLI to make Managed Runtime API calls without handling the API key directly.
Have access to your DNS provider to create and update CNAME records, and access to your third-party CDN provider (as applicable). If you’re using a vanity domain, see Storefront Zone Creation for how to add an SSL certificate to your zone and configure the CNAME mapping, or eCDN Automatic Certificates to have eCDN manage the certificate for you.
To make requests to the SCAPI CDN Zones API, you must have an API client with the sfcc.cdn-zones and sfcc.cdn-zones.rw OAuth scopes. See Authorization for SCAPI Admin APIs for steps on creating an API client and assigning scopes. Alternatively, use the B2C CLI to make eCDN API calls without constructing requests yourself.
The launch process is the same for staging and production. The only difference is the domain name and Managed Runtime environment.
We strongly recommend going through the launch process on a staging environment before running it on production. Complete these steps as soon as you start a Storefront Next project and at least two weeks before your launch date.
Warning
Before you can launch the storefront in another instance, export it from the sandbox or development instance, and then import it to the staging or production instance. The storefront import creates an initial environment that you can deploy a bundle to from the sandbox or development instance.
The storefront itself must always be imported. No replication path exists for storefronts. How you move the storefront’s associated data, such as sites, catalogs, and price books, depends on the target instance:
You can only export, and therefore import, one storefront at a time. Repeat these steps for each storefront, if necessary.
Note
sfcc-post-import-setup-storefront job starts. For this instance, the job sets up an Account Manager API client, a SLAS client, a default environment, and an eCDN default domain. These configurations and environment are separate from the sandbox or development instance that the storefront was exported from. Next, the job deploys an initial bundle to the default environment, which sets up the environment and its environment variables. If an error occurs during the job execution, check the job logs in Administration > Operations > Jobs. See Managing Jobs in Salesforce Help.If you’re using a vanity domain, add that domain to the redirectUri array of the SLAS client used by the storefront. Otherwise, shopper login requests that redirect back to your vanity hostname are rejected. See the redirectUri array description in Authorization for Shopper APIs, and update the client using the SLAS Admin API or SLAS Admin UI.
To move your storefront to staging or production, configure eCDN routing only for vanity domains or for new zones.
Default domains and default zones don’t require eCDN configuration. Environments created in Storefront Next are preconfigured with eCDN and a default domain, which is routed to the Managed Runtime domain.
If you’re using a vanity domain or a new zone:
To add a new access control header value for your vanity domain, use Advanced Environment Settings in Runtime Admin or the projects_target_access_control_header_create API, and use that value in the upsert API call in the next section.
Storefront Next environments support up to 4 access control headers, and the header that Salesforce configures for your default domain can’t be deleted. Add a separate header value for each vanity domain instead of reusing or replacing the default one. See Access Control Headers.
Note
Use the upsertOriginHeaderModification API in B2C Commerce API (SCAPI) to set the headerValue. This example shows how to call this SCAPI endpoint to set an access control header with the header value 25pn5dec7f1c:
1curl "https://$CODE.api.commercecloud.salesforce.com/cdn/zones/v1/organizations/$ORG/zones/$ZONE/origin-header-modification/mrt" \
2 --method 'PUT' \
3 --header "Authorization: Bearer $TOKEN" \
4 --header 'Content-Type: application/json' \
5 --data '{ "headerValue" : "25pn5dec7f1c" }'production. Customers with a Signature Success Plan receive proactive site monitoring for environments marked as production. For more information, see the section on environments in Managed Runtime Overview.Monitor the eCDN and MRT metrics in Log Center, in the Metrics Dashboard. See Embedded Content Delivery Network (eCDN) Metrics and Managed Runtime Metrics in Salesforce Help.
After you confirm that the launch succeeded, lock down the production default domain to accept traffic only from your corporate VPN, so that public traffic flows only through your vanity hostname. Use an access control rule in the CDN API to allowlist your VPN’s IP addresses on the zone that fronts the default domain.
j