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/

“Inside length in meters”

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

Library of preset containers, trailers, ULDs, pallets plus custom containers; typed or overridden dimensions via API container_types.

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" flag and "Max load" (weight the part can support on its top surface). Wheel wells are shown modelled this way in the touring guide.

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.

“Custom | Custom part”

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

“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/

Multiple components per container, each with its own L/W/H and X/Y/Z (or anchoring). No stated maximum count. Separately, custom rule "Cannot be loaded in zone" gives per-plan keep-clear regions anchored to container sides.

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.

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

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

“Max loading height allowed of cargoes in m”

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

Per-equipment Max loading height is editable per load plan in Setup ("Now you can change some container properties on the fly") without editing the library container; plan-level Max stacking height also exists. The docs mostly show max height used to raise the limit on open equipment (wrong-settings page); lowering it below internal height rests on the field definition.

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. ... Height | How much higher the deck sits above the main floor.”

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

Decks span the full width only; mezzanine levels are floor components.

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.

“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/

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

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

Side 1 / Side 2 contours cut the cross-section (e.g. ULD lower-deck cut-backs). One triangular cut per corner; arbitrary polygons need components.

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/

“Contours — triangular cuts at the bow and stern corners of the hold to describe the taper of the hull.”

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

Front/rear contours change the floor or ceiling height along the length; side contours change the cross-section; all eight are defined on the same container. Decks (lengthwise steps) and contours are both tabs of the same container editor.

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.

“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.”

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

“Length or Width | How far in from the corner edge the cut starts. ... Height | How much of the corner is cut away, measured from the floor or ceiling.”

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

The ULD guide states curves themselves are not modelled ("Curves themselves are a hard problem"), so a curved roof is one chamfer per corner.

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.

“Add a Floor preset, set the Z position to the mezzanine height, and Stick to Side 1 + Side 2 so the floor spans the full width. Leave Not stackable off and set Max load to describe what the mezzanine can carry.”

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

“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/

Most widely available form: floor/wall components inside one container. The full multi-hold/road-train form (Set Builder) is Enterprise-only.

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 info ... Door height in m ... Door width in m”

https://api.cargo-planner.com/api/2/schema/ (HoldData.door / HoldDoor)

Set Builder group doors are explicitly "not currently enforced by the load calculation"; the container-level door is enforced per the FAQ.

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.

“If the door is at longside of container”

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

“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/

A longside-door flag exists but no page says it changes how the load is built; the set-level door incl. At longside is stated as not enforced. Loading style (front-to-back / bottom-up) is a fill direction, scored under positioning. Open-top containers are "Loaded from above" as a description of the equipment, not as a solver setting.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "side load", "curtain", "longside", "access", "loading face", "top load", "door"; container editor, open containers, set builder, primary settings (loading style), API HoldDoor.

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. No side walls | Removes Side 1 and Side 2 | Cargo may overhang laterally past the width. No end walls | Removes Front and Rear | Cargo may overhang past the length.”

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

“Max length, Max width, max height on the trailer | Setup → Expand selected equipment | Grants items permission to overhang in given directions by a set distance.”

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

Source nuance: the open-containers page says overhang "is unbounded on any open side unless the equipment has a Max length, Max width or Max height set", while the OOG page states a 33% default. API field descriptions for no_roof and no_side_walls are swapped (no_roof says "If there should be side walls").

Correction: Before publication, Cargo-Planner corrected its open-containers page, which had contradicted the 33% out-of-gauge default stated elsewhere. The verdict is unchanged.

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/

Limits: max 40 000 loadable cargoes per calculation; optional cap via "Max number of trailers to be used" / per-type qty.

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/

“The solver then chooses between the selected equipment (containers, pallets, sets) based on the load and its constraints.”

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

The docs example (wrong-settings) shows a 20ft DV, 40ft HC and 40ft OT selected together with the tool assigning cargo across types.

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.

“A max number of this container type to be avaialable”

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

“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 qty (API; "max quantity" in aircraft setup) and a combined max_containers cap. The docs state the remainder becomes unloaded items 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.

“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/schema/ (Calculation.containers)

“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/

A library "priority" integer on holds (Hold.priority) has no description and is not relied on.

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

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

“The 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/schema/ (InlineHoldData.cost)

“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/

How it is done with general settings

1. Offer several container types and give each a fixed cost that rises with size (API InlineHoldData.cost, example 100 for 20ft / 180 for 40ft) [api]. 2. The solver minimises total cost across the plan [cost-function page: "Cargo-Planner will try to find a solution where the cost is minimal"; export-container guide]. 3. With size-ordered costs, the minimum-cost solution uses the smallest type(s) that hold the load, including for the last unit [inferred from 1-2].

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

No dedicated "smallest sufficient type" or last-unit downsizing option is documented. greedy_container_selection ("Generally minimizes the contents of the last container-type") is a related but different API switch. Without costs the docs only say the tool picks the "most suitable" types.

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.

“Default Cost | The set’s default relative cost, used by the solver’s cost objective when the set is chosen.”

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

“The plan then minimises total cost rather than maximising how full each container is, which are two different answers whenever container types are priced differently.”

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

Flat cost per container/set type; optional cost function adds per-container costs; no rate tables. Solver wording is "will try to find a solution where the cost is minimal".

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 loading volume allowed of cargoes in m3”

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

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

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

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

Cap is an absolute volume (m3) per container, and payload can be overridden lower per plan; no percentage input. A percentage cap is reached by arithmetic on the container volume.

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.

“Items cannot be loaded in a container that doesn't meet the limitations provided. The rule is applied after the container is finished loading”

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

The API condition cannot_load_in_container_with could plausibly express a minimum-fill test, but "the limitations provided" are not described anywhere, so it does not meet the pass condition (undescribed field). Minimize mixing thresholds concern mixing, not fill.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "minimum", "min fill", "min_", "under-filled", "at least", "threshold"; primary settings, custom rules page, API ConditionEnum and settings.

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/

“We need to tell the app to load the cargo in specific pallet types. To do this, we double click the “load in” column for the cargo, and in the dialog we select the pallets that this cargo should be loaded in.”

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

Per item (Load in / allowed_containers) and per selector (Must be loaded in / Cannot be loaded in rules); includes pallet type.

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)

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

Only via API endpoints that load given items into one designated existing container. In the web app, assignment to an individual unit is by drag and drop (workaround); the Load in column and rules work on container types, not 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 crate guide recommends building two or three candidate crates and comparing counts. The Packaging and crating solutions page claims "Design optimal crate dimensions" (marketing), contradicted by the guide.

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: Length Width Height Weight”

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

“Max number of loadable cargoes in one calculation: 40 000”

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

Limits: 40 000 loadable cargoes per calculation; minimum side 1 mm, minimum volume 3 cm3. No limit on number of item types stated.

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. Supported in excel exports, placement and instructions”

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

“For Regular Cylinders: Length: Outer diameter of the cylinder Width: Outer diameter of the cylinder (typically same as Length for circular cross-section) Height: Length/height of the cylindrical object”

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

Solid and hollow cylinders (outer and inner diameter). Whether packing uses the round shape rather than the bounding box is stated only for display/placement ("proper rounded objects").

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.

“We’ve added pipe and coil loading capabilities to Cargo-Planner, with the possibility to nest pipes within pipes.”

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

Only telescoping (pipes inside hollow pipes) is documented, which is cavity use, not offset-row nesting. Marketing says the tool "will find an optimized solution even if you add pipes and boxes" without describing arrangement.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "nest", "honeycomb", "stagger", "pyramid", "hexagonal", "offset"; cylinders doc, pipe-loading news post, road/sea landing pages, feature 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 user works out the interlocked pair outside the tool and enters the combined bundle dimensions; the planner does not use both shapes. Inner spaces place cargo by its outer dimensions.

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 - Smaller cargo items can be loaded into the inner cavities - Weight and stacking rules still apply within inner spaces”

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

Up to 10 box-shaped cavities per item, positioned by anchors or X/Y/Z; hollow cylinders also take items. Custom rule "Cannot contain" restricts what goes inside. The crate guide notes the host item is not reported as a container.

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.

“3D model”

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

Geometry is box, cylinder or hollow cylinder; "Complex geometries" are handled via inner spaces (box cavities). Items can have an attached file of type "3D model" but no page says the planner packs by it. Project-logistics marketing claims "Model complex geometries", undocumented.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "CAD", "mesh", "STL", "3D model", "arbitrary", "irregular", "complex geometr"; cargo properties (Geometry), inner spaces, API GeometryEnum/FileTypeEnum.

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.

"Breakbulk" pages concern piece cargo in vessel holds, not bulk cargo.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "bulk", "liquid", "shapeless", "amorphous", "by volume"; cargo properties, API GeometryEnum.

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/

Compression exists only as a plan-wide negative error margin (-50 to 50 %) applied to every cargo, not as a per-item allowance; the pass condition requires per item.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "compress", "squeeze", "bulge", "error margin", "margin"; cargo properties, primary/secondary settings, custom rules, API item fields.

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/

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

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

Several bundle levels per item with their own dimensions, weight and properties; partial bundles and even spread options. The documented breakdown fills the largest level first.

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 The cargo can be rotated. Default option for box geometry”

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

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

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

Per item. "Rotatable" (value 3) = the two orientations with the original height vertical, i.e. upright with turning allowed.

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/

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

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

Per item (Longship = orientation value 1). Also per rule: "Must load with pattern" restricted heightwise two-block keeps most cargo longship.

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/

“Tiltable (index 63 orientations): Can be oriented in any direction”

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

Per item (value 63 = all six bits).

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.

“Custom 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

A six-bit mask (1-63) with one bit per orientation allows partial tipped sets. Only bits 1 and 2 are named; the meaning of bits 4, 8, 16, 32 is not listed, and the custom editor is shown only in screenshots (pipe-loading news: "We’ve clicked the Custom value in Orientations to get a 3D view of the rotations that are allowed").

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

“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/

“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

Same evidence as side-not-end; 63 values = 2^6-1 non-empty subsets of six orientations.

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/

No per-item soft orientation preference. The closest is a pattern option that keeps "the majority" of cargo longship, which is a pattern, not a preferred orientation.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "prefer", "preferred", "where possible", "soft"; orientations doc, cargo properties, custom rules, API.

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.

Custom rules can combine selectors but no condition ties orientation to floor/non-floor placement.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "floor", "bottom layer", "orientation" combined with floor/bottom; custom rules conditions list (API ConditionEnum), orientations doc.

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.

Max layers and max load are single values per item.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "on side", "per orientation", "orientation" with "layers"/"max load"/"stack"; cargo properties, custom rules, API item fields.

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.

"Tiltable" means any of the six orthogonal orientations. The windows case study describes windows leaning on a pallet wall modelled as custom equipment, not angled placement by the planner. The interactive view allows manual rotation (workaround).

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "angle", "lean", "tilt", "degrees", "non-orthogonal"; orientations doc, interactive view, news (windows on trailers).

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 (crosswise) The cargo can only be loaded laying in its crosswise direction”

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

Per item. Minor source conflict: the cargo-properties page says "Cylinder: A cylinder laying down" while the orientations and cylinders pages say cylinders stand by default.

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.

“Not stackable 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/

Per item; custom rule "Always stackable" can override for selected items/pallets.

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

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

“Bottom only 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.

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/

“Selected items must be on top of specified item types. `value` should be an ItemSelector”

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

How it is done with general settings

1. Add custom rule with condition "Must be on top of" [custom-rules page]. 2. Selector = the item(s) that must not stand on the floor [custom-rules page, Selector]. 3. Second selector (the permitted base items) = all cargo, e.g. an empty selector or weight > 0 [API ItemProperty/ItemSelectorField: empty selector matches all items; comparison gt]. Result: the item must rest on another item, never on the floor.

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

No dedicated "not on floor" flag; the condition names specific base item types.

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.

“Max Layers 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 number representing the max amount of layers this item can be stacked in”

https://api.cargo-planner.com/api/2/schema/ (ExtendedBaseItem.max_layers, maximum 255)

Per item (0-255). "Max Layers per SKU" / max_layers_by_prop restricts the count to same SKU or same 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.

“Max Layers per SKU Cargo max layer option is only applicable on items with same SKU. This means that when this is enabled, even if SKU-A has max layers set to 3, we can still stack SKA-B on top of it.”

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

“If enabled then cargo max layer option is only applicable per item property (like SKU or Shipment) (and not aggregated)”

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

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

That the per-item limit counts mixed stacks by default is stated only as the converse of the per-SKU option ("and not aggregated").

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. ... Max stacking height limits how high the item needs to be lifted during loading.”

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

Per item or attribute-selected group via custom rules, in length units; both top-of-item and bottom-of-item forms.

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 load 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/

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

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

Per item, weight. Whether it counts the whole column above or only the directly supported item is not stated. Components also carry a 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 plain weight.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "pressure", "per area", "kg/m2", "contact area", "surface"; cargo properties, API 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.

“Max load 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/

No statement either way on whether max load is checked within stacks of the same item; the Ti-Hi guide discusses bottom-layer load but describes it as a limit the user sets as max layers or max load.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "same item", "same SKU", "identical", "max load"; cargo properties, primary settings (max layers per SKU), API.

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

Counts when: A documented weight-ordering stacking rule.

“Allow heavy on light 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. It will likely affect the utilization. It is set to true by default.”

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

“If loading a cargo with weight 20kg is okay to be loaded on top of a cargo with weight 10kg is allowed”

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

Plan-level switch (default: heavy on light allowed). Custom rule "Cannot support" can express "restricting stacking to items within a certain weight ratio".

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/

“Cannot support Selected items cannot support specified item types. Useful when you need fine-grained control over stacking combinations”

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

How it is done with general settings

1. Create a Number custom column, e.g. "Stackability grade" [cargo-properties page, Custom columns]. 2. For each grade value g, add a custom rule: selector grade eq g, condition "Cannot support", second selector grade gt g (items with a higher required grade) [custom-rules page; API ComparisonEnum eq/gt; custom columns are looked up in item metadata per ItemSelectorField]. 3. Items are then never placed on an item with a lower grade.

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

No built-in stacking index; the vendor names "Stackability grade" as an example column but does not show the ordering rule.

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.

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

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

“Can only support Selected items can only support specified item types. The inverse of Cannot support — useful when a base item is only structurally suitable for specific cargo on top, such as a pallet designed for a particular product.”

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

Pairwise permission via item selectors (by SKU, name, class, any property).

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/

“Cannot support ... 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 with condition "Can only support"/"Cannot support" [custom-rules page]. 2. Second selector on length and width relative to the base item (is_dynamic: "Is this value relative to the main selected value? Only viable on sub-selectors like condition: can_only_support") [API ItemSelectorField.is_dynamic]. The vendor shows the same-dimensions variant as an example rule.

• Combination of general settings, shown by the vendor

No dedicated footprint/column switch; the vendor example image is the main evidence of the configuration.

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.

“Allowed overhang 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/

“Allowed overhang Selected items can have this amount of overhang. Overrides the overhang in settings for these items. If multiple overlapping overhang rules apply, the smallest will be used.”

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

Separate values for the pallet stage (secondary 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.

“Height tolerance 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/

Plan-level (and pallet stage via 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 and hollow cylinders let cargo go inside an item (cavity row), not nesting height increments or top-shape bearing.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "nest", "nesting", "increment", "open top" (cargo), "top shape", "smaller top"; cargo properties, inner spaces, API.

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.

“It lets you specify what a master carton looks like, how a pallet should be packed when full”

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

“Setting it to `false` will load non-full bundles without any bundling”

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

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

No complete-stacks/complete-layers/flat-top rule. A user can enter a complete layer or stack as a bundle with partial bundles off, so only full ones are built and the remainder is loaded loose, but the layer/stack geometry has to be worked out outside the tool.

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/

“Cargo with the same value of the given property will be loaded closely together. ... Set `ignore_reachability` to true to only keep the groups together”

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

How it is done with general settings

1. Custom rule "Group by" [custom-rules page]. 2. Property = SKU (or Name) [custom-rules page: "Property: The column in 1.Data that determines what group a cargo belongs to"; API: property may be any item property]. 3. Optionally ignore_reachability=true to only keep groups together [API].

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

No dedicated like-items-together switch is documented; the API example request contains "group_items": true, which is not in the schema. Block patterns ("One block") concern orientation of large groups, not togetherness.

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 / Consignment 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/

“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/

One grouping field plus Group by rules on any other property (e.g. Destination, custom column), so two-level grouping is composable.

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.

“Use at most a single container per shipment 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/

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.

“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/

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

“Can only be side-by-side with Selected items can only share a lengthwise section of the container with specified item types. The container is divided into slices along its length, and this rule restricts which other items are allowed to occupy the same slice.”

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

“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/

How it is done with general settings

1. Give items a Group/Consignment ID [cargo-properties page]. 2. For each group G, add custom rule: selector Group eq G, condition "Can only be side-by-side with", second selector Group eq G [custom-rules page]. 3. Each lengthwise slice then holds items of one group only, giving separate sections along the length.

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

No physical divider/barrier item is documented. "Group shipments together" gives contiguity but not an exclusive section.

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.

“Cannot support Selected items cannot support specified item types. Useful when you need fine-grained control over stacking combinations — for example, preventing cargo from different shipments from supporting each other”

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

How it is done with general settings

1. Custom rule "Cannot support" with the selector on one group (Group/Shipment eq A) and the second selector on another group (ne A) [custom-rules page, which names this use].

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

“Cannot be loaded with Selected items cannot be loaded in the same container as specified items. Useful for segregating incompatible cargo”

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

“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/

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/

“Say you’re loading Class 3 flammable liquids and Class 8 corrosives that can share a container but need at least a meter of separation. Rather than eyeballing that gap in the load plan, a single Must keep distance rule between the two classes holds it on every container the engine generates”

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

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/

Segregation is user-defined (Class + segregation table, custom rules). Marketing claims "Ensure proper planning for dangerous goods" (airlines page).

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.

“Cannot exceed quantity A max cap for the specified items in specified container types.”

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

“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/schema/ (ConditionEnum)

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 number of different cargo types that can be loaded into specified containers.”

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

“A max cap for number of types that can be loaded into specified containers. `value` consist of `{count: positive integer, property: ItemProperty}`”

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

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/

• Follows from documented behaviour rather than stated outright

The ratio is taken from the loaded quantities (e.g. 10 tables, 40 chairs over 2 units gives 5 and 20 per unit); no user-entered ratio or set definition; behaviour when quantities do not divide evenly is not stated.

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.

Bundles pack items in fixed counts but do not constrain how many units of an item a container receives.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "multiple of", "batch", "increments", "per container" with quantity; custom rules, bundling, API.

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.

“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/schema/ (Calculation.containers)

“All items in container (also including any non cargo items like posts, frames etc”

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

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

API only: existing (already loaded) containers can be passed in and the calculation loads items into them first, then into new containers; insert_items/load_into_space add items to an existing container. The web docs describe manual modification (drag, unload, move) but no automatic completion around manual placements.

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.

“Position of cargo”

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

“Load cargo into this space”

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

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

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

API only. Positions can be supplied through existing containers (HoldData.items with pos) or a load_at_position point for load_into_space. Neither is described as an input contract beyond the one-line field descriptions.

Correction: Item.pos is a results field reused by the containers input; no source says users may enter coordinates or that given positions stay fixed.

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/

“Must touch side Selected items must be placed flush against specified container sides.”

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

Zones are side-anchored depths (intersection when several sides); empty zones leave items unloaded.

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. See Must be loaded in zone for a description of how zones are defined.”

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

Per item/selector (empty selector = all items); side-anchored zones only, so a central aisle is not expressible this way.

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. ... Load from bottom up | Will load the cargoes from floor and upwards.”

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

“Row-by-row | Fill cargo across the full width one row at a time, advancing from front to back. ... Stack-by-stack: sweep across width ... Stack-by-stack: sweep along length”

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.

“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/

“Row-by-row | Fill cargo across the full width one row at a time, advancing from front to back. Keeps height low and uniform.”

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

Stated as "will try".

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

Reach applies between groups of the Group by rule.

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.

“Margin 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 (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/schema/ (ExtendedBaseItem.free_space)

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.

“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/schema/ (CalculationSettings.require_front_support)

“Must touch side Selected items must be placed flush against specified container sides. Useful for cargo that needs to be loaded against a wall for stability”

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

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

require_front_support appears only in the API schema, not in the web docs.

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 in kg - max net weight”

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

“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); per-plan override in Setup. No scale switch-off documented.

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.

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

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

“Per-hold adjustments — a slightly deeper hold three, a heavier payload on hold one — are stored as overrides on the position, not on the container type.”

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

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

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

“The length of the container is divided into fixed sections of `value.length` meters, measured from the loading end. The cargo weight within each section cannot exceed `value.weight` kilograms.”

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

The documented per-section limit uses one weight value for equal-length sections (scored under linear density); different maxima for front/middle/rear sections are not documented. Zones cannot carry a weight cap (max_total is per container).

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "section", "floor strength", "meter weight", "zone" with weight; custom rules page, API ConditionEnum, axles page.

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.

“The length of the container is divided into fixed sections of `value.length` meters, measured from the loading end. The cargo weight within each section cannot exceed `value.weight` kilograms. Cargo that overlaps a section boundary contributes weight to each section it overlaps, in proportion to how much of its footprint lies within that section. ... Useful for floor strength and axle load limits, sometimes called meter weight.”

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

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

API only; not listed on the web custom-rules page (which says "This list is frequently being updated").

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”

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

Two axle sets (front, rear), each 0-9 axles treated as one bearing point.

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. An axle set is a group of axles the load plan treats as one bearing point.”

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

Exactly two axle groups per container (each up to 9 axles). Road-landing marketing mentions "a custom supertrailer with 8 axles", which fits within two groups.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "axle", "tridem", "third", "tractor", "drive axle"; axles page, set builder, decks, road landing page, API (HoldData.axles is "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/

A single container tare is used for gross axle limits and reports, but how the tare is split between the front and rear sets is not documented; per the definition note this fails.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "tare", "empty weight", "unladen"; axles page, API HoldData.tare.

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.

Road trains are modelled as sets; no axle-load transfer between units is described.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "kingpin", "fifth wheel", "drawbar", "coupling", "tractor", "towing"; axles page, set builder (road trains), OOG road guide.

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/height and axle limits are values typed per vehicle; no region or jurisdiction presets.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "jurisdiction", "country", "region", "bridge formula", "permit", "legal"; axles page, OOG road guide, 53ft trailer guide.

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.

“Limit the allowed center of gravity This setting will make sure the center of gravity is put in the specified X (length) and Y (width) interval. Will most likely affect the utilization of the container in a negative way.”

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

“Limit the distance the center of gravity can have from the center of a container”

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

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.

“This setting will make sure the center of gravity is put in the specified X (length) and Y (width) interval.”

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

“Distance from center in percentage”

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

Also per-item "Must be loaded along centerline" rule for lateral balance of heavy 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.

CenterOfGravity has x and y only.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "vertical", "height of centre", "z", "centre of gravity"/"center of gravity"; primary settings, API CenterOfGravity (x and y only).

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

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

“Improve stability | Will try to pick solutions that are more stable”

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

“If set to true then all containers must have its Center of Gravity within 10%”

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

CoG and axle rules are hard limits; "Improve stability" is not defined as weight balancing. Marketing mentions "Optimize weight distribution" and "keeps overhang balanced" without a mechanism.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "balance", "centre", "center", "even", "distribute", "stability"; primary settings, guides (loading instructions, OOG road, touring), landing pages.

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 of the design, but no item CoG input exists in the item schema.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "centre of gravity"/"center of gravity" per item, "offset", "eccentric"; cargo properties, API item fields.

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: loaded first = deeper (further from the door).

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

“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/

“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/

API: set_as_fillers loads "into existing containers where there are space left", i.e. fillers do not open another unit.

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.

“Enable routing when you want the load plan to sequence cargo by delivery stop so the trailer is unloaded in the reverse of the loading order — last-loaded first-out. Cargo-Planner reads the per-item Destination value and orders the plan accordingly.”

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

“Routing is only available for road-type load plans.”

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

• The vendor's own sources disagree on this point

Road load plans only; requires Port of loading. Stops are matched as text. Priority within a stop is not described (routing overrides priority for load order).

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.

“Group by ... Includes options for reachability to ensure the loading and unloading of each group can be handled without moving another cargo group.”

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

“Set `ignore_reachability` to true to only keep the groups together, without enforcing that each group stays reachable while loading and unloading”

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

How it is done with general settings

1. Set Destination per item [cargo-properties page]. 2. Custom rule "Group by" with property Destination, reachability on (reach length, reach to back of cargo, access width) [custom-rules page; multi-drop guide shows exactly this]. 3. Optionally Enable Routing for the stop order [routing page].

• Combination of general settings, shown by the vendor

Routing alone is described as last-in-first-out sequencing without a stated blocking guarantee in the docs; the 2022 routing news post says it "can now ensure that each package is possible to unload at each stop". The multi-drop guide lists Group by among the "loose end" options and says routing and custom rules "do not combine".

Correction: Before publication, Cargo-Planner corrected its multi-drop guide, which had described Group by as a loose option while the rules reference and API state reachability is enforced. The verdict is unchanged.

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 a loader can reach over another group) is related but is not a stop-overlap distance.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "overlap", "mix", "look-ahead", "reach length"; routing, custom rules (Group by, Minimize mixing), multi-drop guide.

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.

Items have a Destination only; the plan has one Port of loading.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "pickup", "pick-up", "collection", "origin", "load at"; routing, cargo properties (Destination only), API item fields.

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/

Evidence is a product-update news post (30 Nov 2022); the docs routing page is silent on multi-unit plans.

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/

“Group / Consignment Different cargoes can belong to the same group / shipment / consignment.”

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

How it is done with general settings

1. Give all items of one stop the same Group/Consignment ID [cargo-properties page]. 2. Enable "Entire shipments must be loaded or none" [primary settings]. 3. Allow shipments to share a container (the default puts different IDs in different containers; change in Load settings) [cargo-properties page].

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

No stop-level (Destination) all-or-nothing switch.

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 for organising load lists; moving cargo between dates is manual.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "date", "due", "ETD", "calendar", "recurring"; projects, creating a load plan, API loadlist fields.

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/

“The General tab’s separate Floor height field is the thickness of the floor or deck below the cargo”

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

• Follows from documented behaviour rather than stated outright

Pallet = secondary equipment with floor height (deck thickness) and max height. Whether max height is measured from the ground (including the deck) is not stated; the pallet guide says the Max Height "should not exceed the size of the trailer door".

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

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/

“One block — all cargo is rotated in the same direction - Two block — two groups of cargo where the rotation differs between each block - Four block — four adjacent groups of cargo, each with a different rotation”

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

Patterns are documented for "large groups of cargo within the container"; that they apply to pallet builds is by way of secondary settings rules. No alternate-layer rotation (interlock) switch is documented, though the Ti-Hi guide says customers' interlock builds "usually work straight away".

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/

“Instead, we set up their standard builds in Cargo-Planner and 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.

“One detail catches out more of our customers than anything else in this section: the edge of the pallet is a hard limit. ... To a load planning algorithm, a few millimetres over is simply not allowed, so that pattern never comes up. Fixing it is a judgement call - trim the packaging, or set up a custom pallet a few millimetres larger”

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

“Import your cartons from Excel and Cargo-Planner returns the palletization: layer patterns per pallet, balanced overhang where you allow it”

https://cargo-planner.com/pallet-calculator-software/

• The vendor's own sources disagree on this point

The vendor guide states pallet-edge overhang is not allowed and recommends a larger custom pallet (workaround). The pallet landing page claims overhang "where you allow it" without documenting a setting; equipment Max length/width overhang limits are documented for open containers and trailers only.

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.

“If none of them are large enough to fit your cargo, we will load the item with balanced overhang on each side.”

https://cargo-planner.com/pallet-calculator-software/

Only a marketing mention of balanced overhang for oversized items; no centre-load or inset setting.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "centre", "center", "centred", "underhang", "inset", "edge"; working with pallets, secondary settings, Ti-Hi guide, pallet landing page.

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

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

A "slip-sheet" is mentioned only as a reason to use a container bottom spacer.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "interlayer", "slip sheet", "slip-sheet", "tier sheet", "layer pad"; all pages.

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”

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/

• Follows from documented behaviour rather than stated outright

Via the shipment settings in the secondary (pallet-stage) settings; the docs do not name this setting on the secondary page.

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.

“This is set if this item itself is a container (for example a pallet with items inside)”

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

A pallet-with-contents item representation exists in the schema but saving a built pallet or carton as an item for a later plan is not described; "Display secondary equipments as cargo" is a display preference.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "save pallet", "built pallet", "from_container", "carry", "reuse", "as cargo", "Display secondary equipments as cargo"; working with pallets, modifying a load plan, preferences, API.

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.

“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/

“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/

How it is done with general settings

1. Define a bundle (e.g. a 12-pack carton) on the item and set that bundle to be palletised [bundling page]. 2. Add pallet types as secondary equipment [working-with-pallets page]. 3. Calculate: pieces are packed into 12-packs, 12-packs onto pallets, pallets into the container [bundling page example].

• Combination of general settings, shown by the vendor

The inner level is a user-defined bundle (fixed carton contents), not an optimised cartonisation; pallets on pallets is claimed on the features 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.

“Preload If this cargo should be pre loaded on a pallet or box (secondary equipment) before being loaded into the container - check this to true”

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

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

“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/

“`in_secondary` - This selector applies to secondary containers (like pallets) containing items matching the selector”

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

Pallet (sub-container) types also carry item-style properties (orientations, not_stackable, bottom_only, max_layers, max_load) in the API (InlineSubContainer.properties), listed without further description.

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/

Evidence is a product-update news post (4 Mar 2024) describing the palletisation algorithm; not repeated in the docs.

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/

“Max number of trailers to be used Set an upper limit to how many containers are to be used for loading your imported cargo. Excess cargo will become unloaded items.”

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

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 volumetric weight is compared against the package’s actual weight. Whichever number is higher is used as the chargeable weight which may affect the loading of cargoes.”

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

Secondary goals are minimise length, minimise height, stability. Chargeable weight "may affect the loading" without a stated objective. A cost function could in principle reward weight, but its grammar is undocumented.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "maximize weight", "weight utilization", "objective", "goal", "chargeable"; primary settings (secondary goal options), cost function, API SecondaryGoalEnum.

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 all items [custom-rules page]. 2. Property = one shared by all items (or per SKU) [custom-rules page]. 3. Each container then receives an equal share of the items (count), instead of filling containers in turn [custom-rules page example: 10 items over 2 containers = 5 each].

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

On independent verification: unclear. Docs allow two readings of 'Keep equal ratio'; under one the recipe does nothing. Left as scored, as for competitor cells the verifiers marked unclear.

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.

“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. With Cargo-Planner you can easily do this, or use "fillers" - cargoes to fill up remaining space in a container when all other cargoes have been loaded”

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

“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/

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.

“Max calculation time A number (defaults to 2), between 0 and 15 that sets the timeout for the load engine (in seconds). In general if you have multiple container types and many different cargo types a better result can be generated by increasing this number.”

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

“Long running job (Minutes) ... In these cases, allowing the calculation engine to work for minutes can produce better results.”

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

API timeout 0-15 s, async 30-1800 s. Reproducibility 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.

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

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

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

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

Alternatives require separate calculations (e.g. several load plans per load list).

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”. You can combine multiple filters, selecting a smaller and smaller section of the total items with each filter.”

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

“Items with a weight greater than 25 kg cannot be loaded in 747-400F Bulk Compartment”

https://cargo-planner.com/news/loading-with-custom-rules/

Any item property; comparisons eq, gt, lt, ne, contains, not_contains; ANDed selectors.

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 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/

“If not a base property is provided, a lookup will be done in item metadata if any”

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

Text, Number, Checkbox, Dropdown columns; example "self-stackable only" checkbox used in a rule (screenshot). Company-level custom fields on load lists are metadata only.

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 Used for adding custom classes to your cargo. Classes can be used together with a segregation table to separate loading of certain cargoes.”

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

“Cannot support Selected items cannot support specified item types. Useful when you need fine-grained control over stacking combinations”

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

How it is done with general settings

1. Assign each item a Class [cargo-properties page]. 2. For each forbidden (lower class, upper class) pair add a "Cannot support" rule with selector Class eq lower and second selector Class eq upper, or one "Can only support" rule per class listing allowed upper classes [custom-rules page; DG guide maps class stacking to these rules].

• Combination of general settings, shown by the vendor

No matrix editor for stacking (the segregation table is for sharing a unit); the matrix is a set of pairwise rules.

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/

“A symmetrical table with codes”

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

Items may carry several classes (class_id accepts a list).

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.

“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/schema/ (ConditionEnum)

“The property of the item, (lengt, width, height, weight...). If not a base property is provided, a lookup will be done in item metadata if any”

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

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

Per container (type-scoped); the ItemProperty also carries its own selector. Documented in the API only; the web rule list shows "Cannot exceed quantity".

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/

“The center of gravity of the specified containers must be within the provided distance from their center. Overrides the `cog_limit` in settings for those containers.”

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

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.

“The property that decides the most here is which pieces can be a base and which cannot. Four fields carry it: Not stackable ... Bottom only ... Max load ... Max Layers”

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

“Where stability matters more than the last few centimetres, building in layers rather than towers is a setting rather than a discipline, and the allowed overhang and single cargo support settings decide how much a piece may stand proud of whatever is under it.”

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

• Follows from documented behaviour rather than stated outright

Per-item stacking properties, plan-level stacking settings (heavy on light, overhang, height tolerance, single support) and stacking rules are independent inputs; the explicit "all of them at once" statement is on a feature page. "If multiple overlapping overhang rules apply, the smallest will be used."

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.

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

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

“A secondary goal — minimise used length or height, or improve stability — applies once the vehicle count is settled.”

https://cargo-planner.com/guides/what-is-a-load-plan/

Only one secondary goal at a time; no user tolerance between levels.

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 Operator grammar (scalar, item, unique, count, multiply, sum, average, min, max, per_solution, per_container, per_unique_value) is listed in the schema without descriptions or examples; the docs page gives no syntax.

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.

“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/

“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/

“Position of cargo”

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

Per item position (x, y, z) plus placed L/W/H in m; rotation format and origin/axes are not described (components use a front-left-floor origin).

The plan includes step-by-step loading instructions, with a diagram for each step.

Counts when: Documented step-by-step instructions with per-step views.

“Loading Instructions Step-by-step instructions for loading the container. Configure: - Mode: By layers, by stacks, or by custom property - Show secondary equipment: Include pallets, frames, etc.”

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

“Our software will make sure that for each step, there is enough support from below in the previous steps, when filling a container or a truck and that there is a good balance between number of cargoes in each step”

https://cargo-planner.com/guides/the-importance-of-proper-loading-instructions/

• Evidence is a label in a screenshot

Per-step views are shown in screenshots ("Loading instructions of a trailer", "A load plan printed as a numbered, step-by-step loading sequence"); the text does not say each step carries its own diagram.

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/

Also for secondary equipment ("Simply toggle between viewing your primary and secondary equipment"); Excel export with per-container sheets.

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

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

“Linear foot [ft] (trucking formula)”

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

“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/

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/

“items that could not be loaded”

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

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

“The reason the cargo was unloaded”

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

“As we see in this example, some of the cargoes found here are either too tall or too wide to be fit in the selected containers.”

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

API field per unloaded item; its possible values are not listed. The web docs describe the unloaded-items panel with examples of causes but do not state that a reason is shown per item.

Correction: On independent verification: the field's purpose is described, so the undescribed-field tag was misapplied. Raises Cargo-Planner by one row.

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”

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

• Follows from documented behaviour rather than stated outright

The interactive view shows only a CoG marker ("a circular symbol"); numbers are in the layout block. The API result schema has no CoG field. Axes shown are not stated.

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: - Front axle weight / Rear axle weight — gross weight on each set, including tare (shown when a tare is set). - Front net axle weight / Rear net axle weight — cargo weight on each set only.”

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

Two sets; whether limits/margins are shown alongside 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 a constraint, not an output.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "distribution", "per metre", "per meter", "along the length", "section"; layout blocks, export options, 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/

“Tare in kg - the weight of the container”

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

Gross weight per container in the Container Totals layout block; the axle page confirms gross values include tare.

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.

“Build a load plan layout with the loading instructions block, which gives step-by-step instructions by layers, by stacks or by a custom property — on a routed load that sequence is the reverse of the discharge order”

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

“showInstructions - Loading instructions mode (‘layers’, ‘stacks’, ‘by-prop’, or null)”

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

How it is done with general settings

1. Set Destination per item [cargo-properties page]. 2. Add the Loading Instructions block with mode "by custom property" [layouts page] and choose Destination as the property. 3. Each instruction group then corresponds to one stop.

• Follows from documented behaviour rather than stated outright
• Combination of general settings, shown by the vendor

No per-stop summary or unit view at each stop; the multi-drop guide says "Nothing recalculates it for you between stops".

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.

Manual edits are described without any rule validation. The interactive view flags OOG and extended trailers only; the data view warns about suspicious dimensions at input.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "violation", "warning", "validate", "check", "rule" with manual edit; modifying a load plan, interactive view, planner view, API move/insert endpoints.

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

Counts when: Documented void or empty-space output.

The automatic bottom spacer inserts dunnage under ULD builds; that is not a void report.

Where we looked

All 53 English /docs/ pages (sidebar incl. developer pages), the OpenAPI 3.0.3 schema v2.1.0 at https://api.cargo-planner.com/api/2/schema/ (all components), all 18 /guides/ pages, 16 /news/ posts, 5 /features/ pages, 6 /solutions/ pages, the four *-loading-software landing pages, calculators, integration, pricing; full-text grep of the downloaded text for: "void", "empty space", "gap", "dunnage", "airbag"; outputs, layouts, API.

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/

Container cost only; no per-item cost allocation documented.