Get client feedback on your Magento Open Source storefront

Q: Should I share Magento Admin with reviewers?

No. Reviewers can comment on an accessible rendered storefront without receiving the separate Admin URL or Admin credentials.

Q: What is Magento production mode?

Adobe describes production mode as the mode for a production system. It serves static view files from the cache and logs errors instead of displaying them to visitors.

Q: Why might theme changes not appear after deployment?

Magento production mode relies on deployed static view files. The project’s normal deployment and cache workflow must make the updated presentation available before review.

Q: Can reviewers open a store in maintenance mode?

Only when their requesting client IP is authorized. Otherwise Magento returns its 503 maintenance page, and a pasted URL does not bypass that rule.

Q: Can I review a custom Magento storefront?

Yes, when the custom browser frontend is deployed and accessible. Adobe documents the Magento Open Source GraphQL schema as a foundation for custom and headless storefronts.

Q: Does a BugSmash link create a customer or cart session?

No. Customer authentication, cart state and checkout access remain part of the storefront. Use an authorized session or the Feedback Widget when that state is required.

Q: Does BugSmash deploy Magento changes?

No. Magento still controls application mode, configuration, static view deployment and store operation. BugSmash records contextual feedback on the rendered storefront.

Paste an accessible storefront page, send one review link, and collect contextual comments on the customer-facing Magento experience.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Magento runs the store. BugSmash organizes feedback on the storefront.

Magento Open Source controls storefront URLs, application modes, generated view files and store access. Those controls remain in effect during a BugSmash review.

Four documented boundaries matter before you share the store:

The storefront and Admin have different URLs.
Adobe documents a base URL for each storefront and another URL for Admin. Send reviewers the customer-facing storefront, not the administrative interface.
Production output follows Magento’s deployment process.
Production mode serves static view files from the cache. Magento provides a static-content deployment command to write those presentation files before they are served.
Maintenance mode restricts the storefront.
Magento returns a 503 maintenance page while maintenance mode is active, except when the requesting client IP appears in the authorized IP list.
Custom storefronts are separate deployments.
The Magento Open Source GraphQL schema can support a custom or headless storefront. Review the deployed browser frontend, not the GraphQL endpoint.

BugSmash keeps feedback attached to the rendered storefront:

share an accessible storefront URL, preserve the browser context, and leave Magento configuration, catalog changes and deployment under the delivery team’s control.

How it works

Three steps to a reviewed Magento storefront

Choose the storefront URL

Use the public store, an accessible staging store, or a deployed custom storefront backed by Magento Open Source.

Send one BugSmash link

Paste the accessible page into BugSmash and share the generated review link with the client, merchant or QA team.

Apply, deploy and verify

Make approved catalog, theme or code changes through the normal Magento workflow and, when the store runs in production mode, deploy the required static view files before reviewing the resulting storefront again.

Review the Magento storefront, not the Admin interface

Comment on customer-facing pages

Attach feedback to the rendered home, category, product or content page the reviewer is discussing.

Review staging before launch

Use a browser-accessible staging storefront while Magento remains responsible for its environment and access rules.

Cover custom storefronts

Review a deployed browser frontend that consumes the Magento Open Source GraphQL API.

Check responsive presentation

Review desktop, tablet and mobile layouts while retaining the viewport with every comment.

Capture technical context

Keep the page URL, browser, operating system, viewport and screenshot with each website comment.

Keep Admin access separate

External reviewers can comment on an accessible storefront without receiving Magento Admin credentials.

Which Magento Open Source URL should I review?

Use an accessible rendered storefront. Magento application mode, maintenance settings, customer authentication and hosting rules continue to control access.

Your URL	Review by URL	What to do
Public Magento Open Source storefront	Works	Paste the public store or product-page URL into BugSmash.
Accessible staging storefront	Works	Use the staging URL after confirming every reviewer can reach it.
Basic Auth-protected storefront	Works with credentials	Use BugSmash’s documented Basic Auth support and provide the credentials to authorized reviewers.
Deployed custom or headless storefront	Works	Review the deployed browser URL, not its GraphQL endpoint.
Magento maintenance mode	IP-dependent	Magento returns a 503 page unless the requesting client IP is authorized. A pasted URL does not bypass that maintenance restriction.
Customer-account or checkout state	Access-dependent	Authenticate in the authorized storefront session or use the Feedback Widget. A review link does not create a customer session.

Using the Feedback Widget on a Magento storefront

Add the BugSmash Feedback Widget to the rendered storefront when reviewers must stay inside an authorized customer, cart or application session. Magento continues to control that session and every store permission.