> 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.5-loading-rules/4.5.6-calculate-max-stack.md).

# 4.5.6 Methods for Calculate Max Stack

Each cargo has a corresponding max stack value under each load orientation.

1\) \[Calculate the max stack for each cargo type] means that the number of staking layers for a cargo type cannot exceed its max stack value, and there is no limit between different types of cargoes.

3\)\[Cargoes with the same stacking code is used as the same type to calculate the max stack] means that LoadMaster calculates the total number of layers when different cargoes are stacked. Cargoes with the same stack code are regarded as the same kind of cargoes and the stacking layers are accumulated. For details, see “stack code”.

For example: when a variety of different sizes of goods are loaded, it is required that all goods are placed in no more than 5 layers. Set all goods with the same \[stack code], and set the “max stack” for each cargo to “5”, and then select \[Cargoes with the same stacking code is used as the same type to calculate the max stack].


---

# 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.5-loading-rules/4.5.6-calculate-max-stack.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.