> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/data-model/shipping/shipping-carriers.md).

# Shipping carriers

<figure><img src="/files/A8wuesFyPnl3jYsOPMCo" alt=""><figcaption></figcaption></figure>

{% hint style="info" icon="lightbulb" %}
Multiple carriers can serve the same market. This enables you to always pick the best rate for each shipment.
{% endhint %}

## What is a shipping carrier?

[Shipping carriers](/core-api-reference/carrier_accounts.md) move parcels from a stock location to the customer's address. You can get shipping rate options for each shipment and select the most suitable one. Shipping labels and tracking numbers can then be assigned to orders before shipment.

You can connect more than one carrier to the same market to get more rate options. Supported carriers include USPS, DHL, UPS, DPD, FedEx, Amazon Services, Asendia, Aramex, and others.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.commercelayer.io/data-model/shipping/shipping-carriers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.