Verify your storefront setup

Confirm that a new or changed storefront connection supports the content, catalog, and shopping features in your project’s agreed scope. Start after the local or shared development preview is running.

This process is a development-readiness check, not a production launch review. Check only the features included in your project’s agreed development scope.

Before you start

Gather these details from the project owner or Commerce administrator:

• The local or shared development preview URL.
• The intended Commerce environment and store or catalog.
• A content page and an available product from that catalog.
• The product’s expected price and currency for the shopper being tested.
• A search term and filter to test, if search is configured.
• An approved test account, if account features are required.

The storefront should already be running. For setup instructions, use Create a storefront, Run your storefront locally, or Storefront configuration.

With Adobe Commerce Optimizer, identify both the catalog service and the platform that handles cart, checkout, and accounts. A successful catalog connection does not prove that the transactional integration is ready.

Confirm the active configuration

Check the settings the storefront loaded, rather than only the settings saved in a file or configuration service.

Follow Confirm the loaded configuration to compare the active endpoints and store or catalog context with the approved development settings.

Continue only when the values match. If they still point to a demo or another environment, resolve the configuration issue before testing shopping features.

Check content and catalog data

Use known pages and products so you can distinguish a working connection from sample content.

1. Open the agreed content page in your development preview.

   Confirm that the expected heading, text, or images appear.

2. Open the agreed product page.

   Confirm that the product name and images match the intended catalog.

3. Compare the displayed price and currency with the expected values.

   Use the same store and shopper context that the Commerce administrator used to provide those values.

4. Search for the agreed term, if search is configured.

   Confirm that the results include the expected products.

5. Apply the agreed filter, if filtering is configured.

   Confirm that the displayed products match the selected filter.

If search or filtering is intentionally outside the current scope, record it as not applicable. If it is required but does not work, record a failed check rather than skipping it.

Check cart and checkout

Run these checks when cart and checkout are part of the project. For a catalog-only development phase, record these features as outside the current scope.

Use an approved test environment

Use a test product and environment approved by your team. Do not submit an order or use real payment details during these checks. A separate end-to-end order test needs the team’s approved test-payment procedure.

1. Select any required options on the test product.

   Skip this step if the product has no options.

2. Add the product to the cart.

   Confirm that the cart shows the selected product and options.

3. Change the quantity to another allowed value.

   Confirm that the cart updates the quantity and totals as expected.

4. Open checkout from the cart.

   Confirm that the expected cart items and checkout fields appear. Check any sign-in requirement against the project’s intended behavior.

Opening checkout does not verify payment processing or order placement. Keep those results separate from this setup check.

Check account features

Use these checks when customer accounts are included in the project.

1. Sign in with the approved test account.

   Confirm that the storefront shows the expected signed-in state.

2. Open the account page.

   Confirm that it shows the test account’s information.

3. Sign out of the storefront.

   Confirm that the storefront returns to its expected signed-out state.

Resolve failed checks

Start with the symptom that matches the failure. A working product page and a failing cart can indicate different backend connections, not a broken content page.

Symptom	What to check next
Content does not load.	Confirm the content source and preview URL using Create a storefront and the local setup troubleshooting checks.
Configuration still contains demo or old values.	Recheck the current origin, code branch, configuration source, and browser cache using Storefront configuration.
Products are missing or search returns unexpected data.	Confirm the intended store or catalog context. For Adobe Commerce Optimizer, check Data Sync . If you use Adobe Commerce Optimizer Connector, also review Connector troubleshooting . For Catalog Service or Live Search configurations, use Data export validation.
The browser reports blocked cross-origin requests.	Use CORS Troubleshooting to investigate requests between the storefront and Commerce services.
Catalog data loads, but cart, checkout, or sign-in fails.	Check the transactional connection and Backend options. For Adobe Commerce, confirm the Storefront Compatibility package. For a third-party platform, ask the integration owner to check its APIs.

When asking for help, include the page URL, intended environment, failed action, and error message. Remove account details, authentication tokens, and other sensitive data from screenshots or logs.

Confirm readiness for development

Project setup is complete for the agreed scope when the required checks pass against the intended environment. Record the environment, tested features, failed checks, and any features explicitly outside that scope.

A required feature with an unfinished backend integration is still blocked. Do not treat a successful catalog check as approval for the whole shopping experience.

If you have not made a local code change yet, continue with Make your first change. Otherwise, return to the planned feature work. Before production, complete the separate Launch checklist.