Launch checklist
Use this checklist to verify that your production Adobe Commerce Optimizer project is configured, tested, and ready for launch. Work through each section with your team and track completion in your own project plan or tracker. For product capabilities and UI areas referenced below, see the Adobe Commerce Optimizer documentation.
Use case and architecture use-case
Use this checklist when you deliver a B2C experience that combines Adobe Commerce Optimizer and Edge Delivery Services (EDS) with an existing Adobe Commerce on Cloud instance.
Your solution typically includes these components:
- Cloud—Adobe Commerce on Cloud manages catalog data, customers, assets, and purchase flows (checkout, order management, shipping, and so on).
- Optimizer—Adobe Commerce Optimizer delivers merchandising experiences.
- Storefront—Adobe Commerce Storefront on Edge Delivery Services provides the UI.
- Third-party services—Payment, shipping, and tax providers.
- App Builder—Extensibility.
- API Mesh—Request routing.
Verify Adobe Commerce on Cloud verify-cloud
Confirm that your Adobe Commerce on Cloud environment is ready for production.
▢ The Cloud instance is provisioned.
▢ Testing and dummy data are removed from the instance.
▢ Production data is loaded on the instance.
▢ You know the GraphQL endpoint.
▢ The instance meets ready-for-launch requirements.
Verify Commerce Optimizer instance verify-optimizer
Confirm that your Adobe Commerce Optimizer production instance is set up correctly.
▢ The production instance is active. See Get started for how you provision it.
▢ The instance is in the correct region.
▢ The environment type is Production.
▢ You know the organization ID, client ID, ingestion URL, and Commerce Optimizer URL. See Get started.
▢ Configured limits and boundaries match the values confirmed by your Adobe Customer Technical Advisor (CTA).
▢ Testing artifacts and dummy data have been removed from the instance.
Verify storefront site verify-storefront-site
Confirm that your Edge Delivery Services storefront site exists and access is restricted.
▢ The storefront site exists. See Create a storefront.
▢ You know the site name.
▢ Only authorized people have permission to publish.
▢ Only authorized people have permission to author.
Verify Cloud and Optimizer integration cloud-optimizer-integration
Confirm that Adobe Commerce on Cloud and Adobe Commerce Optimizer exchange data correctly.
On Adobe Commerce
Complete these checks in your Cloud project.
▢ The Commerce Optimizer connector is installed and configured.
▢ The aco:conf:show CLI command confirms connection to the production Commerce Optimizer instance. The organization ID, client ID, ingestion URL, and Commerce Optimizer URL match production.
▢ Synchronization scopes in Export configuration match your requirements.
▢ Data feed sync status confirms data export from the Cloud instance.
In Commerce Optimizer
Complete these checks in the Adobe Commerce Optimizer UI.
▢ The data sync dashboard shows received data. Products, prices, and attributes appear for Catalog Service, Product Discovery, and Recommendations.
▢ Price books are auto-created from customer groups on Cloud.
▢ Catalog views exist and you know their IDs.
▢ Policies exist and you know their IDs.
▢ Facets are configured.
▢ Synonyms are configured.
▢ Merchandising rules are configured.
▢ Price faceting and search language match your requirements when you use those features.
▢ Product recommendations exist and behave as expected in preview.
▢ Search performance data appears in the Admin.
▢ Recommendations performance data appears in the Admin.
Verify storefront and Cloud integration storefront-cloud-integration
Confirm that the storefront reads from the correct Adobe Commerce GraphQL endpoint.
On Adobe Commerce
▢ Storefront compatibility packages are installed.
On the storefront
▢ The storefront commerce-core-endpoint setting points to your Cloud GraphQL endpoint.
▢ If you use API Mesh as a proxy for Cloud GraphQL, commerce-core-endpoint points to the API Mesh endpoint instead of the Cloud GraphQL endpoint.
Verify storefront and Optimizer integration storefront-optimizer-integration
Confirm Commerce Optimizer settings in the storefront configuration.
▢ Your storefront uses the correct Commerce Optimizer settings.
▢ adobe-commerce-optimizer is true.
▢ commerce-endpoint points to the production Commerce Optimizer GraphQL endpoint, or to the API Mesh endpoint when you use API Mesh.
▢ headers.cs.AC-view-ID holds the catalog view ID from your production Commerce Optimizer instance.
Verify third-party services on Cloud third-party-services
Confirm integrations that run on your host commerce system (not in Adobe Commerce Optimizer).
▢ Payments: Payment gateway is live and tested (Stripe, PayPal, Adyen, and so on).
▢ Shipping: Shipping API connections work (UPS, FedEx, and so on).
▢ Shipping: Fulfillment platform is connected and tested (for example, ShipStation).
▢ Tax: Tax calculation integration is validated (Avalara, TaxJar, and so on).
▢ Tax: Accounting software sync works (QuickBooks, and so on).
▢ Inventory: PIM, ERP, or inventory management integration is tested and syncing.
▢ Architecture: The host commerce system handles payment, shipping, tax, and inventory (not Adobe Commerce Optimizer).
▢ Architecture: API Mesh and App Builder stay in sync between the host commerce system and Adobe Commerce Optimizer.
▢ Email: Transactional email delivery works (order confirmation, shipping, and so on).
▢ Email: Email templates match your brand and use correct links.
Verify App Builder and API Mesh app-builder-mesh
Confirm extensibility configuration for production.
App Builder
▢ The production workspace includes all required configurations and services.
▢ The production app passes testing across build scenarios.
▢ Product limits and boundaries have been reviewed and confirmed based on the Adobe Developer App Builder product description and App Builder system settings and limitations.
▢ The production app uses App Builder production endpoints.
▢ Custom Admin panel extensions are deployed to the production workspace.
API Mesh
▢ Configurations and sources are ready for production.
Events
▢ Adobe I/O Events are configured and subscriptions are verified.
Finalize storefront experience finalize-storefront
Polish content, SEO, performance, security, and CDN behavior before launch.
Content and authoring
Confirm authoring workflow and storefront components.
▢ The AEM/EDS go-live checklist review is complete.
▢ The authoring source is document-based or Universal Editor (and configured).
▢ Content is published using the preview → publish cycle.
▢ Content and design QA is complete on the .aem.live domain.
▢ A favicon is configured and served correctly by the site.
▢ da.live and product visuals use configured dedicated credentials.
▢ Drop-ins (cart, checkout, PDP, PLP, auth, account) are customized and tested.
▢ Storefront branding reflects CSS design tokens, typography, and colors.
SEO and indexing
Confirm metadata, URLs, and crawl behavior.
▢ Document title metadata is present for key pages (especially PDPs and PLPs). See SEO metadata in the Adobe Commerce Storefront documentation.
▢ PDPs include metadata and structured data (for example, JSON-LD).
▢ Product URL formats are consistent (for example, domain/product-name).
▢ Vanity URLs redirect to canonical URLs.
▢ The project includes robots.txt that allows indexing where appropriate, references sitemaps, and blocks paths you do not want indexed (for example, /drafts).
▢ Redirect files cover URL changes from migration (for example, after removing .html).
▢ Sitemap exists and is submitted to Google Search Console as needed.
▢ Canonical URLs return 2xx status (not 3xx or 4xx).
▢ Multilingual sites include hreflang tags in the sitemap.
▢ The Google Search Console coverage report is current.
Pre-rendering
Confirm server-side rendering where you enable it.
▢ Pre-rendering is on for key pages. See Pre-rendering for AEM in the Adobe Commerce Storefront documentation.
▢ URLs use lowercase so pre-rendering does not break links.
▢ HTML source includes metadata and body content that confirm pre-rendering works.
▢ Locales show the correct translated pages where applicable.
▢ Additional HTML markup is configured as needed.
Performance and monitoring
Confirm performance baselines and analytics wiring.
▢ Your storefront follows performance best practices in the Adobe Commerce Storefront documentation.
▢ (Optional) Google Analytics and Google Tag Manager are configured.
▢ Storefront events implementation is valid and data appears in your Live Search and Product Recommendations dashboards in the Adobe Commerce Admin.
▢ The environment analytics parameter in Commerce configuration is "Testing" during development and "Production" at go-live. See Analytics instrumentation.
▢ Lighthouse scores meet your targets (for example, 100 on key pages) given the guidance in this topic.
Security and access
Confirm permissions and secrets.
▢ Appropriate permissions are configured for DA content and EDS sites. See DA.live permissions and Authentication setup for authoring.
▢ The product visuals integration is provisioned. See AEM Cloud Service access overview.
▢ Password reset links in email templates match your Edge Delivery Services setup. See the storefront FAQ: What should I do if my email template links are broken after migrating to Edge Delivery Services or Helix?.
▢ Production keys for integrations and payment providers are in place.
▢ Domains are allowlisted and backend webhooks work.
CDN and caching
Confirm CDN, DNS, and cache behavior.
▢ The CDN configuration uses the production GraphQL endpoint (yourproject.com/graphql) for Sidekick extensions and scripts (for example, sitemap generation and the image importer).
▢ When you use Adobe Commerce Fastly, a CDN purge token is available and site configuration includes authToken and serviceId.
▢ CDN configuration validates caching and invalidation.
▢ For multi-store setups, Catalog Service and Live Search requests include a store-specific cache buster (for example, a query parameter or CDN rule).
▢ Push invalidation works end to end (publish a change, then verify on the production domain).
▢ DNS TTL is low enough before cutover.
▢ DNS A and CNAME records are correct for all domains and hostnames.
▢ The SSL/TLS certificate is provisioned and verified for the production domain.
▢ www and apex redirects behave correctly.
Security and compliance security-compliance
Confirm security posture and compliance tasks.
▢ SSL: A trusted SSL/TLS certificate is installed.
▢ SSL: HTTPS is enforced site-wide.
▢ Access: Default Admin passwords are changed and a strong password policy is in place. See Adobe Commerce Optimizer User and identity management.
▢ Access: The Admin URL is not the default.
▢ Access: Two-factor authentication is enabled for all Admin users.
▢ Access: No inactive or unused Admin users are associated with the project.
▢ Firewall: Web Application Firewall (WAF) is configured and verified.
▢ PCI: Security penetration testing on production (PCI scope) is complete.
▢ Scanning: The Adobe Security Scan Tool is registered and an initial scan is complete.
▢ Access: CORS allows only approved origins.
▢ Compliance: The shared responsibility model for Adobe Commerce Optimizer is up to date and clearly defines Adobe versus customer responsibilities.
▢ Compliance: Privacy policy, cookie consent, and GDPR or CCPA requirements are verified.
Analytics and monitoring analytics-monitoring
Confirm measurement and baselines.
▢ RUM: Real User Monitoring (RUM) is instrumented for before-and-after comparison.
▢ Analytics: Adobe Experience Platform data collection is configured (if applicable).
▢ Analytics: Verified that MarTech tags fire on the production hostname.
▢ Analytics: Baseline analytics are documented; post‑launch fluctuations (page views, bounce rate, and so on) are expected.
▢ Events: Conversion tracking works end to end (add to cart → checkout → confirmation).
Testing testing
Confirm quality before and after launch.
▢ Functional: Core flows work end to end: browse → search → filter → add to cart → checkout → account creation.
▢ Functional: Payment gateways accept real and test transactions.
▢ Functional: Order placement, confirmation email, and order tracking work.
▢ Functional: Shipping options and tax calculations are accurate.
▢ Functional: Coupons, discounts, and loyalty programs behave as expected.
▢ UAT: User acceptance testing is complete on staging and production.
▢ Performance: Load and stress testing is complete and Adobe CTA or CSE has the results.
▢ Performance: Page load time is under three seconds on desktop and mobile.
▢ Performance: Lighthouse scores meet targets on key pages (for example, via PageSpeed Insights).
▢ Performance: Images, scripts, and assets are optimized.
▢ Compatibility: Chrome, Firefox, Safari, and Edge behave as expected.
▢ Compatibility: Responsive layouts work on mobile, tablet, and desktop.
▢ Compatibility: Performance is acceptable on 3G, 4G, and Wi-Fi.
▢ Accessibility: An accessibility audit is complete (WCAG, screen reader, keyboard navigation).
▢ Functional: A post‑launch 404 monitoring plan is in place.
▢ UAT: A rollback plan exists and passes testing if launch issues occur.
Launch day and post-launch launch-post-launch
Confirm communication, support, and follow-up tasks.
▢ Launch coordination: Adobe has your confirmed launch date; the CTA has been notified by email.
▢ Support: The P1 hotline number is recorded: US (+1) 800-497-0335, then press 6 for Commerce.
▢ Support: Your team is trained to open a support ticket before calling the P1 hotline.
▢ Post launch: Verify Lighthouse scores on the production domain.
▢ Post launch: Monitor Google Search Console for indexing and crawl errors.
▢ Post launch: Monitor 404 reports and add redirects for high-traffic legacy URLs.
▢ Post launch: Confirm MarTech and analytics data on production.
▢ Post launch: Ask your CTA, CSE, or AM to enable high-SLA monitoring.
▢ A disaster recovery plan exists and passes testing.
▢ A process is in place to track and upgrade boilerplate and extension packages to current versions.