# Settings

## Set up redirect behavior

When connecting multiple stores, you can decide how redirections between them should work. There are two options:

<figure><img src="/files/NelJidzohkiskbdrsyfB" alt=""><figcaption></figcaption></figure>

### Redirect to homepage

Use this if **your stores don’t share the same URL structure**.

This option redirects users to the homepage of the correct store. It helps prevent 404 errors when equivalent pages don’t exist across stores.

### Redirect to the same page

Use this if **your stores share the same URL paths**.

When enabled, Orbe redirects users to the same page they were visiting, but in the correct store.

For example:

* The user lands on: `https://store-a.com/products/example1`
* They are redirected to: `https://store-b.com/products/example1`

If this option is disabled, they will be redirected to: `https://store-b.com/`

## Exclude specific URLs from geolocation

Sometimes you might want to disable the popup or redirection on specific pages—like a shared blog, press section, or landing pages. By excluding URLs, Orbe will stay inactive on those pages.

<figure><img src="/files/RaQYVaXu9Ef749R8l8l6" alt=""><figcaption></figcaption></figure>

#### Example use case

Imagine you have a shared blog hosted in your US store, and users from other countries should access it without redirection. To prevent Orbe from triggering, add an exclusion like: `/blogs/global-blog*`

This disables both the popup and any redirection logic on all pages that start with that path.

{% hint style="info" %}
URL exclusions give you control over where and when Orbe’s popup and redirect logic should apply.
{% endhint %}

#### How to format exclusions

* Add **relative URLs only** (no domain)
* Use an asterisk `*` to match all content after the URL
* Separate multiple URLs with commas

Example: `/blogs/global-blog*, /pages/summer-sale, /pages/about-us`

### FAQs

<details>

<summary>What happens if my store doesn't have the same URL structure?</summary>

Use the "Redirect to homepage" option. It avoids 404 errors by sending users to the homepage of the correct store.

</details>

<details>

<summary>What if I want users to land on the same page in another store?</summary>

Enable "Redirect to the equivalent page in the correct stores." It works only if all your stores follow the same URL structure.

</details>

<details>

<summary>How do I make sure certain pages never trigger the popup or redirection?</summary>

Use the [exclusion rules](#exclude-specific-urls-from-geolocation) to disable Orbe on any URL. Make sure to format the paths correctly (e.g., `/blogs/global*`).

</details>

<details>

<summary>Can I exclude only one specific page?</summary>

Yes. Just use the full relative URL without `*`, like `/pages/press`.

</details>

## Shared settings across stores <a href="#shared-settings" id="shared-settings"></a>

{% hint style="warning" %}
You’ll only see **Shared settings** if your account meets both conditions below:

* You’re on an **Orbe Plus or Enterprise plan**;
* You have **more than one store** connected to Orbe.

If either requirement isn’t met, the Shared settings option won’t appear in **Connect stores**.
{% endhint %}

### What Shared settings is <a href="#shared-settings-definition" id="shared-settings-definition"></a>

Shared settings let you **apply the same configuration across all your connected stores**, so you don’t need to repeat the same update over and over. **Each section can be shared or kept independent**, giving you full flexibility: make a change once when all stores should behave the same, or switch a section back to local settings when you need exceptions for specific markets.

**It works per section, not globally**. This means you decide **in each specific tab** whether settings are shared or kept independent. The feature is available in:

* **Settings →** [**Geolocation**](/settings/geolocation.md);
* **Settings →** [**Custom code**](/settings/custom-code.md);
* and [**Integrations**](/general/integrations.md) **→ All**, **Internationalization** and/or **marketing**.

You choose, in each section, whether the settings are shared between stores or managed independently. It does **not** affect the “Connect stores” setup itself.

<figure><img src="/files/SGja0knINnuu4Flqegf3" alt=""><figcaption></figcaption></figure>

#### When you turn Shared settings **on** <a href="#shared-settings-on" id="shared-settings-on"></a>

When you activate Shared settings in a section, Orbe immediately takes the settings from the store you’re currently editing and **copies them to all other connected stores** for that specific section.

From there, the section becomes shared: **any change you make and save is automatically synced across all stores**, so you only need to configure it once.

#### When saving changes with Shared settings **on** <a href="#save-shared-settings" id="save-shared-settings"></a>

Once a section is shared, you only need to configure it **once**. Any change you make (no matter **which store** you’re editing from) will automatically sync across all connected stores for that section.

All stores stay perfectly aligned, so your setup remains consistent everywhere without extra steps.

#### When you turn Shared settings **off** <a href="#shared-settings-off" id="shared-settings-off"></a>

When you switch Shared settings off in a section, **synchronization stops right away**. Nothing is reversed or overwritten: **each store keeps the settings it already had** at that moment.

From then on, changes you make apply **only** to the store you’re currently editing, and that section becomes fully independent again for every store.

### FAQs <a href="#shared-settings-faqs" id="shared-settings-faqs"></a>

<details>

<summary>If I activate Shared settings, will changes apply to all my stores?</summary>

**Yes**. As long as Shared settings is **on** in a section, anything you edit there will be synced across all connected stores.

</details>

<details>

<summary>If Shared settings is off, do changes apply only to one store?</summary>

**Exactly**. With it off, each store has its own local settings. Changes affect **only** the store you're editing.

</details>

<details>

<summary>Can I keep different settings for different stores?</summary>

**Yes**. Shared settings works **per section**, not globally.

* If Shared settings is **on** in a section, all stores share those settings.
* If it’s **off**, that section is independent for every store.

</details>

<details>

<summary>What happens if I turn Shared settings on later?</summary>

Orbe will take the settings of the store you are currently editing and **push them to all other stores** for that section, then start syncing going forward.

</details>

<details>

<summary>What happens if I turn it off later?</summary>

The sync stops. All stores keep the settings they currently have (nothing is undone). From there, each store becomes independent again for that section.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.orbe.app/general/connect-stores/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.