> 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/tutorials/oms/shipping-management.md).

# Shipping Management

This tutorial provides guidance on adding and editing shipping details within OMS. Shipping management is crucial for efficient order fulfillment.

## <mark style="color:red;">Step 1: Adding a New Shipping​</mark> <a href="#step-1-adding-a-new-shipping" id="step-1-adding-a-new-shipping"></a>

* From the OMS screens, navigate to the **Settings** tab in the OMS menu.
* Select **Shipping Management** on the next page.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FxgoKacogyW86btwDX42W%2Fimage.png?alt=media&amp;token=e94fc2c1-54ea-42e5-977c-122ef001c8e8" alt=""><figcaption></figcaption></figure>
* Click the **+New Shipping** button.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2Fa3btKe2gTG4OlWvxKzTw%2Fimage.png?alt=media&amp;token=edb5e287-c0ba-40cd-836c-7ce89f41f310" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">Step 2: Editing an Existing Shipping​</mark> <a href="#step-2-editing-an-existing-shipping" id="step-2-editing-an-existing-shipping"></a>

* To edit an existing shipping record from the OMS screens, select the **Settings** tab under the OMS menu.
* Choose **Shipping Management** on the following page.
* Select the shipping name you wish to edit from the list, and proceed to the shipping detail.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F5CczlHrVjeX13icfmxPD%2Fimage.png?alt=media&amp;token=e171d5d8-367e-45e2-8297-edc4383fe62b" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">Step 3: Completing Shipping Details​</mark> <a href="#step-3-completing-shipping-details" id="step-3-completing-shipping-details"></a>

* To add or edit a shipping, fill in the following fields:
  * **Shipping Name**: Choose any name you prefer for the shipping.
  * **ERP Code**: Ensure this code matches the ERP code of the shipping company in Omnitron.
  * Set the **Status** to active if you intend to use this shipping company.<br>

    <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FIlGGrXk9G5Wdn7QfvTUS%2Fimage.png?alt=media&amp;token=2834504a-1c27-4cde-8c1b-4da7c0884a29" alt="" width="375"><figcaption></figcaption></figure>

## <mark style="color:red;">Step 4: Cargo Management Preferences​</mark> <a href="#step-4-cargo-management-preferences" id="step-4-cargo-management-preferences"></a>

If desired, select the checkbox for **"I want my cargo to be managed by OMS."** This option allows you to:

* Create a packaging order for shipment.
* Query shipment information.
* Generate label information for each package.

If desired, customize the **Demo Client** field for non-integrated shipping companies or to exclude specific processes such as writing to shipment, querying, and label generation. Additional customizations can be applied in the **Klass** field.

## <mark style="color:red;">Step 5: Shipping Company Configuration​</mark> <a href="#step-5-shipping-company-configuration" id="step-5-shipping-company-configuration"></a>

* Choose the appropriate **Shipping Company** from the list defined within Omnitron. This selection may dynamically display additional fields based on your choice. See more on the [Invoice Code on the Cargo Label](/technical-guides/oms/invoice-code-on-the-cargo-label.md) guide.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FFuWyW889mHuuVq9sfLzl%2Fimage.png?alt=media&amp;token=24dcd4a3-c186-42a7-a43e-8eb1930f47bc" alt="" width="375"><figcaption></figcaption></figure>

## <mark style="color:red;">Step 6: Cargo Conditions (Optional)​</mark> <a href="#step-6-cargo-conditions-optional" id="step-6-cargo-conditions-optional"></a>

* Set **Cargo Conditions** for this shipping company by filling in the following fields:
  * Condition Klass
  * Condition Type
  * Channels
* Please note that some shipping companies may require extra information, such as Username, Password, Customer Code, Query Shipment URL, Create Shipment URL, Tracking URL, and Authentication URL.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FB1vwMlp8msvhFugxqiFy%2Fimage.png?alt=media&amp;token=58aa8d31-9497-49b4-bc1e-2e6e68b0fba4" alt="" width="375"><figcaption></figcaption></figure>


---

# 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/tutorials/oms/shipping-management.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.
