packVol 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.

“The input fields (L) Length, (W) Width, and (H) Height refer to the “internal” or to the “nominal” dimensions of the container. Data are integer valued and must always be set.”

https://www.packvol.com/packvol-en.pdf#page=33

“Closed cnt This is the standard container, defined as any rectangular envelop with fixed assigned sizes.”

https://www.packvol.com/packvol-en.pdf#page=34

All editions. Integer dimensions only (decimals via a unit scale factor, p.68).

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.

“The program allows you to define irregular containers with unusable volumes so that no package will be placed inside these regions. Such spaces must have “rectangular” shape”

https://www.packvol.com/packvol-en.pdf#page=50

“rect Unusable space row. Columns B, C, D are the “low” coordinates, E, F, G are the edges.”

https://www.packvol.com/packvol-en.pdf#page=101

Stored with the container type (Excel import, ODBC pv_obs, or a manual session). Whether cargo may stand on top of an unusable space is not stated. All editions.

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.

“enter in the Dim. grid the dimensions of the “blocks” that form the unusable volumes. It is not necessary to specify their number”

https://www.packvol.com/packvol-en.pdf#page=51

“so that blocks can be placed in arbitrary positions”

https://www.packvol.com/packvol-en.pdf#page=51

Any number of rectangular blocks, each with its own low coordinates and size (Excel rect/bbox rows, ODBC pv_obs rows). Saved as a property of the container type. The per-solution 'unusable section' (one length range per container) is separate.

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.

“You can also define an effective height of the container, to prevent the placing of the packages near the “ceiling” of the container.”

https://www.packvol.com/packvol-en.pdf#page=51

““Unusable sections”, be changeable as desired in the solution and not saved into the internal database.”

https://www.packvol.com/packvol-en.pdf#page=50

Set per individual container in the current solution via Settings > Unusable Section, without editing the container record. Desktop dialog; no ODBC field for it is listed.

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.

“In the example, the layout of a drop-deck type trailer is shown”

https://www.packvol.com/packvol-en.pdf#page=102

“the cnt rect reports the size of the unusable space.”

https://www.packvol.com/packvol-en.pdf#page=102

How it is done with general settings

1. Define the container with its full nominal length, width and height as a cnt row (Container data layout, p.100-101). 2. Add a rect unusable-space row covering the raised section at its position and height (p.101); the vendor's drop-deck example blocks 384 x 249 x 35 at the rear (p.102). 3. The planner keeps packages out of unusable volumes (p.50).

• Combination of general settings, shown by the vendor

The vendor documents this route for a drop-deck trailer. Steps are rectangular; any number of blocks is possible.

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.

“This way you can model a wide variety of containers: railway wagons, aerospace ULDs, refrigerated units, etc..”

https://www.packvol.com/rules.html

“Such spaces must have “rectangular” shape”

https://www.packvol.com/packvol-en.pdf#page=50

How it is done with general settings

1. Define the bounding box of the space as the container (p.33). 2. Add rectangular unusable spaces running along the length at the upper (or lower) corners, each with its own low coordinates and size, to cut the cross-section into steps (Container data layout rect/bbox rows, p.100-101; pv_obs, p.110). 3. The planner never places a package inside an unusable volume (p.50).

• Combination of general settings, assembled by the auditor from documented parts

Stepped approximation only (unusable spaces must be rectangular).

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.

Rectangular unusable spaces could in principle combine a lengthwise step with a cross-section cut, but the documentation shows only the drop-deck (lengthwise) example; no single unit combining both is shown.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: ULD, wagon, contour, profile, slope, irregular, unusable space, drop-deck; checked every unusable-space example (p.50-51, 100-102, 110). Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Such spaces must have “rectangular” shape”

https://www.packvol.com/packvol-en.pdf#page=50

Contours are built only from rectangular unusable blocks, so sloped walls can only be approximated by steps.

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.

Nothing models several sub-spaces of one unit. 'Unusable section' blocks a length range and max mixing 0 splits a container into longitudinal destination sections, but neither gives sub-spaces with their own geometry.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: compartment, section, deck, double deck, shelf, hold, trailer, road train, sub-space, zone, divider. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Only the rear/front convention (origin at the rear) and a pre-run check that packages fit the container dimensions (p.50) are documented.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: door, opening, aperture, entrance, access. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The loading direction is fixed by the coordinate convention (origin at the rear, fill Rear-Front, Bottom-Top or Layer-Front). The Rack/Flat type is 'open on width side' for overhang, not documented as a loading face.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: door, loading face, side loading, top loading, access, curtain. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Open Top The container allows loading of packages taller than the height of the container. The exception is applied when packages are on floor”

https://www.packvol.com/packvol-en.pdf#page=34

“Rack/Flat This is a special container (C, D), open on width side and with usable height greater than the height of the front wall. Floor packages are positioned with symmetrical overhang if they have a greater extension than the base.”

https://www.packvol.com/packvol-en.pdf#page=34

Not counted: part of the pass condition is not shown.

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

The maximum over-length check is ticked for DYNLOAD only in the edition table ('Check of maximum overlength on open container'), while the manual says STANDARD can set rack/flat parameters.

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.

“b) minimize the number (or capacity) of containers needed to load the entire loading list.”

https://www.packvol.com/packvol-en.pdf#page=52

“In the case of minimizing the number of containers with the “base” methods, completion occurs using the last container in the load list.”

https://www.packvol.com/packvol-en.pdf#page=52

Methods seq-a and fst-a (auto add). STANDARD and DYNLOAD; 'The Lite version has only the sqn-f method for a single container' (p.53). No stated cap on added units ('no limits on the number of containers', p.1).

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.

“The application tries to estimate the best combination of types to minimize the capacity or the cost of the containers needed to load the whole loading list.”

https://www.packvol.com/packvol-en.pdf#page=53

“Ability to check for the best container type”

https://www.packvol.com/versions.html

DYNLOAD 'mbin' (multibin) method only; type quantities need only be > 0. In the base methods the user lists the units and the last type completes the 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.

“qty number of containers.”

https://www.packvol.com/packvol-en.pdf#page=38

“The value qty=0 excludes the type from the optimization list.”

https://www.packvol.com/packvol-en.pdf#page=38

Honoured by the fixed-list methods (seq-f, fst-f), which leave the excess unloaded. Not a cap under auto-add (the last listed type completes the load, p.52) or mbin (quantity only needs to be > 0, p.53). Input tab absent in LITE (single container).

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.

“In the case of minimizing the number of containers with the “base” methods, completion occurs using the last container in the load list.”

https://www.packvol.com/packvol-en.pdf#page=52

“Loading is normally done (seq-f and seq-a methods) in a “sequential” manner, one container at a time until the list is exhausted.”

https://www.packvol.com/packvol-en.pdf#page=52

How it is done with general settings

1. List the preferred types first, each with its available quantity (Input tab qty, p.38; pv_cnt ordered by ID, p.108). 2. Put the fallback type last in the list. 3. Run a sequential auto-add method (seq-a), which fills one container at a time (p.52) and completes the load with the last listed container (p.52).

• Combination of general settings, assembled by the auditor from documented parts
• Follows from documented behaviour rather than stated outright

No dedicated preference field; a fixed-list-then-fallback split follows from list order. STANDARD and DYNLOAD.

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.

“The application tries to estimate the best combination of types to minimize the capacity or the cost of the containers needed to load the whole loading list.”

https://www.packvol.com/packvol-en.pdf#page=53

“With the plt-r and plt-e methods the application optimizes each package in the input list, “row by row” (or by groups of rows controlled by fml), looking for the best possible saturation on the container types available in input.”

https://www.packvol.com/packvol-en.pdf#page=54

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

DYNLOAD only. mbin minimises total capacity across the offered types; plt-r/plt-e pick the container type with the best saturation per item.

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.

“cost cost associated to the container.”

https://www.packvol.com/packvol-en.pdf#page=38

“The application tries to estimate the best combination of types to minimize the capacity or the cost of the containers needed to load the whole loading list.”

https://www.packvol.com/packvol-en.pdf#page=53

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

DYNLOAD mbin only. Flat cost per container type (decimal >= 1, default 1).

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.

Only an absolute Max Load (weight) and an effective height per container exist; there is no percentage fill cap.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: fill, percentage, max volume, utilisation limit, saturation, cap. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

'Clean'/'Remove unused' only drop empty containers; 'Redistribute load' evens out containers but sets no minimum.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: minimum fill, minimum load, min volume, under-filled, remove unused. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“If the name of the container is entered in the cell, as shown in the Input tab, the row is loaded only on that type of container.”

https://www.packvol.com/packvol-en.pdf#page=27

“To force, enter the string @=n1=n2... in the cell. To exclude, enter the string #=n1=n2... in the cell.”

https://www.packvol.com/packvol-en.pdf#page=27

DYNLOAD: plt-e/plt-r by container name (including the pallet type an item is built on), mbin force/exclude lists of type indexes (added 4.1.0). In STANDARD the mc field ties an item to the n-th container instead (see fleet-item-to-unit).

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.

“In this case, the constraint mc = n requires that a package be loaded into the nth container in the list.”

https://www.packvol.com/packvol-en.pdf#page=27

“For the methods seq-a and fst-a, the number of containers to be used is unknown at startup, and the constraint is therefore removed.”

https://www.packvol.com/packvol-en.pdf#page=28

Fixed-list methods seq-f and fst-f only; STANDARD and DYNLOAD. An mc index above the container count stops the run with an error (p.49).

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.

Partial form only: a DYNLOAD 'Load extension' primary container takes the load height as the package height after conversion (p.36), and height can be adapted to the secondary container (p.73). No length/width sizing within ranges.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: variable height, load extension, dimension range, carton size, box size, minimum/maximum dimensions. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Length l, width w and height h of the item. The fields are integer valued.”

https://www.packvol.com/packvol-en.pdf#page=21

“Weight of the package. Must be expressed in the same unit of measure used in Current Tab of the Container Panel.”

https://www.packvol.com/packvol-en.pdf#page=23

All editions. Integer dimensions; no documented count limits.

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.

All items are rectangular packages.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: cylinder, cylindrical, drum, barrel, roll, pipe, tube, diameter, round. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: nest, nesting, honeycomb, staggered, hexagonal, pyramid, cylinder, roll. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: shape, L-shape, interlock, irregular item, non-rectangular package. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Loading into crates or pallets is done by treating them as containers (two-stage, DYNLOAD), not by filling an item's free space.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: cavity, inside, hollow, frame, overhang space, under. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

'Load by objects' refers to objects 'of unspecified shape' but only counts them into packages (p.64).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: CAD, mesh, 3D model, arbitrary shape, free shape, STL. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

'Load by objects' fills a package with a number of objects 'of unspecified shape' (p.64), but by count, not by volume and weight.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: bulk, amorphous, liquid, volume-only, loose, unspecified shape. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: compress, soft, bulge, squeeze, tolerance, deform. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Partial form: STANDARD/LITE 'Load by objects' splits an incoming object count into packages of up to qt/b objects (optionally n per layer) by modular division, e.g. 14 objects at 8 per box give a box of 8 and a box of 6 (p.64-65). That is arithmetic with a single pack size, not a choice between several pack levels.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: load by objects, qt/b, objects per package, per layer, case, pack level, bundle, configuration. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Easy to remind values are: 1 (the package cannot be rotated), 3 (only the positions corresponding to rotations about the vertical axis), 63 (all positions allowed).”

https://www.packvol.com/packvol-en.pdf#page=24

“For a pallet, which should never be lying on its sides, you need ps = 3 (1+2).”

https://www.packvol.com/packvol-en.pdf#page=121

Per item (ps). All editions. Default for Excel import is 3, for manual entry 63 (configurable).

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.

“Easy to remind values are: 1 (the package cannot be rotated)”

https://www.packvol.com/packvol-en.pdf#page=24

“1 reference position: length, width, and height are aligned with length, width, and height of the container.”

https://www.packvol.com/packvol-en.pdf#page=120

ps=1 fixes the item in its reference orientation (length along the container length); ps=2 alone forces it crosswise.

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.

“When all positions are allowed you set ps = 63 (1+2+4+8+16+32).”

https://www.packvol.com/packvol-en.pdf#page=121

“32 the reference position 1 is “lying down” on the length side”

https://www.packvol.com/packvol-en.pdf#page=120

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.

“The parameter ps which describes the allowed positions is encoded with a single integer obtained by summing up the values in the following table for each allowed position.”

https://www.packvol.com/packvol-en.pdf#page=120

“For a freezer, that you want to just lay on a given side, you must force ps = 12 (8+4) or ps = 48 (16+32), according to the definition of the edges.”

https://www.packvol.com/packvol-en.pdf#page=121

Each lying orientation has its own bit, so e.g. ps = 1+2+4+8 allows upright and lying on the width side but never on the length side.

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).

“The parameter ps which describes the allowed positions is encoded with a single integer obtained by summing up the values in the following table for each allowed position.”

https://www.packvol.com/packvol-en.pdf#page=120

“Values between 1 and 63 in which a given package can be loaded.”

https://www.packvol.com/packvol-en.pdf#page=24

Equivalent positions of square faces are merged (p.43).

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.

The 'Default positions' preference (p.71) only pre-fills ps at data entry; it is not a solver preference.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: prefer, preferred position, default position, soft, orientation priority. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“fl floor-only The numerical value, between 1 and 63 defines the positions for which the constraint must be applied.”

https://www.packvol.com/packvol-en.pdf#page=24

“nf not at floor The value, between 1 and 63, defines the positions for which the package cannot stay at floor.”

https://www.packvol.com/packvol-en.pdf#page=24

Floor-only and not-at-floor are each set per orientation bitmask; clm=8 widens orientations for the top of a stack.

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 xs value can be defined with respect to each support face”

https://www.packvol.com/packvol-en.pdf#page=25

“g mxp01 max bearing weight position 1; null or zero value excludes the constraint”

https://www.packvol.com/packvol-en.pdf#page=106

Excel master-data import accepts only one global value for max stack, stack index and bearing weight (p.98); per-face values need the Constraint Panel or ODBC. Bearing weight is STANDARD/DYNLOAD.

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.

Positions are the six axis-aligned orientations only (p.120).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: angle, tilt, lean, inclined, diagonal, degrees. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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

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

No cylindrical item type.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: cylinder, drum, roll, upright, lying, barrel. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“The value, between 1 and 63, defines the positions for which packages of different type, or of same type but with a different orientation, cannot be placed on top of it.”

https://www.packvol.com/packvol-en.pdf#page=24

“To avoid positioning on the face you can impose a small non-zero value, for example 0.01.”

https://www.packvol.com/packvol-en.pdf#page=25

tp: all editions; bearing weight: STANDARD/DYNLOAD. The vendor documents both combinations for a 'two-dimensional' plan (p.25).

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.

“fl floor-only The numerical value, between 1 and 63 defines the positions for which the constraint must be applied.”

https://www.packvol.com/packvol-en.pdf#page=24

“Set as floor only The package should be placed only on floor.”

https://www.packvol.com/packvol-en.pdf#page=26

Per item and per orientation. Mutually exclusive with not-at-floor.

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.

“nf not at floor The value, between 1 and 63, defines the positions for which the package cannot stay at floor.”

https://www.packvol.com/packvol-en.pdf#page=24

“The field forces the package to stay above others.”

https://www.packvol.com/packvol-en.pdf#page=24

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.

“Relative stack - The xs value can be imposed on packages that have been assigned the constraint fl, nt, or nf and indicates how many packages of the same type and with the same orientation can be stacked one on top of the other.”

https://www.packvol.com/packvol-en.pdf#page=25

“the text box for the max stack (xs) is enabled only if the package has been marked as floor-only (fl), top-only (tp), or no-floor (nf)”

https://www.packvol.com/packvol-en.pdf#page=43

Per item and per support face; available only when fl, tp or nf is set. Counts same type and same orientation.

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.

“Absolute stack - The value xs minus one indicates the maximum number of packages that can be found below the package at hands. For example, if xs=3, a maximum of two packages can be found below it or, equivalently, the package will be in third position at most.”

https://www.packvol.com/packvol-en.pdf#page=25

“Introduced absolute stack constraint.”

https://www.packvol.com/changelog.html

Per item, activated with clm=16; added in 4.1.0 (Sep 2025). clm is a STANDARD/DYNLOAD feature ('Check of columnar order'). No container-wide tier cap.

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.

“The Max height - The value indicates the maximum height at which a package can be placed. The parameter can be set for each support face.”

https://www.packvol.com/packvol-en.pdf#page=25

“g mht01 max height position 1; null or zero value excludes the constraint”

https://www.packvol.com/packvol-en.pdf#page=106

Per item and per support face, in length units. The manual does not say whether the height refers to the package's bottom or top face. Disabled when floor-only is active.

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.

“Maximum weight that the package can bear.”

https://www.packvol.com/packvol-en.pdf#page=25

“Vertical ordering according to the maximum weight supported by each package (normal stress)”

https://www.packvol.com/versions.html

Per item and per support face (mw; g_mxp01-32). STANDARD and DYNLOAD, not LITE. Evaluated as pressure (see stacking-bearing-pressure). Whether the whole column above or only the directly resting item is counted is not stated. The 4.1.4 release (Jan 2026) fixed a calculation error.

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.

“The program requires a value of weight but converts it internally in the normal stress through division by the area of the supporting surface.”

https://www.packvol.com/packvol-en.pdf#page=25

“Hence, in a situation as depicted in figure, the object cannot be positioned above because, although its weight is lower than pm, it generates a stress higher than the maximum allowed.”

https://www.packvol.com/packvol-en.pdf#page=25

The user enters a weight; the engine divides it by the area of the supporting surface and compares the stress an upper item exerts over its contact area, so a light item on a small footprint can be refused (figure: 80 kg item refused on an item with mw 100). A limit can be set per support face. The exact formula (full face area versus contact area on each side) is described only in words and the figure. STANDARD/DYNLOAD.

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.

“Sometimes you want a “two-dimensional” loading plan in which no packages are stacked on top of others. You can achieve this in three different ways, by setting the following for all rows:”

https://www.packvol.com/packvol-en.pdf#page=25

“or c) pm = 0,01. Case c) requires the weight of the package to be indicated”

https://www.packvol.com/packvol-en.pdf#page=25

• Follows from documented behaviour rather than stated outright

The vendor states that a near-zero bearing weight on all rows yields a plan with no stacking at all, which implies the bearing check also applies when an item rests on units of the same item.

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

Counts when: A documented weight-ordering stacking rule.

“The rule enforces that no package with a lower stk value can be placed on top of it.”

https://www.packvol.com/packvol-en.pdf#page=27

“The stk and pm constraints impose vertical ordering and can compete. It is recommended not to use them at the same time.”

https://www.packvol.com/packvol-en.pdf#page=27

Not counted: only reachable by manual work or off-label use.

No weight-ordering rule. A user could rank items by weight outside the tool and enter the rank as the stacking index (lighter items getting higher stk), which the vendor does not document for this purpose.

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.

“The rule enforces that no package with a lower stk value can be placed on top of it.”

https://www.packvol.com/packvol-en.pdf#page=27

“It is possible to stow other packages on top of an item marked as nf, if these have a stacking index no lower than stk.”

https://www.packvol.com/packvol-en.pdf#page=24

Per item, optionally per face (g_stk01-32). All editions per the edition table. The vendor advises against combining it with bearing weight.

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.

“In addition to being an analysis tool, the panel allows you to define “exceptions” to the default stacking constraints”

https://www.packvol.com/packvol-en.pdf#page=47

“Each row defines a rule that allows a stacking otherwise forbidden, or forbids a stacking otherwise allowed.”

https://www.packvol.com/packvol-en.pdf#page=111

Per item pair and per lower/upper orientation; UI, Excel stack-matrix import or ODBC pv_stack. STANDARD/DYNLOAD.

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.

“clm=1 - “columnar order” The package should stay within the base provided by the lower package.”

https://www.packvol.com/packvol-en.pdf#page=29

“clm=2 - “face on face” The surfaces between lower and upper packages must coincide.”

https://www.packvol.com/packvol-en.pdf#page=29

Per item. STANDARD/DYNLOAD ('Check of columnar order').

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.

“Defines the default value of max overhang when a package is stacked on another. The allowed value is expressed as percentage of the edge dimension and varies from 0 to 49 (physical limit).”

https://www.packvol.com/packvol-en.pdf#page=35

“The program checks that the position of center of mass of each package lies within the base (physical equilibrium).”

https://www.packvol.com/packvol-en.pdf#page=29

Per container default (8% default) and per item override (overh). Support check can be switched off as a test setting (p.6). Per-item overh is STANDARD/DYNLOAD.

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.

The support-surface check is documented (p.6, p.29) but has no height-difference parameter.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: height difference, bridging, gap, level difference, uneven, support surface. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

'Open Top' is a container type, not an item shape.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: nest, nesting, nestable, top shape, open top item, increment. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Batch load (multiples of n per container) and pattern minimum object counts (p.66) exist, but no complete-stack or complete-layer rule.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: complete layer, full layer, complete stack, flat top, level top, remainder. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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).

“The program internally assigns a fictitious ds index to each type, so that identical packages are always grouped together, deciding the best sequence.”

https://www.packvol.com/packvol-en.pdf#page=47

“g block loadable check loading / unloading, [0] no, [1] yes.”

https://www.packvol.com/packvol-en.pdf#page=112

Per plan option 'Check loading / unloading for each package' (FI/LO Advanced dialog); needs no user destinations.

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.

“Numerical identifier of longitudinal ordering along depth (length axis).”

https://www.packvol.com/packvol-en.pdf#page=27

“The empty field allows the application to minimize the overlap, while the zero value completely prevents the mixing. In the latter case, one has a simple subdivision of the container in independent longitudinal sections.”

https://www.packvol.com/packvol-en.pdf#page=46

How it is done with general settings

1. Give every item of a group the same destination index ds (List grid, p.27; text labels are mapped to indexes, p.70). 2. Keep FI/LO ordering active (Destinations dialog, p.45). 3. Set max mixing to 0 so the container is split into 'independent longitudinal sections' per ds (p.46).

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

No separate group attribute; the destination index doubles as a group key and imposes a lengthwise order between groups. STANDARD/DYNLOAD.

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.

DYNLOAD families: in plt-r/plt-e rows with the same fml 'are optimized in the same container (multi-item pallet formation)' and in mbin they are 'optimised simultaneously and separately from the others' (p.54). Neither is stated as forbidding a group from spanning several units.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: group, family, same container, split, keep together, one container, set. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The priority list loads an index only after all lower indexes are completely loaded (p.45), and set load stops the run if the ratio cannot be found (p.23); neither leaves a whole group out instead of part of it.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: all or nothing, complete, whole order, partially loaded, set load, priority, left on the ground. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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).

“The empty field allows the application to minimize the overlap, while the zero value completely prevents the mixing. In the latter case, one has a simple subdivision of the container in independent longitudinal sections.”

https://www.packvol.com/packvol-en.pdf#page=46

“max mixing Allows you to limit the extension of the overlap of blocks of packages with different ds destinations within a maximum value”

https://www.packvol.com/packvol-en.pdf#page=46

Sections are lengthwise, one per destination index, ordered by ds; no physical divider or thickness is inserted. STANDARD/DYNLOAD.

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.

“Numerical identifier of longitudinal ordering along depth (length axis).”

https://www.packvol.com/packvol-en.pdf#page=27

“The empty field allows the application to minimize the overlap, while the zero value completely prevents the mixing. In the latter case, one has a simple subdivision of the container in independent longitudinal sections.”

https://www.packvol.com/packvol-en.pdf#page=46

How it is done with general settings

Route A: 1. Give each group its own destination index ds (p.27). 2. Set max mixing to 0 so each ds gets an independent longitudinal section (p.46); items of different groups then never share a section and cannot rest on each other. Route B: 1. Open the stack matrix (p.47). 2. For each pair of items from different groups use 'Deny shown stacking' (all positions) (p.48) or import the pairs with a negative g_status (p.100, p.111).

• Combination of general settings, assembled by the auditor from documented parts
• Relies on a setting other rows also use; they may not all work at once

Route A also forces a lengthwise order between groups; route B works item pair by item pair (no group or class code). STANDARD/DYNLOAD.

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.

“In this case, the constraint mc = n requires that a package be loaded into the nth container in the list.”

https://www.packvol.com/packvol-en.pdf#page=27

“To force, enter the string @=n1=n2... in the cell. To exclude, enter the string #=n1=n2... in the cell.”

https://www.packvol.com/packvol-en.pdf#page=27

How it is done with general settings

1. Use a fixed-list method (seq-f or fst-f) so containers are numbered in advance (p.27, p.53). 2. Give the items to be kept apart different matching codes mc = n, so each is tied to a different container (p.27).

• Combination of general settings, assembled by the auditor from documented parts
• Only in some editions, plans, methods or equipment types

Works only with a fixed container list (the mc constraint is removed under auto-add, p.28). In DYNLOAD mbin, force/exclude acts on container types, not on sharing.

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.

Padding space (spL/spW/spH) keeps a clearance around an item against all neighbours (see positioning-clearance), not between chosen items or classes. The stack matrix bans direct contact only.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: separation, distance, apart, segregation, not above, padding, spacing. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The only 'hazardous' mention is in the licence text (p.123).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: dangerous, hazardous, hazmat, IMDG, ADR, class, segregation. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Weight (Max Load) is the only per-container sum that can be capped.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: value, price, points, piece count, maximum number, sum, cap. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

DYNLOAD plt-e builds single-reference pallets first ('Mono article, without reuse'), but remainders then go to mixed loading; it is not a cap on distinct items per unit.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: distinct, number of items, number of types, single reference, mono article, SKU per container. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“In each container, items with the same alphanumeric label must be in a defined ratio.”

https://www.packvol.com/packvol-en.pdf#page=23

“The program calculates the ratio automatically from the item with minimum quantity.”

https://www.packvol.com/packvol-en.pdf#page=23

Ratio taken from the input quantities. The run stops if the ratio cannot be met. STANDARD/DYNLOAD.

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.

“Packages are loaded in each container in multiples of the bat number.”

https://www.packvol.com/packvol-en.pdf#page=23

“Batch Load - ability to load packages in multiples of an assigned number”

https://www.packvol.com/versions.html

Per item (bat). A dialog handles quantities that are not a multiple (p.50). STANDARD/DYNLOAD.

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.

“To modify a verified solution while keeping the position of the packages of the current solution unchanged, use Solution → Start from current command.”

https://www.packvol.com/packvol-en.pdf#page=61

“load some packages manually and then request the positioning of the others automatically”

https://www.packvol.com/packvol-en.pdf#page=61

All editions. Quantities can only be increased. 'Re-optimize selected' (STANDARD/DYNLOAD) re-plans chosen containers while others stay; DYNLOAD fml = -2 leaves preformed packages unchanged.

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.

“insert the coordinates of the control point L, W and H in the spin controls and click on the tool New point [N]”

https://www.packvol.com/packvol-en.pdf#page=60

“load some packages manually and then request the positioning of the others automatically”

https://www.packvol.com/packvol-en.pdf#page=61

Not counted: only reachable by manual work or off-label use.

Exact coordinates can be typed only inside the manual 3D session, then frozen with Start from current. No input field for positions in the Excel or ODBC input tables (pv_geom is output only); the XML exchange format is not public.

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.

“Rsp, Fsp spaces not allowed Prevents placement of the package in rear (for a length Rsp) or at the front (for a length Fsp) of the container.”

https://www.packvol.com/packvol-en.pdf#page=31

“The two text boxes from front of the container and from rear of the container set the values of the unavailable spaces.”

https://www.packvol.com/packvol-en.pdf#page=44

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

Lengthwise bands only; no sideways or named zones. Per item.

Correction: Uses the dedicated per-item Rsp/Fsp control.

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.

“Rsp, Fsp spaces not allowed Prevents placement of the package in rear (for a length Rsp) or at the front (for a length Fsp) of the container.”

https://www.packvol.com/packvol-en.pdf#page=31

“The command Settings → Unusable Section opens a dialog where you enter the extension of the unusable section with the text boxes from – to.”

https://www.packvol.com/packvol-en.pdf#page=51

Rsp/Fsp ODBC fields are marked UNUSED (p.107).

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.

“Rear-Front the program places the packages starting from the rear of the container, filling as much as possible a “slice” upward, and then continues to the front of the container.”

https://www.packvol.com/packvol-en.pdf#page=34

“Bottom-Top The program places the packages starting from the bottom of the container, filling the base, and then goes upward.”

https://www.packvol.com/packvol-en.pdf#page=34

Per container (Pack combo; g_bottom_top).

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-Top The program places the packages starting from the bottom of the container, filling the base, and then goes upward.”

https://www.packvol.com/packvol-en.pdf#page=34

“the height of the load is kept as low as possible, by maximizing the base as in Bottom-Top ordering”

https://www.packvol.com/packvol-en.pdf#page=34

Plan/container scope (fill pattern), 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.

“If you set tpl=1 the program checks that, when the package is loaded with the long side aligned with the short side of the container, there is enough space for the complete rotation of the package. The constraint applies only to closed containers and is disregarded for containers with overflow or rack/flat type.”

https://www.packvol.com/packvol-en.pdf#page=28

“Maximum depth of a box with respect to packages that support it.”

https://www.packvol.com/packvol-en.pdf#page=29

Forklift check: closed containers only; STANDARD/DYNLOAD. The geometry of 'depth' is not defined.

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.

“Sometimes it is necessary to leave free space around a package (for example, due to anchor hooks).”

https://www.packvol.com/packvol-en.pdf#page=31

“If spH=-1 (or otherwise negative), the orientation instead refers to the container (“absolute”, see figure), regardless of the position of the package.”

https://www.packvol.com/packvol-en.pdf#page=31

Per item: spL and spW padding along length and width, relative to the package or absolute to the container. STANDARD/DYNLOAD ('Check of separation between adjacent packages').

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.

“When applied, the program checks that the back of the package is resting against the rear wall of the container or against another package. Stiffness is a measure of how strong must be the rule, whereas Check width-axis enforces the control along container short side.”

https://www.packvol.com/packvol-en.pdf#page=47

“g back face perc face contact percentage. The values is applied in case g back equil is active.”

https://www.packvol.com/packvol-en.pdf#page=113

Per plan; minimum face contact default 30%.

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.

“The text field Max Load, having decimal values, allows you imposing the maximum load of the container.”

https://www.packvol.com/packvol-en.pdf#page=34

“g maxLoad container max load; null or a negative value excludes the constraint”

https://www.packvol.com/packvol-en.pdf#page=109

Per container type, all editions; pallets are modelled as containers and use the same field. Can be disabled as a test setting.

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.

No compartments exist; the only split limit is the lengthwise load profile (next row).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: compartment, deck, zone, section weight, part. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“The program allows you to assign a maximum load for different sections of the container, up to a maximum of five sections.”

https://www.packvol.com/packvol-en.pdf#page=35

“The program can impose a limit on the maximum load of each container, with uneven distribution between user-defined “sections” if needed.”

https://www.packvol.com/rules.html

Up to 5 lengthwise sections per container type, each with length and maximum weight; Max Load becomes their sum. All editions ('Unequal load distribution').

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.

“To ensure this, the application checks that in every possible “strip” of length L, the weight W of the strip satisfies the relationship W/L ≤ weight/length”

https://www.packvol.com/packvol-en.pdf#page=34

“If l exceeds the base length of the package, other packages are spaced appropriately.”

https://www.packvol.com/packvol-en.pdf#page=35

Per container; requires Max Load active. All editions ('Control of linear density and average load on container floor').

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).

No axle model anywhere in the manual, feature pages or changelog. rules.html's 'ascending order with respect to the container axle' refers to destination ordering along the length axis, not to axle loads.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axis, kingpin, fifth wheel, drawbar, tractor, trailer, tare, gross, bridge formula, permit, jurisdiction, legal limit. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

No axle model anywhere in the manual, feature pages or changelog. rules.html's 'ascending order with respect to the container axle' refers to destination ordering along the length axis, not to axle loads.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axis, kingpin, fifth wheel, drawbar, tractor, trailer, tare, gross, bridge formula, permit, jurisdiction, legal limit. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

No axle model anywhere in the manual, feature pages or changelog. rules.html's 'ascending order with respect to the container axle' refers to destination ordering along the length axis, not to axle loads. A container tare exists only for DYNLOAD primary containers (pallets/crates) converted to packages.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axis, kingpin, fifth wheel, drawbar, tractor, trailer, tare, gross, bridge formula, permit, jurisdiction, legal limit. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

No axle model anywhere in the manual, feature pages or changelog. rules.html's 'ascending order with respect to the container axle' refers to destination ordering along the length axis, not to axle loads.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axis, kingpin, fifth wheel, drawbar, tractor, trailer, tare, gross, bridge formula, permit, jurisdiction, legal limit. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

No axle model anywhere in the manual, feature pages or changelog. rules.html's 'ascending order with respect to the container axle' refers to destination ordering along the length axis, not to axle loads.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axis, kingpin, fifth wheel, drawbar, tractor, trailer, tare, gross, bridge formula, permit, jurisdiction, legal limit. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“The rule forces the solution to have the center of mass of the load included in a target rectangle”

https://www.packvol.com/packvol-en.pdf#page=35

“The target rectangle is defined by the four values DL (maximum and minimum) and DW (maximum and minimum), expressed as a percentage of the length and width of the container.”

https://www.packvol.com/packvol-en.pdf#page=35

Per container, integer percentages 0-100 of the length; package weights required. All editions. The ODBC value 'forbid shift' (g_enforce_cm = 3) is not explained.

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.

“The target rectangle is defined by the four values DL (maximum and minimum) and DW (maximum and minimum), expressed as a percentage of the length and width of the container.”

https://www.packvol.com/packvol-en.pdf#page=35

“g c of mLowW lower percentage limit for the center of mass along g width axis”

https://www.packvol.com/packvol-en.pdf#page=109

Same rectangle rule, width limits in % of container width. All editions.

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.

“No control is operated in the vertical direction.”

https://www.packvol.com/packvol-en.pdf#page=35

The centre-of-mass rule covers length and width only.

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.

DYNLOAD 'Center load on container base' centres the load after calculation (p.37), but it is described as a geometric centring, not as balancing weight. The centre-of-mass rule is a hard window. 'Side shift' is undescribed beyond one sentence.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: balance, centre, center load, even, distribute, shift, side shift. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The support check uses 'the position of center of mass of each package' (p.29), but no input sets it; it is implicitly the geometric centre.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: center of mass of each package, offset, eccentric, off-centre, item centre of gravity. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Numerical identifier of longitudinal ordering along depth (length axis).”

https://www.packvol.com/packvol-en.pdf#page=27

“When FI/LO is active, the program always checks that no packages with lower ds indexes are “in front of” or “above” others with higher indexes”

https://www.packvol.com/packvol-en.pdf#page=46

Per item ds (integer or named string mapped by first occurrence). STANDARD/DYNLOAD.

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.

“A package is loaded only after complete loading of all packages with lower ds value.”

https://www.packvol.com/packvol-en.pdf#page=45

“minimum number: in case you input a positive value, the solver tries to load at least this number of packages for the given item.”

https://www.packvol.com/packvol-en.pdf#page=27

Applies with a fixed number of containers; min priority is not applied by methods that load the whole list except sqn-a (p.45). The minimum quantity is soft ('tries'; warns if not met). STANDARD/DYNLOAD ('Loading of the packages according to priority list').

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.

“A package is loaded only after complete loading of all packages with lower min value.”

https://www.packvol.com/packvol-en.pdf#page=45

“It is applied in the case of solutions with fixed number of containers.”

https://www.packvol.com/packvol-en.pdf#page=27

How it is done with general settings

1. Use a fixed number of containers (seq-f/fst-f, p.53). 2. Enable 'min index as priority rule' in FI/LO Advanced (p.45). 3. Give required items low min values and fill items the highest value; fill items are then loaded only after all required items are completely loaded (p.45).

• Combination of general settings, assembled by the auditor from documented parts
• Only in some editions, plans, methods or equipment types

No optional flag. Under auto-add methods the priority index is not applied (except sqn-a), so fill items could trigger another container.

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.

“Numerical identifier of longitudinal ordering along depth (length axis).”

https://www.packvol.com/packvol-en.pdf#page=27

“according to a priority rule in ascending order with respect to the container axle, a rule needed for example in presence of different deliveries”

https://www.packvol.com/rules.html

Per item destination ds; per plan mode. Priority within a stop can be added with the min index (p.45). STANDARD/DYNLOAD.

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.

“When FI/LO is active, the program always checks that no packages with lower ds indexes are “in front of” or “above” others with higher indexes, but no check is performed in lateral direction.”

https://www.packvol.com/packvol-en.pdf#page=46

Hard rule for front and above. Gap: no lateral check, so blocks of different stops can stand side by side (the vendor says this 'is not always acceptable'); max mixing limits it.

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.

“max mixing Allows you to limit the extension of the overlap of blocks of packages with different ds destinations within a maximum value”

https://www.packvol.com/packvol-en.pdf#page=46

“The empty field allows the application to minimize the overlap, while the zero value completely prevents the mixing.”

https://www.packvol.com/packvol-en.pdf#page=46

Per plan length value; empty = minimise, 0 = clean split, positive = cap.

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.

Only one destination index per item.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: pickup, pick-up, collection, origin, loading stop, route. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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).

“Keep order between containers The packages are ordered by considering the ordering between consecutive containers.”

https://www.packvol.com/packvol-en.pdf#page=45

“Absolute ordering of packages in case of multi-container solutions”

https://www.packvol.com/versions.html

STANDARD/DYNLOAD.

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.

With ds as a priority, a destination is loaded only after all lower ones are complete (p.45), but nothing prevents the last destination loaded from being partial.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: complete, partially loaded, whole destination, all or nothing, left on the ground. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The only date field is the report header date (pv_job.g_date).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: date, due, deadline, shipping date, storage date, days. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Base height Lower external vertical dimension, the thickness of the base for a pallet or the plinth for a crate.”

https://www.packvol.com/packvol-en.pdf#page=36

“the Load extension option takes as height of the package the height of the load (pallet type)”

https://www.packvol.com/packvol-en.pdf#page=36

• Evidence is a label in a screenshot
• Only in some editions, plans, methods or equipment types

DYNLOAD: a pallet is a container with base height, tare and nominal height. In STANDARD the pallet base in Additional data is 'used for visualization purposes only' (p.36); 'load by objects' plt packages carry a base height hbase (p.64).

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.

“With the plt-r and plt-e methods the application optimizes each package in the input list, “row by row” (or by groups of rows controlled by fml), looking for the best possible saturation on the container types available in input.”

https://www.packvol.com/packvol-en.pdf#page=54

“0 or blank With the plt-r and plt-e methods the row is optimized individually (single-item pallet formation).”

https://www.packvol.com/packvol-en.pdf#page=54

DYNLOAD. One pattern (the best found) per item; no list of alternative patterns.

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.

“The pattern is built in manual session, reproducing a known scheme, for example that of an automatic palletizer.”

https://www.packvol.com/packvol-en.pdf#page=66

“If the field is validated with the name of a pattern the formation of single-reference containers is performed by applying the palletizing scheme. Pattern and item size must be consistent.”

https://www.packvol.com/packvol-en.pdf#page=54

DYNLOAD ('Ability to manage predetermined single-reference load models'). No pattern-style choice (block, pinwheel) or alternate-layer rotation setting.

The planner builds pallets that carry several different item types.

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

“> 0 or string With the plt-r and plt-e methods, the rows with the same value of the fml parameter are optimized in the same container (multi-item pallet formation).”

https://www.packvol.com/packvol-en.pdf#page=54

“The remaining packages are then optimized in mixed loading.”

https://www.packvol.com/packvol-en.pdf#page=54

DYNLOAD. Mixed pallets are built by the general 3D solver (pallets are containers), not in a stated layer or column mode. Any edition can load several item types onto a pallet defined as a container.

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.

“Max over length assumes the value as the maximum overhang with respect to the dimensions of the base. The “x 2” label reminds that the values are applied symmetrically.”

https://www.packvol.com/packvol-en.pdf#page=37

DYNLOAD, per primary container type; length and width values.

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.

“Center load on container base At end of calculation, load is centered on container base.”

https://www.packvol.com/packvol-en.pdf#page=37

DYNLOAD Additional data.

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

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

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: slip sheet, interlayer, layer pad, tier sheet, separator, cardboard. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“All methods take into account the “family” fml parameter of the Box tab to section the input list into independent calculations.”

https://www.packvol.com/packvol-en.pdf#page=53

“> 0 or string With the plt-r and plt-e methods, the rows with the same value of the fml parameter are optimized in the same container (multi-item pallet formation).”

https://www.packvol.com/packvol-en.pdf#page=54

DYNLOAD. Families are calculated independently, so items of different families do not share a pallet. fml -1 sends an item only to mixed loading; -2 excludes it.

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.

DYNLOAD two-stage loading needs a user step between runs: optimise the first stage, then 'Convert to packages' and optimise again (p.65). That passes pallet-carry-over, not this row. The integrable pv_exec.g_stage field is 'RESERVED for future developments' (p.112).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: two-stage, multi-stage, convert to package, second stage, g stage, single run. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“This feature responds to a commonly used scheme, which requires a “first stage” where the packages are loaded into containers (“primary” in the program terminology, for example boxes on pallets), and a subsequent “second stage” in which these are further loaded into larger containers”

https://www.packvol.com/packvol-en.pdf#page=65

“The conversion is done with the Solution → Convert → Convert to package command”

https://www.packvol.com/packvol-en.pdf#page=65

DYNLOAD. Converted pallets carry external dimensions, tare, base height and fixed or load-derived height into the next stage; 'Convert to containers' goes the other way.

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.

“Ability of optimization at “multiple steps” (objects in boxes → boxes on pallets → pallets in container)”

https://www.packvol.com/versions.html

“Assign as first stage records the current solution as the first stage.”

https://www.packvol.com/packvol-en.pdf#page=9

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

DYNLOAD. Stages are chained by repeated conversion; each stage is a separate run.

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.

“The remaining packages are then optimized in mixed loading. In the case plt-r, before starting the optimization in mixed loading, the program checks if the packages can be loaded in the nominal volume of the containers formed.”

https://www.packvol.com/packvol-en.pdf#page=54

“With the plt-e method the step is skipped, and the containers formed in the initial step remain with the assigned items.”

https://www.packvol.com/packvol-en.pdf#page=54

DYNLOAD.

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.

“Constraints for second stage The grids replicate those of the Package manager and allow you to assign the constraints of the package obtained by conversion of the container.”

https://www.packvol.com/packvol-en.pdf#page=37

“Q integer positions allowed after conversion (only for [cnt] rows)”

https://www.packvol.com/packvol-en.pdf#page=101

DYNLOAD, per primary container type: all package rules (positions, floor/top-only, stacking, bearing) apply to the converted pallet. No minimum top-fill rule.

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.

“The option “Apply the rule and subtract ... to container height” adapts the height of the primary container to the height of the secondary container in which the object will be placed.”

https://www.packvol.com/packvol-en.pdf#page=73

“The assignment of the secondary container, other than to speed up the conversion operations, allows to adapt the nominal dimensions of the containers of the first stage.”

https://www.packvol.com/packvol-en.pdf#page=39

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

DYNLOAD; requires a secondary container. Adapts to the vehicle height, not to the space above a lower tier.

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.

“a) maximize the volumetric occupation of the loading list in a predetermined number of containers”

https://www.packvol.com/packvol-en.pdf#page=52

Measure: volume by default (weight optional). All editions (LITE: one container).

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.

“The program optimizes the volumetric occupation of the container (default option), or the weight loaded in the container. It applies only to “base” methods.”

https://www.packvol.com/packvol-en.pdf#page=55

“g cost function cost function, [0] by volume, [1] by weight.”

https://www.packvol.com/packvol-en.pdf#page=112

Base methods only (seq/fst).

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.

“Using the same number of containers, it is often preferable to have a homogeneous distribution of the load among the containers. The command Tools → Redistribute Load meets this need.”

https://www.packvol.com/packvol-en.pdf#page=55

“In the case of an optimal multi-container solution, optimizes again the solution by placing the packages in the most uniform possible way among the various containers.”

https://www.packvol.com/packvol-en.pdf#page=8

• Follows from documented behaviour rather than stated outright

Post-optimisation command keeping the container count.

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.

“Don’t fix package qty in advance Starts the session without assigning the number of packages, which can then be placed at will.”

https://www.packvol.com/packvol-en.pdf#page=56

“paste of packages takes place only for those objects that satisfy all constraints”

https://www.packvol.com/packvol-en.pdf#page=57

Not counted: only reachable by manual work or off-label use.

Only in the manual solver: the user places or pastes extra units by hand. No automatic cube-out, maximum-sets or top-up mode is documented; the integrable 'g_max_exec_time_ms = 0' only estimates a container count (p.113).

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.

“Execution time Maximum execution time, expressed in seconds for Standard version, milliseconds for Dynload version.”

https://www.packvol.com/packvol-en.pdf#page=54

“Random start The optimization begins from a random choice. This allows you exploration of different possible solutions.”

https://www.packvol.com/packvol-en.pdf#page=55

Also stop/improve/continue on optimality, 'Improve solution' restart, thread count (DYNLOAD) and fast vs sequential methods. The seed makes runs reproducible but is labelled a test option.

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.

One solution per run. Re-optimising or random start lets the user explore configurations one at a time (p.55).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: alternative, several solutions, compare, options, re-optimize, random start. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Every rule is set per item row. 'Set parameters' applies a value to rows the user selects in the grid (p.26, p.32); the database filter (SQL LIKE on code or description, p.76) selects records to load, not rule targets.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: rule, condition, filter, if, threshold, greater than, attribute. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The 'other' secondary description is for reports only (p.22, p.117). The DYNLOAD family label fml is a free text that drives built-in rules (sectioning, pallet grouping), which the definition note scores under the between-items rows.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: custom field, user field, other, optional description, attribute, label, family. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The stack matrix is item-to-item (with per-orientation exceptions and a 90-degree 'conjugate rule'), keyed by item ID in pv_stack; there is no class code. The stacking index stk is an ordered index, not a matrix. Passes stacking-item-pair instead.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: class, category, stack matrix, stack code, group, pv_stack. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: compatibility, combination, incompatible, class, same container, matrix. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: sum, total, cap, limit per container, value, custom quantity. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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 Current panel carries the dimensions of the container and parameters for the positioning of the load. If the solution has more than one container type, the panel becomes active once the type is assigned.”

https://www.packvol.com/packvol-en.pdf#page=33

“Constraints for second stage The grids replicate those of the Package manager and allow you to assign the constraints of the package obtained by conversion of the container.”

https://www.packvol.com/packvol-en.pdf#page=37

Per container type: fill pattern, default max overhang, max load and load profile, density mode, centre-of-mass window, side shift, open-top/rack type. Item rules and FI/LO settings are per plan, not per container.

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.

“It’s opened via the menu command Tools → Open Stack Matrix , and shows the stack rules between pairs of packages resulting from the setting of constraints fl, tp, stk and xs..”

https://www.packvol.com/packvol-en.pdf#page=47

“The combination of constraints is performed by simple addition. For example, clm=5 (1+4) enforces the two constraints clm=1 and clm=4 simultaneously.”

https://www.packvol.com/packvol-en.pdf#page=30

Top-only, max stack, stacking index, bearing weight, columnar flags and stack-matrix exceptions apply together. The vendor advises against combining stk with bearing weight.

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 objective per run (volume, weight, or in mbin capacity or cost). 'Enable max mixing' reduces destination overlap 'with the same volumetric occupancy' (p.46), a fixed built-in secondary goal rather than a user-ordered set of objectives.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: objective, cost function, secondary, priority, weight, tolerance, then. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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 DLL exposes only connect/execute/logging methods (pvDLL page). Vendor-side customisation exists: 'Possibility to request changes and extensions of functionality' (versions.html, STANDARD/DYNLOAD) and pv_job.g_customxml 'input parameters for custom versions' (p.104).

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: script, plug-in, plugin, callback, custom, extension, API, customxml. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“Enable max mixing The program tries, as far as possible and with the same volumetric occupancy, to reduce the interpenetration of blocks with different ds parameter.”

https://www.packvol.com/packvol-en.pdf#page=46

“The empty field allows the application to minimize the overlap, while the zero value completely prevents the mixing.”

https://www.packvol.com/packvol-en.pdf#page=46

Destination mixing can be a preference (empty value: minimise) or a hard cap (0 or a positive length). The minimum quantity per item is also soft ('tries', p.27).

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.

“g posID position of the item according to the application encoding”

https://www.packvol.com/packvol-en.pdf#page=118

“The origin of the coordinates is located at the rear of the container.”

https://www.packvol.com/packvol-en.pdf#page=121

Per package: container index, orientation code (1-32), low-corner coordinates and edges (ODBC pv_geom; Excel per-container sheet). Origin at the rear, 'low' vertex nearest the origin.

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.

“Print instructions For each block the document reports a summary of weight and volume of the block, orientation of the package, position and extent of the block, label position if defined.”

https://www.packvol.com/packvol-en.pdf#page=92

“0x0100 STEP BLOCK - step images by blocks”

https://www.packvol.com/packvol-en.pdf#page=115

LITE: single container only; all-container export STANDARD/DYNLOAD.

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.

“shows in tabular form the percentages of load weight, used volume, and number of loaded packages”

https://www.packvol.com/packvol-en.pdf#page=40

“The grid lists the association between the realized container (“bin”) and the number (“pk”) of the package type (“code”) loaded in that bin.”

https://www.packvol.com/packvol-en.pdf#page=62

Output tab (not LITE), distribution grid and report, container statistics, Excel per-container sheets.

The plan reports the floor length used or left free (loading metres).

Counts when: A documented loading-metre, length-used or end-gap figure.

The Weight/Density tool reports the 'linear dimension' of a section the user marks (p.63), and empty spaces can be measured, but no length-used or free-length figure is documented.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: loading metre, length used, free length, linear dimension, remaining space. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

The plan lists the items that could not be loaded, with quantities.

Counts when: A documented not-loaded or cut list.

“If the option is set, the report displays, besides the list of loaded items, a list of all packages left on the ground.”

https://www.packvol.com/packvol-en.pdf#page=72

“→ Save unloaded packages saves the list of packages that are not been loaded.”

https://www.packvol.com/packvol-en.pdf#page=5

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).

Reasons appear only in the manual solver ('A short message ... shows the reason that prevents the insertion', p.58) and in a pre-run dialog for packages larger than the container (p.50). No reason per unplaced item after an automatic run.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: reason, why, error, warning, not loaded, left on the ground. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

The centre of mass is shown only as a crosshair in the view (p.12); no numeric value in any report or output table.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: center of mass, centre of gravity, crosshair, report, coordinates. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

No axle model.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: axle, axle load, kingpin, weight per axle. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“The program displays a summary on linear dimension, volume, loaded weight, and the load distribution per unit length.”

https://www.packvol.com/packvol-en.pdf#page=63

“planar layout [static] A single view from above is generated, with progressive numbering of the stacked packages. The layout shows the summary view and the load distribution.”

https://www.packvol.com/packvol-en.pdf#page=90

Interactive Weight/Density tool for a user-chosen section; the PDF planar layout also shows 'the load distribution' (content not detailed).

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.

Tare exists only for DYNLOAD primary containers converted to packages; no gross-mass output is documented.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: gross, VGM, total weight, tare, container weight. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.

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.

“tot number of packages per destination”

https://www.packvol.com/packvol-en.pdf#page=62

“pk number of loaded packages per destination”

https://www.packvol.com/packvol-en.pdf#page=62

Destination grid with totals and loaded counts per destination; packages of a destination can be hidden from the view; PDF can colour by destination. No per-stop contents list or per-stop views in the report are described.

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.

“After selection, the box is displayed with green color if the position is valid, with red color if any rule is violated.”

https://www.packvol.com/packvol-en.pdf#page=57

“A short message displayed in the right pane of the status bar and in the view of the load shows the reason that prevents the insertion.”

https://www.packvol.com/packvol-en.pdf#page=58

Not counted: part of the pass condition is not shown.

Manual edits are checked against all rules at insertion (can be disabled). Drag mode checks only collisions and bounds. No violations list for a whole imported plan.

The plan identifies empty voids above a set size (for example for dunnage or airbags).

Counts when: Documented void or empty-space output.

“The tool Report → Measurements → View empty spaces ( ) allows you to visualize the empty spaces.”

https://www.packvol.com/packvol-en.pdf#page=63

“Use the “min Dim.” text box to control the spaces to visualize.”

https://www.packvol.com/packvol-en.pdf#page=63

Interactive view with a minimum-size filter; not part of exported reports.

The plan reports the cost of the equipment used, and the cost allocated to each item.

Counts when: Documented plan cost output.

Container cost is an input to DYNLOAD mbin only; no cost appears in any documented output.

Where we looked

Searched the full text of User Guide 4.1.4 (https://www.packvol.com/packvol-en.pdf, all 123 pages, pdf.js extraction) for: cost, price, freight, total cost, report. Also read in full rules.html, features.html, index.html, versions.html (edition comparison table), changelog.html (1.9 to 4.1.4, Jan 2026), tutorials.html, tutorial3.html and pvDLL/index.html.