> For the complete documentation index, see [llms.txt](https://doc.loadmaster.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.loadmaster.biz/4-ui-and-terminologies/4.3-cargo/4.3.3-attributes-of-the-cargoes/4.3.3.7-stacking-orders.md).

# 4.3.3.7 Stacking Orders

When the loading demands involve light and heavy collocation, or heavy/big cargoes are not allowed on light/small cargoes, the stacking orders can be set according to the “gross weight” or “density” or “size” of the cargo. The value of the stacking orders indicates the loading capacity of the cargo. Cargoes with large stacking orders will be placed under cargoes with small stacking orders.

The stacking orders is a relative value. The larger the value, the stronger the loading capacity, and it will be placed lower. The default stacking orders is 10.

For example: Cargo C cannot be pressed, it must be placed on top; Cargo A must be at the bottom. The "stacking orders " of cargo A, B, C can be set to 11, 8, 9.

![](/files/-MDnkAWWbZ-kgh6-T4mU)

The result is:

![](/files/-MDnkCl1Kt6ygJqrok49)


---

# 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://doc.loadmaster.biz/4-ui-and-terminologies/4.3-cargo/4.3.3-attributes-of-the-cargoes/4.3.3.7-stacking-orders.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.