Commerce Cloud Pre-Launch Checklist

Review the documentation about testing and going live Site launch documentation

NOTE

Ensure a comprehensive “go live readiness plan” is fully prepared with your partner or system integrator, incorporating all necessary action items. Remember, while the pre-launch checklist emphasizes Adobe’s best practices, it does not replace the need for your own go-live readiness plan.

Blocker Review the Support Insights (SWAT) Recommendations and Information (User Guide)

End user/merchant conducted UAT (User Acceptance Testing), including backend operations.

The system integrator team has performed end-to-end UAT on staging and production. Refer to the Experience League Documentation.

Confirm code deployment and testing in staging and production environments (Read more).

The production cluster has been up-sized permanently to the contracted daily baseline. Speak to the assigned CTA/CSE for more details, or raise a support ticket.

Blocker Make sure that caching is working (Full-Page Cache or GraphQL caching). Read the Fastly set up guide.

Use the GET method for GraphQL queries on PWA/Headless websites when applicable.

NOTE

Only the queries submitted with an HTTP GET operation can be cached (if applicable). POST queries cannot be cached.

Ensure that Fastly Image Optimization is enabled (See Fastly Image Optimization)

Verify that the correct shield location is configured (Configure cache, backends and origin shielding).

Web Application Firewall (WAF) is working. (See Troubleshooting blocked requests, if any, and limitations)

Update the Fastly “Ignored URL Parameters” list in the admin panel to enhance cache performance.

NOTE

In the Fastly configuration under _Admin > Stores > Configurations > System > Full Page Cache > Fastly Configuration

Advanced Configuration > Ignored URL Parameters (Global)_, you can find a comma-separated list of parameters that Fastly should disregard when searching for cached pages. Please make sure to re-upload the VCL after modifying this list

Blocker Confirm all required domain names are requested. (Submit a support ticket in-advance for any added or changed domains)

Blocker SSL (TLS) certificate has been applied to the domain(s). Read this article for more information.

Update DNS TTL (Time to Live) value to the minimum possible, for the go live.

Enable Sendgrid SPF and DKIM

NOTE

Add the SendGrid CNAME records for each domain to the DNS configuration. Read SendGrid email service to see how to change the sender domains and more.

Test the outgoing transactional emails. Read more about Adobe Commerce Cloud - SendGrid Mail functionality.

Blocker Any blockers with Adobe?

Blocker Perform load and stress testing on the Production instance before going live and share results with the assigned CTA/CSE.

NOTE

A load and stress test serves the purpose of identifying bottlenecks and uncovering performance issues within the application. It plays a crucial role in managing expectations regarding cluster size and determining the necessary scaling adjustments to meet the business requirements effectively.

IMPORTANT

WARNING: When preparing a load test please_ do not send out live transaction emails (even to dummy addresses). Sending emails during testing can cause the project to reach the default send limit (12k) configured for SendGrid prior to launch.

• How to disable email communication:
  Go to Store > Configuration > Advanced > System > Email Sending Settings.

Conduct security penetration testing on the production instance as part of the shared responsibility security model. For PCI (Payment Card Industry) compliance, the customized site requires penetration testing.

Switch indexing to "update on schedule", except the customer_grid which remains on “SAVE” (see Indexing modes).

Are you using any third-party search engines or extensions?

Confirm that SEO (Search Engine Optimization) configurations are properly set up to enable indexers/crawlers to scan the website, if relevant.

Add redirects and routes (see Configure routes)

NOTE

Add redirects and routes to the routes.yaml file in the Integration environment and verify the configuration in this environment before deploying to Staging and Production.

 "http://{all}/":
     type: upstream
     upstream: "mymagento:http"

 "http://{all}/":
     type: upstream
     upstream: "mymagento:http"

Ensure XDebug is disabled if enabled during development (see Configure Xdebug).

Verify that op-cache and other configurations have been accurately updated in the php.ini file (refer to this sample).

Subscribe to the Adobe Commerce status page.

Subscribe to New Relic “Managed Alerts for Adobe Commerce” notification channels to monitor the given performance metrics (read more).

Setup the Adobe Commerce Security Scan

NOTE

Adobe Commerce Security Scan is a useful tool that helps discover outdated software versions, incorrect configuration, and potential malware on the site. Sign up, schedule it to run often, and make sure that emails are sent to the right technical security contact.

Complete this task during UAT. If you use the periodic scans option, be sure to schedule scans at low demand times. See the Security Scan page in the Adobe Commerce Account. You must log in to an Adobe Commerce account to access the Security Scan.

Change the default settings for the Adobe Commerce Admin.

Change the admin password (see Configuring Admin Security).

Change the admin URL (see Using a custom Admin URL).

Remove any users no longer on the project (see Create and manage users).

Passwords for administrators are configured (see Admin Password Requirements).

Configure two-factor authentication (see Two-Factor Authentication).