CubeMaster vs Cargo-Planner

The user can define a loading space by its internal length, width and height, and the planner keeps all cargo inside it.

Counts when: Documentation shows a loading space with user-entered or preset internal length, width and height that the planner packs within.

“These values represent the inside (loadable) dimensions of the vehicle.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

“length | integer | Length in UOM units.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

All editions (Online, API V2, Windows, SDK). Container types Carton, Pallet, SeaVan, Truck, AirPallet; preset databases plus user-entered sizes.

The user can mark a fixed part of the loading space (such as a reefer unit, wheel arch or corner casting) as unusable, and the planner keeps cargo out of it.

Counts when: A documented input for at least one obstruction with a position and size inside the space, which the planner does not load into.

“Unusable Spaces - Corner castings and unusable spaces at the sea containers and trucks.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/extensive-vehicle-and-cargo-types.html

“Corner Castings : This is the structure attached onto ceil of the sea container for the crane lifting. Its 3 dimension should be defined with container together when a load data is defined before running the load.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/terminology.html

• Only in some editions, plans, methods or equipment types
• Follows from documented behaviour rather than stated outright

Windows edition only. Fixed kind: corner castings with a user-given 3D size, position implied (ceiling corners). The SDK lists a SetContainerCornerCastSize function with no page. Nothing equivalent in Online help or API V2. Whether cargo may be stacked on top is not stated.

The user can block any number of box-shaped regions, each at a freely chosen position and size, inside the loading space.

Counts when: Documentation shows more than one blocked region per space, each with its own free position and size.

Windows mentions 'unusable spaces' in the plural next to corner castings, with no input described for free regions. API V2 zones have position and size, but they are not documented as blocked regions.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'unusable', 'obstruct', 'corner cast', 'wheel', 'blocked', 'zone' (zones are sub-volumes, not blocked regions), SDK function list.

For a plan, the user can keep a set gap below the ceiling (or cap the load height below the internal height) without redefining the equipment.

Counts when: A documented setting, per plan or per equipment, that lowers the usable height or enforces a ceiling clearance, separate from the internal height.

“Use the Max Height to limit the maximum height of the cargo regardless of the inside dimensions of the vehicle. This comes in handy when you're evaluating refrigerated or frozen loads that need room for air circulation.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

“maxHeight | integer | Maximum cargo height (e.g., 111).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point

Per equipment (truck, sea container; pallets have their own Max Height including deck). Online and API V2. Max Volume % is a separate volume cap.

The user can model a loading space whose floor or ceiling height changes along its length (drop-deck, step-deck, gooseneck, split-level), and the planner respects the steps.

Counts when: A documented input for at least one step in floor or ceiling height at a set distance along the space.

“Rear Distance The distance from the rear wall of the trailer to the drop off point at floor level. Rear Depth The drop off depth in the rear of the vehicle at floor level.”

https://cubemaster.net/Help/webhelp/pages/drop-deck1.html

“vehicleDropDeckRearSize | null/object | Rear drop deck size for trucks: {length, width, height}.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Online and API V2 (vehicleDropDeckFrontSize, vehicleDropDeckRearSize). Trucks and sea containers. Windows lists drop-off (goose neck) under Enterprise container types.

The user can model a loading space whose cross-section is not rectangular, such as a ULD with a cut-back side or a rail wagon with a curved roof, and the planner keeps cargo inside that contour.

Counts when: A documented input that describes the contour (points, slope parameters or steps across the width or height), which the planner respects.

“A custom shape can be defined at the ULD Shape window by defining six points”

https://cubemaster.net/Download/CubeMaster_Online_Overview.pdf (p. 17)

“The size and shape of new air container and pallet is defined by user with air container shape editor.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/enterprise-edition.html

• Evidence is documentation five or more years old
• Only in some editions, plans, methods or equipment types

ULDs only: a six-point contour. Windows Enterprise edition and the 2018 Online overview. The API V2 EmptyContainer schema has no shape field, and the current Online ULD help pages do not mention shapes.

The user can model a loading space whose cross-section is not rectangular and whose floor or ceiling height also changes along its length, both in the same unit, and the planner respects both. †

Counts when: Documentation shows a single space definition that combines a non-rectangular cross-section with a lengthwise height change, and the planner keeps cargo inside both.

“Allows defining custom non-standard container shapes, irregular vehicle beds, and specialized racks.”

https://cubemaster.net/Subscription/features.html

The drop deck (trucks, sea containers) and the ULD contour (air) are separate equipment types; no documented single unit combines both. The features page claims custom non-standard shapes without describing them.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'contour', 'shape', 'six points', 'drop deck' in combination with ULD, 'irregular', 'custom equipment'.

The planner treats a sloped contour face as a slope, so cargo can be placed right up to the sloped wall rather than stopping at a rectangular step.

Counts when: Documentation shows the contour defined by an angle, chamfer or interpolated points, and cargo placed against it.

“A custom shape can be defined at the ULD Shape window by defining six points”

https://cubemaster.net/Download/CubeMaster_Online_Overview.pdf (p. 17)

The six-point ULD contour could describe sloped faces, but no source says whether cargo is placed against a slope or a stepped approximation.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'slope', 'angle', 'chamfer', 'contour', 'six points', 'shape editor'.

The user can model one unit made of several separately packed sub-spaces, such as holds, sections, bays, a second deck, shelves or the two parts of a road train, each with its own dimensions.

Counts when: A documented input for at least two internal sub-spaces of one unit, each with its own geometry, that the planner packs as parts of that unit.

“zones | null/array | Zoning information (null if not used). Array of zone objects with position, size, maxWeight.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“"maxVolUtilization": { "type": "number", "format": "double" }, "sequence": { "type": "integer", "format": "int32" }, "fillDirection": { "$ref": "#/components/schemas/FillDirectionEnum" }”

https://api.cubemaster.net/swagger/v2/swagger.json

Not counted: the product reports this, but the documentation does not show the planner keeps to it; the evidence is a field name with no description of what it does.

• Only in some editions, plans, methods or equipment types

API V2 only (container zones as sub-volumes with their own position and size; swagger adds per-zone sequence and fill direction). The SDK lists an AddSubContainer function with no page. An aircraft as a set of ULDs (2018 PDF) is several units, not sub-spaces.

The user can set a door opening smaller than the internal cross-section, and the planner does not load items that cannot pass through it.

Counts when: A documented door width and height input, documented as limiting what is loaded.

“Core container properties: Description, internal Length, Width, Height, Max Weight, Door Opening dimensions, and Tare Weight.”

https://cubemaster.net/Help/webhelp/pages/container-edit-popup.html

“Too Large: The item's dimensions exceed the container's interior dimensions or door size.”

https://cubemaster.net/Help/webhelp/pages/report-exceptions.html

• Only in some editions, plans, methods or equipment types

CubeMaster Online UI only; API V2 has no door field. The engine effect is shown by the Exceptions report citing door size as a reason an item was not loaded.

The user can set which face of the space is the loading face (rear, side or top), and the planner builds the load, and any unloading order, from that face.

Counts when: A documented per-space loading or access face that changes how the load is built.

Loading direction is fixed as front (inside) to rear (door); the truck overview mentions side doors only descriptively. No per-space loading face.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'side door', 'door', 'loading face', 'top loading', 'access', 'fillDirection', 'near door'.

On open-top, flat-rack or flatbed equipment, the planner can let cargo rise above the walls or extend beyond the deck edges, up to set limits.

Counts when: A documented open-equipment behaviour or envelope setting that allows cargo beyond the wall height or deck length/width, with a stated limit, used by the planner when placing.

“These refer to the maximum dimensions allowed for the load of truck against the Empty Width and Empty Height, respectively. The Max Width and Height are available if the truck style is a Flatbed. Max Height is available if the truck style is an Open Top.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

“Max Load Height & Width | Over-dimensional limits. | Used for Flatbed trailers and Open Top containers where cargo exceeds standard walls.”

https://cubemaster.net/Subscription/features.html

• The vendor's own sources disagree on this point

Online and API V2 (vehicleType Dry | OpenTop | FlatRack; maxWidth/maxHeight). Limits are set per equipment.

When the cargo does not fit one unit, the planner places the rest in further units of an offered type and reports how many are needed.

Counts when: Documentation shows the planner adding units automatically until the list is loaded (or an available quantity runs out), without the user adding each unit.

“MixLoad | Finds optimal number of containers to fill all cargoes when each cargo has different sizes and quantities to be shipped.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“If cargo remains after all available containers have been filled, CubeMaster selects the next available empty containers based on priority and continues the process until all cargo is placed or there are no more empty containers available.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

All editions. Online plan quotas cap containers per shipment (5/10/20 by plan, per the first audit pass pricing note).

From several offered equipment types, the planner decides which types to use and how many of each, in one run.

Counts when: Documentation shows an automatic choice among two or more equipment types within one plan.

“If isMultiContainerTypesEnabled is set to false, the algorithm will use only the first container type specified in the request.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“You can add multiple container types to a single load — CubeMaster will select the most optimal combination.”

https://cubemaster.net/Subscription/faq.html

Online, API V2, Windows ('Multiple Containers Selection by Algorithm Choice'). How types are combined depends on the Goal of Mix Load.

The user can cap how many units of each type are available, and the planner never uses more, leaving any remainder unloaded.

Counts when: A documented available-quantity input per equipment type that the planner honours.

“This value is only used when Rules.bestFitContainersSelectionType is BestfitDisabled.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“BestfitDisabled | Quantities and Sequences are limited | Fills empty containers sequentially according to their Priority/Sequence. This is the only mode that strictly complies with the specified 'Qty' limits and 'Seq' ordering of the containers.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Honoured only under the goal 'Quantities and Sequences are limited' (BestfitDisabled); all four best-fit goals ignore Qty and Seq.

The user can rank equipment so that a preferred type (or a given set of units) is filled first, and other types are used only when needed.

Counts when: A documented priority, preference or fill-order setting on equipment, or a documented fixed-then-automatic split.

“Lower numbers = Higher priority.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“The order in which containers are filled is determined by their priority value, with lower values being filled first.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

Per container priority/Seq; used only under 'Quantities and Sequences are limited'.

Given several candidate equipment types, the planner picks the smallest type that holds a load: the whole shipment, or the last, partly filled unit.

Counts when: Documentation shows the planner selecting (not the user comparing) the smallest sufficient type for a whole shipment or swapping the last unit for a smaller type.

“This option evaluates whether a less-filled container can be replaced with a smaller container without compromising the load.”

https://cubemaster.net/Help/webhelp/pages/balancing.html

“isBalanceReplacedWithSmallerSizes | boolean | If true, replaces with smaller sizes for balance.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Balancing can apply to all containers or only the last one.

Each equipment type can be given a cost, and the planner chooses the combination of units with the lowest total cost.

Counts when: A documented per-equipment cost input and a documented cost-minimising selection.

“CubeMaster's optimizer will determine the best combination of containers to minimize cost or maximize utilization based on your cargo and rules.”

https://cubemaster.net/Help/webhelp/pages/faq.html

“Provides instant financial visibility to select the most economical vehicle combination.”

https://cubemaster.net/Subscription/features.html

• The vendor's own sources disagree on this point

A per-container price input exists (Empty Price / price) and costs are reported, but none of the five documented Goal of Mix Load strategies minimises cost.

The user can cap the fill of a unit at a set percentage of its volume or weight.

Counts when: A documented maximum fill-percentage input per unit or per plan that the planner respects.

“If set to 80, the algorithm will not allow the total volume of the placed cargo to exceed 80% of the container's total volume.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“This refers to the maximum volume allowed for the load of truck which is presented by the percent of the Empty Volume of truck.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

All container types; Online, API V2, Windows, SDK (MaxCE). The best-fit selection thresholds (bestFitContainersSelectionMax*UtilThreshold) are separate and undescribed.

The user can set a minimum fill for a unit, below which the unit is not used and its cargo is moved or left unloaded.

Counts when: A documented minimum-fill input (percentage, weight, volume or unit count) that the planner acts on.

“Containers with volume usage below a predetermined threshold can be canceled if the cargo has not yet been loaded, to avoid transporting partially filled containers.”

https://cubemaster.net/Help/webhelp/pages/balancing.html

“A container less than a certain condition is cancelled and all the cargoes in the container are kept unloaded.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/balancing.html

Balancing rule (isBalancePoorUtlizationUnloaded); cargo of a cancelled container is left unloaded. Online, API V2, Windows, SDK.

The user can restrict a specific item (or group) to certain equipment types, or exclude it from others, including which pallet type it is built on.

Counts when: A documented per-item or per-group rule, hard or stated as such, that limits which equipment types it may be loaded into.

“Allows you to select from various types of pallets and slipsheets already defined in the Pallet database.”

https://cubemaster.net/Help/webhelp/pages/palletizing.html

“A different pallet is assigned to a group for the palletizing rules.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/101070-june-2022.html

Passes on the per-cargo pallet choice. The preferred-container lists (emptyContainersFavorite, isGroupsToPrefContainers, swagger CargoGroup *NameFavorite) are not documented as binding.

The user can assign a specific item (or group) to one particular unit of the plan.

Counts when: A documented input that ties an item or group to an individual unit (for example the n-th container, or a named unit), which the planner respects.

Preferred containers refer to container types, not individual units. Moving cargo between loaded containers is manual (Windows Edit Containers / Magic), a workaround.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'favorite', 'preferred container', 'assign', 'container sequence', 'isGroupsToPrefContainers', 'AddPreloadContainer'.

The planner can determine the dimensions of a new container, carton or pallet load within user-set minimum and maximum ranges.

Counts when: Documentation shows the planner choosing the dimensions of the space itself within stated ranges.

“New Size Load - Finds a new size of Trucks/Sea Containers/Pallets/Cartons/ULDs from an order of mixed items. Once the min and max sizes ranges are given to CubeMaster, a list of new sizes are found from the calculation which load all the items in the different ways.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/buttons-group.html

Windows edition only; not among the Online or API V2 load types.

The user can enter several box-shaped item types in one plan, each with length, width, height, weight and quantity.

Counts when: Documentation shows several cuboid item types with dimensions, weight and quantity in one calculation.

“Each cargo item is treated as a rectangular shape with specific physical properties and loading constraints.”

https://cubemaster.net/Help/webhelp/pages/cargo.html

“qty | integer | Quantity of the cargo to ship. For pre-pack unitloads, represents number of unitloads. Required.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

All editions. Online plan quotas: 300/600/900 cargoes per shipment by plan (the first audit pass pricing note). API validation rejects a cargo whose width exceeds its length (error -2).

The user can enter cylindrical items (drums, rolls, pipes) by diameter, and the planner packs them as cylinders rather than as bounding boxes.

Counts when: A documented cylinder item type with a diameter input.

“diameter | integer | Diameter for cylindrical cargo (rolls). Set to 0 for non-cylindrical.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Roll | Cylindrical cargo.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Online, API V2, Windows (cargo style Roll; Reel added in 10.10.6.3). Not in the SDK. How rolls are packed is not described.

The planner can nest cylinders in offset rows (hexagonal or pyramid packing), so that each sits in the gap between two cylinders below or beside it.

Counts when: Documentation of a nesting, staggered or honeycomb arrangement for cylindrical items.

FormPyramidStack is a layer contour for boxes, not cylinder nesting. StyleEnum NestedCube and Reel appear only in the swagger/release notes with no description.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'nest', 'honeycomb', 'stagger', 'pyramid', 'roll', 'reel', 'cylinder', 'NestedCube'.

Two items of a non-rectangular shape can interlock: the planner uses the shape of both the item being placed and the item it is placed against (for example L-shapes nested into each other, or tapered items flipped against each other). †

Counts when: Documentation shows the planner fitting a shaped item against another shaped item using both shapes, not only the bounding box of the item being placed.

The swagger AlgorithmTypeEnum value 'Interlocked' has no description; pallet 'interlock' patterns concern box layers.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'interlock' (only pallet patterns), 'L-shape', 'shape', 'nest', 'faceOpen', 'NestedCube'.

Other cargo can be placed into the free space inside or under an item (a cavity, a frame, the space under an overhang or an L-shape's seat), with the placed cargo treated as its bounding box. †

Counts when: Documentation shows cargo of a different item placed into the free space of another item.

Cargo faceOpen (NeitherSide | LengthSide | WidthSide) has no documented purpose. Box-in-box carton loads pack items into cartons used as containers, not into another cargo's free space.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'cavity', 'inside', 'open face', 'faceOpen', 'hollow', 'frame', 'under'.

The user can enter items of arbitrary 3D shape (for example from a CAD or mesh model), and the planner packs the actual shape.

Counts when: Documentation of an arbitrary-geometry item input that the planner packs by its real shape.

All documented cargo is rectangular or roll. 'Custom non-standard container shapes' on the features page concerns equipment.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'CAD', 'mesh', 'irregular', 'shape', 'complex'.

The user can plan bulk or shapeless cargo given by volume and weight rather than by dimensions.

Counts when: A documented bulk or amorphous cargo input with a stated way of occupying space.

The 'Loose Item' feature (2018 PDF) breaks pallets into loose cartons; it is not bulk cargo.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'bulk', 'loose', 'amorphous', 'liquid', 'volume only'.

The planner can compress a soft item (pillows, duvets) by up to a set percentage in a dimension so that it fits.

Counts when: A documented compression allowance per item, with a limit, applied by the planner.

“Negative bulge: If a container is compressed when it is packed, the result is a negative bulge.”

https://cubemaster.net/Help/webhelp/pages/advanced.html

“Currently CubeMaster takes the positive bulge.”

https://cubemaster.net/Help/webhelp/pages/advanced.html

Bulge allowance exists per cargo (bulgeSize), but only expansion is applied; compression is not. Online and Windows help both state this.

An order quantity can be given in inner units, and the planner breaks it down into the item's available pack levels or bundles (each, case, layer, pallet, bundle).

Counts when: Documentation shows several packaging configurations for one item and the planner choosing the breakdown.

“Number of pieces inside each cargo unit (e.g., smaller boxes in a shipping box). Used to calculate total pieces as qty * pieceInside.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

pieceInside is report arithmetic. orderPieces ('Number of pieces ordered') has no described breakdown. Case-to-pallet conversion by the palletizing rule uses one pallet configuration per cargo and is scored under pallet rows.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'pieceInside', 'orderPieces', 'SubPackQty', 'pack level', 'case', 'bundle', 'inner'.

The user can keep an item upright (a set face down), so that it is never tipped onto a side or an end.

Counts when: A documented per-item setting that keeps the item's vertical axis fixed.

“The #1 and #2 orientations are termed 'Basic orientations' as they position the cargo's height vertically to the container's bottom, aligning with the manufacturing position.”

https://cubemaster.net/Help/webhelp/pages/orientations.html

“For example, "Orientations12" allows the cargo to sit upright lengthwise (#1) and turned horizontally (#2).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Per cargo orientationsAllowed (OrientationsBasic). All editions.

The user can stop an item turning about the vertical axis, so that it keeps a set direction relative to the equipment's length (for example forklift entry from the door).

Counts when: A documented per-item setting that fixes the horizontal orientation, or forces lengthwise or widthwise alignment.

“Values can combine numbers 1 through 6, representing all possible orthogonal rotations (e.g., "Orientations123456" opens all 6 permutations).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Orientation #1 only: The pallet is placed with its length along the vehicle's length.”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

Per cargo. All editions.

When the user allows it, the planner can place an item on any of its six faces.

Counts when: Documentation shows that an item may be laid on its side and stood on its end by the planner.

“Since the cargo has a rectangular shape, it can be stacked in six different orientations within a load.”

https://cubemaster.net/Help/webhelp/pages/orientations.html

“Values can combine numbers 1 through 6, representing all possible orthogonal rotations (e.g., "Orientations123456" opens all 6 permutations).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

OrientationsAll. All editions. Built pallet loads cannot be turned onto #3-#6 in the Magic editor.

The user can let an item lie on its side while forbidding it to stand on its end (that is, choose which of its dimensions may be vertical).

Counts when: A documented per-item setting that allows some but not all tipped orientations.

“Any combination of integers 1 through 6 appended to Orientations (e.g. Orientations145 or Orientations123456) is valid.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“L × H × W Orientation #3 Turning”

https://cubemaster.net/Help/webhelp/pages/orientations.html

Per cargo.

The user can allow any subset of an item's six orientations.

Counts when: Documentation shows each of the six orientations can be allowed or forbidden independently (for example a six-bit mask or six checkboxes).

“Any combination of integers 1 through 6 appended to Orientations (e.g. Orientations145 or Orientations123456) is valid.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“A number representing the loading orientations permitted.”

https://cubemaster.net/Help/webhelp/pages/uploading-cargoes-from-excel-file.html

• The vendor's own sources disagree on this point

Each of the six orientations (#1-#6, both directions per axis listed separately) can be allowed on its own.

The user can mark a preferred orientation that the planner uses where possible, while other orientations stay allowed.

Counts when: A documented soft preference for one orientation.

“Sets or returns the primary orientation among the permitted ones.”

http://www.logensolutions.com/VMS/TechSupport/SDK_Help/pages/primaryorientationindex-property.html

“Sets or returns the orientation to allow placing the SKU into the last space at near top of the door.”

http://www.logensolutions.com/VMS/TechSupport/SDK_Help/pages/secondaryorientationindexatlastspace-property.html

Not counted: the evidence is a field name with no description of what it does.

• Follows from documented behaviour rather than stated outright
• Only in some editions, plans, methods or equipment types

SDK and Windows documented; API V2 has orientationPriority {used, orientationNumberPrimary, orientationNumberNearDoor} in the swagger only (guide types it as a string with no values).

The user can allow an orientation only when the item is not on the floor (or only when it is).

Counts when: A documented rule that ties an allowed orientation to floor or non-floor placement.

“Boolean flag determining if the cargo can be placed in orientations 3 (side), 4 (side turned), 5 (end), or 6 (end turned) directly on the container floor or pallet deck.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“This forces the engine to always place the very bottom layer of refrigerators upright (1 or 2) on the floor, while permitting subsequent stacked units to be laid on their side (3 or 4).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Per cargo. Online, API V2, Windows; SDK bKeepBasicOrientationOnSimpleLoad for single loads.

The user can set stacking limits (stack count or load-bearing weight) that differ with the item's orientation.

Counts when: A documented per-orientation stack limit or load-bearing limit for an item.

“The maxLayersOnOrientation is a hard constraint. If the calculated number of layers exceeds this value, it will be excluded from the results.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“For instance, to load cargo in fewer than 3 layers on orientation #1 and 4 layers on orientation #2, set the Max Layer value for orientation #1 to 3 and orientation #2 to 4.”

https://cubemaster.net/Help/webhelp/pages/orientations.html

Per cargo. All editions (SDK LoadDir1MaxLayer-LoadDir6MaxLayer).

The planner can place items at angles other than multiples of 90 degrees (for example leaning against a wall).

Counts when: Documentation of automatic non-orthogonal placement.

The Magic editor offers only the six orthogonal directions.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'angle', 'tilt', 'lean', 'degree', 'rotate' (only 90-degree layer rotation and the six orthogonal orientations).

The user can choose whether a cylindrical item stands upright or lies down.

Counts when: A documented per-item upright/lying choice for cylinders.

• Follows from documented behaviour rather than stated outright

Rolls have a diameter, but no source says whether orientationsAllowed applies to them or how a roll can stand or lie.

Correction: Industry use cases page sets drums to 'upright only'; cargo edit popup documents per-cargo orientation.

The user can make an item non-stackable, so that nothing is placed on top of it.

Counts when: A documented per-item setting that forbids any cargo on top of the item.

“floorStackSupportsOthers | boolean | If true, this cargo supports others on top in floor stacking.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Can other Cargo be Stacked on Top? Indicate whether other cargo can be stacked on top of this item. Select "Yes" if stacking is allowed, and "No" if it is not (e.g., for a delicate item like a paper mache lampshade).”

https://cubemaster.net/Help/webhelp/pages/basic3.html

Per cargo, active only when the plan's stacking rule is FloorStack (or FloorStackAndHeavierBottomFirst). Stacking rules cover different cargoes only, so identical units also need Max Layers = 1. Also per built pallet (palletizing 'Supports Others').

The user can require an item to stand on the floor of the space.

Counts when: A documented per-item must-be-on-floor setting.

“'Bottom Only', which only allows cargo to be placed on the floor”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“Bottom Only: Any solutions are disregarded in which the cargo is not placed on the floor.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/basic.html

Per cargo floorStackType, with stacking rule FloorStack. All editions; also per built pallet.

The user can require an item to be placed on top of other items, never on the floor.

Counts when: A documented per-item must-not-be-on-floor setting.

“'No Bottom', which prohibits cargo from being placed on the floor”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“No Bottom: Any solutions are disregarded in which the cargo is placed on the floor.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/basic.html

Per cargo floorStackType, with stacking rule FloorStack.

The user can limit how many units of the same item may be stacked on each other.

Counts when: A documented per-item tier or stack-count limit.

“To restrict the stacking layers of the same cargo, use the Max Layer option within the cargo information.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

“The maximum number of layers permitted when stacking cargo in each orientation is determined by the Max Layers value.”

https://cubemaster.net/Help/webhelp/pages/orientations.html

Per cargo and per orientation. Built pallets have maxLayersOnVehicle.

The user can limit the tier an item may occupy, or the total number of tiers in a stack, whatever items are below it (for example never above the second tier).

Counts when: A documented limit on stack levels that counts different items, per item or for the whole unit.

“MaxLayersExtended A number to present whether the max layers of the cargo are extended on the other cargoes.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/importing-cargoes-form-excel-template-file.html

“maxLayersAllowedOverDifferentCargoes | boolean | If true, allows stacking over different cargoes.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point
• Follows from documented behaviour rather than stated outright

Per cargo flag. No container-wide tier cap is documented. The SDK lists SetItemCumulativeLayerLimitAt without a page.

The user can limit the height above the floor at which a specific item may be placed or to which it may be stacked.

Counts when: A documented per-item maximum placement or stacking height in length units.

“maxStackingHeight | object | Controls maximum stacking height dynamically using specific proportional rules.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“proportionalRateToSetMaxStackingHeight (number): The multiplier applied to the chosen algorithm's dimension to calculate the maximum allowable stacking height.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Not counted: the evidence is a field name with no description of what it does.

• Only in some editions, plans, methods or equipment types

API V2 only.

The user can set the maximum weight an item may carry on top of it.

Counts when: A documented per-item load-bearing (weight on top) limit that the planner enforces.

“maxSupportingWeight | integer | Maximum weight that can be safely placed on top of this cargo. This determines how many layers high the engine can safely stack other cargoes on top of this one.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“In order to activate this property, you should set True to the bUseSafeStacking of the Calculator class.”

http://www.logensolutions.com/VMS/TechSupport/SDK_Help/pages/maxweightallowedonme-property.html

Per cargo, all editions. Applies to different cargoes stacked on it. Whether the whole column or only the directly resting item counts is not stated. Also 'Max supporting weight of the pallets' in Online palletizing rules.

The load-bearing limit is evaluated as pressure (weight per area of the supporting face) rather than as a total weight per item. †

Counts when: Documentation states that the bearing limit depends on the contact area or is given per support face as a pressure.

maxSupportingWeight is a plain weight per cargo.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'pressure', 'per area', 'kg/m', 'psi', 'contact area', 'maxSupportingWeight'.

The load-bearing limit also applies within a stack of identical units.

Counts when: Documentation shows the weight-on-top limit checked when an item is stacked on units of the same item.

“This rule determines the positioning of two different cargo items in relation to one another. Note that it doesn't apply to identical cargo items. To restrict the stacking layers of the same cargo, use the Max Layer option within the cargo information.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

“This will determine the number of layers high CubeMaster can safely stack the different cargoes on this cargo.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

Like-item stacks are limited only by Max Layers.

The planner never places an item on top of a lighter, different item.

Counts when: A documented weight-ordering stacking rule.

“HeavierBottomFirst | Cargo is only placed on heavier cargoes. Cargo will never be placed on a lighter cargo.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“If minWeightDifferencePercentageForStackingTwoCargoes is set to n, the engine will only allow stacking two different cargoes if their weights differ by at least n percent.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Different cargoes only; all editions.

The user can give items a numeric strength or fragility index, and the planner never places an item on one with a weaker index.

Counts when: A documented per-item stacking index with a stated ordering rule.

“HigherStackValueBottomFirst | Cargo is only allowed to be placed on top of others with a strictly greater Stack Value.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Cargo with higher stack values are placed below cargo with lower stack values.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

• The vendor's own sources disagree on this point

All editions. One stacking rule per plan.

The user can state, for a specific pair of items, whether one may be stacked on the other.

Counts when: A documented item-to-item stacking permission list or matrix.

“The Yes/No indicate whether a cargo for the corresponding column can be placed on top of a cargo for the corresponding row.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

“"cargoBottom": { "type": "string", "nullable": true }, "cargoTop": { "type": "string", "nullable": true }, "isAllowed": { "type": "boolean" }”

https://api.cubemaster.net/swagger/v2/swagger.json

Windows (since 10.10.7.0, Excel/CSV import) and API V2 (Rules.stackingMatrix). The Online UI labels 'Follow the Stack Matrix' Desktop Only.

The user can forbid an item from being stacked on an item with a smaller (or a different) footprint, or require stacks to form aligned columns.

Counts when: A documented footprint, alignment or column rule for stacking.

“AllowedTopBottomFootPrintSame | Cargo is only allowed to be placed on top of others with the exact same footprint (Length x Width).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“When activated, this rule within CubeMaster prevents the placement of cargo on top of other cargo that has a smaller footprint.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

Plan-level; different cargoes only. isBottomOrientationRespected is marked Read-only in the API guide.

The user can require a minimum share of an item's base to be supported (or limit how far it overhangs the item below), and the planner refuses unsupported placements.

Counts when: A documented support-percentage, overhang-over-support or centre-of-mass-over-support rule enforced by the planner.

“minSupportRate | number | Minimum support rate for safe stacking. Specifies what percentage of a cargo's base must be physically supported by the items beneath it.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“For instance, if the Min Support Rate is set at 51%, it signifies that at least 51% of the top cargo's base area must rest directly on the surface of the bottom cargo.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

Per plan only (isSafeStackingUsed + minSupportRate), not per item. All editions.

The user can set how large a height difference between neighbouring supporting surfaces an item may bridge.

Counts when: A documented maximum vertical gap or height-difference parameter for stacking across several items.

“If maxDepthToSupportForSafeStacking is set to n, the engine will consider the bottom n mm of a cargo for support calculations.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Max supporting depth: Sets the depth from the surface of bottom area which supports the top cargo.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/stacking.html

• The vendor's own sources disagree on this point

Per plan, with safe stacking. Online, API V2, Windows.

Stacking uses the item's actual top shape: nestable items add only a set height per extra unit, and items with a smaller or open top carry load only on the real top surface.

Counts when: A documented nesting height increment or top-shape description used when stacking.

Not counted: the evidence is a field name with no description of what it does.

The cargo popup summary lists 'Nesting' and the swagger has StyleEnum NestedCube and FaceOpenEnum, with no description of any engine behaviour.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'nest', 'NestedCube', 'faceOpen', 'open face', 'top shape', 'increment', 'Nesting' (cargo popup summary).

The user can require that only complete stacks or complete layers of an item are loaded, with remainders handled separately.

Counts when: A documented complete-stacks, complete-layers or flat-top rule.

“If this is ON, the top of the partial unitload is kept even and flat which was cut by the max weight, volume %, price and cargoes on a pallet.”

https://cubemaster.net/Help/webhelp/pages/unitload.html

“The remaining 15 pieces of cargo can then be placed onto a mixed pallet load or the vehicle floor, depending on the settings of the other two parameters”

https://cubemaster.net/Help/webhelp/pages/palletizing.html

Per cargo (palletizing.flatPalletTop, unitloadTopFlat). Also 'Allow unit loads less than full layers' off gives complete unit loads only.

The planner can keep all units of the same item together in one block.

Counts when: A documented setting that keeps like items together (or stops identical items being spread).

“isSpreadIdenticalCargoAllowed | boolean | Same cargoes allowed to be separated. When this rule is activated, CubeMaster will divide the identical cargoes in different spaces for higher space utilization.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“This rule ensures that identical cargoes remain together in the same containers or pallets when they are assigned to the same area. It only applies when the "Same cargoes allowed to be separated" rule is deactivated.”

https://cubemaster.net/Help/webhelp/pages/advanced1.html

Plan level; off keeps like items together, plus an option to keep them in one container. Also 'Same Cargoes Placed in the Same Side' (Read-only in API). Online, API V2, Windows, SDK (bSplitIdenticalItem).

The user can assign items to groups (such as orders or customers), and the planner keeps each group's items together in the unit.

Counts when: A documented group attribute and a keep-together rule.

“isGroupUsed | boolean | If true, respects `groupName` for keeping items together.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Cargoes within the same group will be kept together in a container, while different groups will be separated.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

All editions.

The user can require all items of a group to go in the same unit when the shipment needs several units.

Counts when: A documented rule that forbids splitting a group across units.

“Otherwise, the same group is not placed over two different containers and are kept in either container.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/grouping.html

“isSameGroupAllowedInDifferentContainers | boolean | If true, allows splitting groups across containers.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point
• Only in some editions, plans, methods or equipment types

Windows and API V2. What happens to a group too large for one container is not stated.

When not everything fits, a group of items (for example one order or shipment) is loaded completely or not at all. †

Counts when: Documentation shows an option that leaves a whole group unloaded rather than loading part of it.

Groups can be kept in one container, but no source says an unfitting group is left out whole. Sequences are documented as splittable.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'all or nothing', 'complete group', 'whole order', 'partial', 'group' with 'unloaded', 'isSameGroupAllowedInDifferentContainers'.

The user can have each group loaded in its own section of the unit, with no other group's items in it.

Counts when: A documented rule that separates groups into distinct sections (an invisible wall, zero overlap, segmented stops or barriers).

“Cargoes within the same group will be kept together in a container, while different groups will be separated. The loading order of the groups will be automatically determined to maximize space utilization within the containers.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“Cargoes in identical group will be placed together and different groups will separate in a container.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/basic.html

• Follows from documented behaviour rather than stated outright
• Relies on a setting other rows also use; they may not all work at once

All editions (isGroupUsed).

The user can forbid items of one group (order, stop, customer) from being stacked on items of another group.

Counts when: A documented group-level stacking ban.

“groupsStackingRule | string | Vertical placement constraints resolving separate cargo groups. Unlike individual cargo rules, this has limited specific values: AlwaysNotAllowed (101) or BestFit (100).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

API V2 (plan level, values AlwaysNotAllowed | BestFit). Not described in the Online or Windows help.

The user can prevent specific items or groups from sharing a unit.

Counts when: A documented rule, compatibility matrix or group-to-unit restriction that keeps chosen items out of the same unit.

“If the Load Type is 'Multiple Set Load', activating this rule will allow the CubeMaster to place cargoes from different groups into the same container or pallet.”

https://cubemaster.net/Help/webhelp/pages/grouping.html

“isDifferentGroupAllowedOnMultiSetLoad | boolean | If true, allows different groups in multi-set loads.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point
• Relies on a setting other rows also use; they may not all work at once

Online, API V2, Windows. Hazmat segregation is a marketing claim only.

The user can keep specific items (or classes) apart within the same unit: at least a set distance apart, or never anywhere above one another.

Counts when: A documented separation-distance or not-above rule between items or classes in one unit.

'Spacing' appears only in the cargo popup summary, with no field or definition.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'distance', 'separation', 'apart', 'not above', 'segregat', 'spacing'.

The user can give items dangerous-goods classes, and the planner applies segregation between classes without the user defining each pair.

Counts when: A documented hazard-class attribute with built-in segregation rules.

“Handling Tags (Fragile, HazMat) | Categorical Flags | Places fragile items on top layers and segregates hazardous material SKUs.”

https://cubemaster.net/Subscription/features.html

“Additional properties: Stackability (max stack weight, items on top), Nesting, Fragile flag, Hazardous classification, and custom fields.”

https://cubemaster.net/Help/webhelp/pages/cargo-edit-popup.html

No hazard field in API V2, the detailed cargo pages, Windows or SDK. The documented hazmat use case uses groups, not built-in class rules.

The user can cap, per unit, the total of a per-item quantity other than weight and volume, such as declared value, dangerous-goods points or piece count.

Counts when: A documented per-unit cap on the sum of at least one such per-item quantity.

“When this rule is active, CubeMaster fills the available space in a container or pallet, ensuring the total price doesn't exceed the maximum price for the empty container/pallet.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

“If this is more than 0, CubeMaster will make the total number of cargoes would not exceed this value in the load of each truck.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

Per container (Max Price, Max Cargoes) in Online/Windows; API V2 has per-container maxPrice and a plan-level maxFillQtyPerContainer.

The user can cap how many distinct items (or orders) a unit may contain.

Counts when: A documented per-unit (or per-zone) limit on distinct item types or order numbers.

“This field restricts the number of different SKUs (Stock Keeping Units) or cargo types that can be loaded into a single container.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“If set to 1, only one type of cargo is allowed in the container.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Per container (maxCargoTypes) and per plan (Online Advanced 'Max Different Cargoes per Container'; API maxCargoTypesPerContainer marked Read-only).

The user can require items to be loaded in a fixed ratio in every unit (for example one table to four chairs).

Counts when: A documented set or ratio rule applied per unit.

“setRatio | integer | Ratio for set loads (e.g., 1:2:1 for components). Used in "Set Load" or "Multiple Set Load" types to maintain proportions.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“CubeMaster will then calculate the quantity of each cargo type while maintaining the set ratio and assign it to the Qty field of the respective cargo.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

Set Load (one container) and Multiple Set Load (several). Behaviour when a ratio cannot be met is not documented.

The user can require an item to be loaded into each unit only in multiples of a set number.

Counts when: A documented batch or multiple-of-N rule per item.

fixedCargoCountOnPallet fixes cases per pallet (pallet pattern row), not multiples per vehicle.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'multiple of', 'batch', 'lot', 'fixedCargoCountOnPallet', 'round'.

The user can fix part of a plan (placed items, pre-loaded pallets or whole units) and have the planner complete or re-plan the rest around it.

Counts when: Documentation shows existing placements kept fixed while the planner adds or re-plans the remaining cargo.

“Automatic calculation of the additional cargo quantities fit into the unused spaces of a loaded container”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/using-edit-spaces-view.html

“Full button: fills the unused space with the [additional quantity].”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/using-edit-spaces-view.html

• Evidence is documentation five or more years old
• Only in some editions, plans, methods or equipment types
• Follows from documented behaviour rather than stated outright

Windows edition (Edit Spaces). Re-running the whole load discards pattern-editor changes. No lock field in API V2 or the current Online help.

The user can give an item's exact position as input data, without manual placement in an editor, and the planner loads the rest around it.

Counts when: A documented input field for an item's position (coordinates) that the planner treats as fixed.

Positions appear only in outputs (placements, spaces).

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'position', 'pos', 'coordinate', 'fixed', 'preload', 'AddPreloadContainer' (SDK function name only, no page), request schema of Cargo.

The user can confine an item to a defined region of the unit, such as the front, the rear, one side or a zone.

Counts when: A documented per-item (or per-class) region, zone or location rule the planner respects.

“Advanced loading rules: Grouping (keep items together), Sequencing (load/unload order), Spacing, and Preferred Position within the container.”

https://cubemaster.net/Help/webhelp/pages/cargo-edit-popup.html

“zones | null/array | Zoning information (null if not used). Array of zone objects with position, size, maxWeight.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

The detailed Cargo Advanced page documents only Bulge, and no schema field ties cargo to a zone or position.

The user can keep items out of a defined region of the unit (for example the first metre at the door, or a central aisle).

Counts when: A documented rule that keeps an item, or all items, out of a region of a unit.

Max Volume % reserves volume but not a located region.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'exclude', 'keep out', 'aisle', 'door' region, 'zone', 'reserved'.

The user can choose the direction in which the planner fills the unit (for example front to back, bottom to top or side to side).

Counts when: A documented setting with at least two fill directions or fill patterns.

“FrontToRear | Builds a wall stacking from the inside to the outside (door side of truck/trailer).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“BottomToTop | Places the load on the ground to spread on the floor. Recommended for pallets to stack upwards in a stable spiral shape.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Plan level. Width spread is in Online/Windows, not in the API enum.

The user can make the planner cover the floor before stacking, for a whole plan or for specific items.

Counts when: A documented floor-first, spread or floor-to-ceiling strategy.

“Bottom to top: Loads are placed on the ground and spread out as much as possible.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

“Bottom Spread - Spread the load on the bottom of the less filled container.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/efficient-and-flexible-algorithm.html

Plan scope; not per item.

The user can make the planner respect handling-equipment limits: how deep a loading block may reach, or room to turn an item with a forklift.

Counts when: A documented maximum reach or block depth, or a forklift-turning check.

“It is max reachable size of loading devices or humans to place items into a filled container.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“For example, a value of 1000 mm will ensure that each item placed is kept under 1 meter, and the same items will be repeated until the container or pallet is filled.”

https://cubemaster.net/Help/webhelp/pages/advanced1.html

Plan level. Online, API V2, Windows, 2018 overview ('Limits the placement in vehicle for easy loading and unloading').

The user can require clearance around items: a gap between all units, or extra space around a specific item.

Counts when: A documented gap or clearance setting (plan-wide or per item) that the planner leaves empty.

“The bulge factor allows you to shift the amount of space a box takes up without changing its reported size.”

https://cubemaster.net/Help/webhelp/pages/advanced.html

“bulgeSize | object | Bulge dimensions (length, width, height) for expansion/compression.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

No plan-wide gap setting; 'Spacing' is listed only in the cargo popup summary.

The planner makes sure every item is backed in the loading direction (and, if the user asks, sideways) by a wall or another item, so it cannot shift.

Counts when: A documented check that each item rests against the wall or another item, lengthwise and/or laterally.

Min support rate covers vertical support only.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'shift', 'backed', 'against the wall', 'lateral', 'stability', 'secure'.

The planner never exceeds the maximum payload of a unit, including a pallet's maximum load.

Counts when: A documented maximum-weight input per unit that the planner enforces.

“isWeightLimited | boolean | Enforce container weight limits. When true, the engine fills available space as much as possible without the total weight exceeding the `maxWeight` of the empty container (including the empty container tare weight).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“The Max Weight includes the Empty Weight of the truck.”

https://cubemaster.net/Help/webhelp/pages/basic1.html

Per container including pallets, cartons and ULDs; applied when the 'Load weight limited' rule is on. Windows 10.10.8.5 fixed the weight limit not working for pallet loads.

Each compartment, deck or part of a unit can have its own weight limit, which the planner respects.

Counts when: A documented weight limit per compartment, section, zone, deck or part.

“zones | null/array | Zoning information (null if not used). Array of zone objects with position, size, maxWeight.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Not counted: the product reports this, but the documentation does not show the planner keeps to it; the evidence is a field name with no description of what it does.

• Only in some editions, plans, methods or equipment types

API V2 only; zones are the only sub-unit with a weight field (swagger also gives maxPrice and maxVolUtilization per zone).

The user can set different maximum weights for lengthwise sections of the unit (for example front, middle and rear floor sections).

Counts when: A documented per-section weight limit along the length that the planner enforces.

“zones | null/array | Zoning information (null if not used). Array of zone objects with position, size, maxWeight.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Not counted: the evidence is a field name with no description of what it does.

API V2 only.

Correction: Auditor-built recipe on a one-line zone field whose enforcement is never described.

The planner keeps the weight per unit of length below a set value everywhere along the unit.

Counts when: A documented maximum weight-per-length rule.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'per metre', 'per foot', 'linear', 'density', 'kg/m', 'weight distribution'.

The user can set a maximum load for each axle group, and the planner does not produce a plan that exceeds it.

Counts when: Documentation stating that axle limits are respected while the plan is built (not only calculated afterwards).

“Advanced space-filling algorithms automatically calculate optimal 3D cargo arrangements, maximizing volume and balancing axle weight limits.”

https://cubemaster.net/Subscription/features.html

“Internal dimensions, max weight, door opening, Axle Weight limits (front/rear/tandem), and trailer type selection.”

https://cubemaster.net/Help/webhelp/pages/container-edit-popup.html

Not counted: the product reports this, but the documentation does not show the planner keeps to it.

The axle report is documented (see output-axle-loads), but no field, unit or rule for axle limits exists in API V2, the swagger, SDK or the detailed truck page.

The axle model accepts three or more axle groups on one vehicle, each with its own position and limit.

Counts when: A documented axle input that allows at least three groups per vehicle.

“Details the weight resting on the steer, drive, and trailer axles.”

https://cubemaster.net/Help/webhelp/pages/report-axle-weight.html

“Internal dimensions, max weight, door opening, Axle Weight limits (front/rear/tandem), and trailer type selection.”

https://cubemaster.net/Help/webhelp/pages/container-edit-popup.html

Not counted: the evidence is a field name with no description of what it does.

• Follows from documented behaviour rather than stated outright

Online reports only.

The axle calculation includes the empty vehicle's own weight on each axle.

Counts when: A documented tare-per-axle, empty-axle-load or tare centre-of-gravity input used in the axle calculation.

“Computes net cargo weight, tare weight of containers/pallets, and total gross weight.”

https://cubemaster.net/Subscription/features.html

A single tare per container exists; no split across axles is documented.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'tare' with 'axle', 'empty axle', 'axle weight', 'kingpin'.

The axle calculation includes the towing unit: the load on a semi-trailer's kingpin (or on a drawbar) is passed to the tractor's axles.

Counts when: Documentation that coupling load is transferred to the towing vehicle's axles.

“Internal bed dimensions, kingpin-to-axle distances, maximum gross weight, drop deck dimensions, carrier info.”

https://cubemaster.net/Subscription/features.html

• Follows from documented behaviour rather than stated outright

The axle report shows steer and drive axles, which implies the trailer load reaches the tractor, but no source says so or documents the tractor model.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'kingpin', 'fifth wheel', 'tractor', 'steer', 'drive', 'coupling', 'drawbar'.

The planner can take axle and gross limits from a chosen jurisdiction or region (including axle-spacing rules and trip permits) rather than from values typed per vehicle.

Counts when: A documented region or jurisdiction setting that supplies legal limits.

“Ensures trailer balance, driving safety, and compliance with DOT axle load regulations.”

https://cubemaster.net/Subscription/features.html

“Compares the calculated weight against the specified legal limits for the selected vehicle profile.”

https://cubemaster.net/Help/webhelp/pages/report-axle-weight.html

Legal limits come from the vehicle profile; no region setting. The truck Basic page only explains that laws vary between states.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'DOT', 'jurisdiction', 'state', 'country', 'bridge formula', 'permit', 'legal'.

The user can set a permitted range for the lengthwise position of the load's centre of gravity, and the planner keeps within it.

Counts when: A documented longitudinal centre-of-gravity range that the planner enforces.

COG is reported, not constrained. Front/rear balancing is claimed (see weight-balance-soft).

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'center of gravity', 'cog', 'balance', 'front/rear', 'isBalanceAlignLoadCenter', 'maxWeightDifference'.

The user can set a permitted range for the sideways position of the load's centre of gravity (left/right balance), and the planner keeps within it.

Counts when: A documented lateral centre-of-gravity range, or maximum left/right difference, that the planner enforces.

“Distributes weight evenly along left/right sides and front/rear axles to prevent uneven trailer tilt.”

https://cubemaster.net/Subscription/features.html

• The vendor's own sources disagree on this point

No lateral COG parameter in any source. The API tutorial's balanceConfiguration {maxWeightDifference} exists in neither the Rules table nor the swagger.

The user can cap the height of the load's centre of gravity.

Counts when: A documented vertical centre-of-gravity limit that the planner enforces.

COG height is reported (cog.height) but not limited.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'vertical', 'height of center', 'cog height', 'top-heavy'.

The planner can improve weight distribution as a goal rather than a limit: moving the load's centre of gravity toward the centre, or evening out axle loads.

Counts when: A documented option that shifts or arranges the load for balance without a hard bound.

“Distributes weight evenly along left/right sides and front/rear axles to prevent uneven trailer tilt.”

https://cubemaster.net/Subscription/features.html

“Balancing — Weight distribution rules to balance loads for safe transport and axle weight compliance.”

https://cubemaster.net/Help/webhelp/pages/faq.html

Not counted: the evidence is a field name with no description of what it does.

• The vendor's own sources disagree on this point

The swagger flag isBalanceAlignLoadCenter has no description; the documented Balancing rule only replaces, cancels or tops up containers.

The user can give an item an off-centre centre of gravity, and the weight calculations use it.

Counts when: A documented per-item centre-of-gravity offset input.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'center of gravity' per cargo, 'offset', 'cog' in Cargo schema.

The user can set an order among items or groups, and the planner places earlier ones deeper in the unit (further from the door).

Counts when: A documented user-set sequence (list order, sequence number or group order) that the planner follows when placing.

“This means that all cargoes with a sequence of "1" will generally be placed before (and therefore in the front of the vehicle) cargoes with a higher sequence value.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“isGroupSequenceUsed | boolean | If true, respects the sequence of the groups. The smaller sequence number will be loaded first.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point

All editions. Group sequence is footnoted as not available in the Online UI but is in API V2.

When not everything fits, the user can decide by priority which items are loaded and which are left out.

Counts when: A documented priority that controls which items are loaded first or dropped.

“Required items must be loaded (unfitted items appear in Exceptions). Optional items fill remaining empty space after Required items are loaded.”

https://cubemaster.net/Subscription/faq.html

“If there's not enough room to load all cargoes with a particular sequence value, CubeMaster will load as much of the sequence as possible, leaving the remaining cargoes.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

All editions.

The user can mark items as optional (fill items), so that they are loaded only into space left after all required items.

Counts when: A documented optional or fill-item flag.

“isOptional | boolean | If true, cargo is optional for filling space in balancing.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“GroupSequenceRespectedAndDisplacementMinimized | Respects group sequence while minimizing displacement.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Optional items can respect cargo or group sequence (optionalCargoesFillingAction). Whether surplus optional items open another container is not stated. Requires the Balancing rule.

The user can assign items to delivery stops, and the planner places each stop's items nearer the door than the items for later stops.

Counts when: A documented stop or destination attribute with a load rule that orders stops along the unit.

“By defining stops as groups in CubeMaster, you can control how cargo is loaded and segregated within containers.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“Basic → Sequencing — Enable "Small sequences placed earlier than large ones". Assign Sequence numbers so Store-5 (Seq 1) loads first (back) and Store-1 (Seq 5) loads last (near doors) for LIFO unloading.”

https://cubemaster.net/Help/webhelp/pages/industry-use-cases.html

How it is done with general settings

1. Give each stop's cargo one groupName and turn on 'Same groups placed together' (https://cubemaster.net/Help/webhelp/pages/basic3.html, 'Multi-Stop Routing with Groups'). 2. Give the last stop the lowest Sequence and turn on 'Small sequences placed earlier than large ones'; Seq 1 loads at the back, the highest sequence nearest the doors (https://cubemaster.net/Help/webhelp/pages/industry-use-cases.html; https://cubemaster.net/Help/webhelp/pages/basic3.html). 3. Optionally order the groups with isGroupSequenceUsed (https://cubemaster.net/Subscription/Guides/API/api_guide.html) and check with the Routing Sequence report (https://cubemaster.net/Help/webhelp/pages/report-routing-sequence.html).

• Combination of general settings, shown by the vendor
• Relies on a setting other rows also use; they may not all work at once

No dedicated stop attribute; the vendor documents groups-as-stops plus sequence as the method.

The planner guarantees that no item for a later stop is in front of or on top of an item for an earlier stop, so each stop unloads without moving other goods.

Counts when: Documentation stating that items of later stops never block earlier stops (front or above), as a hard rule.

“Enforces Last-In-First-Out unloading constraints across multi-destination truck deliveries, reducing dock handling time.”

https://cubemaster.net/Subscription/features.html

“Prevents mixing items from different drop-offs and enforces LIFO (Last-In-First-Out) unloading sequence.”

https://cubemaster.net/Subscription/features.html

The documented mechanism is sequence ordering, which the help says can be split; no source states that later stops never block earlier ones in front or above.

The user can set how far one stop's goods may overlap the next stop's along the unit's length.

Counts when: A documented overlap or mixing distance between stops or sequences.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'overlap', 'mix', 'look ahead', 'sequence' with distance.

The user can give items a pickup stop as well as a drop-off stop, and the planner keeps the load accessible at every stop.

Counts when: A documented per-item origin and destination stop.

Shipping.where from/to in the swagger is shipment-level contact data.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'pickup', 'pick-up', 'origin', 'collect', 'load at stop'.

Stop-order rules still apply when the shipment spans several units.

Counts when: Documentation that multi-drop ordering works in multi-unit plans (within each unit or across consecutive units).

“MultipleSetLoad | Calculates containers to fill a shipment utilizing multiple destinations and stops.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Multiple Set Load - Finds optimal number of vehicles to load all orders of different size cartons with regarding multiple destinations and stops.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/various-load-types.html

• Follows from documented behaviour rather than stated outright

Multiple Set Load load type (Online, API V2, Windows, SDK).

When not everything fits, each stop's (or sequence's) items are loaded completely or not at all.

Counts when: A documented rule that a stop or sequence is never partially loaded.

“If there's not enough room to load all cargoes with a particular sequence value, CubeMaster will load as much of the sequence as possible, leaving the remaining cargoes. In other words, sequences can be split up.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

Stated for sequences; no whole-stop option is documented for groups either.

The planner can assign items to units or shipping dates by due or storage date, within set limits.

Counts when: A documented date input and a rule that uses it to allocate cargo.

“When Multiple Time Windows is selected as the Load Type, cargoes are grouped by their storage date. The engine loads each group as a separate time window.”

https://cubemaster.net/Help/webhelp/pages/pulling.html

“With Pulling: Due-date cargo fills the truck first. The remaining space is then filled with newer inventory, controlled by the Pulling rules (strategy, day limits, and max fill % per day).”

https://cubemaster.net/Help/webhelp/pages/pulling.html

CubeMaster Online UI only; not in the API V2 schema.

The user can build a load on a pallet, with the deck height counted and a maximum total height that includes the deck.

Counts when: Documentation of a pallet as a loading space with deck height and total height limit.

“The loading space is calculated as Length × Width × (Max Height – Height). The Max Height value includes the pallet's own height.”

https://cubemaster.net/Help/webhelp/pages/basic2.html

“palletThickness | integer | Pallet thickness in cm (e.g., 0).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

All editions.

For a single item type, the planner generates the layer pattern and number of layers for a pallet (Hi/Ti).

Counts when: Documentation of automatic single-item pallet pattern generation.

“UnitLoad | Calculates the full capacities of containers/pallets when filled with one cargo; used to calculate the Hi/Ti of a pallet configuration.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Alternative Patterns for Unit Pallet Load – Allows you to choose the correct pattern for a different load requirement.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/efficient-and-flexible-algorithm.html

All editions. The number of alternative patterns offered is not stated.

The user can steer the pallet pattern: choose a pattern style (block, pinwheel, interlocked), supply a saved pattern, fix the number of cases per pallet, or rotate alternate layers.

Counts when: At least one documented control over the pattern the planner builds.

“Pattern4Blocks | Arranges cargoes in a 4-block spiral (pinwheel) pattern towards the center.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“It defines the number of layers to be rotated on a pallet load.”

https://cubemaster.net/Help/webhelp/pages/unitload.html

Per cargo. Saved pallet solutions can be reused as cargo.

The planner builds pallets that carry several different item types.

Counts when: Documentation of automatic mixed-item pallet building.

“All remaining quantities are mixed into a new pallet (specified by the Pallet for mix load setting).”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

“Advanced Mixed Pallet Con­figuration – For detail configuration of the mixed pallet load. Choose between the block or individual placement, volume or area utilization ­first and layer or column stacking.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/load-rules.html

Also a Mix Load onto pallets as containers (pallet load). All editions.

The user can allow cargo to overhang the pallet edge by up to a set distance.

Counts when: A documented pallet overhang allowance with a limit.

“It represents the distance cargoes can be placed over the edge of the pallet along the length and width dimensions.”

https://cubemaster.net/Help/webhelp/pages/extended.html

“palletOverhangLength | integer | Overhang length in cm (e.g., 0).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

• The vendor's own sources disagree on this point

Per pallet (length and width) and per cargo unit load. Online, API V2, Windows, SDK single loads.

The user can control where the load sits on the pallet deck: centred, or within a set distance inside the edge.

Counts when: A documented centre-load or underhang (inset) setting.

“It represents the distance cargoes can be placed under the edge of the pallet along the length and width dimensions.”

https://cubemaster.net/Help/webhelp/pages/extended.html

“palletUnderhang | boolean | Whether pallet underhang is allowed (e.g., false).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

The planner inserts slip sheets or interlayers of a set thickness every N layers.

Counts when: A documented interlayer setting with thickness and frequency.

Slipsheet is a pallet base type; SDK top panels, banding and wrapping are added to a finished pallet load, with no thickness-every-N-layers rule.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'slip sheet', 'interlayer', 'tier sheet', 'layer pad', 'ApplyTopPanel', 'banding'.

The user can prevent items of different groups (customers, orders, stops) from sharing a pallet.

Counts when: A documented rule keeping groups on separate pallets.

“When unchecked, only cargo belonging to the same group name will be placed on a single mixed pallet.”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

“palletizing.isDifferentGroupsAllowedInSamePallet | boolean | If true, allows different groups on a pallet.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Online, API V2, Windows (since 10.10.7.0).

In one run, the planner builds pallets from cases and then loads those pallets into vehicles or containers.

Counts when: Documentation of a single calculation that palletises and then loads the pallets.

“The engine will first build optimal pallets, then load those structured pallets into the target truck instead of loose boxes.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Unit loads are created based on the palletizing rule of each cargo. All remaining quantities are mixed into a new pallet (specified by the Pallet for mix load setting). All the unit load and mix load pallets are placed into vehicles.”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

Online, API V2, Windows Enterprise. Windows states palletizing is active for sea container and truck loads only.

A built pallet or packed carton can be carried into a later vehicle plan as an item with its actual size and weight, without re-entering them.

Counts when: Documentation of saving a pallet or carton result as a loadable item, or of assigning a built pallet to a vehicle.

“A complete unitload created by the Pallet Load. It can only be created by saving a solution of the pallet load build via the button Save as Cargo at the Analysis View.”

https://cubemaster.net/Help/webhelp/pages/basic3.html

“This function enables to bring Cargoes from the saved Unit Load file and to build the 2-stage load for example the pallet loaded with cartons can be packed into the container or truck.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/add-unitloads-as-cargoes.html

Online (Save as Cargo, pre-pack unitload style) and Windows (Save as Unit Load file). Size and weight are filled automatically.

The planner chains three or more packing levels (for example items into cartons, cartons onto pallets, pallets into trucks).

Counts when: Documentation of at least three nested levels in one plan or chained stages.

“To build 2-stage load, you should save the loaded container as the Unit Load file first.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/save-a-solution-as-unit-load-file.html

Two stages are documented. Windows 'Save as Unit Load' applies to 'the loaded container', which might allow a carton result to feed a pallet load, but no source shows three levels.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: '3-stage', 'three', 'carton' with 'pallet' and 'truck', 'Save as Unit Load', 'Save as Cargo', 'pre-pack'.

The user controls how an item's quantity splits between full pallets, partial or mixed pallets and loose loading (or packed versus shipped in its own box), or the planner decides per unit.

Counts when: A documented remainder rule or palletise-or-loose choice per item.

“palletizing.remainQtyToMixPallet | boolean | If true, remaining qty placed on mixed pallets.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“palletizing.remainQtyToVehicle | boolean | If true, remaining qty placed directly on vehicle floor.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Built pallets get their own orientation and stacking rules in the vehicle, independent of the items on them (including whether a pallet may carry another and how full its top must be).

Counts when: Documented orientation, stacking or floor rules set on built pallets for the next stage.

“Orientation #1 + #2: The pallet can be placed in both orientations (lengthwise and widthwise) relative to the vehicle.”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

“When checked, the completed pallets are allowed to support other pallets or cargo on top of them. When unchecked, nothing may be placed on top of these pallets.”

https://cubemaster.net/Help/webhelp/pages/palletizing1.html

No top-fill threshold for stacking pallets. Online, API V2 (swagger SingleCargoPalletizingRules), Windows.

The planner sizes pallet height to the space available in the vehicle (for example shorter pallets for the top tier).

Counts when: Documentation of pallet heights adapted to the vehicle or to the space above a lower tier.

“palletizing.palletizingAlgorithm | string | Algorithm to use for building pallets - "UnitloadsDevelopedInAdvance", "UnitloadsDevelopedDinamically".”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Not counted: the evidence is a field name with no description of what it does.

Only 'developed in advance' is described.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'dynamic', 'Dinamically', 'height' with 'vehicle', 'top tier', 'palletizingAlgorithm'.

The planner maximises the cargo loaded into a given set of units, leaving any excess unloaded.

Counts when: Documentation that the planner fills fixed units as fully as possible.

“This option directs CubeMaster to prioritize maximum capacity utilization. The program identifies the container with the highest load volume as the solution and disregards the remaining containers.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

“isWeightLimited | boolean | Enforce container weight limits. When true, the engine fills available space as much as possible without the total weight exceeding the `maxWeight` of the empty container (including the empty container tare weight).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

With limited container quantities, remaining cargo is left unloaded and reported in Exceptions.

The user can make the planner maximise loaded weight (or weight utilisation) instead of volume.

Counts when: A documented weight-based objective or selection strategy.

“BestfitMaxWeightUtilFirst | Weight utilization maximized | Picks the filled container with the highest weight utilization (Total Cargo Weight / Max Weight limit) as the solution. Container Qty and Seq are ignored.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Goal of Mix Load, Mix Load only. Ignores container quantity and sequence.

The planner can spread the load evenly over the units used, instead of filling each to the maximum in turn.

Counts when: A documented balancing or redistribution option across units.

“Purpose: To distribute the weight and volume of items evenly across all containers, preventing any single container from becoming overloaded or significantly underutilized.”

https://cubemaster.net/Help/webhelp/pages/balancing.html

“It allows the user for example to equally divide the boxes among the available containers.”

https://cubemaster.net/Download/CubeMaster_Online_Overview.pdf (p. 58)

• Follows from documented behaviour rather than stated outright
• Evidence is documentation five or more years old

Online, API V2, Windows (Balancing rule).

The planner works out how many units of an item (or complete sets) fit, or tops up leftover space with more of the items already planned, without a quantity being given.

Counts when: A documented cube-out, maximum-sets or top-up mode.

“UnitLoad | Calculates the full capacities of containers/pallets when filled with one cargo; used to calculate the Hi/Ti of a pallet configuration.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“SetLoad | Calculates the number of complete products to maximize space utilization when the product consists of multiple cargoes kept in a proportional ratio.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

The user can trade calculation time for plan quality (for example a time limit, search depth, quality level or fast mode).

Counts when: A documented run-time or quality control.

“The Optimization algorithm has 5 levels (1–5) balancing load time and quality. Level 1 is the fastest but least efficient, while Level 4 is the slowest but most efficient.”

https://cubemaster.net/Help/webhelp/pages/basic4.html

“maxRunTimeSeconds | integer | Max runtime in seconds for calculation.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Level 5 is documented as unsuitable for small cargo. The SDK says its time limit is 'Not available at this time'. Reproducibility is not stated.

The planner returns several alternative plans (for example one per strategy or per candidate equipment) for the user to compare.

Counts when: Documentation of multiple solutions produced in one run.

“Alternative Solutions for Mixed Pallet Load – Makes different pallet loads for the same shipments.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/efficient-and-flexible-algorithm.html

“a list of new sizes are found from the calculation which load all the items in the different ways.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/buttons-group.html

• Only in some editions, plans, methods or equipment types
• Follows from documented behaviour rather than stated outright

Windows edition only. No alternatives in API V2 or the Online help.

The user can write a rule that selects items by a condition on an attribute (for example all items over 500 kg) and applies a constraint to them.

Counts when: A documented rule mechanism that selects items by an attribute condition.

“maxStackingHeight | object | Controls maximum stacking height dynamically using specific proportional rules.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“If minWeightDifferencePercentageForStackingTwoCargoes is set to n, the engine will only allow stacking two different cargoes if their weights differ by at least n percent.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Not counted: the evidence is a field name with no description of what it does.

API V2.

The user can define their own item attributes and use them in planning rules.

Counts when: Documentation of user-defined fields that a rule, matrix or objective can select on.

“A string to describe the cargo (max. 50 characters for each property). Just for displaying in a report.”

https://cubemaster.net/Help/webhelp/pages/extended1.html

“property1 to property10 | string | Custom properties for additional metadata (max 50 characters each). For display in reports.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Properties 1-10 are display only. The SDK's ItemCompareCondition can use them to decide which SKU lines count as identical, which is not a planning rule. Free-text groupName, alias and stackCode drive built-in rules (scored elsewhere).

The user can define item classes and a matrix of which class may be stacked on which.

Counts when: A documented class code per item and a class-to-class stacking matrix.

“AllowedTopBottmStackValueSame | Cargo is only allowed to be placed on top of others with the exact same Stack Value.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“A Stack Code defines the stacking relations among different cargoes. The code establishes parameters that a class of cargoes would use.”

https://cubemaster.net/Help/webhelp/pages/stacking.html

Stack codes and the matrix are 'Desktop Only' in the Online UI; API V2 exposes FollowStackMatrixByStackCodes. No per-orientation exceptions.

The user can define item classes and a matrix of which classes may share a unit.

Counts when: A documented class code per item and a class-to-class compatibility matrix for sharing a unit.

Group-level mixing on/off (Multiple Set Load; swagger CargoGroup.isMixedWithOthers) exists, but no class-to-class matrix. Cargo.sharingCode appears in the swagger with no description.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'compatib', 'matrix', 'mix', 'segregat', 'isMixedWithOthers', 'sharingCode'.

The user can cap, per unit (or per group within a unit), the sum of any per-item numeric value they choose.

Counts when: A documented mechanism in which the user chooses the attribute to be summed and capped.

“"maxVolumePerContainer": { "type": "number", "format": "double" }, "maxWeightPerContainer": { "type": "number", "format": "double" }”

https://api.cubemaster.net/swagger/v2/swagger.json

Partial form only: swagger CargoGroup has per-group max weight and volume per container, with no description. Price and piece caps are fixed attributes.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'sum', 'total', 'max' per container fields, CargoGroup, property1-10.

Rule settings can differ from one equipment unit to another within one plan.

Counts when: Documentation of rule or optimiser profiles assigned per unit or equipment type.

The Rules object is one per shipment. Containers carry their own limits (max weight, volume %, price, cargo count, distinct cargo types), which are equipment data, not rule profiles.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'rules' per container, 'profile', 'per container', 'Rules' object location in Shipment.

Several stacking criteria (for example footprint, weight order and a class matrix) can be active at the same time in one plan.

Counts when: Documentation that more than one stacking criterion applies simultaneously.

“FloorStackAndHeavierBottomFirst | Composite logic combining FloorStack preferences with weight distribution requirements.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“AllowedTopBottomFootPrintSameHeavierBottomFirst | Composite logic requiring matching footprints while enforcing heavier items at the bottom.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Arbitrary combinations (e.g. stack matrix plus footprint) are not possible.

The user can combine several objectives in a priority order or with weights (for example fewest units, then axle balance, within a tolerance).

Counts when: A documented mechanism for ordered or weighted multiple objectives.

One Goal of Mix Load per plan. The features page lists 'Default optimization goals (Maximize Volume, Balance Weight, Minimize Cost)' as a single default choice.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'goal', 'objective', 'weight' + 'priority', 'tolerance', 'bestFitContainersSelectionType'.

The user can add their own constraint or objective logic (script, plug-in or callback) that the planner evaluates.

Counts when: Documentation of a user-accessible extension mechanism for constraints or objectives.

The SDK is a calculation library with properties and methods; every SDK object's Events page reads 'None'.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'script', 'plug-in', 'callback', 'custom rule', 'event', SDK Events pages.

For a given rule, the user can choose whether it is a hard limit or a preference the planner follows where it can. †

Counts when: Documentation shows at least one constraint type that can be set either as a hard rule or as a soft preference.

Constraints are fixed as hard (max layers is stated as hard) or as preferences (orientation priority); no rule offers the choice.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'hard', 'soft', 'preference', 'try', 'strict'.

The plan gives the position and orientation of every loaded unit, individually or as blocks with counts along each axis.

Counts when: Documented coordinates (and orientation or placed dimensions) for each unit or block.

“Placements originate from the back-left-floor corner (0,0,0).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“spaces[].placements[].fillDirection | integer | Orientation used (e.g., 2 which means the cargo was placed in direction #2).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Origin back-left-floor; length = X (depth), width = Y, height = Z. Online Placements report, Windows, SDK.

The plan includes step-by-step loading instructions, with a diagram for each step.

Counts when: Documented step-by-step instructions with per-step views.

“Displays individual cargo items or blocks of items as they are added to the container from front to back, or bottom to top.”

https://cubemaster.net/Help/webhelp/pages/report-loading-map.html

“Accompanies each visual step with clear textual instructions (e.g., "Load 5 boxes of Item A against the back wall").”

https://cubemaster.net/Help/webhelp/pages/report-loading-map.html

Online Loading Map report; API reportLinks.loadingInstruction; Windows loading guide.

The plan lists, for each unit (including each built pallet), which items it holds and how many, and its volume and weight utilisation.

Counts when: Documented per-unit contents and utilisation figures.

“manifest | array | Summary per cargo type loaded, similar to the Cargoes section in the Report View, showing loaded quantities and utilizations.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“loadSummary.floorUtilization | number | Percentage of floor space utilized (e.g., 84.11).”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Per container: counts, volume %, weight %, floor %, price %, dim weight; pallet loads report cargoesPerLayer and layersPerUnitload (swagger ContainerLoadSummary).

The plan reports the floor length used or left free (loading metres).

Counts when: A documented loading-metre, length-used or end-gap figure.

“loadSize | object | Dimensions of the loaded cargo footprint {length, width, height}.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

API V2; the sample response shows loadSize.length 554.68 in a 630-unit trailer.

The plan lists the items that could not be loaded, with quantities.

Counts when: A documented not-loaded or cut list.

“The Exceptions report lists all cargo items that were not loaded into any container during the optimization process.”

https://cubemaster.net/Help/webhelp/pages/report-exceptions.html

“loadSummary.cargoesLeft | integer | Cargo units not loaded.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

Online Exceptions report and List View; API gives counts (cargoesLeft, piecesLeft) per shipment.

The plan states why each unplaced item was not loaded.

Counts when: A documented reason per unplaced item (for example too large, over weight, no space, rule violation).

“Crucially, it provides the reason for each exception, such as:”

https://cubemaster.net/Help/webhelp/pages/report-exceptions.html

“Too Large: The item's dimensions exceed the container's interior dimensions or door size. Weight Exceeded: Adding the item would surpass the container's maximum weight limit. No Space Left: The container reached its volume capacity before the item could be loaded. Constraint Violation: The item conflicts with stacking rules, orientation limits, or priority settings.”

https://cubemaster.net/Help/webhelp/pages/report-exceptions.html

Online Exceptions report only; the API V2 response has counts but no reasons.

The plan reports the load's centre of gravity as a position (lengthwise and sideways).

Counts when: A documented numeric centre-of-gravity output, or numeric offsets from the centre of the space.

“cog | object | Center of gravity {length, width, height}, used for balance checks.”

https://cubemaster.net/Subscription/Guides/API/api_guide.html

“Shows the precise 3D center of gravity for the loaded cargo.”

https://cubemaster.net/Help/webhelp/pages/report-axle-weight.html

Per filled container, numeric in length, width and height. Online, API V2, Windows.

The plan reports the load on each axle group and whether it is within its limit.

Counts when: Documented per-axle load figures in the output.

“Details the weight resting on the steer, drive, and trailer axles.”

https://cubemaster.net/Help/webhelp/pages/report-axle-weight.html

“Compares the calculated weight against the specified legal limits for the selected vehicle profile.”

https://cubemaster.net/Help/webhelp/pages/report-axle-weight.html

Online Axle Weight Compliance report; Windows properties preview. API V2 exposes only a weight diagram image, no axle numbers.

The plan reports how weight is distributed along the unit's length (per section or per unit length).

Counts when: A documented weight-distribution output along the length.

“Analyzes lateral and longitudinal weight distribution along trailer/container axles.”

https://cubemaster.net/Subscription/features.html

“3D Weight Distribution Chart - With axle weight and center of gravity.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/multiple-reports-and-printouts.html

A weight distribution chart (Windows) and a weight diagram image (API path3DDiagramWeight) exist, but no source describes a distribution along the length.

The plan reports gross weight including the equipment's tare (for example for a verified gross mass declaration).

Counts when: A documented gross or total weight that includes tare.

“Returns the gross weight (load weight + container weight) of the container.”

http://www.logensolutions.com/VMS/TechSupport/SDK_Help/pages/loadedweight-property.html

“Returns the total weight (load weight + empty weight of the container) of the filled container.”

http://cubemaster.net/subscription/webservices/Help/pages/grossweight-property.html

SDK (LoadedWeight) and legacy web service (GrossWeight). API V2 has weightTotal without a description; the Packing List report gives gross and net weights.

The plan gives per-stop information: the contents for each stop and a view of the unit at each stop.

Counts when: Documented per-stop summaries or views.

“A list of stops in order. The specific cargo assigned to each stop.”

https://cubemaster.net/Help/webhelp/pages/report-routing-sequence.html

“"cargoQty": {"type": "integer", "format": "int64"}, "bytesImage3D": {"type": "string", "nullable": true}”

https://api.cubemaster.net/swagger/v2/swagger.json

Not counted: the evidence is a field name with no description of what it does.

Online reports; API cargoGroups ('Grouped cargoes if grouping rules were applied').

The planner checks a plan, including one edited by hand, against the item rules and lists any violations.

Counts when: Documented rule validation of an edited or imported plan, with a violations list or warnings.

The Magic editor marks cargo moved outside the container with an X, and Edit Containers refuses moves above the available quantity; no rule validation of an edited plan. The API validation errors concern inputs.

Where we looked

Searched 2026-09-30, all saved locally and grepped: API V2 guide (full text) and swagger.json (all 76 schemas/enums); CubeMaster Online help (all 102 pages from webhelpcontents.html); CubeMaster for Windows help (197 pages); SDK reference (274 pages); legacy Calculation Web Service help (187 pages); Overview PDF 2018 (all 62 pages, text); features.html; faq.html. Terms: 'validat', 'violation', 'check', 'warning', 'Magic' editor, 'Edit Containers', 'error message'.

The plan identifies empty voids above a set size (for example for dunnage or airbags).

Counts when: Documented void or empty-space output.

“The Empty Space tab provides a comprehensive list of all remaining, unoccupied spaces inside the selected container.”

https://cubemaster.net/Help/webhelp/pages/analysis-empty-space.html

“When the bFillAirbagOnContainer property is set to TRUE, the optimization fills containers with air-bags after filling inside the containers with single SKU type completely.”

http://www.logensolutions.com/VMS/TechSupport/SDK_Help/pages/bfillairbagoncontainer-property.html

No minimum void size setting.

The plan reports the cost of the equipment used, and the cost allocated to each item.

Counts when: Documented plan cost output.

“Costing Calculations - Once the price of an empty container was provided, the cost of individual cargoes in the filled container is analyzed and shows the total and percentage in the well formatted table.”

https://www.logensolutions.com/VMS/TechSupport/CubeMaster_Help/pages/load-rules.html

“By utilizing the price per container or pallet, as well as activating the price per cargo, the rule can calculate the individual cargo price for each piece within those containers or pallets.”

https://cubemaster.net/Help/webhelp/pages/advanced1.html

Online, Windows; API isCargoCostComputedFromShipCost (Read-only).