> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.pandectes.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to switch to the new banner or switch back to the previous version

### Overview

This article explains how to move between the **Legacy Banner** and the **New Banner**. After you switch, the Banner page tabs and some settings change.

| | Legacy | New version |
| -------- | -------- | -------- |
| Banner tabs | Behavior, Style, Content | Layout, Content, Style, Advanced |
| Consent policy | Banner Behavior (policy mode) | **Settings > Consent model & regions** |
| Storefront | `#pandectes-banner` | `pandectes-cmp` web component |

On the New Banner page you can use **Switch to previous version**. Upgrading uses the in-app upgrade flow on the Banner page.

Read the product overview first: [Introducing our New, Faster and Optimized Pandectes GDPR Compliance Banner](/en/article/introducing-our-new-faster-and-optimized-pandectes-gdpr-compliance-banner-znfci6/).

### Before you start

* Note any **custom CSS** on the Legacy Style tab. It does **not** copy automatically.
* Note any **JavaScript API** snippets in the theme. The New Banner uses a redesigned API.
* Legacy **Reset consent on reopen** is **not** available on the New Banner.
* After a switch, check Checkout block, custom storefront (headless), and JS API usage.

### Switch to the New Banner

1. Open **Shopify Admin > Apps > Pandectes GDPR Compliance**.
2. Go to **Settings > Banner**.
3. Follow the in-app **upgrade** / New version prompt if you are still on Legacy.
4. Confirm the page badge shows **New version**.

![Banner page with the New version badge and Switch to previous version](https://images.pandect.es/knowledge-base/how-to-switch-to-the-new-banner-or-switch-back-to-the-previous-version-1.png =900xauto)
5. Open **Settings > Consent model & regions** and set consent model and regions (this replaced Geolocation + Legacy policy mode).
6. Recreate look and feel: [Migration Guide: Recreating your Legacy Look in New Version](/en/article/migration-guide-recreating-your-legacy-look-in-new-version-1r1oqc2/).
7. Paste needed CSS under **Style > Custom styling**. See [Custom styling with CSS](/en/article/custom-styling-with-css-52oqz4/).
8. If you used the JS API, follow [Javascript API (New Version)](/en/article/javascript-api-new-version-1ojr39k/).
9. Test with **Enable for admins**, then enable for visitors.

### Switch back to the previous version

1. Open **Settings > Banner** (New version).
2. Choose **Switch to previous version**.
3. Confirm the Banner tabs are **Behavior**, **Style**, and **Content** again.
4. Re-check Geolocation / Legacy policy mode, custom CSS, and any reopen or JS API snippets that were written for the New Banner.

||| Switching back can change how visitors see the banner. Test in a private window. Consider **Reset user consents** only if your privacy notice or consent logic changed in a way that requires asking again.

### What does not carry over

* Legacy custom CSS — [Custom styling with CSS (Legacy Banner)](/en/article/custom-styling-with-css-legacy-banner-1qt8dtl/)
* Legacy JS API method names and events
* Reset consent when the reopen button is clicked

Consent records already stored are not deleted by switching banner generation. Use **Settings > Reset user consents** only when you intend to ask every visitor again.

### Related articles

* [Consent Model & Regions (New Version)](/en/article/consent-model-regions-new-version-jvhtj5/)
* [Javascript API (Old Version)](/en/article/javascript-api-old-version-aaogmd/)