> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/technical-guides/oms/inventory-locations-and-engine/properties-and-domain-relation.md).

# Properties & Domain Relation

## <mark style="color:red;">Properties</mark> <a href="#properties" id="properties"></a>

Inventory locations can be described as the full list of your stores/ warehouses and their specific properties. With Akinon OMS, Inventory Locations can be used as selection criteria in Scenario creation for Package & Inventory Management.

Users are able to;

* Give **Contact and Address Information Details** about the Inventory Location.
* Decide your Inventory Location whether can it be used as
  * **Store or Warehouse**,
  * **Packaging Center**,
  * **Delivery Location,** for the customers who would rather take their *items* from the store,
  * **Transfer Location,** for being used as a transfer center for packages that are packed from different locations,
  * **Return Location,** for being used as the returned goods delivery location.
* Assign your Inventory Location as
  * **Shipper Location**,
  * **Fast Delivery Available Location**,
* Set **Priority**, **Targeted Packaging and Exit Times** to your Inventory Location in order to be used for scenario criteria.

To add an Inventory Location, follow the steps below.

1. Sign in to Omnitron via <https://{yourcompany}.omnitron.akinon.net/signin>.
2. Go to **Akinon OMS > Locations**.
3. Click on the button.
4. Assign the properties that are explained below.
5. Click on the <img src="https://2911598027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlQinVPnOffBiOp126ldR%2Fuploads%2Fgit-blob-39e0d38846590504e1592efb8e929f90dbfe1313%2Fimage.png?alt=media" alt="" data-size="line"> button.

Users can also Update/Delete their Inventory Locations via **Akinon OMS > Locations > Location Detail**.

## <mark style="color:red;">Domain Relations​</mark> <a href="#domain-relations" id="domain-relations"></a>

Inventory Locations can be used as the center of Packaging Orders and/or Transfer Orders, based on Packaging and Transfer Scenarios with respect to their properties.

* **Store/ Warehouse Selection**, **Packaging Center**, **Targeted Packaging and Exit Times**, **Contact and Address Information Details**, **Priority** properties are related with the Packaging Orders.
* **Delivery Location**, **Transfer Location**, **Return Location** **Priority**, **Shipper Location**, **Fast Delivery Available Location**, **Contact and Address Information Details** properties are related with the Transfer Orders.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akinon.com/technical-guides/oms/inventory-locations-and-engine/properties-and-domain-relation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
