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.

“A container is defined by an internal length, width, height and payload but does often have additional properties.”

https://cargo-planner.com/docs/introduction/

“L: Inside length in meters”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Preset library plus custom containers. Limit: 40 000 loadable cargoes per calculation (Introduction).

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.

“Use the Components tab in the container editor to model the geometry that lives inside a container: corner posts, structural frames, internal walls, mezzanine floors, and arbitrary blocks that occupy space or provide a loading surface. The load plan treats each component as a solid shape the solver must place cargo around.”

https://cargo-planner.com/docs/equipment/hold-parts/

“X, Y, Z | Position of the part inside the container, measured from the front-left-floor corner.”

https://cargo-planner.com/docs/equipment/hold-parts/

Stacking on top of an obstruction is controlled per component: "Not stackable" and "Max load" fields. Equipment-level (container editor), not per plan; Equipment Editor permission needed for library equipment.

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.

“Every component uses the same six-field layout. The title of each card shows the position number and the component’s raw type in upper case (`1 - WALL`, `2 - CORNER`, `3 - FLOOR`).”

https://cargo-planner.com/docs/equipment/hold-parts/

“Custom | Custom part”

https://cargo-planner.com/docs/equipment/hold-parts/

Any number of components per container is implied by the numbered cards; no stated maximum. Each has free L/W/H and X/Y/Z unless anchored with Stick to.

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.

“max_height: Max loading height allowed of cargoes in m”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“You can select multiple container types for each load plan and Cargo-Planner will try to select the most appropriate one to fit your cargoes. Do adjustments on the fly like Max Loading Height, Payload, Max Volume etc...”

https://cargo-planner.com/features/equipment/

Max loading height is a separate field from inside height H and can be set per load plan in Setup ("change some container properties on the fly", Creating a load plan). The custom rule Max height with an empty selector ("If left empty this rule will apply to all items") is a second, explicit ceiling. Plan-level Max stacking height also exists but lets a single tall item exceed it. Most worked examples use max loading height to raise the limit on open-top equipment.

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.

“Use the Decks card on the Road tab to describe trailers with raised loading platforms at the front or rear — step-decks, low-boys, drop-decks and any custom shape where the deck height changes along the length of the trailer.”

https://cargo-planner.com/docs/equipment/decks/

“Length | How far the raised area reaches from that end of the trailer.”

https://cargo-planner.com/docs/equipment/decks/

At most two floor steps (front deck and rear deck), each spanning the full width; mezzanines via floor components. Road tab of the full container editor only.

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.

“Use the Contours tab to describe corners of a container that are not perfect right angles: the sloped nose of a trailer, the curved top of a ULD, the tapered sides of a specialty flatrack. Each contour is a triangular cut into one corner of the container envelope. The load plan treats the cut as unusable space.”

https://cargo-planner.com/docs/equipment/contours/

“Front and rear contours use Length; side contours use Width.”

https://cargo-planner.com/docs/equipment/contours/

Maximum eight contours, one triangular cut per corner; available on every equipment type.

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.

“A container can have a maximum of eight contours — one at each corner (front top, front bottom, rear top, rear bottom, and the four equivalents on the two long sides). Rotate the 3D preview on the right to see all of them.”

https://cargo-planner.com/docs/equipment/contours/

“The four cards on the tab correspond to the four faces of the container. Each card holds two sub-groups:”

https://cargo-planner.com/docs/equipment/contours/

• Follows from documented behaviour rather than stated outright

One container definition holds front/rear contours (height change along the length) and side contours (non-rectangular cross-section) at the same time, and the planner treats every cut as unusable space. Decks (Road tab) can also be combined with contours on a trailer, but no page shows that combination. Shapes are limited to one triangular cut per corner.

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.

“Each contour is a triangular cut into one corner of the container envelope. The load plan treats the cut as unusable space.”

https://cargo-planner.com/docs/equipment/contours/

“The fair question about all of this is how close a triangle is to a curve, and whether the answer means you should hold a margin back under the crown.”

https://cargo-planner.com/guides/building-a-uld-for-mixed-cargo/

• Follows from documented behaviour rather than stated outright

The contour is a chamfer defined by two lengths (a straight slope, not a stepped approximation). Curves are approximated by the single triangle; the vendor states curves are not modelled ("Curves themselves are a hard problem").

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.

“Set Builder is the tool for defining a piece of equipment that contains more than one container: an aircraft with cargo bays, a cargo vessel with holds, a road train with a tractor and trailers, a warehouse with numbered bays. The load plan then treats the whole thing as one unit and places cargo across its parts according to a fixed layout.”

https://cargo-planner.com/docs/equipment/set-builder/

“A floor component placed at a non-zero Z acts as a tween deck, and cargo above and below is planned around it.”

https://cargo-planner.com/docs/equipment/breakbulk-vessels/

Set Builder is Enterprise-only ("Set Builder is an Enterprise subscription feature"). The components route (mezzanine floor, internal wall) is on the general container editor with no tier restriction stated, so the row passes on that route for all plans.

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.

“If the containers you have selected also have the door property set which is smaller than the cargoes you will also receive this message.”

https://cargo-planner.com/docs/help/faq/

“door: Door info”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Door W/H per container (HoldDoor). Door specifications on Set Builder groups are explicitly not enforced: "Door dimensions are stored with the set but are not currently enforced by the load calculation."

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.

“longside: If the door is at longside of container”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“Each group can carry a door specification — width, height, and an At longside flag — for future-facing use. Door dimensions are stored with the set but are not currently enforced by the load calculation.”

https://cargo-planner.com/docs/equipment/set-builder/

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

A container door can be flagged "at longside" in the API, but no source says this changes how the load is built. load_direction has no described values. Loading style Auto picks front-to-back or bottom-up by equipment type, which is a fill direction, not an access face. Must touch side (custom rule) can put selected items at a side, but that is not a per-space access face.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for door, longside, side door, loading face, access, load direction, rear, top loading. Checked HoldDoor, load_direction (string, no values described), load_style and the Auto loading style description in Primary settings.

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.

“No roof | Removes the ceiling | Cargo may extend upward past the container height, capped only by Max height if set.”

https://cargo-planner.com/docs/equipment/open-containers/

“Open sides allow 33% out-of-gauge loading by default. To allow more, or less, set a Max length, Max width or Max height on the equipment — the directional limits described for out-of-gauge cargo apply here.”

https://cargo-planner.com/docs/equipment/open-containers/

Default 33% when no limit is set. Extendable trailers (Max Length With Extension) are a separate mechanism.

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.

“If all rows have a quantity set, then the tool loads the cargoes in as many containers as is necessary”

https://cargo-planner.com/docs/cargo/cargo-properties/

“This view contains all the containers needed to load the provided cargoes. In the top there is a summary containing how many and what type of containers are used”

https://cargo-planner.com/docs/creating-a-loadplan/

No limit on added units documented other than the optional caps (max number of containers, per-type qty) and 40 000 cargoes per calculation.

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

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

“If more than one container type is available here then the tool will try to determine which one(s) is most suitable.”

https://cargo-planner.com/docs/creating-a-loadplan/

“Predictive | Predicts the best combination of containers. Generally gives the lowest total cost. This is the default”

https://cargo-planner.com/docs/calculation/primary-settings/

Two selection strategies (Predictive, Greedy).

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: A max number of this container type to be avaialable”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“All of the configurations for the premade aircrafts are active by default. Set the max quantity of the ULDs available to 0 in order to disable certain configurations.”

https://cargo-planner.com/docs/equipment/planning-aircrafts/

Per-type cap via qty (API; max quantity in aircraft setup); plan-wide combined cap via Max number of containers. Remainder goes to unloaded items (stated for the combined cap).

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.

“containers: Load items into existing containers first. Either this and / or `container_types`/`set_types`/`sets` field needs to be set”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“To force the plan to always fill sets before falling back to individual containers, enable Load in sets in Primary settings.”

https://cargo-planner.com/docs/equipment/set-builder/

No general rank among container types is documented; the Hold record has an undescribed "priority" integer. Load in sets requires Set Builder (Enterprise); the API existing-containers route has no stated restriction.

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.

“A container is only approved if its contents meet a minimum. The limitation is either Cargo Volume, Net Weight or Chargeable Weight, and the container is rejected if the total is less than the specified value. The rule is checked after the container has finished loading. A rejected container is emptied and the engine tries another container type”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Two rules — 40ft HC cannot be loaded with less than 70 m³, and 40ft DV cannot be loaded with less than 60 m³ — with a 20ft DV also available. Full loads go into 40ft containers, and the remainder ends up in 20ft containers instead of a half-empty 40ft.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Select several container types for the plan; the tool chooses among them ("If more than one container type is available here then the tool will try to determine which one(s) is most suitable", https://cargo-planner.com/docs/creating-a-loadplan/). 2. Add a "Cannot load in container with" custom rule per large type with a minimum volume or weight; a container below it is emptied and the engine tries another type (https://cargo-planner.com/docs/calculation/custom-rules/). 3. Result: full units in the large type, the remainder in the smaller type, as in the vendor example (https://cargo-planner.com/docs/calculation/custom-rules/).

• Combination of general settings, shown by the vendor

Vendor-shown combination for this purpose. Without the rule, cost-based Predictive selection with a fixed cost per type ("Generally gives the lowest total cost") also tends to pick the smaller sufficient type, but that is hedged and not stated as smallest-fit. The user must set the thresholds.

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: The cost of this container. Does not need to be a currency, but a number. Example, 100 for a 20ft DV and 180 for a 40ft DV.”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“Select the container types you are willing to book in the setup step and give each one a fixed container cost — the freight rate you would actually be quoted for it. The plan then minimises total cost rather than maximising how full each container is”

https://cargo-planner.com/guides/planning-an-export-container-shipment/

Flat cost per container type (and per set type; per set configuration). A cost function can add load-dependent cost per container. No rate tables.

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.

“max_volume: Max loading volume allowed of cargoes in m3”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“Do adjustments on the fly like Max Loading Height, Payload, Max Volume etc...”

https://cargo-planner.com/features/equipment/

Volume cap is absolute (m³), not a percentage; a weight cap is reached by overriding payload per plan. Set per container in Setup or via the API.

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.

“A container is only approved if its contents meet a minimum. The limitation is either Cargo Volume, Net Weight or Chargeable Weight, and the container is rejected if the total is less than the specified value.”

https://cargo-planner.com/docs/calculation/custom-rules/

“A rejected container is emptied and the engine tries another container type; if no other type is available, the cargo is left unloaded.”

https://cargo-planner.com/docs/calculation/custom-rules/

Custom rule "Cannot load in container with".

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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 a cargo needs to be loaded in a specific container type then double-click in this column and a new dialog will be shown where you can select the allowed equipments.”

https://cargo-planner.com/docs/cargo/cargo-properties/

“Must be loaded in: Selected items must be loaded in specified container types.”

https://cargo-planner.com/docs/calculation/custom-rules/

Per item (Load in column, API allowed_containers) or per selector (Must be loaded in / Cannot be loaded in). Covers pallet types.

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.

“Load items into a designated space into a designated container”

https://api.cargo-planner.com/api/2/schema/ (/api/2/calculate/load_into_space/)

“Load items into this container”

https://api.cargo-planner.com/api/2/schema/ (LoadIntoSpace.container)

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

Through the API only: a dedicated endpoint loads given items into one designated container of an existing plan. That it targets one unit of a multi-unit plan follows from its container input, which identifies an individual unit. In the web app, Load in, allowed containers and custom rules work on container types rather than individual units.

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.

“What none of this does is invent a crate size. It evaluates the configurations you give it.”

https://cargo-planner.com/guides/designing-a-crate-for-shipping/

The packaging solution page markets "Calculate exact lumber and material requirements" and comparing candidate crate sizes; the crate guide states the planner only evaluates sizes the user supplies.

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

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

“Each row needs at least data for the following fields to be accepted:”

https://cargo-planner.com/docs/creating-a-loadplan/

“If all rows have a quantity set, then the tool loads the cargoes in as many containers as is necessary”

https://cargo-planner.com/docs/cargo/cargo-properties/

Length, width, height, weight and quantity per row. Limit: "Max number of loadable cargoes in one calculation: 40 000" (Introduction).

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.

“Cylinders appear in the load plan as proper rounded objects (not boxes), and hollow cylinders show the internal cavity.”

https://cargo-planner.com/docs/cargo/cylinders/

“Length: Outer diameter of the cylinder”

https://cargo-planner.com/docs/cargo/cylinders/

• The vendor's own sources disagree on this point

Geometry types Cylinder and Hollow cylinder (outer and inner diameter). Whether packing uses the round footprint rather than the bounding box is not stated beyond "proper rounded objects" in the plan.

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.

“Loading solid pipes and drums was something we were already capable of, so the challenge wasn’t necessarily how to fill voids with these items, but rather how one would go about have a geometrical shape with a hole in it.”

https://cargo-planner.com/news/pipe-loading/

"Nest pipes within pipes" (hollow cylinders) is cavity filling, scored under cargo-cavity-fill. No offset-row or honeycomb arrangement of cylinders is described.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for nest, honeycomb, stagger, offset, pyramid, hexagonal in the cylinders, cargo properties and orientations docs, the pipe-loading news post, and the feature and mode pages.

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.

“It lets you specify what a master carton looks like, how a pallet should be packed when full, or represent packing of a non-regular interlocking shape.”

https://cargo-planner.com/docs/cargo/bundling/

“In this example we created a bundle that is larger than the sum of its parts (due to the cardboard mentioned earlier), but if we have a shape that interlocks a certain way, we can also create something that is smaller.”

https://cargo-planner.com/docs/cargo/bundling/

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

The only documented route is pre-computing the interlocked arrangement as a bundle, which is data prepared outside the tool. Inner spaces let items go into another item’s cavity, but the placed item is handled by its outer dimensions (cargo-cavity-fill). Pipe-in-pipe nesting may use both shapes, but this is not stated.

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.

“Inner spaces allow you to define hollow areas inside cargo that can be used for additional loading space. This feature is useful for items like cabinets, shelving units, L-shaped furniture, and any cargo with usable internal cavities.”

https://cargo-planner.com/docs/cargo/inner-spaces/

“The inner spaces become available loading areas”

https://cargo-planner.com/docs/cargo/inner-spaces/

Up to 10 inner spaces per item, positioned by anchors or X/Y/Z. Hollow cylinders can also contain other items ("Cannot contain" rule controls which). The crate guide calls it "a new feature" that is "still growing".

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.

“`model` - 3D model”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Items can have a 3D model file attached (API files), but no source says the planner packs that shape. Complex shapes are handled through inner spaces carved out of a box.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for CAD, mesh, 3D model, STL, arbitrary shape, complex geometry. Checked the GeometryEnum (box, cylinder, hollow_cylinder; drum and pipe deprecated) and the item files field.

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.

Every item needs length, width, height and weight.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for bulk, loose, liquid, granular, amorphous, volume-only cargo. "Bulk" occurs only in "breakbulk", "bulk create" API endpoints and an aircraft "Bulk compartment" example.

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.

“In the same way if a value of -10 is provided then the cargo will be smaller than the provided dimension. This might be useful to simulate cargoes that can be “compressed” when loading by pushing and squeezing.”

https://cargo-planner.com/docs/calculation/primary-settings/

Partial form only: a plan-wide error margin of -1 to -50% shrinks every item by that amount, always, not just as needed to fit, and cannot be set per item. The per-item Margin adds space and is not documented as accepting negative values.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for compress, squeeze, soft, negative margin. Checked the Error margin (primary and secondary settings), cargo Margin, API free_space and error_margin.

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.

“We want to pack 644 pieces, which means that the tool will first fill an entire pallet (with 460 pieces). The remaining 184 pieces will be loaded in the 15 pcs of the 12-packs (a total of 180 pcs), the remaining 4 pieces don’t divide evenly with a 12-pack, so the remainder will be loaded piece by piece.”

https://cargo-planner.com/docs/cargo/bundling/

“bundles: A list of possible bundles that this item can utilize”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Bundles per item with their own dimensions, weight, inner quantity and stacking/orientation properties. Partial bundles and even spread are optional (API Bundling).

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.

“Rotatable says whether the unit may be turned about its vertical axis; tiltable says whether it may be laid on another face at all.”

https://cargo-planner.com/guides/designing-a-crate-for-shipping/

“tiltable: If true, item can be rotated in any direction”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Per item. Rotatable (bitmask 3) is the default for boxes and keeps the item upright; tilting needs Tiltable or a custom mask.

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.

“Longship | The cargo can only be loaded in its lengthwise direction”

https://cargo-planner.com/docs/cargo/orientations/

“not_rotatable: If true, item can only be loaded in lengthwise direction”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Forces lengthwise alignment per item. No documented "crosswise only" option for boxes except through the custom mask.

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.

“Tiltable | The cargo can be rotated in any direction”

https://cargo-planner.com/docs/cargo/orientations/

“orientations: Possible orientations - this will overide not_rotatable and tiltable properties. 1 = Longship, 3 = Rotatable, 63 = Tiltable”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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.

“You can set a custom orientation as well and select variations of the above.”

https://cargo-planner.com/docs/cargo/orientations/

“If you need to enter an orientation for your cargo through the Excel sheet or by using the API - you have to enter a number from 1-63 - (which is what the app is using internally). This number is actually a bit mask of values between 1-63.”

https://cargo-planner.com/docs/cargo/orientations/

• Follows from documented behaviour rather than stated outright
• Evidence is a label in a screenshot

A six-bit mask per item. Only bits 1 (Longship) and 2 (rotated about Z) are named in the text. The meaning of bits 4 to 32 is not given, so an API user cannot build "on its side but not on its end" from the docs alone; the app’s Custom option shows the allowed rotations in 3D (news post image).

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

“This number is actually a bit mask of values between 1-63.”

https://cargo-planner.com/docs/cargo/orientations/

“The first orientation, which in the app is called “Longship” means a value of 1. The second orientation which essentially means the cargo rotated around its Z axis has a value of 2. This means that if you allow both those values it results in an orientation number of 3”

https://cargo-planner.com/docs/cargo/orientations/

• Follows from documented behaviour rather than stated outright
• Evidence is a label in a screenshot

Six-bit mask (values 1 to 63), so every subset of the six orientations has a code. Only two bits are explained.

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.

“Restricted heightwise two block — like heightwise two block, but with strict limitations that keep the majority of cargo oriented longship”

https://cargo-planner.com/docs/calculation/custom-rules/

Orientation settings are hard (allowed set). Pattern rules restrict block rotations; none is a soft preference for one orientation.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for prefer, preferred orientation, soft orientation, where possible. Checked orientations docs, custom-rule patterns and cylinder settings.

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.

“Example 2: Items with Used orientation “HxLxW” must touch the Floor as they are not stable enough to stack on other cargo in the given orientation.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Used orientation | List | The orientation the item is placed in. Evaluated during loading”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Custom rule with a selector on "Used orientation" (evaluated during loading) (https://cargo-planner.com/docs/calculation/custom-rules/). 2. Condition "Must touch side" with side Floor (https://cargo-planner.com/docs/calculation/custom-rules/). Items in that orientation can then only be placed on the floor.

• Combination of general settings, shown by the vendor

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“Example: Items with Used orientation not equals “LxWxH” or “WxLxH” cannot support any item. The cargo can only support other cargo when placed in certain orientations.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Selector on "Used orientation" (https://cargo-planner.com/docs/calculation/custom-rules/). 2. Condition "Cannot support" (any item, or a selector including weight) (https://cargo-planner.com/docs/calculation/custom-rules/).

• Combination of general settings, shown by the vendor

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“You can rotate a cargo in any direction by clicking on the cargo rotate button”

https://cargo-planner.com/docs/workspace/the-interactive-view/

The only rotation beyond the six orientations is manual rotation in the interactive view, and its angles are not specified. The windows news post describes custom pallets with a supporting wall, not angled placement by the planner.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for angle, tilt, lean, degrees, diagonal, non-orthogonal.

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

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

“Cylinders, Standing | The cargo can only be loaded standing. Default option for cylinders”

https://cargo-planner.com/docs/cargo/orientations/

“Cylinders, Laying (lengthwise) | The cargo can only be loaded laying in its lengthwise direction”

https://cargo-planner.com/docs/cargo/orientations/

• The vendor's own sources disagree on this point

Standing, laying crosswise, laying lengthwise, or a custom mix. The cargo properties page instead describes the Cylinder geometry as "A cylinder laying down".

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.

“If checked, then no cargo (including itself) is allowed to be put on top. The cargo itself is however allowed to be put on other cargoes which are stackable.”

https://cargo-planner.com/docs/cargo/cargo-properties/

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.

“If checked then this cargo must be loaded at the bottom on the floor. If nothing else is specified then other cargoes can still be loaded on top of this cargo”

https://cargo-planner.com/docs/cargo/cargo-properties/

Per item (Bottom only). Weight-threshold variants are possible with custom rules (Must touch side Floor with a weight selector).

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.

“Must be on top of: Selected items must be on top of specified item types.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Cannot be loaded in zone: Selected items cannot be loaded within a specified zone. See Must be loaded in zone for a description of how zones are defined.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

Either: 1. Select the item(s) (https://cargo-planner.com/docs/calculation/custom-rules/). 2a. Condition "Must be on top of" with a second selector that matches all possible base items, e.g. Weight Greater than 0 (https://cargo-planner.com/docs/calculation/custom-rules/); or 2b. Condition "Cannot be loaded in zone" with side Floor and a small depth (https://cargo-planner.com/docs/calculation/custom-rules/).

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

Auditor-built. The vendor example for Must be on top of is lids on drums, not "never on the floor".

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.

“If a layer option is provided for a cargo (a number) it means that this cargo can only be stacked up to a certain amount of times (layers).”

https://cargo-planner.com/docs/cargo/cargo-properties/

“A cargo property | Only cargo with the same value for the selected property counts. If SKU is selected and SKU-A has max layers 3, SKU-B can still be stacked on top”

https://cargo-planner.com/docs/calculation/primary-settings/

Max layers 0-255 per item; counting mode set plan-wide by Max layers property.

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.

“Aggregated for all cargo | All cargo in the stack counts towards the limit, regardless of what it is”

https://cargo-planner.com/docs/calculation/primary-settings/

Per item Max layers counted over the whole stack when the plan setting is "Aggregated for all cargo". The Max layers setting chooses one counting mode for the whole plan.

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.

“Max height: The top of the selected items cannot exceed specified height.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Max stacking height: The bottom of the selected items cannot exceed the specified height.”

https://cargo-planner.com/docs/calculation/custom-rules/

Custom-rule conditions applied per selector (any item property, including SKU). Both top-of-item and bottom-of-item limits.

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.

“Max weight (in dimension specified by loadlist) that is allowed to be loaded on top of a cargo.”

https://cargo-planner.com/docs/cargo/cargo-properties/

“Applies to all cargo, regardless if it’s a stack of identical SKUs or other items.”

https://cargo-planner.com/docs/cargo/cargo-properties/

Per item. The docs do not say whether the limit counts the whole column above or only the item resting directly on it. Components also have Max load.

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.

Max load is a weight per item, with no area basis.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for pressure, per area, per m², contact area, footprint load. Checked Max load (cargo properties, API) and component Max load.

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.

“Applies to all cargo, regardless if it’s a stack of identical SKUs or other items.”

https://cargo-planner.com/docs/cargo/cargo-properties/

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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

Counts when: A documented weight-ordering stacking rule.

“Usually a cargo weighing 100kg cannot be loaded on a cargo weighing 50kg. However a box weighing 5kg can usually be loaded on a box weighing 4 kg. There are different opinions on this so you can change it here to fit your requirements.”

https://cargo-planner.com/docs/calculation/primary-settings/

“For example, Cannot support items with Weight Greater than 120% of selected item means no item can carry another item more than 20% heavier than itself.”

https://cargo-planner.com/docs/calculation/custom-rules/

"Allow heavy on light" is enabled in the system default preset, so the rule is off by default. Its exact threshold when disabled is not stated; the custom rule gives an explicit percentage.

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.

“Number: metrics for use in ordering or summing. For example “Square meters” or “Stackability grade””

https://cargo-planner.com/docs/cargo/cargo-properties/

“Custom columns | Text/Number | Any custom columns you have added to the load list”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Add a Number custom column such as "Stackability grade" (https://cargo-planner.com/docs/cargo/cargo-properties/). 2. Custom rule: all items "Cannot support" items whose grade is Greater than 100% of the selected item, using a relative value in the second selector (https://cargo-planner.com/docs/calculation/custom-rules/). Custom columns are selectable properties (https://cargo-planner.com/docs/calculation/custom-rules/).

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

Auditor-built. The vendor names "Stackability grade" as a custom-column example and shows relative-value Cannot support rules on weight, but not this combination. That relative values work on custom number columns is inferred.

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.

“Example: Items with SKU “CRATE-BASE” can only support items with SKU “CRATE-TOP”.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Cannot support: Selected items cannot support specified item types.”

https://cargo-planner.com/docs/calculation/custom-rules/

Cannot support / Can only support between any two selectors (SKU, class, custom column).

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.

“A rule that limits stacking to only be allowed on cargo of the exact same dimensions”

https://cargo-planner.com/docs/calculation/custom-rules/

“Useful when you need fine-grained control over stacking combinations — for example, preventing cargo from different shipments from supporting each other, restricting stacking to items within a certain weight ratio, or requiring identical dimensions before allowing stacking.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Custom rule "Cannot support" with a relative-value second selector on Length/Width Not equals 100% of the selected item (https://cargo-planner.com/docs/calculation/custom-rules/). Alternative top-not-larger: 2. Allowed overhang 0 ("all cargoes need full support from below") plus Single cargo support (https://cargo-planner.com/docs/calculation/primary-settings/).

• Combination of general settings, shown by the vendor

The exact rule in the vendor example is shown in an image; its purpose is stated in text.

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.

“If you allow a cargo to not have full support from below you can change the allowed overhang setting. Setting it to 0 means all cargoes need full support from below.”

https://cargo-planner.com/docs/calculation/primary-settings/

“The overhang can be given either as a Percentage of the cargo’s dimensions (0–35%) or as a Length.”

https://cargo-planner.com/docs/calculation/primary-settings/

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.

“In a situation where you have different cargo being used as support, what is the largest accepted difference in height between the packages the system should allow to consider the space on top a single loadable area? Defaults to 5mm.”

https://cargo-planner.com/docs/calculation/primary-settings/

Height tolerance, plan-wide (and secondary settings).

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.

Inner spaces model cavities but no nesting height increment or top-surface shape for stacking is documented.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for nesting height, nestable, stackable cups/chairs, open top surface, top shape. Checked cargo properties, inner spaces, bundling and the API Item schemas.

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

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

“If enabled pallets are built in layers, rather than towers, and stability is prioritized over utilization.”

https://cargo-planner.com/docs/calculation/primary-settings/

"Prioritize pallet stability" builds in layers but does not require complete layers. Full-pallet bundles fix a full pallet’s contents, but remainders are still loaded; this is pallet-split-routing.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for complete stack, full layer, complete layer, flat top, even top.

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

“Group by: Selected items are loaded closely together if they have the same value for the specified property.”

https://cargo-planner.com/docs/calculation/custom-rules/

“SKU | Text |”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Custom rule "Group by" with the property SKU (https://cargo-planner.com/docs/calculation/custom-rules/); SKU is a selectable property (https://cargo-planner.com/docs/calculation/custom-rules/).

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

The vendor shows Group by on Group/Shipment and Destination, not on SKU. It is a single general rule set to a property the vendor does not show, so it is scored as auditor-built. The API examples use a "group_items" setting that is not described.

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.

“Group shipments together: This setting will make sure that cargo that belong to the same shipment are packed next to each other without cargo in between.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Different cargoes can belong to the same group / shipment / consignment. If you enter an ID (number or text) then cargoes with the same ID will be loaded together.”

https://cargo-planner.com/docs/cargo/cargo-properties/

One level of grouping natively (Group/Consignment); the Group by rule can group on any other property as well.

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.

“If this setting is enabled, a shipment will be packed into a single container. If the entire shipment does not fit, the entire shipment will be unloaded.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Must be loaded in a single container: Selected items with the same value for the specified property must be loaded in a single container.”

https://cargo-planner.com/docs/calculation/custom-rules/

Failure mode stated: an unfitting shipment is unloaded whole.

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.

“This setting ensures that entire shipments are packed. If one cargo item from the shipment is excluded from the load plan, then the entire shipment will be unloaded.”

https://cargo-planner.com/docs/calculation/primary-settings/

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

“Reach length: How far can the loader physically reach for a cargo, over another group. In other words, the maximum distance one group’s cargo may overlap the next group’s along the container’s length. When loading with a forklift this might be a greater distance than when loading by hand. A reach length of 0 gives a clean split between groups.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Can only be side-by-side with: Selected items can only share a lengthwise section of the container with specified item types.”

https://cargo-planner.com/docs/calculation/custom-rules/

Lengthwise sections via Group by (reach length 0). No physical divider of set thickness is inserted.

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.

“Example: All items cannot support items with Group/Shipment Not equals the selected item’s Group/Shipment — cargo is only stacked on cargo from the same shipment.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Custom rule, all items (https://cargo-planner.com/docs/calculation/custom-rules/). 2. Condition "Cannot support" with a relative-value second selector: Group/Shipment Not equals the selected item’s value (https://cargo-planner.com/docs/calculation/custom-rules/).

• Combination of general settings, shown by the vendor

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.

“The segregation table enables you to tell which cargoes can or cannot be loaded together in the same equipment.”

https://cargo-planner.com/docs/calculation/segregation-table/

“Cannot be loaded with: Selected items cannot be loaded in the same container as specified items.”

https://cargo-planner.com/docs/calculation/custom-rules/

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.

“Must keep distance: Selected items must maintain a minimum distance from specified item types. For example, cargo from shipment A must stay at least 2m away from cargo from shipment B.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Items with Class “Oxidizer” must keep 3 m distance from items with Class “Flammable”.”

https://cargo-planner.com/docs/calculation/custom-rules/

How the distance is measured (gap between boxes or between centres) is not stated.

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.

“Cargo-Planner doesn’t classify cargo or look up those rules for you - it gives you the tools to encode whatever the regulation requires into a load plan, and then packs around them.”

https://cargo-planner.com/guides/loading-dangerous-goods/

Classes and the segregation table are user-defined; there are no built-in IMDG/ADR/IATA segregation rules.

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

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

“Max total: A max cap for the summed value of a numeric property across all selected items in a single container. The value is entered in the property’s unit — weight, volume, length or plain number.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Cannot exceed quantity: This condition is deprecated and is converted to Max total using Inner quantity as the property.”

https://cargo-planner.com/docs/calculation/custom-rules/

Per container (and per container type). No documented ceiling.

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.

“Max cargo types: A max cap for the number of unique values of a property that can be loaded into specified containers. Set Unique to the property to count, and the maximum number per container.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Unique SKU, max 3 — each container holds at most three different SKUs”

https://cargo-planner.com/docs/calculation/custom-rules/

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.

“Keep equal ratio: Selected items with the same value for the specified property must be loaded in an equal ratio in each container. For example, if shipment A and shipment B each have 10 items and there are 2 containers, each container will receive 5 items from each shipment.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Keep equal ratio on SKU for a retail replenishment — every container delivered to a store holds the same product mix.”

https://cargo-planner.com/docs/calculation/custom-rules/

The per-unit ratio is the ratio of the total quantities, spread equally over the containers, rather than an entered N:M. What happens when quantities do not divide evenly is not stated. Bundles are single-item pack levels, not kits.

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.

“The checkbox called Allow partial bundles, allows the system to have bundles that are not completely full.”

https://cargo-planner.com/docs/cargo/bundling/

Bundles of N without partial bundles still load the remainder piece by piece ("the remainder will be loaded piece by piece"), so this is not a multiple-of-N rule per unit.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for multiple of, multiples, batch, lot size, increments. Checked bundling (partial_bundles, even_spread), Max total, Keep equal ratio, and the API Bundling schema.

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.

“A locked container is marked with a lock icon and cannot be opened in the Interactive view or changed by drag and drop.”

https://cargo-planner.com/docs/workspace/modifying-a-loadplan/

“When you return to Setup and click New load plan, the locked containers and their cargo are kept as they are, and only the rest of the cargo is recalculated.”

https://cargo-planner.com/docs/workspace/modifying-a-loadplan/

Locking works at whole-container level. Single items cannot be locked while the rest of the same container is re-planned.

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.

“load_at_position: Load cargo into this space”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“load_into_space: Load items into a designated space into a designated container”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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

The API has a load_into_space endpoint with a load_at_position point, and existing containers (whose items carry pos) can be passed in to load into first. Neither description says that given coordinates are kept fixed while the planner loads the rest around them. In the app, positions are set by dragging (workaround).

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for coordinates, position input, fixed position, pre-placed, pos, load_at_position. Checked the Item (pos, rotation), HoldData.items, LoadIntoSpace and InsertItems schemas, the developer examples, and the interactive view and planner view docs.

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.

“Must be loaded in zone: Selected items must be loaded within a specified zone. A zone is defined by one or more container sides (Front, Rear, Side 1, Side 2, Floor, Roof) and a depth — the zone extends inward from each selected side by that length.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Items with Weight/bundle Greater than 1,000 kg must be loaded within 3 m of the Front, keeping heavy cargo over the trailer’s kingpin.”

https://cargo-planner.com/docs/calculation/custom-rules/

Zones are bands measured inward from container sides (intersections give corners or edges). A free-standing interior box region is not expressible. Items are left unloaded if the zone is empty.

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.

“Cannot be loaded in zone: Selected items cannot be loaded within a specified zone.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Items with Group/Shipment “Fragile” cannot be loaded within 0.5 m of the Rear, keeping them away from the doors where impacts during handling are most likely.”

https://cargo-planner.com/docs/calculation/custom-rules/

Applies to selected items, or to all items with an empty selector. Same side-based zone geometry, so a central aisle is not expressible this way. Equipment components can block fixed regions instead.

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.

“Front to back | Will load cargoes from the front to back. This is the default when creating truck and ocean container load plans.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Load bottom up | Will load the cargoes from floor and upwards and minimize the used height.”

https://cargo-planner.com/docs/calculation/primary-settings/

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.

“Load bottom up | Will load the cargoes from floor and upwards and minimize the used height.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Minimize Height | Will try to “compress” the used height. Useful if you want to spread the load over the whole container area.”

https://cargo-planner.com/docs/calculation/primary-settings/

Scope: whole plan (primary or secondary settings), 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.

“Reach length: How far can the loader physically reach for a cargo, over another group. In other words, the maximum distance one group’s cargo may overlap the next group’s along the container’s length. When loading with a forklift this might be a greater distance than when loading by hand.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Access width: How wide does a corridor need to be in order for the loader to walk/drive into it without any reaching necessary?”

https://cargo-planner.com/docs/calculation/custom-rules/

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

Reach length and access width apply only within the Group by rule, i.e. reach over another group’s cargo. They are not a general block-depth limit.

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.

“A distance around the cargo that will act as “free space”. Enter a number here if your cargo needs extra room for lashings or other purposes”

https://cargo-planner.com/docs/cargo/cargo-properties/

“free_space: Free space (in dimension specified by loadlist) which will be added to this cargo. If specified as a String with 'X;Y' - X will be added to length direction and Y to width direction”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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.

“Require front support: Only available for trucks/trailers and sea containers. Requires every cargo to have front-facing support, which prevents cargo from shifting forward during braking. Will likely reduce utilization.”

https://cargo-planner.com/docs/calculation/primary-settings/

“require_front_support: All cargo need to have part of the front supported. Useful when loading trailers to ensure stability when braking”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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

The API description says "part of the front supported"; how much is not stated.

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.

“payload: Payload in kg - max net weight”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“The cargoes are too heavy for the selected containers. Maybe the payload of your container is 20 000 kg and the weight of each cargo is 22 000kg - then these cargoes cannot be fit due to weight restrictions”

https://cargo-planner.com/docs/help/faq/

Per container, pallet and set (set payload independent of member payloads).

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.

“Payload | The total payload the whole set can carry. Independent of the payloads of its individual containers.”

https://cargo-planner.com/docs/equipment/set-builder/

“Max load | Maximum weight the part can support on its top surface.”

https://cargo-planner.com/docs/equipment/hold-parts/

Set positions can carry per-position payload overrides (Set builder).

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.

“To give each section of a trailer its own weight limit - for example the front, middle and rear - add one Floor per section.”

https://cargo-planner.com/docs/equipment/hold-parts/

“Then set a different Max load on each. Max load caps the total weight of all cargo resting on that floor, and the planner never exceeds it, so each section is limited separately.”

https://cargo-planner.com/docs/equipment/hold-parts/

How it is done with general settings

1. In the container editor add one Floor component per lengthwise section, stuck to Floor + Side 1 + Side 2, with consecutive X and L (https://cargo-planner.com/docs/equipment/hold-parts/). 2. Give each floor its own Max load; the planner never exceeds it (https://cargo-planner.com/docs/equipment/hold-parts/).

• Combination of general settings, shown by the vendor

Vendor-shown for this purpose. The "Max weight per section" rule gives one limit for all equal-length sections, not different limits.

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“Useful for floor strength and axle load limits, sometimes called meter weight.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Semi-trailer with a max weight of 1,800 kg per 1 m section, matching the trailer manufacturer’s floor rating.”

https://cargo-planner.com/docs/calculation/custom-rules/

Fixed sections from the loading end (section length chosen by the user), rather than a sliding window.

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

“Use the Road tab in the container editor to set axle weight limits, axle spacing and road-legal limits on trailers and on sea containers with axles. The load plan respects these limits when placing cargo and reports the resulting axle weights in the interactive view.”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

“Set the limits for the front and rear axle sets on the trailer and the plan respects them while placing cargo, then reports the resulting weights — gross and net of tare — for each set.”

https://cargo-planner.com/guides/planning-out-of-gauge-road-transport/

Two axle sets (front, rear). The equipment feature page words it as reporting ("the plan reports back against them rather than against the total"), and the multi-drop guide says axle weights are not recalculated between stops.

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.

“The Road tab has two identical cards, Front axle set and Rear axle set.”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

“Axles | Number of axles in the set, `0`–`9`.”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

The documented model has exactly two axle groups per container (each 0-9 axles at a set spacing). The "supertrailer with 8 axles" on the road marketing page fits that two-group model. In a set, each part has its own two groups, but no source says sets add up to one vehicle model with three or more groups.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for axle group, third axle, tridem, axle set, axles. Checked the axles docs, set builder, equipment library trailer pages and the API (axles: "For internal use").

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.

“If Tare on the General tab is set, the limit is the gross weight allowed on the set (tare included).”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

“Front axle weight / Rear axle weight — gross weight on each set, including tare (shown when a tare is set).”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

Tare is one value per container. The axle figures include it, but no source shows how it is split between the front and rear sets (no tare per axle or tare centre-of-gravity input). That fails the row per its definition note.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for tare, empty weight, tare distribution, tare centre of gravity, empty axle load.

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.

“Kingpin Position | Rear Axle”

https://cargo-planner.com/equipment-library/53ft-step-deck-trailer-us/

Library trailers list a "Kingpin Position", and road trains are modelled as sets, but no source says that coupling load is passed to a tractor’s axles or that tractor axle loads are reported.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for kingpin, fifth wheel, tractor, drawbar, coupling, transfer.

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.

“Legal weight | Weight above which the load counts as a special transport. If one cargo exceeds this weight, no other items are co-loaded on the same trailer.”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

Legal weight and legal height are typed per vehicle. No jurisdiction presets, spacing rules or permit model are documented.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for jurisdiction, country, region, legal limits, bridge formula, permit, ADR, EU, DOT.

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.

“This setting will make sure the center of gravity stays within the given distance from the center of the container, set as a percentage in the X (length) and Y (width) direction. Both default to 20% when enabled.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Allowed Center of Gravity: The center of gravity of the specified containers must stay within the given distance from the container’s center, expressed as a percentage in the X-direction (length) and Y-direction (width).”

https://cargo-planner.com/docs/calculation/custom-rules/

• The vendor's own sources disagree on this point

Symmetric window around the centre, in percent; per container type via the custom rule. Older sources state a fixed 10% ("Prioritize Center of Gravity ... within 10%", sea mode page; API prioritize_cog), the current docs 20% default.

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.

“set as a percentage in the X (length) and Y (width) direction”

https://cargo-planner.com/docs/calculation/primary-settings/

“Must be loaded along centerline: Selected items must be placed along the lateral centerline of the container (the center of the width).”

https://cargo-planner.com/docs/calculation/custom-rules/

Y percentage window; Must be loaded along centerline for selected items.

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.

The CoG limits cover X and Y only.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for vertical centre of gravity, CoG height, Z direction, height of centre of gravity.

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.

“Move cargo to the center of selected pallets | Pallet load lists only. Moves the cargo on each pallet so it is centred on the pallet’s length and width.”

https://cargo-planner.com/docs/workspace/modifying-a-loadplan/

“Stability | Shown as “Stability of [equipment type]”. If two solutions have the same cost, the more stable one is picked”

https://cargo-planner.com/docs/calculation/primary-settings/

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

The CoG limit is hard. Secondary goal "Stability" is not defined in terms of CoG or axle balance. Marketing claims balanced distribution ("Optimize weight distribution", airlines solution page) without a documented soft-balance option.

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 crate guide lists the machine’s centre of gravity as a fixed fact, but there is no item CoG input.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for item centre of gravity, off-centre, eccentric, CoG offset in cargo properties and the API item schemas.

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.

“A cargo with a higher priority will be loaded before a cargo with a lower priority”

https://cargo-planner.com/docs/cargo/cargo-properties/

“Must be loaded before: Selected items must be loaded before specified item types. Since items loaded first end up deeper in the container, this also controls unloading order — items that should be unloaded last should be loaded first.”

https://cargo-planner.com/docs/calculation/custom-rules/

Direction stated: loaded first means deeper. Order by is explicitly about load order, not position.

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.

“Priority still influences which items ship if the plan does not fit everything.”

https://cargo-planner.com/docs/calculation/routing/

“Strict priorities: A lower priority cargo is never allowed to be loaded before a higher priority, even if the higher priority can’t be loaded at all.”

https://cargo-planner.com/docs/calculation/primary-settings/

The routing page uses hedged wording ("influences"); Strict priorities is the hard form.

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.

“Set as fillers: Selected items will only be loaded where there is space left after all other cargo has been placed.”

https://cargo-planner.com/docs/calculation/custom-rules/

“If some rows have a quantity set and some have not - then the tool will load the cargoes that have a quantity set in as many containers as needed - and then use the items that have no quantity set as “fillers””

https://cargo-planner.com/docs/cargo/cargo-properties/

Fillers do not trigger extra units ("only be loaded into existing containers").

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.

“Sets the load order from each cargo’s destination, so the first stop is loaded last.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Groups cargo by destination, so each stop can be unloaded without moving any other cargo.”

https://cargo-planner.com/docs/calculation/primary-settings/

• The vendor's own sources disagree on this point

Sources conflict on whether the stop order is derived from a computed route: Primary settings says routing "Finds the optimal delivery route, using roads the loaded trucks can actually drive", while the out-of-gauge guide says "it sequences by destination grouping rather than computing a route for you". Routing overrides priority.

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.

“Groups cargo by destination, so each stop can be unloaded without moving any other cargo.”

https://cargo-planner.com/docs/calculation/primary-settings/

“The reachability you set is guaranteed, not a preference: the plan keeps each stop’s cargo reachable within those limits.”

https://cargo-planner.com/guides/planning-a-multi-drop-trailer-load/

Stated as a hard guarantee of reachability (door-nearest, or by a corridor of the set access width). That is slightly broader than "never in front of or on top", since an access corridor may count as reachable.

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.

“Reach length: How far can the loader physically reach for a cargo, over another group. In other words, the maximum distance one group’s cargo may overlap the next group’s along the container’s length.”

https://cargo-planner.com/docs/calculation/custom-rules/

“A reach length of 0 gives a clean split between groups.”

https://cargo-planner.com/docs/calculation/custom-rules/

Group by rule with the property Destination.

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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 a destination per item and a single Port of loading per load list.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for pickup, pick-up, collection, origin stop, load at stop, en route loading.

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

“Although the planning of multiple trucks at once will work, there are certain scenarios where the division of packages between trucks is not optimal. At times the algorithm will end up using multiple trucks for a single destination when it could have been avoided.”

https://cargo-planner.com/news/loading-cargoes-with-routing/

Stated only in the November 2022 routing release post, which was updated in October 2026. The current docs pages do not address multi-unit routing.

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.

“Entire shipments must be loaded or none: This setting ensures that entire shipments are packed. If one cargo item from the shipment is excluded from the load plan, then the entire shipment will be unloaded.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Different cargoes can belong to the same group / shipment / consignment. If you enter an ID (number or text) then cargoes with the same ID will be loaded together.”

https://cargo-planner.com/docs/cargo/cargo-properties/

How it is done with general settings

1. Give every item for a stop the same Group/Consignment ID (e.g. the destination string) (https://cargo-planner.com/docs/cargo/cargo-properties/). 2. Allow different IDs to share a container (turn the default separation off) (https://cargo-planner.com/docs/cargo/cargo-properties/). 3. Enable "Entire shipments must be loaded or none" (https://cargo-planner.com/docs/calculation/primary-settings/).

• 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

Auditor-built: the vendor applies whole-or-nothing to consignments, not stops. Using the Group ID for stops means it cannot also be used for orders.

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.

“We can also move cargoes from one day to another by highlighting a few rows, right-clicking and selecting Move to loadlist… This opens the calendar for the project and lets you change the date of the cargo.”

https://cargo-planner.com/docs/workflow/projects/

ETD and recurring project dates exist, but cargo is moved between dates by hand. No date rule allocates cargo.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for due date, ship date, ETD, storage date, days range, date window, recurring.

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.

“When creating a custom pallet (i.e. Secondary Equipment), please note that the “Max Height” setting is 0 by default which means only one layer of cargo will be loaded on that pallet.”

https://cargo-planner.com/docs/equipment/working-with-pallets/

“floor_height: Thickness of floor in m”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Pallet is a container with floor height (deck) and max height. Whether max height counts from the ground including the deck is not stated in words.

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.

“The layer pattern, mixed orientations included, is worked out from the carton dimensions and the limits you give it:”

https://cargo-planner.com/guides/ti-hi-pallet-stacking-patterns/

“For a single carton on a standard pallet, the free pallet calculator gives you the answer straight away: enter the carton and it shows how many fit, in 3D.”

https://cargo-planner.com/guides/ti-hi-pallet-stacking-patterns/

One pattern returned; no alternative patterns offered.

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.

“Must load with pattern: Selected items must be loaded using the specified pattern. Patterns control the layout and orientation of large groups of cargo within the container.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Two block — two groups of cargo where the rotation differs between each block”

https://cargo-planner.com/docs/calculation/custom-rules/

Interlocked (alternating layer) patterns are claimed in a guide ("interlocking ... usually works straight away") and on the home page, but no setting for layer rotation is documented.

The planner builds pallets that carry several different item types.

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

“When examining the results in the workspace tab, we can quickly see that all the items were loaded in full size Euro Pallets and some pallets contained both milk and cereal.”

https://cargo-planner.com/docs/equipment/working-with-pallets/

“let it put the leftover cartons on mixed pallets and plan the container around the lot”

https://cargo-planner.com/guides/ti-hi-pallet-stacking-patterns/

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.

“Pallets allow cargo to overhang the deck when they are loaded. To manage how far, set Max length and Max width on the pallet in Setup → Expand selected equipment, the same way as on any other container. The planner treats them as hard limits: it never places cargo past them. When they are left blank, pallets allow 33% overhang by default, as open containers do.”

https://cargo-planner.com/docs/equipment/working-with-pallets/

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“To build pallets whose load is balanced on the center of the deck, turn on Limit the allowed center of gravity and set both the length (X) and width (Y) values to 0%. The planner then only builds pallets whose center of gravity sits at the center of the deck.”

https://cargo-planner.com/docs/equipment/working-with-pallets/

How it is done with general settings

1. In the secondary (pallet) settings enable "Limit the allowed center of gravity" (https://cargo-planner.com/docs/calculation/secondary-settings/, https://cargo-planner.com/docs/calculation/primary-settings/). 2. Set X and Y to 0% (https://cargo-planner.com/docs/equipment/working-with-pallets/).

• Combination of general settings, shown by the vendor

Vendor-shown. Centring is by centre of gravity, not by the geometric footprint. A post-plan menu item centres cargo geometrically ("Move cargo to the center of selected pallets"), which is a manual step.

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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

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

"Slip-sheet" appears only as a reason for a bottom spacer (contours page).

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for interlayer, slip sheet, tier sheet, layer pad, separator sheet.

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.

“Secondary load settings take the same parameters as the primary settings, but they apply only to preloaded hold types — the pallets, boxes and cases that cargo is loaded into before that unit is loaded into a container or trailer.”

https://cargo-planner.com/docs/calculation/secondary-settings/

“Shipments cannot be mixed: This setting will make sure that cargo from different shipments are not packed into the same container.”

https://cargo-planner.com/docs/calculation/primary-settings/

How it is done with general settings

1. Set Group/Consignment per order (https://cargo-planner.com/docs/cargo/cargo-properties/). 2. In Secondary settings, enable "Shipments cannot be mixed", which then applies to pallets (https://cargo-planner.com/docs/calculation/secondary-settings/, https://cargo-planner.com/docs/calculation/primary-settings/).

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

Auditor-built. That the shipment settings are among the "same parameters" carried to secondary settings is inferred from the general statement. A custom rule "Cannot be loaded with" with a relative Group/Shipment value, limited to the pallet type, is an alternative.

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.

“A common scenario is to load cargoes on pallets and then load them into containers. This type of “nested calculation” is easy to set up in Cargo-Planner.”

https://cargo-planner.com/docs/equipment/working-with-pallets/

“Below example will first load the cargoes with the palletize field set to true into the provided pallet type and then load the pallets and the other cargoes into our custom container type”

https://cargo-planner.com/docs/developer/examples/

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.

“In a pallet load list, Load selected pallets into… turns each pallet, with its cargo, into one piece of cargo in a new load list. The new cargo keeps the pallet’s built dimensions and its gross weight: the pallet’s own weight plus its cargo.”

https://cargo-planner.com/docs/workspace/modifying-a-loadplan/

“Add to Cargo Library | Saves the selected container, with its cargo, to the Cargo Library as one pre-planned cargo.”

https://cargo-planner.com/docs/workspace/modifying-a-loadplan/

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“It will then preload the 12 packs and single pieces on a pallet, before loading them into a 20ft DV container.”

https://cargo-planner.com/docs/cargo/bundling/

“In this example we have specified that the 12-pack should be loaded on pallets, but the full pallet size should not.”

https://cargo-planner.com/docs/cargo/bundling/

The carton level is a predefined bundle (fixed carton geometry and count chosen by the planner), not a carton packed by the planner. Pallets on pallets is stated on a feature page only.

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 checkbox called Allow partial bundles, allows the system to have bundles that are not completely full. If this is checked the system will always use a bundle, even if we can’t fill it”

https://cargo-planner.com/docs/cargo/bundling/

“Must be loaded into secondary equipment (palletize): Selected items will be loaded into secondary equipment — such as pallets, cartons, or inner containers — before being placed in the main container.”

https://cargo-planner.com/docs/calculation/custom-rules/

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.

“Use Secondary equipment containing when the rule should act on the preloaded pallet rather than on the loose items, for example pallets containing Group/Shipment “Fragile” cannot support any cargo.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Always stackable: Selected items (or pallets) are always stackable, regardless of weights and stackability properties. Useful for controlling the stackability when preloading pallets.”

https://cargo-planner.com/docs/calculation/custom-rules/

Rules for built pallets use the custom-rule scope "Secondary equipment containing". No top-fill threshold for stacking pallets is documented.

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.

“In Preloader 2.0 we have turned the traditional method upside down. We start by placing an empty pallet into the trailer, and build it up from there. Even though this is very impractical as a real-world solution it comes with a lot of benefits. Not only does this ensure that every built pallet will fit in the trailer”

https://cargo-planner.com/news/improved-palletization/

“if the trailer was almost full, except for some space with half the height of the trailer, we wouldn’t be able to fit a fully loaded pallet.”

https://cargo-planner.com/news/improved-palletization/

Release-note evidence (March 2024). Stated as building each pallet in place in the vehicle so it fits the space available.

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.

“If no rows have a quantity set - then the tool will try to fit as much as possible into one of the selected containers.”

https://cargo-planner.com/docs/cargo/cargo-properties/

“Cargo-Planner always tries to maximize the chargeable weight loaded, and the shipping factor decides how chargeable weight is calculated.”

https://cargo-planner.com/docs/calculation/primary-settings/

Measure: chargeable weight (volumetric weight vs actual weight via the shipping factor). With quantities set and Max number of containers capped, the excess becomes unloaded items.

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 shipping factor is the main setting for deciding whether Cargo-Planner should aim for containers that are full by weight or full by volume.”

https://cargo-planner.com/docs/calculation/primary-settings/

“Low (e.g. 167) | Weight | Heavy cargo counts for more, giving containers close to max weight”

https://cargo-planner.com/docs/calculation/primary-settings/

Correction: Cargo-Planner revised its documentation after v1.0 and requested a re-audit. Re-scored from the live site on 5 October 2026 by a fresh auditor and independently verified.

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.

“Keep equal ratio: Selected items with the same value for the specified property must be loaded in an equal ratio in each container. For example, if shipment A and shipment B each have 10 items and there are 2 containers, each container will receive 5 items from each shipment.”

https://cargo-planner.com/docs/calculation/custom-rules/

How it is done with general settings

1. Custom rule "Keep equal ratio" on a property (e.g. SKU) for all items (https://cargo-planner.com/docs/calculation/custom-rules/). Each value is then split equally over the containers used, which evens out the item count per container.

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

Auditor-built. The vendor presents Keep equal ratio as a product-mix rule, not as load balancing over units (a use the vendor does not show). No documented option to spread volume or weight evenly.

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.

“No problem, just use the Quantity column”

https://cargo-planner.com/docs/help/faq/

“Sometimes you do not have a fixed number of cargoes to load and distribute on a certain number of containers but you would rather like the tool to tell you how many pieces of a cargo can fit into one or several types of containers.”

https://cargo-planner.com/features/cargo-import/

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.

“A number (defaults to 2), between 0 and 10 that sets the timeout for the load engine (in seconds).”

https://cargo-planner.com/docs/calculation/primary-settings/

“In these cases, allowing the calculation engine to work for minutes (up to 30) can produce better results.”

https://cargo-planner.com/docs/calculation/primary-settings/

Long-running calculations only when the load list has more than 10 cargo types. The API async variant is labelled "Experimental feature - will most likely be charged separately". Reproducibility is not stated.

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

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

“// At the moment each calculation gives one solution (in the future we might provide more)”

https://cargo-planner.com/docs/developer/developer/

“solutions: An array of solutions (Only one solution per calculation is available at the moment)”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

A load list can hold several load plans, but each comes from a separate user-run calculation.

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.

“Selector: What items the rule should apply to. You can create filters with specific properties of items like Items with a length greater than 100cm or Items with a Group/Shipment of “Group A”.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Example: Items with Weight/bundle Greater than 500 kg have a max height of 1.8 m”

https://cargo-planner.com/docs/calculation/custom-rules/

Selectors on about 25 properties plus custom columns, combined with AND; comparisons equals / not equals / less / greater / contains.

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.

“Custom columns come in four variants:”

https://cargo-planner.com/docs/cargo/cargo-properties/

“Custom columns are also very useful in combination with Custom Rules, as you can create effects similar to the default fields.”

https://cargo-planner.com/docs/cargo/cargo-properties/

Cargo-level custom columns (Text, Number, Checkbox, Dropdown). The separate load-list "Custom fields" are metadata only. API: non-base properties are looked up in item metadata.

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.

“Class | Text | Includes classes from the segregation table”

https://cargo-planner.com/docs/calculation/custom-rules/

“A class can’t be stacked, or can’t support other cargo | Cannot support / Can only support”

https://cargo-planner.com/guides/loading-dangerous-goods/

How it is done with general settings

1. Give each item a Class (https://cargo-planner.com/docs/cargo/cargo-properties/). 2. For each forbidden pair, add a Cannot support (or Can only support) rule with Class selectors (https://cargo-planner.com/docs/calculation/custom-rules/); the DG guide shows class-based stacking rules (https://cargo-planner.com/guides/loading-dangerous-goods/). Diagonal case: Cannot support with Class Not equals the selected item’s Class (https://cargo-planner.com/docs/calculation/custom-rules/).

• Combination of general settings, shown by the vendor

The matrix is expressed as a list of pairwise rules. No matrix editor for stacking exists; the segregation table covers unit-sharing only.

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.

“When you have created your classes you need to define which classes that can not be loaded together. If class B cannot be loaded together with class C, press the checkmark in column B on row C and click “Segregate”.”

https://cargo-planner.com/docs/calculation/segregation-table/

“class_id: Any special handling class. Can be used together with the segregation table. Accepts either a string or list of strings”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Symmetric class matrix; an item can carry several classes (API).

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.

“Max total: A max cap for the summed value of a numeric property across all selected items in a single container.”

https://cargo-planner.com/docs/calculation/custom-rules/

“max_total - A max total of summed value based on specified item property that can be loaded into specified containers. `value` consist of {max_total: positive number, property: ItemProperty}”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

The user chooses the property (including custom columns), per container and container type. Per group within a unit is not documented.

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.

“Containers: In what hold-type this rule applies. If left empty, the rule applies to all container types.”

https://cargo-planner.com/docs/calculation/custom-rules/

“Secondary: The same parameters, but applied only to preloaded pallets and boxes, so the two stages of a nested load plan can behave differently”

https://cargo-planner.com/docs/calculation/load-settings/

Custom rules can be limited to container types. Allowed Center of Gravity and Max weight per section are per container type. Primary and secondary settings differ by stage.

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.

“Height and layers. Each item can have a maximum number of layers and a maximum load on top, and a max stacking height caps the build as a whole. Items marked not stackable carry nothing.”

https://cargo-planner.com/guides/ti-hi-pallet-stacking-patterns/

“If multiple overlapping overhang rules apply, the smallest will be used.”

https://cargo-planner.com/docs/calculation/custom-rules/

• Follows from documented behaviour rather than stated outright

Max layers, max load, allow-heavy-on-light, overhang and Cannot support rules are independent settings used together. The only explicit "all at once" statement is on a feature page; docs say only that overlapping overhang rules resolve to the smallest.

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.

“secondary_goal: The secondary objective to optimize for (after minimizing the cost of the solution)”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

“A cost function can be used to optimize for specific goals in addition to loading utilization. The calculated function is added as an additional cost per loaded container.”

https://cargo-planner.com/docs/calculation/cost-function/

The user picks the secondary goal and can add cost terms, but cannot reorder the objectives or set a tolerance.

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.

“A cost function can be used to optimize for specific goals in addition to loading utilization. The calculated function is added as an additional cost per loaded container.”

https://cargo-planner.com/docs/calculation/cost-function/

“Cost functions are an advanced feature for experienced users. Get in contact with us if you need assistance in setting one up”

https://cargo-planner.com/docs/calculation/cost-function/

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

The cost function is a user-writable objective term, but its syntax (API Operator fields scalar, item, unique, count, multiply, sum, average, min, max, per_solution, per_container, per_unique_value) has no descriptions or examples anywhere public. No user extension mechanism for constraints. Custom rules are a fixed list of vendor conditions.

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.

“Strict priorities is the hard version of the same field: a lower-priority cargo is never loaded before a higher-priority one, even if the higher-priority cargo cannot be loaded at all.”

https://cargo-planner.com/guides/planning-a-multi-drop-trailer-load/

“Minimize mixing: Items with different values for the specified property should not be mixed in the same container. A threshold condition controls when mixing is acceptable as a trade-off.”

https://cargo-planner.com/docs/calculation/custom-rules/

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.

“If you want to you can get a detailed response consisting of each container used and the position of each cargo loaded.”

https://cargo-planner.com/docs/developer/faq/

“pos: Position of cargo”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

Origin for components is "measured from the front-left-floor corner"; the origin of cargo pos is not stated. Orientation is given as a rotation.

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.

“Loading Instructions: Step-by-step instructions for loading the container. Configure:”

https://cargo-planner.com/docs/output/loadplan-layouts/

“Mode: By layers, by stacks, or by custom property”

https://cargo-planner.com/docs/output/loadplan-layouts/

Per-step views are shown in images (view settings, features sharing page).

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.

“Container Utilization: Shows weight and volume utilization with percentage bars.”

https://cargo-planner.com/docs/output/loadplan-layouts/

“Items Table: A detailed table of all cargo items in the container.”

https://cargo-planner.com/docs/output/loadplan-layouts/

Per container and, in the Secondary view, per pallet.

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

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

“Cargo-Planner fills the trailer with as many cargoes as possible, and also automatically sums the Loading meters of the cargo in the trailer.”

https://cargo-planner.com/guides/calculate-loading-meters/

“linear_feet: Linear foot [ft] (trucking formula)”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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

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

“It’s a panel which contains cargoes from the load list not currently loaded into any container.”

https://cargo-planner.com/docs/creating-a-loadplan/

“unloaded_items: items that could not be loaded”

https://api.cargo-planner.com/api/2/docs/ (schema https://api.cargo-planner.com/api/2/schema/)

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

“reason: The reason the cargo was unloaded”

https://api.cargo-planner.com/api/2/schema/ (UnloadedItem.reason)

“It’s a panel which contains cargoes from the load list not currently loaded into any container.”

https://cargo-planner.com/docs/creating-a-loadplan/

• Evidence is a label in a screenshot
• Follows from documented behaviour rather than stated outright

The unloaded items panel shows a reason under each item (for example 'Could Not Fit'), seen in the screenshot on the Creating a load plan page, and the API returns a reason per unloaded item. The possible reasons are not listed.

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.

“Center of Gravity: Shows center of gravity position and axle weight distribution (critical for transport safety).”

https://cargo-planner.com/docs/output/loadplan-layouts/

“The axle-weight and centre-of-gravity figures can be placed directly into a custom export layout, so the numbers on the permit paperwork are the same numbers the plan was built on rather than something re-typed from a screen.”

https://cargo-planner.com/guides/planning-out-of-gauge-road-transport/

Layout block for PDF/print; the interactive view shows a CoG marker.

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.

“Once cargo is placed, the interactive view reports the actual axle weights per set. The values shown are:”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

“Front axle weight / Rear axle weight — gross weight on each set, including tare (shown when a tare is set).”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

Whether limits or margins are shown next to the figures is not stated.

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.

Max weight per section is an input rule; no per-section weight output is documented. The CoG block shows "axle weight distribution" (two axle sets), which is the axle row.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for weight distribution, per section output, meter weight report, longitudinal distribution in layouts, exports, interactive view and API HoldData/HoldSummary.

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.

“Container Totals: Displays total weight, gross weight, volume, and Out of Gauge (OoG) information.”

https://cargo-planner.com/docs/output/loadplan-layouts/

“Front axle weight / Rear axle weight — gross weight on each set, including tare (shown when a tare is set).”

https://cargo-planner.com/docs/equipment/axles-and-legal-limits/

That the container "gross weight" includes the container tare is stated for axle figures and pallets; for Container Totals it follows from the term.

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.

“Mode: By layers, by stacks, or by custom property”

https://cargo-planner.com/docs/output/loadplan-layouts/

“Nothing recalculates it for you between stops — if you want to see a later state, you plan it as its own load with the remaining consignments and read the axle weights off that.”

https://cargo-planner.com/guides/planning-a-multi-drop-trailer-load/

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

Loading instructions can be grouped "by custom property" (possibly Destination), but what that mode produces is not described. The routing view shows a map of the route. No per-stop contents summary or view of the unit at each stop is documented; the multi-drop guide says later states must be planned as separate loads.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for per stop, each stop, per destination, stop summary, route view, map view.

Correction: The evidence is unchanged since v1.0. On re-reading, no page describes what loading instructions by a custom property produce, so a per-stop summary rests on an undescribed setting (rule: undescribed field). Confirmed on independent verification.

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.

“When cargo actually uses its overhang permission, the interactive view marks the trailer with an OOG indicator in the out-of-gauge list.”

https://cargo-planner.com/docs/cargo/oog/

Manual editing (drag, snap, rotate) and API edit endpoints exist, but no check of an edited plan against the item rules or a violations list is documented. Only the OOG/extended-trailer indicators and the import data warnings are described.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for validate, violation, warning, check plan, rule check, invalid placement, conflict in the interactive view, modifying a load plan, planner view and the API edit endpoints (insert_items, move_items, remove_items).

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

Counts when: Documented void or empty-space output.

“Set the automatic bottom spacer property and the tool will check if this increases the utilization and add this dunnage material for you!”

https://cargo-planner.com/air-container-loading-software/

The automatic bottom spacer adds dunnage under a ULD build, but that is not void detection or void output.

Where we looked

Read in full on 2026-10-05: all 53 English pages under cargo-planner.com/docs/ (admin pages skimmed), the full OpenAPI 2.1.0 schema at api.cargo-planner.com/api/2/schema/ (all component schemas and paths), all 18 guides, all 16 news posts, the 6 feature pages, 6 solution pages, 4 mode pages, calculators, integration, pricing, about, and 8 sampled equipment-library pages. Text-searched the extracted text of all of these; searched for void, empty space, gap report, dunnage, airbag, filler material.

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

Counts when: Documented plan cost output.

“Container Info: Displays container dimensions, payload capacity, and cost information.”

https://cargo-planner.com/docs/output/loadplan-layouts/

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

A layout block lists 'cost information', but nothing says what cost is shown, and the API result has no cost output (a container's cost is an input). No per-item cost allocation is documented.

Correction: The evidence is unchanged since v1.0. The only source is 'cost information' in a list of what one layout block shows, with nothing saying what cost is reported (rule: undescribed field). Found on independent verification.