# Shipping categories

Shipping categories determine which [shipping methods](/core-api-reference/shipping_methods.md) are available for the associated [SKUs](/core-api-reference/skus.md). Unless the selected inventory model strategy is [no split](https://docs.commercelayer.io/developers/v/how-tos/inventory-model-strategies/no-split), if an order contains line items belonging to more than one shipping category it is split into more [shipments](/core-api-reference/shipments.md).

{% hint style="info" %}
In case the inventory model strategy is left as default — **no split** — just a single shipment is always created, no matter if the order contains SKUs associated with different shipping categories. In this case, the number of available shipping methods will increase accordingly since they won't be filtered by shipping category.
{% endhint %}

You can optionally define a custom alphanumeric (case-sensitive) `code` for your shipping categories, provided that it's unique across the environment (it can contain underscore and hyphens, spaces are not allowed, the maximum length is **25** characters).

<details>

<summary>Data model</summary>

Check the related [ER diagram](/data-model/shipping/shipments-and-shipping-categories.md) and explore the flowchart that illustrates how the shipping category resource relates to the other API entities.

</details>

<details>

<summary>How-to</summary>

Check the related [guide](https://docs.commercelayer.io/developers/v/how-tos/inventory-model-strategies) to learn more about the available inventory model strategies, how they work, and how shipping categories are involved in the process.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.commercelayer.io/core-api-reference/shipping_categories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.