SeaRates Load Calculator vs Cargo-Planner

SeaRates Load Calculator by SeaRates

SeaRates Load Calculator 26 of 149 documented · #9 of 9

Cargo-Planner 109 of 149 met · #1 of 9

What was read: Load Calculator API v2 (OpenAPI spec version 02.1.1, retrieved 2026-09-30).

About the evidence: Release notes before 2024 were not searched: the site could not be reached when the re-check was run. Pricing tiers require a sign-in and were not read.

Where Cargo-Planner goes further

83 requirements Cargo-Planner meets that SeaRates Load Calculator's public documentation does not show.

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.
The user can block any number of box-shaped regions, each at a freely chosen position and size, inside the loading space.
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.
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.
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.
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.
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.
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.
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.
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.
The user can cap how many units of each type are available, and the planner never uses more, leaving any remainder unloaded.
Given several candidate equipment types, the planner picks the smallest type that holds a load: the whole shipment, or the last, partly filled unit.

71 more

Each equipment type can be given a cost, and the planner chooses the combination of units with the lowest total cost.
The user can cap the fill of a unit at a set percentage of its volume or weight.
The user can assign a specific item (or group) to one particular unit of the plan.
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.
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).
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).
The user can allow any subset of an item's six orientations.
The user can require an item to stand on the floor of the space.
The user can require an item to be placed on top of other items, never on the floor.
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).
The planner never places an item on top of a lighter, different item.
The user can give items a numeric strength or fragility index, and the planner never places an item on one with a weaker index.
The user can state, for a specific pair of items, whether one may be stacked on the other.
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.
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.
The user can set how large a height difference between neighbouring supporting surfaces an item may bridge.
The planner can keep all units of the same item together in one block.
The user can assign items to groups (such as orders or customers), and the planner keeps each group's items together in the unit.
The user can require all items of a group to go in the same unit when the shipment needs several units.
When not everything fits, a group of items (for example one order or shipment) is loaded completely or not at all.
The user can have each group loaded in its own section of the unit, with no other group's items in it.
The user can forbid items of one group (order, stop, customer) from being stacked on items of another group.
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.
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.
The user can cap how many distinct items (or orders) a unit may contain.
The user can require items to be loaded in a fixed ratio in every unit (for example one table to four chairs).
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.
The user can confine an item to a defined region of the unit, such as the front, the rear, one side or a zone.
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).
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).
The user can make the planner cover the floor before stacking, for a whole plan or for specific items.
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.
The user can require clearance around items: a gap between all units, or extra space around a specific item.
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.
Each compartment, deck or part of a unit can have its own weight limit, which the planner respects.
The planner keeps the weight per unit of length below a set value everywhere along the unit.
The user can set a maximum load for each axle group, and the planner does not produce a plan that exceeds it.
The user can set a permitted range for the lengthwise position of the load's centre of gravity, and the planner keeps within it.
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.
When not everything fits, the user can decide by priority which items are loaded and which are left out.
The user can mark items as optional (fill items), so that they are loaded only into space left after all required items.
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.
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.
Stop-order rules still apply when the shipment spans several units.
When not everything fits, each stop's (or sequence's) items are loaded completely or not at all.
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.
The planner builds pallets that carry several different item types.
The user can prevent items of different groups (customers, orders, stops) from sharing a pallet.
The planner chains three or more packing levels (for example items into cartons, cartons onto pallets, pallets into trucks).
The planner sizes pallet height to the space available in the vehicle (for example shorter pallets for the top tier).
The planner maximises the cargo loaded into a given set of units, leaving any excess unloaded.
The planner can spread the load evenly over the units used, instead of filling each to the maximum in turn.
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.
The user can trade calculation time for plan quality (for example a time limit, search depth, quality level or fast mode).
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.
The user can define their own item attributes and use them in planning rules.
The user can define item classes and a matrix of which class may be stacked on which.
The user can define item classes and a matrix of which classes may share a unit.
The user can cap, per unit (or per group within a unit), the sum of any per-item numeric value they choose.
Rule settings can differ from one equipment unit to another within one plan.
Several stacking criteria (for example footprint, weight order and a class matrix) can be active at the same time in one plan.
The user can combine several objectives in a priority order or with weights (for example fewest units, then axle balance, within a tolerance).
For a given rule, the user can choose whether it is a hard limit or a preference the planner follows where it can.
The plan reports the floor length used or left free (loading metres).
The plan lists the items that could not be loaded, with quantities.
The plan states why each unplaced item was not loaded.
The plan reports the load's centre of gravity as a position (lengthwise and sideways).
The plan reports the load on each axle group and whether it is within its limit.
The plan reports gross weight including the equipment's tare (for example for a verified gross mass declaration).
The plan gives per-stop information: the contents for each stop and a view of the unit at each stop.
The plan reports the cost of the equipment used, and the cost allocated to each item.

By area

Area	SeaRates Load Calculator	Cargo-Planner
Equipment geometry	1 / 12	11 / 12
Fleet and equipment selection	4 / 11	9 / 11
Cargo items and shapes	2 / 9	4 / 9
Orientation	4 / 10	6 / 10
Stacking and load-bearing	4 / 17	13 / 17
Rules between items	1 / 13	11 / 13
Positioning	0 / 9	8 / 9
Weight, balance and axle loads (enforced)	1 / 14	6 / 14
Sequencing, priority and multi-drop	1 / 10	7 / 10
Pallet building, cartonisation and multi-stage loading	5 / 14	10 / 14
Objectives and search control	0 / 6	4 / 6
Expressiveness (user-built rules)	0 / 10	9 / 10
Plan output	3 / 14	11 / 14

Considering SeaRates Load Calculator? Test Cargo-Planner on the same load

Bring the load you would plan in SeaRates Load Calculator to a free trial, or book a demo and we will plan it with you.

Start a free trial Book a demo

Equipment geometry 1 of 12

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.

“length REQUIRED number ... width REQUIRED number ... height REQUIRED number ... maxWeight REQUIRED number”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Yes. You can customize container or truck dimensions by entering your own values in the corresponding fields during the calculation process.”
https://www.searates.com/help/tools/load-calculator/is-it-possible-to-change-truck-or-container-sizes-in-the-load-calculator

Each container/truck is one or more rectangular spaces (length, width, height, maxWeight, all required). Web tool adds preset container and truck types.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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

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

The containerSpace schema has only length, width, height and maxWeight; no field for a blocked region.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: obstruction, wheel arch, reefer unit, cooling unit, blocked, unusable, dead space, corner casting; container/containerSpace schema fields.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

No obstruction input of any kind is documented.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: blocked region, keep clear, obstruction, dummy item, forbidden zone.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

Only routes: edit the space height (workaround) or set per-item stacking.maxHeight (scored under stacking-max-height). No plan- or equipment-level ceiling clearance.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: ceiling clearance, height limit, loading height, gap below roof, usable height.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

Multi-section spaces exist (ULD 2-3 sections) but no offsets or spatial relation between sections are documented, so a step cannot be modelled.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: drop deck, step deck, gooseneck, split level, floor step, mega trailer.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

ULDs are described only as 2 or 3 rectangular sections with no stated spatial relation; the definition note says this does not pass.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: contour, ULD shape, cut-back, sloped, profile, curved roof.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

No contour input of any kind.

Where we looked

Not documented

Cargo-Planner: Documented

1 of 8 others document this.

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.

No contour input of any kind.

Where we looked

Not documented

Cargo-Planner: Documented

1 of 8 others document this.

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.

“spaces ... An array of container spaces. Standard containers have only 1 section, but ULD containers can contain 2 or 3 sections.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“length REQUIRED number ... width REQUIRED number ... height REQUIRED number ... maxWeight REQUIRED number”
https://docs.searates.com/reference/load-calculator/get-packing-result

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

Only in some editions, plans, methods or equipment types

Per container definition (fixed and auto). The docs name only ULDs as the use case; the response does not identify which section an item is in.

Documented, not counted

Cargo-Planner: Documented

4 of 8 others document this.

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.

Door width/height appear only as descriptive data for preset containers in the web tool; no engine effect is stated and the API has no door fields. Fails per definition note.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: door width, door height, door opening, aperture; API containerSpace fields.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

No loading-face setting. loadType (auto/wallLength/wallWidth/floor) is a fill pattern with no concept of a door; scored under positioning-fill-direction.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: loading face, door side, side loading, top loading, rear door, access.

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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.

Marketing mentions "trailer" and "oversized goods" but no open-equipment behaviour or envelope setting is documented.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: open top, flat rack, flatbed, overhang, over-height, over-width, out of gauge.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

Fleet and equipment selection 4 of 11

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.

“autoContainers REQUIRED array[object] The algorithm determines which type will be used for loading automatically.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Our team has added an Auto count checkbox to the tool for selecting one or more container types for automatic calculation of the number of containers.”
https://www.searates.com/blog/post/searates-updates-week-44-2025

API: autoContainers (required) are added as needed; result[].qty groups identical containers. Web: "Auto count" checkbox (Nov 2025). No documented upper limit on units added.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

“autoContainers REQUIRED array[object] The algorithm determines which type will be used for loading automatically.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Auto count checkbox to the tool for selecting one or more container types for automatic calculation of the number of containers.”
https://www.searates.com/blog/post/searates-updates-week-44-2025

Follows from documented behaviour rather than stated outright

The spec example offers 20st, 40st and 40hq together in autoContainers; result is a list of containers, each with qty.

Documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

Fixed containers carry a qty, but they are only filled before auto containers; autoContainers is a required field, and no source says what happens to cargo that does not fit when only fixed quantities are wanted.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: qty, available quantity, maximum containers, limit units, leftover, remainder not loaded.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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

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

“containers ... fixed quantity of containers that fill up earlier than auto containers”
https://docs.searates.com/reference/load-calculator/get-packing-result

“qty ... Quantity of containers. The option is not taken into account for autocontainers”
https://docs.searates.com/reference/load-calculator/get-packing-result

No ranking among several auto container types is documented.

Documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

Automatic type selection is documented, but the criterion ("optimal") is never defined, so selection of the smallest sufficient type is not shown.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: smallest, best fit, cheapest, recommended container, optimal container type, selection criterion.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

No cost input on containers in the API or web tool; freight rates live in separate SeaRates products.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: cost, price, rate, cheapest, freight cost per container.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

The only fill parameter is pallets.stacking.fill (minimum top-layer fill for stacking pallets), which is not a unit fill cap.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: maximum fill, fill percentage, utilisation cap, air circulation, volume limit.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

No minimum-fill input for containers or trucks.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: minimum fill, minimum utilisation, underfilled, min load.

Not documented

Cargo-Planner: Not documented

2 of 8 others document this.

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.

“groups Optional array List of groups allowed for loading into this container. The option is not taken into account for autocontainers.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“pallets Optional object Pallet settings for a group. If the field is undefined || null, then the pallets will not be used when loading”
https://docs.searates.com/reference/load-calculator/get-packing-result

Container restriction applies to fixed containers only; auto containers ignore it.

Documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

“groups Optional array List of groups allowed for loading into this container. The option is not taken into account for autocontainers.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“you can choose a container or truck for each of them separately with the ‘Load only specific groups’ option.”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

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

Only in some editions, plans, methods or equipment types

A fixed container entry with qty 1 is an individual unit; its groups list ties groups to it. Restriction is on the container side (an allow-list).

Documented, not counted

Cargo-Planner: Documented

4 of 8 others document this.

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.

Container dimensions are always inputs.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: determine container dimensions, carton sizing, custom box size range, min/max dimensions.

Not documented

Cargo-Planner: Vendor documents a limit

2 of 8 others document this.

Cargo items and shapes 2 of 9

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.

“type REQUIRED string Type of cargo Allowed values: box sacks bigbags”
https://docs.searates.com/reference/load-calculator/get-packing-result

“qty REQUIRED integer Quantity of boxes >= 1 <= 1000000”
https://docs.searates.com/reference/load-calculator/get-packing-result

Per item line: length, width, height, weight per unit, qty 1 to 1,000,000. No documented cap on the number of item lines. Sacks and bigbags share the box schema.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

“type REQUIRED string Type of cargo Allowed values: roll barrels pipes”
https://docs.searates.com/reference/load-calculator/get-packing-result

“size REQUIRED object One roll size. ... radius REQUIRED number ... height REQUIRED number”
https://docs.searates.com/reference/load-calculator/get-packing-result

API takes radius (equivalent to diameter); web tool asks for diameter.

Documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“Hexagonal positioning of round objects Load your pipes and barrels for secure and profitable shipping. Save much space on hexagonal placement”
https://www.searates.com/integrations/load-calculator/

Marketing feature page only; no parameter or documentation of the arrangement.

Marketing claim only

Cargo-Planner: Not documented

1 of 8 others document this.

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 box and cylinder schemas exist.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: L-shape, irregular shape, interlock, nest, tapered, shaped items.

Not documented

Cargo-Planner: Documented, not counted

2 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: cavity, inside item, under overhang, frame, free space in item.

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

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.

The blog names irregular shapes as a challenge, but no arbitrary-shape input exists.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: CAD, mesh, 3D model, irregular shape, custom shape, STL.

Not documented

Cargo-Planner: Not documented

No other product documents this.

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.

“cargo type — box, big bags, sacks, barrels, rolls, pipes, or bulk”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

“Specialized stuffing for pipes, barrels and bulk commodities”
https://www.searates.com/integrations/api-load-calculator/

Web tool lists bulk as a cargo type; the API enums do not include it. No description of how bulk occupies space.

Marketing claim only

Cargo-Planner: Not documented

No other product documents this.

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.

“Compressing/squeezing for soft cargoes In the cubic weight calculator for shipping, simply select default measurement and weight units. Enhanced loading estimation by adding the needed margin to your loads if it allows flexible processing.”
https://www.searates.com/integrations/load-calculator/

“Compression & allowance feature”
https://www.searates.com/integrations/api-load-calculator/

No field in the API schema; no percentage or limit documented.

Marketing claim only

Cargo-Planner: Not documented

1 of 8 others document this.

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

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

Each item line is a single package type with a quantity.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: pack level, inner, case, each, bundle, packaging configuration, units per carton.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

Orientation 4 of 10

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.

“tiltX Optional boolean Allow tilting the box along the width Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

“tiltY Optional boolean Allow tilting the box along the length Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

Per item line: set tiltX and tiltY to false and the height axis stays vertical.

Documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

No setting for rotation about the vertical axis; the tilt flags only govern tipping.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: rotate, rotation, turn, lengthwise, widthwise, forklift direction, fixed orientation.

Not documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

“tiltX Optional boolean Allow tilting the box along the width Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

“tiltY Optional boolean Allow tilting the box along the length Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

Follows from documented behaviour rather than stated outright

Both tilt flags default to true, so tipping along width and length is allowed by default.

Documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

“tiltX Optional boolean Allow tilting the box along the width Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

“tiltY Optional boolean Allow tilting the box along the length Default: true”
https://docs.searates.com/reference/load-calculator/get-packing-result

Follows from documented behaviour rather than stated outright

Per item line: enabling one tilt flag and not the other allows only one of the two tipped attitudes.

Documented

Cargo-Planner: Documented

5 of 8 others document this.

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

Two tilt toggles plus no control of rotation about the vertical axis cannot express every subset of the six orientations.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: six orientations, orientation mask, allowed orientations, rotation.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: preferred orientation, prefer, default orientation.

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: floor only orientation, bottom layer, tipped above floor.

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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.

Stacking fields (layers, topWeight, maxHeight) are per item, not per orientation.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: stack on side, per orientation, layers by orientation.

Not documented

Cargo-Planner: Not documented

4 of 8 others document this.

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.

Where we looked

Not documented

Cargo-Planner: Not documented

No other product documents this.

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

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

“arrange Optional string Allowed values: vertical horizontal Default: vertical”
https://docs.searates.com/reference/load-calculator/get-packing-result

“In the case of the transportation of goods in rolls, you will be offered two options for loading them”
https://www.searates.com/blog/post/load-calculator-tool-for-optimizing-cargo-space

Per roll/barrel/pipe item (stacking.arrange). A separate roll tilt flag exists whose description is copied from the box schema.

Documented

Cargo-Planner: Documented

4 of 8 others document this.

Stacking and load-bearing 4 of 17

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.

“adding the "Disable stacking" checkbox on the "Stuffing settings" section for all cargo types (boxes, big bags, sacks, barrels, rolls, etc.). This way you can adjust online stuffing by mentioning the requirement to place cargo in only one layer if nothing can be placed on top.”
https://www.searates.com/blog/post/searates-updates-week-36-2024

“topWeight Optional number Allowed weight on top”
https://docs.searates.com/reference/load-calculator/get-packing-result

Web: "Disable stacking" checkbox per cargo line (Sep 2024). API: topWeight per item (0 would pass per definition note, though a zero value is not shown in the docs).

Documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

"Disable stacking" places cargo "in only one layer", framed as nothing on top of it; it is not stated to force the item onto the floor.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: floor only, bottom, must be on floor, ground layer.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: not on floor, top only, must be stacked, upper layer.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

“layers Optional integer Allowable quantity of boxes in a vertical stack”
https://docs.searates.com/reference/load-calculator/get-packing-result

“stuffing settings — layers count, mass, and height”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

Per item line (box and roll).

Documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

layers is per item line; whether it counts other items in the same stack is not stated. No container-wide tier cap.

Where we looked

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“maxHeight Optional number Maximum stacking height with boxes”
https://docs.searates.com/reference/load-calculator/get-packing-result

“You can also change the number of allowed layers or set a weight or height limit, entering the appropriate values in the “Mass” or “Height” fields.”
https://www.searates.com/blog/post/searates-updates-week-36-2024

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

Per item line, in length units. The request example uses an undocumented key "height" instead of maxHeight.

Documented

Cargo-Planner: Documented

2 of 8 others document this.

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.

“topWeight Optional number Allowed weight on top”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Next, specify the parameters of the allowable load that can be placed on top.”
https://www.searates.com/blog/post/discover-load-calculator-capabilities-for-your-logistics

Per item line, in weight units. Whether it counts the whole column above or only the item directly on top is not stated; no scale limit documented.

Documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

topWeight is a plain weight; no area-based evaluation is documented.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: pressure, per area, kg/m2, contact area, bearing strength.

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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.

The docs do not say whether topWeight is checked within stacks of identical units.

Where we looked

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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

Counts when: A documented weight-ordering stacking rule.

The 2023 blog lists industry rules (quoted) as general advice, not as a product behaviour; no weight-ordering rule is documented for the planner.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: heavy at bottom, heavier below, weight order, light on top.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: strength, fragility index, crush, stack index, class.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: stack on, stackable with, matrix, compatibility, allowed below.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: footprint, same size, column, aligned, larger on top.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: support, overhang, supported area, percentage support, stability.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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.

pallets.stacking.fill gates stacking a pallet on another by top-layer fill; it does not restrict loading to complete stacks or layers or route remainders (scored under pallet-rules-in-vehicle).

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: complete layers, full stacks, flat top, full layers only, remainder.

Not documented

Cargo-Planner: Documented, not counted

3 of 8 others document this.

Rules between items 1 of 13

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

“Explore safe cargo loading calculator for efficient unloading and grouping of the same items”
https://www.searates.com/integrations/api-load-calculator/

“"options": { "lengthUnits": "mm", "weightUnits": "kg", "lengthAccuracy": 5, "remainsNear": true }”
https://docs.searates.com/reference/load-calculator/get-packing-result

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

API marketing claims grouping of the same items; options.remainsNear appears only in the request example, undescribed. Block output (complex counts per axis) shows identical units placed as blocks but is not a user setting.

Marketing claim only

Cargo-Planner: Documented

8 of 8 others document this.

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.

“Groups are an array of JSON objects arranged in a strict order, which is taken into account when stuffing containers. The closer to the beginning of the array the group, the earlier it will be stuffed.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“And your goods can be loaded in groups. This is necessary to ensure that the unloading of goods is predictable and does not cause any delays or difficulties.”
https://www.searates.com/blog/post/load-calculator-tool-for-optimizing-cargo-space

Groups are documented (uid, order, pallet settings), but no source states a keep-together rule; group contiguity is implied only by sequential stuffing and a marketing blog.

Marketing claim only

Cargo-Planner: Documented

8 of 8 others document this.

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.

containers[].groups restricts where a group may go but does not forbid splitting a group across units.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: do not split group, one container per group, keep order in one unit.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: all or nothing, whole order, complete group, leave out group.

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

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

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: section, wall, barrier, separator, divider, zone per group.

Not documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: stack across groups, group stacking, not on top of other order.

Not documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

“groups Optional array List of groups allowed for loading into this container. The option is not taken into account for autocontainers.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“containers ... fixed quantity of containers that fill up earlier than auto containers”
https://docs.searates.com/reference/load-calculator/get-packing-result

How it is done with general settings

1. Put each set of goods that must be kept apart in its own group (groups[]; https://docs.searates.com/reference/load-calculator/get-packing-result). 2. Define fixed containers (containers[], "fixed quantity of containers that fill up earlier than auto containers"; https://docs.searates.com/reference/load-calculator/get-packing-result). 3. On each fixed container list only the group uid(s) allowed in it (containers[].groups, "List of groups allowed for loading into this container"; https://docs.searates.com/reference/load-calculator/get-packing-result).

Combination of general settings, shown by the vendor
Only in some editions, plans, methods or equipment types

Whole-container separation only, and only for fixed containers; auto containers ignore the groups option, so overflow into auto containers could mix groups.

Documented

Cargo-Planner: Documented

4 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: separation distance, keep apart, not above, segregation within container.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

Dangerous goods appear only as general advice in a blog; no hazard-class attribute exists.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: dangerous goods, hazardous, IMO class, IMDG, hazmat, segregation.

Not documented

Cargo-Planner: Vendor documents a limit

No other product documents this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: value cap, declared value, piece count limit, Q-value.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

Restricting a fixed container to one group via containers[].groups limits which groups, not how many distinct items.

Where we looked

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“loadType Optional string Allowed values: auto wallLength wallWidth floor Default: auto”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Customized loading is also available, so you can choose how each cargo group should be loaded in the queue.”
https://www.searates.com/blog/post/load-calculator-tool-for-optimizing-cargo-space

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

Four named fill patterns per container; none is described.

Documented, not counted

Cargo-Planner: Documented

6 of 8 others document this.

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.

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

The loadType value "floor" may be a floor-first strategy, but it is undescribed.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: floor first, spread, cover floor, single layer strategy.

Not documented

Cargo-Planner: Documented

7 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: forklift, reach, block depth, turning, handling equipment.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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 web tool's "Spacing settings" section holds tilt checkboxes, not gaps. The marketing "margin" wording is scored under cargo-compressible.

Where we looked

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

An API page calls it a "cargo lashing calculator" as SEO wording; no shift or support check is documented.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: shift, secure, backed, lateral support, load securing, lashing.

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

Weight, balance and axle loads (enforced) 1 of 14

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.

“maxWeight REQUIRED number Example: 26460”
https://docs.searates.com/reference/load-calculator/get-packing-result

“maxWeight REQUIRED number Maximum permissible pallet load”
https://docs.searates.com/reference/load-calculator/get-packing-result

Per container space (required) and per pallet. No documented switch-off or scale limit.

Documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

“spaces ... An array of container spaces. Standard containers have only 1 section, but ULD containers can contain 2 or 3 sections.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“maxWeight REQUIRED number”
https://docs.searates.com/reference/load-calculator/get-packing-result

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

Only in some editions, plans, methods or equipment types

Each section of a multi-section (ULD) container has its own maxWeight.

Documented, not counted

Cargo-Planner: Documented

2 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: floor section, front/middle/rear weight, segment limit.

Not documented

Cargo-Planner: Not documented

2 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: weight per metre, linear load, kg/m, concentrated load.

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

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

“For trucks, you can customize the axle load: “The location of the truck wheels relative to the container and the weight allowed for each axle. F - Front max weight (kg), F - Front offset (cm), R - Rear max weight (kg), R - Rear offset (cm).””
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

“If you need to plan loading properly for the road transport and intermodal delivery, either this is container or truck, distribute the loading settings with help of built-in axle weight calculator to get the perfect result in means of safety on road and penalty avoidance.”
https://www.searates.com/integrations/load-calculator/

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

Only in some editions, plans, methods or equipment types

Web tool, trucks only, exactly two axles (front and rear: max weight in kg and offset in cm). Not in the API schema. No source states that the planner keeps axle loads within the limits while building the plan.

Marketing claim only

Cargo-Planner: Documented

2 of 8 others document this.

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

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

The only documented axle input has exactly two positions.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: axle groups, three axles, tandem, tridem, add axle.

Not documented

Cargo-Planner: Not documented

4 of 8 others document this.

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.

Axle input covers max weight and offset only; truck presets list no tare.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: tare per axle, empty axle load, vehicle weight distribution.

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: kingpin, fifth wheel, tractor, semi-trailer, drawbar.

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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.

“Different regions have their own load limits and transport safety rules. The tool contains these regulations in the planning process, helping you to avoid penalties and legal issues.”
https://www.searates.com/blog/post/how-to-optimize-your-shipping-goods-stuffing

No region or jurisdiction setting, rule list or parameter is documented.

Marketing claim only

Cargo-Planner: Not documented

No other product documents this.

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.

Central-axis distribution and a "center of gravity calculator" are claimed, but no user-set CoG range is documented (see weight-balance-soft).

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: centre of gravity range, CoG limit, longitudinal balance, tolerance.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

No lateral range or left/right difference input.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: left/right balance, lateral, side-to-side, transverse CoG.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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

Not documented

Cargo-Planner: Not documented

No other product documents this.

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.

“We've upgraded load distribution along the central axis of the container to the web tool for more precise stuffing calculations.”
https://www.searates.com/blog/post/searates-updates-week-25-2026

“Make it easy to handle bulk cargo via our center of gravity calculator for trucks and containers.”
https://www.searates.com/integrations/load-calculator/

Only in some editions, plans, methods or equipment types

Web tool only; no parameters; not in the API schema.

Marketing claim only

Cargo-Planner: Not documented

3 of 8 others document this.

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

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

Where we looked

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

Sequencing, priority and multi-drop 1 of 10

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.

“Groups are an array of JSON objects arranged in a strict order, which is taken into account when stuffing containers. The closer to the beginning of the array the group, the earlier it will be stuffed.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“The sequence in which you enter product groups is the queue for loading them.”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

Group-level only (no per-item sequence number). Direction: earlier groups are stuffed earlier; the docs do not state explicitly that "earlier" means further from the door.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

Group order sets stuffing order, but no source says which cargo is left out when not everything fits (auto containers are always added, and no unplaced list is documented).

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: priority, must load, drop items, what fits first, optional.

Not documented

Cargo-Planner: Documented

7 of 8 others document this.

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

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“Groups are an array of JSON objects arranged in a strict order, which is taken into account when stuffing containers. The closer to the beginning of the array the group, the earlier it will be stuffed.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“The container load calculator evaluates the maximum load for your cargo, taking the following factors into account: Item dimensions and weight Center of gravity Fragile items Delivery sequence.”
https://www.searates.com/blog/post/how-to-optimize-your-shipping-goods-stuffing

How it is done with general settings

1. Create one group per delivery stop (groups[]; https://docs.searates.com/reference/load-calculator/get-packing-result). 2. Order the groups with the last stop first, because "the closer to the beginning of the array the group, the earlier it will be stuffed" (https://docs.searates.com/reference/load-calculator/get-packing-result). Step 2 is not documented as mapping to position along the unit.

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

Combination of general settings, shown by the vendor

No stop attribute. Marketing names "Delivery sequence"; the documented route (group order) does not say the order maps to position along the unit, which the definition note requires for a documented pass.

Marketing claim only

Cargo-Planner: Documented

8 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: no blocking, accessible, unload without moving, LIFO.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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

Not documented

Cargo-Planner: Not documented

2 of 8 others document this.

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.

Where we looked

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: multi-drop across containers, stops in several trucks.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

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

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

Pallet building, cartonisation and multi-stage loading 5 of 14

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.

“size REQUIRED object Area (volume) of the pallet allowed for loading”
https://docs.searates.com/reference/load-calculator/get-packing-result

“depth REQUIRED number Pallet thickness. Length and width are taken from the size field”
https://docs.searates.com/reference/load-calculator/get-packing-result

Per group: deck thickness (depth) plus loadable height (size.height); the response example shows a built pallet of 2100 = 2000 load + 100 deck. Web presets: Euro, Euro 1/2, Euro plastic, US, custom.

Documented

Cargo-Planner: Documented

7 of 8 others document this.

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.

“pallets Optional object Pallet settings for a group. If the field is undefined || null, then the pallets will not be used when loading”
https://docs.searates.com/reference/load-calculator/get-packing-result

“For convenience and efficiency, Load Calculator contains the ability to palletize when planning a load.”
https://www.searates.com/blog/post/pallets-usage-for-loading-containers-and-trucks-in-the-load-calculator

The response example shows 32 identical boxes built onto each pallet as a 2 x 4 x 4 block. One pattern per run; no alternative patterns offered.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

Only the item tilt flags and the pallet size affect the pattern.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: pattern, pinwheel, interlock, cases per pallet, layer rotation.

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

The planner builds pallets that carry several different item types.

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

“Also, it is time to use the palletization option if you plan to freight different types of cargo at the same time.”
https://www.searates.com/blog/post/load-calculator-tool-for-optimizing-cargo-space

“items REQUIRED array (anyOf) List of metadata objects to stuff”
https://docs.searates.com/reference/load-calculator/get-packing-result

Follows from documented behaviour rather than stated outright

A group may hold several item lines and one pallet setting, and pallet results carry a per-uid item count, which allows mixed pallets, but no source shows one.

Marketing claim only

Cargo-Planner: Documented

7 of 8 others document this.

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.

Web tool warns when cargo exceeds maximum pallet dimensions (week 9, 2024), which implies no overhang.

Where we looked

Not documented

Cargo-Planner: Vendor documents a limit

5 of 8 others document this.

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

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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

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

Where we looked

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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.

Follows from documented behaviour rather than stated outright

Pallet settings are defined per group, which suggests pallets are built per group, but no source says groups never share a pallet.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: separate pallets per order, no mixing groups on pallet.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“pallets Optional object Pallet settings for a group. If the field is undefined || null, then the pallets will not be used when loading”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Knowing the size and type of packaging of your product, you specify them at the first stage in the program. Then select the pallet loading option.”
https://www.searates.com/blog/post/pallets-usage-for-loading-containers-and-trucks-in-the-load-calculator

One request palletises groups and loads the pallets into containers/trucks; pallets appear in the result with their children.

Documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

Web import/export of "Packages and Pallets" (July 2026) is not described; it may concern item and pallet-type definitions rather than built pallets.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: save pallet, pallet as item, reuse result, export pallet.

Not documented

Cargo-Planner: Not documented

5 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: cartons, cartonisation, three levels, box into box.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“pallets Optional object Pallet settings for a group. If the field is undefined || null, then the pallets will not be used when loading”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Then select or deselect cargo palletising and click on "Next".”
https://www.searates.com/help/tools/load-calculator/how-to-use-load-calculator

Per group only; an item line placed in its own group gets its own choice.

Documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

“layers Optional integer Quantity of pallets stacked on top of each other”
https://docs.searates.com/reference/load-calculator/get-packing-result

“fill Optional number The minimum stuffing level of the top layer of cargo on a pallet for placing the pallet on top. Indicated in fractions of one, i.e. 80% is 0.8, 90% is 0.9, etc. >= 0 <= 1”
https://docs.searates.com/reference/load-calculator/get-packing-result

Per group pallet: pallet stack count and minimum top-layer fill. No orientation rule for built pallets. Example also has an undocumented pallet stacking.maxHeight.

Documented

Cargo-Planner: Documented

5 of 8 others document this.

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

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

The user-set maximum pallet load height decides whether tiers are possible; pallet height is not adapted by the planner.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: pallet height to container, top tier shorter, dynamic pallet height.

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

Objectives and search control 0 of 6

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.

“Load Calculator is an application intended to compute and to place some goods into container and make their position to place some goods into a transport unit and make their position optimal.”
https://docs.searates.com/reference/load-calculator/get-packing-result

“Save space The cargo lashing calculator allows you to fully optimize container space, saving your costs on every shipment”
https://www.searates.com/integrations/api-load-calculator/

"Optimal" is undefined; no documented objective, and no source says excess cargo is left unloaded in fixed units (auto containers absorb it).

Marketing claim only

Cargo-Planner: Documented

7 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: maximise weight, weight utilisation, objective, strategy.

Not documented

Cargo-Planner: Not documented

2 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: balance containers, even distribution across units, spread load.

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

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.

“our team has developed a revolutionary technology to easily calculate how many items with particular dimensions you can fit in a container.”
https://www.searates.com/blog/post/discover-load-calculator-capabilities-for-your-logistics

“Demonstrate how to calculate how many items fit in each container/truck, compare results, and choose the most efficient option.”
https://www.searates.com/blog/post/discover-load-calculator-capabilities-for-your-logistics

qty is a required input (1 to 1,000,000); no cube-out mode is documented in the API.

Marketing claim only

Cargo-Planner: Documented

5 of 8 others document this.

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.

lengthAccuracy rounds dimensions; it is not documented as a time/quality trade-off.

Where we looked

Not documented

Cargo-Planner: Documented

7 of 8 others document this.

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

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

One result per request; the blog's "compare results" refers to running separate calculations.

“loadType Optional string Allowed values: auto wallLength wallWidth floor Default: auto”
https://docs.searates.com/reference/load-calculator/get-packing-result

“groups Optional array List of groups allowed for loading into this container. The option is not taken into account for autocontainers.”
https://docs.searates.com/reference/load-calculator/get-packing-result

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

Each container entry, fixed or auto, carries its own loadType; group restriction applies to fixed containers only.

Documented, not counted

Cargo-Planner: Documented

3 of 8 others document this.

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.

“Adjust stacking levels for selected cargo by mass, height, and layer count.”
https://www.searates.com/integrations/load-calculator/

“stuffing settings — layers count, mass, and height”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

No footprint, weight-order or class criteria exist, so the combinable set is limited to these three per-item limits.

Correction: Fields in one schema object are not documentation that they apply together; the release note says 'or'.

Marketing claim only

Cargo-Planner: Documented

5 of 8 others document this.

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.

Where we looked

Not documented

Cargo-Planner: Documented

1 of 8 others document this.

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.

Customised versions are offered on request ("get a customized solution"), which is a vendor service, not a user mechanism.

Where we looked

Not documented

Cargo-Planner: Documented, not counted

No other product documents this.

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.

Where we looked

Not documented

Cargo-Planner: Documented

4 of 8 others document this.

Plan output 3 of 14

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.

“spaces array Information about the place of each of the items ... Pallet or Cargo item”
https://docs.searates.com/spec/load-calculator-v2-openapi.json

“complex object Number of adjoining units, by axes. For a single object, this indicator may not be available.”
https://docs.searates.com/spec/load-calculator-v2-openapi.json

Per unit or block: location {x,y,z}, placed size {x,y,z} (orientation implied by placed dimensions, no code) and complex counts per axis; pallets carry children. Manual check #2 confirms the complex-objects page: a block of identical units is one object with counts per axis. Origin and axis directions are not documented.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

“Download a step-by-step stuffing plan and export results to PDF.”
https://www.searates.com/blog/post/how-to-use-the-load-calculator-smart-stuffing-of-containers-trucks

“We have implemented loading animation. You can adjust loading steps visualizing by the ‘Play’ and ‘Pause’ buttons.”
https://www.searates.com/blog/post/searates-updates-week-35-2024

Web tool only; the API returns one image per container.

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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.

“general object General statistics on the placed cargo ... itemQty ... cargoVolume ... cargoWeight ... volumeRatio ... weightRatio ... items Quantities each of items”
https://docs.searates.com/spec/load-calculator-v2-openapi.json

“Review the results of calculation with details of the capacity and volume utilization, as well as the number of required transport units.”
https://www.searates.com/blog/post/pallets-usage-for-loading-containers-and-trucks-in-the-load-calculator

Per container: item counts per uid, volume, weight, volume and weight ratios. Per pallet: itemQty, volume, weight, counts per uid (ratios shown only in the example, not the pallet schema).

Documented

Cargo-Planner: Documented

8 of 8 others document this.

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

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

Where we looked

Not documented

Cargo-Planner: Documented

6 of 8 others document this.

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

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

The response schema (result, cargoAttributes, images, version) has no not-loaded list. An undocumented request key errorProducts appears only in the example. The Errors page concerns input settings (manual check #2).

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: not loaded, unplaced, leftover, remaining, errorProducts.

Not documented

Cargo-Planner: Documented

8 of 8 others document this.

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

Errors are typed warning/ignore/break and concern input settings, not reasons per unplaced item (manual check #2). Week 12 2024 added an "Allowed image size exceeded" error.

Where we looked

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

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.

“Make it easy to handle bulk cargo via our center of gravity calculator for trucks and containers.”
https://www.searates.com/integrations/load-calculator/

No CoG field in the API response; no description of a CoG figure in the web tool.

Marketing claim only

Cargo-Planner: Documented

3 of 8 others document this.

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.

“Save the calculation results to PDF and apply this comprehensive step-by-step loading plan from the axle weight calculator to streamline your warehouse operations”
https://www.searates.com/integrations/load-calculator/

“distribute the loading settings with help of built-in axle weight calculator”
https://www.searates.com/integrations/load-calculator/

No axle fields in the API response; the web axle input (two axles) is documented, but not an axle-load readout.

Marketing claim only

Cargo-Planner: Documented

5 of 8 others document this.

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

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: weight distribution chart, per section weight, along length.

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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.

Preset containers list a tare weight, but the output reports cargo weight only.

Where we looked

Not documented

Cargo-Planner: Documented

3 of 8 others document this.

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.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: per stop, per drop, per group report, unloading view.

Not documented

Cargo-Planner: Documented

5 of 8 others document this.

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.

Input warnings exist (oversize for pallet, overweight); no validation of an edited or imported plan is documented.

Where we looked

OpenAPI spec v02.1.1 (every field description, enum, required list and the request/response examples; https://docs.searates.com/spec/load-calculator-v2-openapi.json); docs.searates.com load-calculator reference (get-packing-result/introduction; complex-objects and errors pages via manual check #2); help centre category and all 5 FAQ answers; vendor blog posts: how-to-use (Apr 2025), discover capabilities (May 2024), optimizing cargo space (May 2023), optimize stuffing (Jun 2024), pallets usage (Jun 2019), video guide text (Sep 2025), how-to-effectively-use-pallets, mastering pallet shipping; feature pages integrations/load-calculator, integrations/api-load-calculator, load-calculator landing, reference/stuffing; all 133 reachable SeaRates Updates weekly posts 2024 wk1 to 2026 wk30 (Load Calculator items extracted); English sitemaps (index, blog, reference) searched for load/stuff/pallet/axle URLs. Row-specific terms searched in all of the above: validate, check plan, violations, manual edit, warnings.

Not documented

Cargo-Planner: Not documented

1 of 8 others document this.

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

Counts when: Documented void or empty-space output.

Where we looked

Not documented

Cargo-Planner: Not documented

3 of 8 others document this.

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

Counts when: Documented plan cost output.

Where we looked

Not documented

Cargo-Planner: Documented

2 of 8 others document this.

Cargo-Planner meets 109 of 149. Try it on yours.

Start a free trial with your own equipment and load list, or book a demo and we will plan it with you.

Start a free trial Book a demo

Sources read

Read on 30 September 2026. Public material only: nothing behind a login, a trial or a video.

Are you SeaRates, and see something we got wrong? How to request a correction.