> 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/shipping-carriers.md).

# Shipping carriers

This topic describes how to configure the shipping carriers used by the store.

Use shipping carriers to identify carriers used by the store.

1. Click **Setup**.
2. Expand **Inventory/Purchasing**.
3. Click **Shipping Carriers**.
4. Click **New**.
5. Enter the carrier's **Name**.
6. Enter the URLs for their:

* Main website
* Shipping portal
* Tracking portal

7. (Optional) On the **Service** tab:
   1. Click **Add** to add a service or click **Properties** to edit an existing service.
   2. Under **Schedule of charges**, select **Weight** to identify services charges by package weight, or select **Total** to identify service charges by other shipment characteristics.
   3. In the table, enter the **Value** increments and the corresponding **Charge**. For example, if you selected **Weight**, you would enter weight increments (kgs or lbs) in the **Value** column such as 5, 10, 15, and 20. You would then enter the corresponding shipping charges for those weights in the **Charge** column such as $10.00, $20.00, $30.00, or $40.00.
   4. (Optional) Enable the **Interpolated schedule** option if you want RMH to calculate (interpolate) the charge if the value falls between the specified increments. For example, if you enter weight increments in the **Value** column for 15 and 20, and the package weight (17.5) falls between those two increments, RMH can calculate the charge based on the charges for the 15 and 20 weight increments.
8. (Central Manager only) On the **Store Groups** tab, select the store groups that use this shipping carrier.
9. 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/shipping-carriers.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.