BlackFriday

50% offon all annual plans

00d00h00m00s
Explore plans
Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
PrestaShop logo

Get client feedback on your PrestaShop front office

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

https://

PrestaShop calls the customer-visible store the front office and its administration panel the back office. Review the front office URL customers open.

Knauf
Radancy
Frontier
City of Boroondara
Berlin Heart
GVBOCES
Bville
Frost Collective
Mediapilote
Medwiki
Musaffa
Sharp Guys Web Design

Loved by1,250+Agenciesand companies in 100+ countries

PrestaShop runs the store. BugSmash organizes feedback on the front office.

PrestaShop controls themes, store modes, cache behavior and multistore URLs. Those controls continue to determine what reviewers can open and see.

Four documented boundaries matter before you share the store:

  1. The front office and back office serve different users.

    The front office is the customer-visible store. The back office is the administration panel and requires employee credentials.

  2. Themes control front-office presentation.

    PrestaShop themes control the front-office layout, templates, styles and client-side behavior. Review the active theme on the rendered store.

  3. Maintenance mode restricts the front office.

    Disabling the store displays the maintenance page. A maintenance IP can still open the front office while other visitors cannot.

  4. Catalog mode is not maintenance mode.

    Catalog mode keeps products visible but removes purchasing features, including add-to-cart, order and payment controls.

BugSmash keeps feedback attached to the rendered front office:
share an accessible store URL, collect page-specific comments, and leave theme activation, cache management and store configuration in PrestaShop.

How it works

Three steps to a reviewed PrestaShop store

1

Choose the front-office URL

Use the public store, an accessible test installation, or the specific multistore URL that contains the pages under review.

2

Send one BugSmash link

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

3

Apply and verify changes

Update the theme, modules or catalog through the project’s normal workflow, clear or rebuild the relevant cache when required, and review the resulting front office again.

Review the PrestaShop front office, not the back office

Comment on customer-facing pages

Attach feedback to the exact rendered store location instead of describing it in a separate message.

Review theme presentation

Check the layout, templates, styles and client-side behavior delivered by the active PrestaShop theme.

Cover multistore URLs

Review the specific domain, subdomain or subfolder assigned to each store in a multistore installation.

Check responsive layouts

Review desktop, tablet and mobile presentation 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 back-office access separate

External reviewers can comment on an accessible front office without receiving employee credentials for the back office.

Which PrestaShop URL should I review?

Use the rendered front office and select the correct store URL in a multistore setup. Maintenance, catalog and customer access rules remain active.

Your URLReview by URLWhat to do
Public PrestaShop front office WorksPaste the public store or product-page URL into BugSmash.
Accessible test or staging store WorksUse the test URL after confirming every reviewer can reach it.
Specific PrestaShop multistore URL WorksUse the domain, subdomain or subfolder assigned to the store under review.
Store in catalog mode Works with limited flowsReview the visible catalog, recognizing that purchasing controls are intentionally removed.
Store in maintenance mode IP-dependentOnly configured maintenance IPs can open the front office. A pasted URL does not bypass that restriction.
Customer account or checkout state Access-dependentAuthenticate in the authorized store session or use the Feedback Widget. A review link does not create customer state.

Using the Feedback Widget on a PrestaShop front office

Add the BugSmash Feedback Widget to the rendered front office when reviewers need to remain inside an authorized customer, cart or maintenance-IP session. PrestaShop continues to control that access.

Turn PrestaShop page feedback into trackable work

Route an actionable website comment with its page URL, selected location, screenshot, browser, operating system and viewport context preserved.

Context stays attached from comment to completion.

Send to your workflow

The destination changes. The context does not.

Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks

The PrestaShop store is one deliverable. Review the complete launch together.

Keep the store beside product images, PDFs, videos and campaign materials, with feedback and approval in one project.

  • Website
  • HTML
  • Widget
  • Video
  • Audio
  • Image
  • PDF
  • PPT
  • Doc
  • Email
  • 3D Model
  • CAD
  • Mobile App
  • Canvas

PrestaShop store feedback, answered

Which PrestaShop URL should I send for review?

Send the customer-facing front-office URL. In a multistore installation, use the domain, subdomain or subfolder assigned to the specific store.

Ship PrestaShop stores without chasing feedback

Paste an accessible PrestaShop front-office URL and send a focused review link.

BugSmash website review interface with comment controls