# Locations

The Locations section lets you define and manage the physical locations (stores, warehouses, offices) for the selected subsidiary in <code class="expression">space.vars.productName</code>. Each location can have registers assigned to it and can be enabled or disabled independently.

## Accessing Locations

{% stepper %}
{% step %}

### Open the NetSuite Admin view

Switch to **NetSuite Admin** in <code class="expression">space.vars.productName</code>.
{% endstep %}

{% step %}

### Select the subsidiary

Use the subsidiary switcher at the top right.
{% endstep %}

{% step %}

### Open Configurations

Click **Configurations** in the left sidebar, then scroll to the **Locations** section at the bottom of the page.
{% endstep %}
{% endstepper %}

![Locations section with the cross-subsidiary toggle, locations table, and edit modal](/files/vFghwJUUE17WHyRF5Ks1)

## Cross-Subsidiary Inventory Viewing

At the top of the Locations section is the **Enable Cross-Subsidiary Inventory Viewing** toggle.

| Setting      | Effect                                                                     |
| ------------ | -------------------------------------------------------------------------- |
| **Enabled**  | Users can see stock levels from other subsidiaries when browsing inventory |
| **Disabled** | Users only see stock for their own subsidiary                              |

Use the **Select Locations to View** dropdown to choose which locations from other subsidiaries are included when cross-subsidiary viewing is turned on.

## Locations table

The table lists all NetSuite locations associated with this subsidiary.

| Column        | Description                                                   |
| ------------- | ------------------------------------------------------------- |
| **Name**      | The location name from NetSuite                               |
| **Registers** | The number of registers assigned to this location             |
| **Enabled**   | Toggle to make this location visible and active in the portal |
| **Actions**   | Edit the location's register and settings                     |

## Enabling or disabling a location

Toggle the **Enabled** switch next to a location name. Disabled locations are hidden from users and can't be selected in workflows or at checkout.

## Editing a location

Click the edit icon (pencil) in the **Actions** column to open the location settings modal.

### Location settings

| Field                          | Description                                                                                                                         |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Location Name**              | The display name for this location                                                                                                  |
| **Default Catalog**            | When a catalog is set, it overrides the subsidiary catalog for this location                                                        |
| **Default Customer**           | When set, this customer is used as the default for location-based customer selection                                                |
| **Payment Processing Profile** | When set, this payment processing profile is used for transactions at this location                                                 |
| **Load Location**              | When enabled, this location is forced to load by setting a session variable with key `location` and this location's ID as the value |

### Location branding

| Field     | Description                                                                                                                |
| --------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Logo**  | If no logo is set, the application shows the <code class="expression">space.vars.productName</code> logo by default        |
| **Theme** | If no theme is selected, the application shows the <code class="expression">space.vars.productName</code> theme by default |

### Registers

Each register assigned to this location is listed with the following details:

| Column                | Description                            |
| --------------------- | -------------------------------------- |
| **Register Name**     | The name of the register               |
| **Assigned Employee** | The employee assigned to this register |

Each register can have one or more **Terminals** configured:

| Field    | Description                 |
| -------- | --------------------------- |
| **Name** | The terminal's display name |
| **TSN**  | The terminal serial number  |

### Session Variables

Define variables specific to this location. These variables can override subsidiary-level session variables for transactions and workflows at this location.

## Tips

* Only enabled locations appear in the portal when users select a location or register at login.
* If a location has no registers assigned, it can't be used at a POS terminal.
* Cross-Subsidiary Inventory Viewing is useful for businesses where stock is shared across multiple subsidiaries or warehouses.

## Related Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Configurations Overview</strong></td><td>All sections on the Configurations page.</td><td><a href="/pages/gogCTxJRLdzy1P6i1xeB">/pages/gogCTxJRLdzy1P6i1xeB</a></td></tr><tr><td><strong>Session Variables</strong></td><td>Setting a default location via session variables.</td><td><a href="/pages/ch1XpdbeBxjt9dL7fnUy">/pages/ch1XpdbeBxjt9dL7fnUy</a></td></tr><tr><td><strong>Card Present Payments</strong></td><td>Subsidiary-level payment profile (location overrides apply on top).</td><td><a href="/pages/JshZK1GWcwOEvoS5oa1q">/pages/JshZK1GWcwOEvoS5oa1q</a></td></tr></tbody></table>


---

# 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://docs.in8sync.com/netsuite-admin-guide/overview-1/locations.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.