> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-shipping-methods.md).

# Shipping methods

This topic describes how to configure the shipping methods the store uses.

Use shipping methods to identify carriers for incoming freight. Shipping methods are not linked to freight rate schedules.

1. Click **Setup**.
2. Expand **Inventory/Purchasing**.
3. Click **Shipping Methods**.
4. Click **New**.
5. In the **Code** field, enter a unique code that identifies the shipping method.
6. In the **Name** field, enter a name for the shipping method.

{% hint style="success" %}
If you enter your account number in the Name field it displays on the purchase order or transfer. This can help clarify the account to charge for shipments.
{% endhint %}

7. (Central Manager only) On the **Store Groups** tab, select the store groups that use this shipping method.
8. Click **Save And Close**.


---

# 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.rmhpos.com/store-manager/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-shipping-methods.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.