> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/profile-and-settings/organization-settings/locations.md).

# Locations

Define shipping, receiving, and facility locations to provide standardized ship-to addresses on POs and integrate with NetSuite, ION, and other systems

Manage shipping, receiving, and facility locations for your organization. Locations provide standardized ship-to addresses for purchase orders, ensuring consistency and integration with external systems.

## Overview

Every order ships to one of your organization's locations. Users pick a **Ship To Location** on the order, and the location's address prints on the PO, so the same place is always spelled the same way.

Locations are added in settings or synced from your integrations (NetSuite, ION).

## Managing Locations

Users with the Buyer or Admin role can add, edit, archive, and delete locations in **Organization Settings** → **Locations**. A custom role needs the `create_location`, `edit_location`, and `delete_location` permissions for these actions.

### Add a location

1. Navigate to **Organization Settings** → **Locations**
2. Click **Add Location**
3. Enter a **Name** and **Address**, then click **Add Location**

Location names are unique within your organization.

### Edit, archive, or delete a location

Open the **⋮** menu on a location's row and choose:

* **Edit** — change the location's name or address
* **Archive** / **Unarchive** — hide the location from order dropdowns, or make it available again
* **Delete** — remove the location permanently

{% hint style="info" %}
A location used by an order or set as the default ship-to location cannot be deleted. Archive it instead.
{% endhint %}

{% hint style="warning" %}
If your organization has turned off location management in Silkline because an integration owns your locations, these controls are disabled. Make changes in the integrated system instead.
{% endhint %}

## Syncing Locations from Integrations

Silkline supports location syncing from:

### NetSuite

When NetSuite integration is configured:

* Locations are automatically synced from NetSuite location records
* Location names and addresses are imported
* Orders synced from NetSuite include their NetSuite location reference

### First Resonance (ION)

When ION integration is configured:

* Locations are automatically synced from ION
* Both ship-to and bill-to addresses can be imported
* Custom ION location attributes can be mapped

## Location Properties

Each location contains:

| Property    | Description                                      |
| ----------- | ------------------------------------------------ |
| **Name**    | Unique identifier for the location               |
| **Address** | Full shipping address (street, city, state, zip) |
| **Status**  | Active or Archived                               |
| **Created** | Date the location was added to Silkline          |

## Default Ship-To Location

You can set a default ship-to location that will be automatically pre-selected when creating new orders. An order created from a quote on a request uses the request's location instead, when the request has one.

To set a default ship-to location:

1. Navigate to **Organization Settings** → **Locations**
2. In the **Default Ship-To Location** section, select a location from the dropdown
3. This location will now be pre-filled on new order forms

{% hint style="success" %}
**Best Practice:** Set your most frequently used location as the default to save time when creating orders.
{% endhint %}

## Require a Ship-To Location

You can require every order to have a ship-to location.

1. Navigate to **Organization Settings** → **Locations**
2. Turn on **Require a ship-to location**

Orders cannot be created or saved until a **Ship To Location** is selected. A default ship-to location fills the field automatically on new orders.

## Require a Location on Requests

You can require every request to have a location, separately from the order setting above.

1. Navigate to **Organization Settings** → **Locations**
2. Turn on **Require a location on requests**

Requests cannot be created, submitted from a Shop cart, or saved until a **Location** is selected. A request without a location shows a "Location is required" error on its Location field.

## Viewing Locations

The **Manage Locations** section lists all of your organization's locations in a table:

* Columns show each location's **Name**, **Address**, **Ship To Usage**, and **Status** (Active or Archived), plus one column per integration that syncs locations
* **Ship To Usage** counts the orders that use the location as their ship-to location
* Locations are sorted alphabetically by name; click a column header to sort by it
* Search matches a location's name, address, or integration ID
* The **Status** filter shows only active or only archived locations

### Bulk editing and merging locations

With [data cleaning mode](https://docs.silkline.ai/administration-tools/data-cleaning-mode.md) on, the locations table shows a checkbox on every row:

* Select locations, click **Edit**, and set **Archived** to archive or unarchive them all at once
* Select locations and click **Delete** to remove them permanently. If any selected location is used by an order, nothing is deleted — archive those locations instead
* Select exactly two locations and click **Merge** to combine duplicates — see [Merging Duplicate Records](https://docs.silkline.ai/administration-tools/merging-records.md)

### Location Status

* **Active** — Available for selection on new orders
* **Archived** — Hidden from order dropdowns but preserved for historical orders

## Using Locations on Orders

The order form includes a **Ship To Location** field:

### Creating Orders

1. Start creating a new purchase order
2. In the **Ship To Location** dropdown, select the appropriate location
3. The selected location's address is automatically applied to the order

### Editing Orders

The ship-to location can be changed on existing orders:

1. Open the order for editing
2. Change the **Ship To Location** dropdown
3. The order's ship-to address updates to match the new location

{% hint style="info" %}
An order always shows its location's current address. Changing a location's address changes the ship-to address on every order that uses that location, including past orders.
{% endhint %}

## Integration Behavior

### NetSuite

* **Sync Direction:** NetSuite → Silkline (ingest only)
* **Updates:** Changes to NetSuite locations sync to Silkline automatically
* **Orders:** Orders created in Silkline can reference NetSuite locations
* **Writeback:** When orders are written back to NetSuite, the location reference is preserved

### First Resonance (ION)

* **Sync Direction:** Bidirectional (ION ↔ Silkline)
* **Updates:** Changes in either system sync automatically
* **Orders:** Orders reference ION locations for procurement workflows
* **Writeback:** An order written back to ION ships to the ION location whose address matches the order's ship-to location
* **Custom Attributes:** ION location attributes can be mapped to custom fields

### ProShop and Custom API

* **Sync Direction:** Order ship-to addresses sync into Silkline (ingest only)
* **Orders:** Each ingested order is linked to the location with a matching address. A new address creates a location named after that address.

## Archiving Locations

Archive a location that is no longer in use but is referenced by historical orders:

* Archive or unarchive a location from its **⋮** menu in settings, or in your external system (NetSuite/ION) for synced locations
* Archived locations are hidden from order dropdowns
* Historical orders still display the archived location

## Common Use Cases

### Multiple Facilities

Organizations with multiple receiving facilities can create locations for each:

```
Headquarters
123 Main Street
San Francisco, CA 94102

Manufacturing Plant
456 Industrial Blvd
Austin, TX 78701

Distribution Center
789 Warehouse Way
Memphis, TN 38101
```

### Department-Specific Locations

Create locations for different departments within the same facility:

```
Engineering Lab - Building A
Receiving Dock 3
123 Campus Drive
Seattle, WA 98101

Manufacturing - Building B
Receiving Dock 1
123 Campus Drive
Seattle, WA 98101
```

### Project-Based Locations

Temporary project sites can be tracked as locations:

```
Project Alpha - Construction Site
Trailer Office, Gate 2
1000 Build Road
Phoenix, AZ 85001
```

Once the project is complete, the location can be archived while preserving order history.

## Reporting by Location

You can:

* Filter orders by ship-to location
* Generate spending reports by facility
* Track delivery performance by location
* Analyze procurement patterns across sites

## Troubleshooting

### Locations Not Syncing

If locations from your integration aren't appearing:

1. Verify the integration is active and connected
2. Check that locations are properly configured in the external system
3. Ensure the integration has permission to sync location data
4. Contact Silkline support if locations still don't sync

### Wrong Address on Orders

If an order has an incorrect ship-to address:

1. **For future orders:** Edit the location in settings, or in your external system (NetSuite/ION) for synced locations
2. **For existing orders:** Edit the order and select the correct location
3. The address will update to match the selected location

### Can't Find Expected Location

If a location you expect doesn't appear in the dropdown:

* Verify it exists in **Organization Settings** → **Locations** or in your external system
* Check whether it is archived
* Ensure the integration has synced recently
* Refresh the page to load latest locations
