Unbatch: Intermediate
The Unbatch node’s Intermediate tab answers three questions: how far into a nested batch to unpack, what to do with the items that come out of nested batches, and what to do with the container once it is empty.
Unbatch Depth
Section titled “Unbatch Depth”A batch can hold other batches: cases on a pallet, cartons in a case. Unbatch Depth decides how far down this node goes.
| Depth | Releases |
|---|---|
| One Level | The immediate members, and nothing more. A pallet gives up its cases, and each case stays a case (the default) |
| Recursive | Everything, all the way down to individual entities |
| To Level N | A set number of levels, then stops |
One Level is the right choice when the next step handles the level below, for example a depalletizer feeding a case opener. Recursive suits a single teardown point where only the individual pieces matter downstream.
Max Depth Level
Section titled “Max Depth Level”Shown for To Level N. How many levels to peel before stopping. A depth of 2 on a pallet of cases of cartons releases the cartons and leaves them intact.
Nested Item Handling
Section titled “Nested Item Handling”What to do with items from nested batches: Keep leaves them as they are, and Destroy removes them. Destroy is the default.
Batch Disposition
Section titled “Batch Disposition”What happens to the container entity once its members have been released:
- Destroy removes it from the model. This is the default and the usual choice, since a box that has been emptied is normally not part of the process any more.
- Keep leaves the container in the model as an ordinary entity with no members. Choose this when the container itself matters: a returnable tote or pallet that has to travel back for reuse, so you can route it to a return loop.
The unbatch node’s other tabs
Section titled “The unbatch node’s other tabs”- Unbatch: the General tab, what comes out and in what order
- Unbatch: Advanced: splitting batch values across the members, and the unbatch resource