Incognito and private browsing: testing a shop without a saved session

A private window starts a separate session without the usual cookies and signed-in account. It is a quick way to view the shop as a new customer, but it does not replace clearing server cache or testing another browser.

When this matters

  • you need to check prices and content for a signed-out customer
  • the normal session retains a cart or old cookies
  • you are diagnosing a redirect, login or cookie consent

How to approach the implementation

  1. Chrome, Edge and Opera on Windows use Ctrl+Shift+N.
  2. Firefox on Windows uses Ctrl+Shift+P.
  3. On macOS, common browsers use Shift+Command+N, while Firefox uses Shift+Command+P.
  4. Close every private window after the test to end the session.
  5. Remember that downloads and bookmarks may remain on the device.

How to assess the result

Treat the implementation as successful when the user completes the full scenario without an error and staff can see the expected data in the back office. The absence of an error message alone is not enough.

Checks before going live

  • back up the settings or files that will change
  • test both a customer account and a guest session
  • check the cart, order flow and email messages
  • clear the relevant cache after the change

Apply the change in a test shop first, then run the complete scenario on desktop and mobile. Record the settings and the test result so that later updates can be compared with the same baseline.

2026 update: What private browsing actually does

A private window uses a separate cookie and session-data store. Cookies still work, but they are isolated from the regular profile and removed after the last private window closes. This is useful for testing a new customer session, not proof of a cache fault.

  1. open the same URL in regular and private windows
  2. test without a saved login, consent choice or old cart
  3. close every private window before starting a fresh private session
  4. if the difference remains, inspect cookies, local storage, browser cache and server layers

What it does not rule out

Private mode does not disable JavaScript, cookies or server-side caching. A CDN, PrestaShop cache and theme cache may serve the same page to both sessions. Use developer tools and record exact reproduction steps for a complete diagnosis.

Source and documentation: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Work_with_the_Cookies_API

Next guide

Fast product editing in PrestaShop: when the product form is no longer enough

Comments (0)

No comments yet.
Product added to wishlist