> 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.13-group.md).

# 4.3.3.13 Group

The group is used to define that certain cargoes cannot be mixed in one container, or that certain cargoes are not divided into multiple containers as far as possible. The name of the group can be Chinese characters, numbers, letters, and combinations of them.

(1) Restrict cargoes cannot be mixed. For example: cargoes A, B and cargoes C, D cannot be mixed.

Set the group name of A and B to "1", set the group name of C and D to 2, and uncheck "Allow different groups of cargoes to be mixed in one container" on the \[Loading Rules] page, i.e. not allow different groups of cargoes to be mixed.

![](/files/-MDrXogaTtNxJsjtguce)

![](/files/-MDrXulmevwCNchTDkPS)

The result is: Cargo A, B and Cargo C, D are not mixed.

![](/files/-MDrXxyp7snXJh2XPd-J)

(2) Restrict the cargoes not to be loaded into multiple containers as much as possible. For example: cargoes A and B belong to different orders, and we require the cargoes in the same order to be placed on the same pallet as much as possible.

Set the “group name” of cargo A to “1” and cargo B to “2”, and check \[Minimize the number of containers which load cargoes from the same group] on the \[Loading Rules] page.

![](/files/-MDrY-qcwNTtpWfuHpL6)

The result is:

![](/files/-MDrY1spEbvMdc0XfIwr)

If you do not define this rule, the result is:

![](/files/-MDrY4IPyoyOXpcg9zmu)


---

# 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.13-group.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.