Goodloading vs Cargo-Planner

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

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

“Enter the name, length, width, height, and the quantity of vehicles of a particular type that should be added to the project.”

https://www.goodloading.com/en/manual/adding-a-vehicle/adding-a-vehicle/

“part.length | number | Yes | Length of the loading space part. Must be greater than 0.”

https://www.goodloading.com/en/api/documentation/api-data-description/

Vehicle, sea container, air container and pallet spaces, from a preset list or typed dimensions (API type vehicle/sea/air x/air y/pallet). Rail wagons are only claimed on a Polish-language page (up to 99 load spaces per project, no rail-specific rules; manual check #1). Freemium restricts custom load dimensions; whether custom space dimensions are also PRO-only is not stated (a Q3 2024 note mentions editing space dimensions in freemium).

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.

“If you want to exclude wheel arches from the loading space, go to the Wheel arches tab. ... Complete the following data: – Distance from the door – Width of wheel arches – Height of wheel arches – Length of wheel arches”

https://www.goodloading.com/en/manual/adding-a-vehicle/wheel-arches/

“If you want to exclude the cooling unit from the loading space, go to the Cooling unit tab.”

https://www.goodloading.com/en/manual/adding-a-vehicle/cooling-unit/

UI only: not in the API field reference. Whether cargo may be stacked on top of the obstruction is not documented. Cooling unit on sea containers is PRO-only per FAQ; its lengthwise position is not a documented field.

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.

Only fixed kinds exist: one wheel-arch definition and one cooling unit per part. No free list of blocked regions.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: blocked area, obstacle, exclusion, zone, wheel arches, cooling unit, keep clear.

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.

“Enhanced functionality of weight and height limits.”

https://www.goodloading.com/en/blog/new-technologies/changes-in-goodloading-summary-of-q4-2024-updates/

The pallet 'maximum height' is part of the pallet space definition, not a separate cap on another space. A Q4 2024 release note mentions 'Enhanced functionality of weight and height limits' without describing any height-limit setting.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: height limit, maximum height, ceiling, clearance, load height.

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.

Variofloor is a full second deck (compartments row), not a step along the length. Nothing models a change of floor or ceiling height along the space.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: step deck, drop deck, low loader, gooseneck, split level, floor height, variofloor.

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.

“Fill in the name and then choose the type of container – single-sided or double-sided. ... Provide the length, width, base, height D and C”

https://www.goodloading.com/en/manual/adding-an-air-container/adding-an-air-container/

““air x” – a container with two slanted sides – “air y” – a container with one slanted side”

https://www.goodloading.com/en/api/documentation/loading-spaces/

part.base and part.heightD appear in the loading-spaces examples but not in the API field reference table.

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.

Air-container contours are crosswise only; no lengthwise height change is documented in the same unit.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: contour, slanted, cut, profile, length, step.

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.

““air y” – a container with one slanted side”

https://www.goodloading.com/en/api/documentation/loading-spaces/

The contour is described as 'slanted sides' defined by base width and height D (a chamfer), but no source says whether cargo is placed against the slope or stopped at a rectangular step.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: slanted, slope, angle, chamfer, cut.

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.

“Every loading space can be divided into a maximum of 2 parts. This is useful, for example, when loading a combination unit, such as vehicles or sea containers.”

https://www.goodloading.com/en/api/documentation/loading-spaces/

“You can add a vehicle with a second trailer as a set. ... Provide the length, width, and height of the trailer. Just like with the first vehicle, you can specify its capacity and loading direction.”

https://www.goodloading.com/en/manual/adding-a-vehicle/double-trailer/

At most 2 parts per space. Variofloor is UI-only and whether it can be partial-length is not documented.

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.

“Go to the Door size tab to add it to the container project. ... Complete data such as: – Door width – Door height”

https://www.goodloading.com/en/manual/adding-a-sea-container/door-size/

“In the first case, the added loads may be indicated as not fitting, precisely due to the limitations resulting from the size of the doors.”

https://www.goodloading.com/en/blog/goodloading-3-0-the-10-most-important-changes-in-the-latest-version-of-the-planner/

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

Sea containers only (single or set). PRO-only per FAQ. Not in the API.

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.

“While creating a vehicle, you can also specify its capacity and indicate the loading direction – from the right, from the back, from the left, from the top. This information allows the algorithm to consider the loading direction when planning the arrangement.”

https://www.goodloading.com/en/manual/adding-a-vehicle/adding-a-vehicle/

“The parameter applies to a specific defined part “part” of the loading space, so it can be set differently for each defined part.”

https://www.goodloading.com/en/api/documentation/loading-spaces/

Vehicles and sea containers; not offered for air containers in the UI. A Q3 2024 note says side-loaded vehicles are now filled from the cab. One access face per part.

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.

“If a rear-loading vehicle has been added in the current project, the load can be set to extend beyond the vehicle’s footprint. For this, check the option ‘Allow load to extend beyond space’.”

https://www.goodloading.com/en/manual/adding-loads-manually/rotate/

A per-load 'Allow load to extend beyond space' flag exists, only for rear-loading vehicles, but no maximum overhang is documented and it is not stated whether the planner places the overhang or the user drags it out. Fails for lack of a stated limit.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: overhang, extend beyond, protrude, open top, flat rack, flatbed.

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.

“The recommendation selects the smallest possible space for the transport order and, where there is a large number of cargo items, indicates how many spaces of a given type would have to be used”

https://www.goodloading.com/en/api/documentation/introduction/

“The algorithm distributed the cargo across 5 loading spaces: Solo truck 15 EP”

https://www.goodloading.com/en/api/documentation/api-recommendations/

Only through the recommendation function (UI 'Show recommendations', API /calculation/recommendation), which covers vehicles and sea containers only. In a normal calculation the user sets the number of spaces and the rest goes to notFittedLoads.

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

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

“The algorithm distributed the cargo across 3 loading spaces: Solo Truck 20 EP and 1 space: Bus 8 EP”

https://www.goodloading.com/en/api/documentation/api-recommendations/

“Enabling this feature allows the application to suggest alternative loaded spaces of the same type that can accommodate the given load.”

https://www.goodloading.com/en/manual/show-recommendations/

• Follows from documented behaviour rather than stated outright
• The vendor's own sources disagree on this point
• Only in some editions, plans, methods or equipment types

Recommendation only; vehicles and sea containers only.

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.

“quantity | integer | Yes | Number of loading spaces. Must be an integer greater than 0”

https://www.goodloading.com/en/api/documentation/api-data-description/

“notFittedLoads | array | Loads that did not fit into any loading space”

https://www.goodloading.com/en/api/documentation/api-data-description/

The quantity adds identical spaces to the project; the calculation stays within them and returns the remainder as not fitted. Whether the recommendation endpoint honours a quantity is not documented.

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.

“This option allows a load to be added to the first loading space with sufficient clearance.”

https://www.goodloading.com/en/manual/adding-loads-manually/adding-loads-manually/

'Add to first free' sends one load group to the first space with room, and without cross-space optimisation loads fill spaces in the order added; neither ranks equipment types. Hiding a saved space only removes it from recommendations.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: priority, preference, preferred vehicle, fill order, first free.

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 algorithm checks which loading space is the most cost-effective for carrying out the transport. The recommendation selects the smallest possible space for the transport order”

https://www.goodloading.com/en/api/documentation/introduction/

“Recommendations support only vehicles and sea containers.”

https://www.goodloading.com/en/manual/show-recommendations/

Vehicles and sea containers only; not air containers or pallets. Saved spaces hidden with the eye icon are excluded.

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.

“The algorithm checks which loading space is the most cost-effective for carrying out the transport.”

https://www.goodloading.com/en/api/documentation/introduction/

The recommendation is called 'most cost-effective' but no cost input exists; it selects the smallest space.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: cost, price, rate, cost-effective, cheapest.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: fill percentage, maximum fill, utilisation limit, percent.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: minimum fill, minimum load, minimum utilisation.

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.

No per-load restriction to equipment types. Pallet 'Loading to vehicle' ties a built pallet to one chosen space (fleet-item-to-unit).

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: allowed vehicle, only in, exclude, assign type, favourite.

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.

“Go to the Loading to vehicle tab if you want the pallet to be loaded onto a previously added loaded space. Select the option Select the space to be loaded. Choose the space you want to load it onto.”

https://www.goodloading.com/en/manual/palletization/loading-to-vehicle/

“You can select and drag specific loads with the left mouse button to move them to other loading spaces or change their order on the list.”

https://www.goodloading.com/en/manual/visualization/managing-added-loads-and-loaded-spaces/

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

UI only. Loads are added to the displayed space or dragged between spaces on the load list; built pallets get an explicit target-space input. The optimiser keeps loads in their space unless cross-space optimisation is on. No documented API field (keepGroupsInGivenSpaces appears only in example responses).

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: custom size, dimension range, box size, carton selection.

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.

“Then enter the dimensions – length, width, and height, and for barrels and pipes, also the diameter. Specify the quantity of such loads that you want to place in the loaded space. You can indicate the weight of individual loads or total weight of all added loads.”

https://www.goodloading.com/en/manual/adding-loads-manually/adding-loads-manually/

“weight | number | Yes | Weight of a single load. Must be greater than or equal to 0.”

https://www.goodloading.com/en/api/documentation/api-data-description/

Several load entries per request or project. . Freemium users can only use the default loads; custom dimensions need PRO. A 2019 blog post states the app 'can load „only" 10,000 loads' (the only stated scale limit found; re-check 30 Sep 2026).

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

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

“diameter | number | Yes | Diameter of the load. Must be greater than zero. Applies only to pipes and barrels.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“loadType | number | No | 0: cuboid load, 1: barrel, 2: pipe”

https://www.goodloading.com/en/api/documentation/api-data-description/

Barrels (upright) and pipes (lying). The API response returns a square bounding footprint for a barrel, but the item is entered and drawn as a cylinder.

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.

“In addition to standard cubic shapes, we can add pipes and barrels. The algorithm will arrange them in a so-called honeycomb, to optimally use the cargo space.”

https://www.goodloading.com/en/blog/goodloading-3-0-the-10-most-important-changes-in-the-latest-version-of-the-planner/

“Adding a third option for the formation of added pipes – the new feature means stacking pipes without stacking, meaning they won’t be stacked in a single line or honeycombed.”

https://www.goodloading.com/en/blog/new-technologies/changes-in-goodloading-summary-of-q2-2024-implementations/

Release-note blog posts only, which the row counts as claimed. The manual and API do not describe the formation options or how to select them.

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.

Only cuboids, barrels and pipes exist.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: interlock, nest, L-shape, shaped.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: cavity, inside, under, hollow, frame.

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

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

Load types are limited to cuboid, barrel and pipe.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: CAD, 3D model, mesh, irregular, custom shape.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: bulk, loose, liquid, volume only, amorphous.

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

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

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: compress, soft, squeeze, deform.

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.

Palletisation computes quantities from layers, but there are no packaging levels per item for the planner to choose between.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: pack, case, carton, inner, bundle, units per.

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.

“allowToRotate | boolean | No | Accepts true or false. Setting it to true lets the calculation swap width and length, i.e. rotate the load around its base. Applies to: cuboids and pipes. Default value: true.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“rotateFreely | boolean | No | ... Setting this value allows the load to be rotated in any direction. Applies only to cuboids. Default value: false.”

https://www.goodloading.com/en/api/documentation/api-data-description/

Per load. Upright is the default: with rotateFreely false a cuboid only turns on its base. Barrels are always upright.

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.

“You can change it to Allow any rotation or Do not allow any rotation.”

https://www.goodloading.com/en/manual/adding-loads-manually/rotate/

“Rotation lock Parameter settings: allowToRotate: false rotateFreely: false”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Per load: keeps the entered length/width orientation. Barrier mode never rotates loads and keeps the length along the vehicle.

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.

“rotateFreely | boolean | No | Accepts true or false. Setting this value allows the load to be rotated in any direction. Applies only to cuboids. Default value: false.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“You can change it to Allow any rotation or Do not allow any rotation.”

https://www.goodloading.com/en/manual/adding-loads-manually/rotate/

Cuboids only. 'Any direction' is not further defined; angled placement is excluded by the vendor (manual tilt only).

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.

Rotation is one of three settings: none, on base only, or any direction; there is no setting that allows only some tipped orientations.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: rotation, axis, lie, side, end, tilt.

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

Only three rotation modes (none / on base / any).

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: orientation, axis, allowed 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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: preferred orientation, prefer.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: orientation floor, bottom layer.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: stacking orientation, on side stack.

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

Counts when: Documentation of automatic non-orthogonal placement.

“The app allows loads to be stacked at an angle. This needs to be done manually as the app will not do it automatically.”

https://www.goodloading.com/en/manual/adding-loads-manually/arranging-loads-at-an-angle/

“Freemium users cannot, among other things: – add their own load dimensions, they use the defaults available in the planner – use the palletization option, rotate loads at different angles – add axle loads and several loading points in the vehicle – add advanced elements to containers (such as center of gravity, cooling unit, or door size)”

https://www.goodloading.com/en/faq/

Manual tilting about the X or Y axis in the 3D view is a workaround; it is PRO-only ('rotate loads at different angles').

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

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

“Barrels are always placed upright only and are not subject to any rotation.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

“Pipes cannot be stood upright; they can only be laid along the length or the width of the loading space.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

How it is done with general settings

1. For an upright cylinder, enter it as a barrel, loadType 1 (DD loadType field; ML 'Barrel': always upright). 2. For a lying cylinder, enter it as a pipe, loadType 2 (DD; ML 'Pipe': laid along the length or width).

• Combination of general settings, shown by the vendor

Fixed by type, as the definition note allows. A pipe can also be locked to its entered direction (allowToRotate false).

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.

“Load stacking. A value of false means the load is not stackable; a value of true means it is stackable.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“for a load, this must be set to true (the default value) for that load to be stackable, i.e. so that other loads can be placed on top of the load for which the parameter is set.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Per load. The API default is stackable; the manual has a 'Stack' checkbox to switch it on.

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.

Non-stackable only stops loads going on top of an item; nothing forces the item itself onto the floor. boxesBelowAllowed limits which items it may stand on, but an empty list means no restriction.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: floor only, must be on floor, bottom layer, do not stack on.

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.

“By adding another load to the project, we can indicate on which loads the newly added load can stand, unless there is a place on the floor without a loss of load meters.”

https://www.goodloading.com/en/blog/goodloading-3-0-the-10-most-important-changes-in-the-latest-version-of-the-planner/

“Selecting loads for stacking means that a given load can only stand on the loads specified in the table.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

• The vendor's own sources disagree on this point

The composable route (stacking false plus boxesBelowAllowed) does not reach this row: the 3.0 release note says the permitted-base list applies only 'unless there is a place on the floor without a loss of load meters', so the item may still go on the floor.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: top only, not on floor, stack only, boxesBelowAllowed.

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.

“Providing an integer greater than 0 means the load is stackable up to that limited number of tiers.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“The value given represents the total number of tiers permitted for the given load, including the bottom layer. By “a given load” we mean, for example, 4 tiers for a group of the same load.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Counts tiers including the bottom layer. The UI hint implies that setting a tier count may also stop other groups being placed on top.

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.

“By “a given load” we mean, for example, 4 tiers for a group of the same load. Tiers will not stack up to the specified number of different loads.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

The tier limit counts units of the same load only; no limit counts mixed stacks, and there is no unit-wide level cap.

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

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

A Q4 2024 release note mentions 'weight and height limits' without describing a per-item height limit.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: maximum height, stacking height, height limit.

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.

“maxWeightOnTop | number | No | Maximum weight that can be placed on top of the load.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“You can specify the maximum stacking weight, which allows placing other loads on the selected one, as long as their total weight does not exceed the value set by the user.”

https://www.goodloading.com/en/manual/adding-loads-manually/stack/

Per load; can be combined with the tier limit. 'Total weight' of loads placed on it suggests the whole column, but that is not stated.

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.

maxWeightOnTop is a plain weight.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: pressure, per area, kg/m2, contact surface weight.

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.

• Evidence is a label in a screenshot

The maxWeightOnTop examples ('Tier weight without setting the number of tiers') use three different loads and show only images of the result; no text says whether the limit is checked within a stack of one load.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: maxWeightOnTop same load, tier weight.

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

Counts when: A documented weight-ordering stacking rule.

“boxesBelowAllowed | array of numbers | No | Array of box IDs that may be placed beneath the load being added.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“Selecting loads for stacking means that a given load can only stand on the loads specified in the table.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

How it is done with general settings

1. Give each load entry an id (DD, id field). 2. For each load, set boxesBelowAllowed to the ids of all loads at least as heavy as it (DD boxesBelowAllowed; ML 'Selecting loads for stacking': a load 'can only stand on the loads specified').

• Combination of general settings, shown by the vendor

No built-in weight-ordering rule. The vendor's LCL blog post presents stacking rules as the way to avoid heavy-on-light. Heaviest-first placement order (loadingOrder weight) orders placement, not stacking.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: strength, fragility, index, crush.

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.

“boxesBelowAllowed | array of numbers | No | Array of box IDs that may be placed beneath the load being added.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“Selecting loads for stacking means that a given load can only stand on the loads specified in the table.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

A per-load whitelist of load IDs it may stand on. The 3.0 note says the load may still go on the floor if floor space is available without losing loading metres.

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.

“by default the degree of support is 100% – in which case only loads whose top load has the same support surface as the bottom load are stacked”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

• Follows from documented behaviour rather than stated outright

This is the default of the support-percentage mechanism, not a separate column or alignment rule.

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.

“pctSupport | number | No | Percentage of the load’s base area that is supported. Allows a load with a larger base area to be stacked on top of a load with a smaller base area.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“The degree of support is set for the upper load; with “pctSupport” : 30, the support/contact surface between the loads must be no less than 30% of our load”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

• The vendor's own sources disagree on this point

The allowed range is not given. A Q1 2024 note says a load up to 50% larger may be stacked on a smaller one, which may cap how low the value can go.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: bridge, height difference, uneven, several loads below.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: nest, nesting height, top shape.

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.

Palletisation builds a chosen number of complete layers and computes the quantity from them, but there is no rule that makes the planner load only complete stacks or layers of an ordered quantity.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: complete layers, full stacks, flat top.

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

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

“keepLoadsTogether | boolean | No | Setting this to true causes loads belonging to the same group to be placed together. Default value: false.”

https://www.goodloading.com/en/api/documentation/api-data-description/

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

API option per request; not described in the UI manual. No example.

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.

“”order” – every load must have its own order identifier”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

“barriers do not fully separate individual orders, i.e. a single column may contain different orders; however, loads do not mix in such a way that a load from order number 1, separated by order number 2, also ends up within order number 3.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

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

API only. Barrier mode never rotates loads. keepLoadsTogether ('same group') may also apply, but its group is undefined.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: same vehicle, do not split, keep group, order in one space.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: all or nothing, whole order, complete order.

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

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

“The barrier-setting feature lets you arrange loads by order and separate them with barriers.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

“barriers do not fully separate individual orders, i.e. a single column may contain different orders; however, loads do not mix in such a way that a load from order number 1, separated by order number 2, also ends up within order number 3.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Barriers of set thickness and height are inserted between full-width columns, not between orders, and the vendor states a column may contain different orders. So no group is guaranteed its own section. API only.

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.

“boxesBelowAllowed | array of numbers | No | Array of box IDs that may be placed beneath the load being added.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“Selecting loads for stacking means that a given load can only stand on the loads specified in the table.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

How it is done with general settings

1. Give each load entry an id (DD, id field). 2. For each load, set boxesBelowAllowed to the ids of the loads of the same group only (DD boxesBelowAllowed; ML 'Selecting loads for stacking').

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

Groups are encoded as lists of load IDs. The floor exception in the 3.0 release note does not affect this row.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: incompatible, separate vehicles, segregation, not together.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: distance, separation, apart, not above.

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.

Hazardous goods appear only in general blog content.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: dangerous goods, hazardous, ADR, IMDG, class.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: value, piece count, points, cap per vehicle.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: number of orders, distinct items, SKU limit.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: ratio, set, kit.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: multiple of, batch, lot size.

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.

“All loads that are outside the cargo space can be placed in the cargo space by clicking on the „Add loads to cargo space” option.”

https://www.goodloading.com/en/manual/visualization/managing-added-loads-and-loaded-spaces/

Loads can be moved by hand and loads outside the space added with 'Add loads to cargo space', and API projects can be edited in the web app and fetched again. No source says manual placements are kept while the planner completes the rest.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: lock, fix, keep position, complete, add loads to cargo space, initial arrangement.

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

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

Positions exist only in the API response, not as request fields.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: position input, coordinates, x y z request.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: front, rear, zone, region, place at.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: keep clear, exclude area, aisle, door area.

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.

Arrangement always starts at the cab (the barrier mode starts on the passenger side). loadingSide sets the access face (scored under equipment-access-side), and alongFloor is scored under floor-first. There is no separate fill-direction setting.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: fill direction, start from, loading side, pattern.

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.

“setting this parameter to true means that, during stacking, loads are first arranged along the floor and only then stacked; setting it to false (the default value) means they are stacked right away at the driver’s cab.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

“If you enable Arrange on the floor option, the algorithm will distribute the loads on the floor evenly before stacking them.”

https://www.goodloading.com/en/manual/adding-loads-manually/stack/

Default is stack first.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: forklift, reach, block depth, handling.

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

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

The UI 'load attracting' magnet only snaps manually moved loads together; there is no clearance setting.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: gap, clearance, spacing, distance between loads.

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.

Marketing mentions planning 'how best to secure loads', but no check is documented.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: shift, lateral support, secured, against wall.

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

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

“The default value, “allowOverweight”: “false”, means the total weight of the cargo cannot exceed the permissible load capacity.”

https://www.goodloading.com/en/api/documentation/loading-spaces/

“Activating this function ensures that loads the weight of which causes the cargo space to be overloaded are not loaded into it.”

https://www.goodloading.com/en/manual/algorithm-settings/include-space-capacity/

Payload per space part, required in the API; can be switched off (allowOverweight true / 'Include space capacity' off). Pallet spaces have a maximum capacity.

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.

“part.limit | number | Yes | Partial payload capacity of the loading space. Must be greater than 0”

https://www.goodloading.com/en/api/documentation/api-data-description/

“Provide the length, width, and height of the trailer. Just like with the first vehicle, you can specify its capacity and loading direction.”

https://www.goodloading.com/en/manual/adding-a-vehicle/double-trailer/

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

The payload rule is enforced by default (allowOverweight false).

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: section weight, floor load, per metre, zone weight.

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

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

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: kg per metre, linear load, weight per length.

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

“The Goodloading algorithm can control the load on a vehicle’s axles.”

https://www.goodloading.com/en/api/documentation/loading-spaces/

“It is also possible to partially indicate whether the obtained design does not exceed axle pressures if spacing and axle lifting capacity rules are described.”

https://www.goodloading.com/en/api/api-frequently-asked-questions/

• The vendor's own sources disagree on this point

Reported only. The axle model and colour-coded result are documented, and one API page says the algorithm 'can control' axle loads. But the API FAQ says it can only 'partially indicate' overloads, and the combination-unit example, run with default options (allowOverweight false), returns addedLoad 6666.67 on an axle with maxLoad 5300. Marketing claims 'loading in accordance with ... axle loads'. PRO-only.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: axle, maxLoad, overload, permissible axle, control, enforce.

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.

“When such an array is added, it must contain exactly two or three elements (the descriptions of the defined axles).”

https://www.goodloading.com/en/api/documentation/loading-spaces/

“We’ve added the option to input a third axle when adding vehicles in Goodloading.”

https://www.goodloading.com/en/blog/new-technologies/new-features-in-goodloading-company-project-sharing-and-more/

2 or 3 axle groups per part, so up to 6 on a two-part combination. Used for reporting only (see weight-axle-limits). PRO-only.

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

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

“part.axi.emptySpaceLoad | number | Yes | Axle load when the loading space is empty. The value must be a number greater than or equal to 0.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“Complete the following data for each axle: – Distance from the front of the semi-trailer – Axle load without weight – Max. permissible load”

https://www.goodloading.com/en/manual/adding-a-vehicle/axle-loads/

Tare load entered per axle. PRO-only.

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.

“We’re also working on another axle-related feature, which will be available soon. Users will be able to add a front axle under the driver’s cabin for curtain-sided trucks.”

https://www.goodloading.com/en/blog/new-technologies/new-features-in-goodloading-company-project-sharing-and-more/

Each part has its own axle array; an axle may sit under the cab (negative distance) for a rigid truck. No transfer of kingpin or drawbar load to a tractor is documented. May 2025: a front axle under the cab for curtain-siders was announced as coming soon.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: kingpin, fifth wheel, tractor, drawbar, coupling, front axle.

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.

A January 2025 blog post explains European axle limits in general; the planner takes limits only as typed per axle.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: legal limits, country, regulation, permit, bridge formula.

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.

“If the weight and distribution of the added loads cause the deviation of the centre of gravity to exceed the value indicated by the user, the application will inform the user about it.”

https://www.goodloading.com/en/manual/adding-a-sea-container/centre-of-gravity/

“By adding information about the center of gravity and its tolerances, the application will indicate if the center of gravity has been exceeded. It will be possible to automatically set the load so that the center of gravity is not exceeded.”

https://www.goodloading.com/en/blog/goodloading-3-0-the-10-most-important-changes-in-the-latest-version-of-the-planner/

• The vendor's own sources disagree on this point

Sea and air containers have length and width tolerances, but the documented effect is a warning. The July 2023 release note described automatic placement within the tolerance as future work ('It will be possible'), and no later source confirms it. PRO-only.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: centre of gravity, tolerance, balance, automatic, exceed.

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.

“If the weight and distribution of the added loads cause the deviation of the centre of gravity to exceed the value indicated by the user, the application will inform the user about it.”

https://www.goodloading.com/en/manual/adding-a-sea-container/centre-of-gravity/

Same as longitudinal: a width tolerance that triggers a warning, with no documented enforcement.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: centre of gravity, width tolerance, left right balance.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: centre of gravity height, vertical, Z.

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.

“In Goodloading, you can set the center of gravity of the container and the cargo, which allows the goods to be evenly distributed over the container space and ensures stability during transport.”

https://www.goodloading.com/en/blog/containers/lcl-container-how-to-optimally-use-cargo-space-in-general-cargo-transport/

“Determining the center of gravity – the algorithm continuously analyzes the weight of individual packages or pallets and calculates the pressure on the floor. This allows for a stable distribution of mass”

https://www.goodloading.com/en/blog/containers/iso-container-international-standard-in-transport/

• The vendor's own sources disagree on this point

Blog posts only. The manual documents a warning, and the 2023 release note announced automatic balancing as future work. It would centre the container's centre of gravity (not axles).

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.

“By default, the centre of gravity for a load is set in its centre. You can change its position, but only for cubic loads.”

https://www.goodloading.com/en/manual/adding-loads-manually/centre-of-gravity-of-load/

“Adjust the position of the centre of gravity along the X, Y, and Z axis.”

https://www.goodloading.com/en/manual/adding-loads-manually/centre-of-gravity-of-load/

Cuboids only. Used with the container centre-of-gravity check (sea containers). UI only, not in the API.

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.

“Enabling this function changes the arrangement according to the order in which loads are added to the selected cargo space. By moving loads on the list of added loads, their arrangement order on the visualization also changes.”

https://www.goodloading.com/en/manual/algorithm-settings/arrange-according-to-the-order-of-adding/

“each load must be assigned a “priority” – it takes numeric values 1..n, where 1 means the highest priority, in the options, set: "loadingOrder": "priority"”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Built-in sorts (heaviest first, largest volume first) also exist. The priority range differs between the field table (>= 0, default 0) and the guide (1..n).

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 | integer | No | Load priority. The value must be an integer greater than or equal to 0. Default value: 0.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“each load must be assigned a “priority” – it takes numeric values 1..n, where 1 means the highest priority”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

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

API only. Priority sets the order in which loads are placed, so higher-priority loads are placed first; notFittedLoads echoes the priority.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: optional, filler, fill items, if space.

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.

“For each load, specify its loading and unloading point by referencing the id and name of a stop defined in the loading space.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

“Automatic loading sequence planning for vehicles with multiple delivery or pickup points. The system ensures that goods intended for the first stop are loaded last (according to the LIFO principle)”

https://www.goodloading.com/en/api/integrations/

Needs at least 3 stops and one loading space. PRO-only ('several loading points'). No priorities within a stop are documented; the order can be changed by hand on the list.

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.

“The application will arrange the loads in such a way that goods from different locations are not mixed, making unloading easier.”

https://www.goodloading.com/en/

Sources say goods for different stops are 'not mixed' and first-stop goods are loaded last (LIFO), but none states as a hard rule that later-stop goods never sit in front of or on top of earlier-stop goods.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: LIFO, block, accessible, not mixed, unload without.

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

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

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: overlap, mixing distance, stop boundary.

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.

“origin | {id: number, name: string} | No | Pickup location of the load (multi stops)”

https://www.goodloading.com/en/api/documentation/api-data-description/

“destination | {id: number, name: string} | No | Applies to the multi-stop feature and indicates the unloading location.”

https://www.goodloading.com/en/api/documentation/api-data-description/

At least 3 stops, one loading space, PRO-only. The API example shows a load being picked up at an intermediate stop.

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

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

“Multistops, i.e. multiple loading and unloading locations, can only be added when you add a single loading space to the project. It is not possible to set points along the route for multiple semi-trailers or containers.”

https://www.goodloading.com/en/manual/multistops/

“Multistops apply to a single loading space only and must have at least 3 stops defined along the route.”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: whole stop, all or nothing, partial stop.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: date, due date, delivery date, ship date.

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.

“Fill in the name, length, width, and height of the pallet – which refers to the height of the empty pallet, as well as the maximum height – which indicates the maximum height the pallet base and the goods stacked on it can have.”

https://www.goodloading.com/en/manual/palletization/adding-pallets/

“part.baseHeight | number | No | Height of the pallet base”

https://www.goodloading.com/en/api/documentation/api-data-description/

Palletisation is PRO-only.

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.

“Click Create a layer. Check the layers proposed by the program and select one of them. Enter the number of layers. The application will automatically calculate the number of loads based on the selected number of layers.”

https://www.goodloading.com/en/manual/palletization/creating-layers/

“the system will analyze the allowed way of rotating the load and display a maximum of 3 arrangement options in the preview – along with information about the number of pieces in the layer.”

https://www.goodloading.com/en/blog/pallets/new-feature-in-goodloading-advanced-palletization/

Up to 3 alternative layer patterns. The user sets the layer count, or 'Fill the pallet' computes the maximum. UI only, PRO-only, added Sep 2026.

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.

“Check the layers proposed by the program and select one of them. Enter the number of layers.”

https://www.goodloading.com/en/manual/palletization/creating-layers/

“By clicking on „+” or „-” you can change the number of layers for a given group of loads.”

https://www.goodloading.com/en/manual/palletization/creating-layers/

No pattern styles (pinwheel, interlocked), saved patterns or alternating layers are documented.

The planner builds pallets that carry several different item types.

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

“If you want to distribute goods on pallets, add them as loaded spaces.”

https://www.goodloading.com/en/manual/palletization/adding-pallets/

“Arranging cargo inside a “pallet” space.”

https://www.goodloading.com/en/api/documentation/loading-spaces/

PRO-only. There are no pallet-specific mixing rules (for example level layers or columns).

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.

The 'extend beyond space' flag applies only to rear-loading vehicles.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: pallet overhang, extend beyond pallet.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: centre on pallet, underhang, inset.

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

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

“Complete the name, thickness and indicate how many layers to add a translator. You can check if you want the last interlayer to be placed on the last layer or the first Interlayer under the first layer.”

https://www.goodloading.com/en/manual/palletization/interlayers/

“If the load is arranged on several layers, you can specify the frequency of adding interlayers – for example, every few layers or only on the very top (on the last one).”

https://www.goodloading.com/en/blog/pallets/new-feature-in-goodloading-advanced-palletization/

Requires layers. Interlayers can be saved for reuse. PRO-only.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: separate pallets, customer, order, do not mix.

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.

“Go to the Loading to vehicle tab if you want the pallet to be loaded onto a previously added loaded space. ... The added pallet will be visible on the selected loaded space. If you add additional loads on it, they will automatically be displayed along with the pallet on the selected trailer or container.”

https://www.goodloading.com/en/manual/palletization/loading-to-vehicle/

“It is possible to arrange goods on pallets according to guidelines and then automatically plan their arrangement on the chosen means of transport.”

https://www.goodloading.com/en/palletizing/

Pallet spaces and vehicles live in one project, and a pallet is linked to its target vehicle. PRO-only.

Correction: Manual shows a linked per-pallet workflow; only marketing says it happens automatically in one calculation.

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.

“Go to the Loading to vehicle tab if you want the pallet to be loaded onto a previously added loaded space. ... The added pallet will be visible on the selected loaded space. If you add additional loads on it, they will automatically be displayed along with the pallet on the selected trailer or container.”

https://www.goodloading.com/en/manual/palletization/loading-to-vehicle/

“After palletizing, you can add a cargo space (a truck or a container) to the project and move the loaded pallet onto it. Its actual height will appear in the load’s description.”

https://www.goodloading.com/en/blog/goodloading-3-0-the-10-most-important-changes-in-the-latest-version-of-the-planner/

The built pallet is carried to the vehicle with its actual height. Carrying over its weight is not stated explicitly.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: carton, box into pallet, nested, three level.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: remainder, partial pallet, loose, palletise or not.

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.

No documented stacking or rotation settings for a built pallet once it is in the vehicle.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: pallet stacking in vehicle, pallet rotation, stack pallets.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: pallet height, vehicle height, top tier.

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

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

“If you enable the „optimal arrangement” function, the algorithm will search the load arrangement providing the greatest possible residual space, regardless of the order in which the loads were added.”

https://www.goodloading.com/en/manual/algorithm-settings/arrange-optimally/

“Enabling this feature will make the algorithm distribute all loads across all loading spaces in the project, regardless of their current position, to find the most optimal arrangement.”

https://www.goodloading.com/en/manual/algorithm-settings/optimization-for-all-loads-and-cargo-spaces/

Loads that do not fit are returned in notFittedLoads.

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.

'Arrange by weight' only orders placement heaviest first.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: maximise weight, weight utilisation, heaviest.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: balance, even distribution across vehicles, spread.

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.

“To fill the pallet with a load, go to the Loading tab, complete the data about the load and click the „Fill the pallet” button. The algorithm will calculate the maximum number of loads that the pallet can hold.”

https://www.goodloading.com/en/manual/palletization/filling-the-pallet/

Only when a pallet is the active loading space. PRO-only. The marketing claim to 'check how many goods a given loading space will fit' is not documented for vehicles.

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.

“If the application still does not perform satisfactorily, you can go to Algorithm settings and select Simple algorithm. Enabling it will make the application faster, but the loads may be arranged less optimally. Importantly, this feature does not allow you to take advantage of the new features present in this version of Goodloading.”

https://www.goodloading.com/en/manual/first-steps-in-the-application/application-speed/

“Its simple algorithm is based on the ability to quickly add cubic loads to a project without the need to use advanced stacking features.”

https://www.goodloading.com/en/manual/algorithm-settings/simple-algorithm/

No time limit or quality level. The API newAlgorithm flag may be the same switch, but that is not stated. Reproducibility is not stated.

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

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

“Enabling this feature allows the application to suggest alternative loaded spaces of the same type that can accommodate the given load.”

https://www.goodloading.com/en/manual/show-recommendations/

Recommendations 'suggest alternative loaded spaces', and palletisation offers up to 3 layer patterns, but neither is documented as returning several complete plans to compare.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: alternative, several solutions, compare, options.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: rule, condition, if weight, attribute.

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.

Load name and colour are display fields only.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: custom field, attribute, tag, label.

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.

boxesBelowAllowed is a per-load-ID whitelist (scored under stacking-item-pair); there is no class code shared across loads.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: class, category, stack code, matrix.

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

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

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: class, compatibility matrix, vehicle.

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

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

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: sum, cap, custom 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.

Loading side and payload are equipment properties set per part; algorithm options (order, optimisation, overweight) apply to the whole request.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: settings per vehicle, profile, per space.

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.

“Stacking can be limited to a certain number of layers or a maximum weight of the loads to be placed on top of each other.”

https://www.goodloading.com/en/faq/

“Tier weight with the number of tiers set”

https://www.goodloading.com/en/api/documentation/managing-loads-in-the-loading-space/

Tier limit, maxWeightOnTop, boxesBelowAllowed, pctSupport and alongFloor are separate per-load fields that can be set together; the API guide shows tiers and weight combined.

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.

'Arrange optimally' can be combined with load priority (API example 3), but that is one objective plus a placement order, not ordered or weighted objectives.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: objective, weighted, priority order, tolerance.

The user can add their own constraint or objective logic (script, plug-in or callback) that the planner evaluates.

Counts when: Documentation of a user-accessible extension mechanism for constraints or objectives.

The vendor offers custom integration development ('Custom Integration'), which is vendor work, not a user mechanism.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: script, plug-in, callback, custom rule.

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.

allowOverweight turns the payload limit on or off; it does not turn it into a preference.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: soft, preference, hard, allowOverweight.

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.

“Position of the load within the loading space, relative to the x, y and z axes. Looking from the front of the space, positions x: 0, y: 0, z: 0 correspond to the bottom right corner of the space.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“loadingSpace.part.load.placement.loadsPerAxis | json | Number of loads arranged along each axis”

https://www.goodloading.com/en/api/documentation/api-data-description/

Orientation is only implied by the placed dimensions (length and width swapped); for pipes, a zero length or width marks the direction. No orientation code, and manual tilts are not represented.

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.

“The file will include loading views, information about the loaded space, and a list of loads with the loading sequence.”

https://www.goodloading.com/en/manual/additional-features-in-the-top-panel/pdf/

“The person who receives the link will have access to the visualization along with the loading animation and the ability to download the project.”

https://www.goodloading.com/en/manual/additional-features-in-the-top-panel/share-a-link-to-the-project/

Sharing is PRO-only per FAQ.

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.

“Z: number of loaded cargo N: number of non-loaded cargo W: total weight loaded P: free space in m² O: available / used load volume in m³ occupied and free LDM vehicle axle load”

https://www.goodloading.com/en/manual/visualization/data-about-the-prepared-project/

“loadingSpace.part.stop.summary.percentVolumeUsd | number | Occupied volume – as a percentage”

https://www.goodloading.com/en/api/documentation/api-data-description/

Per space part: the loads placed in it, occupied/free LDM, area and volume, percentages, and total load weight. There is no weight-utilisation percentage; weight is given as a total next to capacity.

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

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

“loadingSpace.part.summary.occupiedLdm | number | Number of loading meters used”

https://www.goodloading.com/en/api/documentation/api-data-description/

“loadingSpace.part.summary.freeLdm | number | Number of free loading meters”

https://www.goodloading.com/en/api/documentation/api-data-description/

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

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

“notFittedLoads | array | Loads that did not fit into any loading space”

https://www.goodloading.com/en/api/documentation/api-data-description/

“If there is not enough room for all loads, some of them will remain outside the space.”

https://www.goodloading.com/en/manual/visualization/managing-added-loads-and-loaded-spaces/

API list with quantities; the UI shows the N (non-loaded) count and leaves the loads outside the space.

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

notFittedLoads carries no reason field.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: reason, why not loaded, error, not fitting.

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.

“Check Display centre of gravity if you want it to be visible in the visualization.”

https://www.goodloading.com/en/manual/adding-a-sea-container/centre-of-gravity/

“"COG": { "x": 100, "y": 100, "z": 66.66”

https://www.goodloading.com/en/api/documentation/updating-an-api-created-project-in-the-web-browser/

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

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

Containers (sea and air) in the UI; PRO-only.

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.

“loadingSpace.part.axi.addedLoad | number | Axle load exerted by the arranged loads.”

https://www.goodloading.com/en/api/documentation/api-data-description/

“In the visualization of the processing result, the color indicates how heavily the axle is loaded: blue – light load red – overload”

https://www.goodloading.com/en/api/documentation/loading-spaces/

The response repeats emptySpaceLoad and maxLoad per axle, so the margin can be derived; the UI colour-codes overloads. PRO-only in the web app.

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.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: weight distribution, along length, per section.

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 tare is entered for the COG check and axle tare per axle, but no gross weight including tare is documented as output.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: gross weight, VGM, tare, total weight including.

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.

“loadingSpace.part.stop.summary | json | Summary of the data for the given stop”

https://www.goodloading.com/en/api/documentation/api-data-description/

“After clicking on a specific point on the route, you can see a visualization of the loaded space corresponding to a given location.”

https://www.goodloading.com/en/manual/multistops/

Per-stop summaries (LDM, area, volume, weight) and loads, plus a view at each stop. Multistop needs one space and is PRO-only.

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.

“Remember that if you have not enabled the Stack option, you will not be able to place another load on top of it.”

https://www.goodloading.com/en/manual/visualization/working-with-visualization/

The editor blocks stacking on a load without the Stack option, and axle colours and the container COG warning reflect the current plan. There is no documented check of an edited plan against the item rules and no violations list.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: validation, warning, violation, check, manual editing.

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

Counts when: Documented void or empty-space output.

“Highlight free space – shows where the load can be placed with free space highlighting feature.”

https://www.goodloading.com/en/manual/additional-features-in-the-top-panel/load-settings/

The UI option 'Highlight free space' shows where a load could be placed; it is a display aid with no size threshold or output.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: void, free space, airbag, dunnage.

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

Counts when: Documented plan cost output.

A blog post on freight rates refers to LDM and weight figures only.

Where we looked

Searched all 69 English manual pages (wp-json/wp/v2/manual, read in full); API data description, Loading spaces, Managing loads (all worked examples), Recommendations, Introduction, Updating an API-created project, API FAQ; FAQ, home, road/maritime/air/palletizing/manufacturers/about/railway pages, and 98 English blog posts 2022-09 to 2026-09 (wp-json/wp/v2/posts) including all release notes. Terms: cost, price, freight rate.