Cube-IQ vs Cargo-Planner

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

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

“Dimensions: Depth, Width, Height”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

“Weight Capacity: Maximum weight the container can hold.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Container types: Rectangular, Irregular shape / ULD, Truck / Trailer, Pallet, Carton, Railcar, Tube. Depth, Width and Height are required on import.

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.

“Unusable spaces can be added to containers to prevent products from being loaded in that region. Unusable spaces are used for benders or obstacles, with refrigerating units being a common application of unusable spaces.”

https://support.magiclogic.com/hc/en-us/articles/25043970640909-How-To-Create-Unusable-Spaces-In-Cube-IQ

“Specify 3D rectangular spaces within the container that cannot be used for loading.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Each space has Depth/Width/Height Crd and Length/Width/Height. A per-space 'No Stack' checkbox decides whether products may be stacked on top of the unusable space (documented in text).

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.

“If not, click on the " + " icon on the top left to add a new unusable space”

https://support.magiclogic.com/hc/en-us/articles/25043970640909-How-To-Create-Unusable-Spaces-In-Cube-IQ

“Specify the coordinates for where the unusable space will be situated by filling out these fields: Depth Crd Width Crd Height Crd”

https://support.magiclogic.com/hc/en-us/articles/25043970640909-How-To-Create-Unusable-Spaces-In-Cube-IQ

Any number of rectangular regions per container, each with its own position and size; set on the container record.

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.

“If you have a specific height that must be left empty at the top of the container, you can make use of this setting instead of creating a custom unusable space.”

https://support.magiclogic.com/hc/en-us/articles/25043970640909-How-To-Create-Unusable-Spaces-In-Cube-IQ

“Not usable height at top: Enter in the height of the region to be left at the top in this field.”

https://support.magiclogic.com/hc/en-us/articles/25043970640909-How-To-Create-Unusable-Spaces-In-Cube-IQ

Per container (Unusable Spaces tab), separate from the internal height; not a per-plan setting.

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.

“This article describes how to configure an irregular ULD by defining its maximum dimensions and specifying the coordinates that describe the irregular floor and/or ceiling profile.”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

“When entering the coordinates, make sure to use the correct view reference.”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

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

Only the ULD container type has floor/ceiling profiles. For trucks, split-level support is a marketing claim with no documentation of how it is modelled. The worked example uses the Front (width) view only.

The user can model a loading space whose cross-section is not rectangular, such as a ULD with a cut-back side or a rail wagon with a curved roof, and the planner keeps cargo inside that contour.

Counts when: A documented input that describes the contour (points, slope parameters or steps across the width or height), which the planner respects.

“Cube-IQ supports containers with irregular internal geometries, such as Unit Load Devices (ULDs) with non-rectangular floors or ceilings.”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

“The coordinates entered for the irregular floor therefore describe how the floor height changes along the width of the ULD.”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

Container type 'Irregular Shape / ULD': a bounding box plus lists of (Coord, Height) points for floor and ceiling. A screenshot also shows a 'ULD walls NOT supporting' checkbox with no explanation.

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.

“The same view reference should be used when defining both the floor and ceiling coordinates.”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

• Follows from documented behaviour rather than stated outright

The ULD article tells the user to use one view reference for both floor and ceiling ('The same view reference should be used when defining both the floor and ceiling coordinates.'), which suggests a profile in one view per container. No documentation shows a cross-section and a lengthwise change combined in one unit.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: combined front and side profiles, 'Left side' plus 'Front' view in one ULD, floor and ceiling view reference. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“specifying the coordinates that describe the irregular floor and/or ceiling profile”

https://support.magiclogic.com/hc/en-us/articles/48722219134605-How-to-create-an-ULD-container

• Evidence is a label in a screenshot

The Floor Shape screenshot draws straight diagonal lines between the entered points (for example from height 32 at coord 0 to height 0 at coord 30.5), which looks like an interpolated chamfer, but no text says whether the planner treats the segment as a slope or as steps, and no loaded example against a sloped wall is shown.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: slope, angle, chamfer, interpolation between floor/ceiling coordinates. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Divide containers into multiple loadable zones with unique dimensions, weight limits, and load sequences.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

“Zones are defined areas in a container to control which products are loaded based on dimensions and rules.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

Any number of rectangular zones per container, each with its own coordinates, size, sequence, load direction, max weight, matching code, product/unit counts and a 'Flex.' option. Zones must be enabled in Options. Zones are sub-volumes of one rectangular container; truck-and-trailer combinations are not documented.

The user can set a door opening smaller than the internal cross-section, and the planner does not load items that cannot pass through it.

Counts when: A documented door width and height input, documented as limiting what is loaded.

“Maximum loadable dims (door)”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

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

• Evidence is a label in a screenshot

Per container, Outside Dims tab: Length, Width, Height under 'Maximum loadable dims (door)'.

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.

“Dir.: Direction products are carried into the Zone: "B" stands for Back, "F" stands for Front, "R" stands for Right, and "L" stands for Left”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“Configure Load Direction (e.g., Back to Front or Bottom to Top).”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

• Follows from documented behaviour rather than stated outright

The side-loading form exists only per zone, not as a container-level door face; its effect on any unloading order is not described.

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.

“instead of just making the container bigger, we can give the container Maximum Overhang values. An overhang value can be set separately for length and width.”

https://support.magiclogic.com/hc/en-us/articles/28848071893901-How-to-allow-overhang-on-a-container

“Sometimes, open containers such us a pallet or a flat-bed are not big enough to contain a product in full.”

https://support.magiclogic.com/hc/en-us/articles/28848071893901-How-to-allow-overhang-on-a-container

Container dimensions must be increased by the total overhang (documented). Applies to Cube-IQ and BlackBox (XML MaxLengthOverhang / MaxWidthOverhang).

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.

“Make sure to set the quantity of the containers high enough to fill all the products you need.”

https://support.magiclogic.com/hc/en-us/articles/30961394303245-How-To-Set-Up-a-2-Stage-Load

“"containernum" : 999999”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

The user offers container types with an available quantity (a very large number means effectively unlimited); the optimiser adds units as needed (for example 'The rest of the Products are loaded into a second container' in the stack-quantity article).

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

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

“The Selection rule controls the order in which Cube-IQ attempts to load available containers. This is critical when multiple container types are allowed in a single load.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

“Best fill: All containers are simulated per step. The container with the highest utilization is selected.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

Set per load (Loading Rules) with a default in Options > Defaults; XML stage attribute containerselectionrule.

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.

“"containernum" : 1”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

“Not enough containers available to hold all the products in the load.”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

Quantity per container type in the load's container list (containernum). Unloaded remainder appears in the Not Loaded column. Which selection rules honour the quantity is not stated separately; it is documented generally.

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.

“During optimization, Cube-IQ first attempts to fit the entire product load into the preferred container(s).”

https://support.magiclogic.com/hc/en-us/articles/36949130209933-How-to-use-Preferred-Containers

“These containers will be avoided during packing unless a product is too large to fit in the primary containers.”

https://support.magiclogic.com/hc/en-us/articles/35877684746125--Avoid-use-unless-required-Container-Feature

Preferred containers fall back to the standard selection logic if they cannot hold the whole load. Documented for Cube-IQ (Web or standalone) and BlackBox.

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.

“Largest first: The largest available container is used at each step. Except in the final step where the best fit is selected.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

“One container only: Only a single container is loaded. If more than one is needed, the load fails. Used primarily in cartonization applications.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

• Follows from documented behaviour rather than stated outright

Container sizes are chosen by the planner, not by the user reading a list.

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.

“Minimum overall cost: Cube-IQ selects the combination of containers with the lowest total cost.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

“Define advanced settings such as default quantity in new loads, shipping cost, maximum loaded value, and product matching codes.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Flat 'Shipping cost' per container type; no rate tables. 'Minimum overall cost + Largest first' runs both rules and keeps the better result.

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.

“Maximum: Maximum Percent Weight or Volume allowed for this container.”

https://support.magiclogic.com/hc/en-us/articles/31270821474317-How-to-set-Fill-limits-on-containers

“Last Container Maximum: Maximum Percent Weight or Volume allowed for last container.”

https://support.magiclogic.com/hc/en-us/articles/31270821474317-How-to-set-Fill-limits-on-containers

Per container type (Loading tab), with a separate maximum for the last container. The text does not say whether one percentage applies to weight, volume or both.

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.

“Minimum: Minimum Percent Weight or Volume allowed for this container.”

https://support.magiclogic.com/hc/en-us/articles/31270821474317-How-to-set-Fill-limits-on-containers

“Hard Minimum: Denotes value that must be respected and can't be any higher.”

https://support.magiclogic.com/hc/en-us/articles/31270821474317-How-to-set-Fill-limits-on-containers

• Follows from documented behaviour rather than stated outright

What happens to cargo of a unit that stays below its minimum (moved, left unloaded) is not described.

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.

“Matching Code: Restricts products to specific containers or zones.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Remember that, if there's a matching code in this field, the product will only load into a container with the same matching code.”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

Codes on products, product configurations, containers (several codes allowed) and zones. Hard rule. The linked article 'How to Match Products with Containers' is login-gated (manual-checks #7) and was not used.

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.

“Product seq. is Container seq. – Matches product sequence numbers directly to container sequence numbers.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

“One Container per sequence number – Keeps all products with the same sequence number in a single container.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

Per load Loading Rules; the container sequence is the 'Seq.' column in the load's container list. Manual placement via Load Edit also exists but is a workaround.

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.

“It is possible to model a plastic or fabric bag as a container in Cube-IQ.”

https://support.magiclogic.com/hc/en-us/articles/29629781410957-How-to-set-up-bags-as-containers

“Set the container sizing minimum and maximum according to the possible values.”

https://support.magiclogic.com/hc/en-us/articles/29629781410957-How-to-set-up-bags-as-containers

Must be enabled in Options > General > Container Sizing; container dimensions must equal the maximums. Minimum/maximum per axis ('Dimensions to be optimized' in screenshot).

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.

“Products can be rectangular (e.g., boxes or cartons), cylindrical (e.g., rolls or drums), or L-shaped (e.g., sofas).”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“ProductId, Length, Width, Height, and Weight columns are required fields.”

https://support.magiclogic.com/hc/en-us/articles/25455347460109-How-To-Import-Products-From-Excel-Into-Cube-IQ

No overall item or type count limit is documented. Scale-related limit elsewhere: Max supported weight is switched off above 200 units in a load.

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.

“Products can be rectangular (e.g., boxes or cartons), cylindrical (e.g., rolls or drums), or L-shaped (e.g., sofas).”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Cylindrical objects are for example drums, rolls or tubes.”

https://downloads.magiclogic.com/Help/REST/glossary.html

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

• Evidence is a label in a screenshot

Shape tab option 'Cylinder/Roll/Tube' (screenshot); API product shape 'cylinder'. How the diameter is entered (no diameter field is shown; the product record has Length, Width, Height) and whether cylinders are packed as cylinders rather than boxes is not described.

Where we looked

Zendesk help centre (all 100 public articles, full text search for diameter/cylinder/roll), downloads.magiclogic.com REST glossary, New Features in Cube-IQ 5.1.

Correction: Re-checked 30 Sep 2026: all 100 public help articles, the REST glossary and the 5.1 release notes. A cylindrical product type is documented, but no diameter input and no description of packing as cylinders; the pass condition asks for a diameter input.

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.

The only statement on roll behaviour is the 5.1 release note line 'Improved Roll loading', which says nothing about the arrangement.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: nesting, staggered, honeycomb, hexagonal or pyramid arrangement of rolls/drums/cylinders; 'Improved Roll loading' release note. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Cube-IQ’s optimizer recognizes the shape geometry and can nest L-shaped products together.”

https://support.magiclogic.com/hc/en-us/articles/38575070713869-L-Shaped-products-in-Cube-IQ

“If rotation options 1 (On feet) and 2 (Upside Down) are both allowed, Cube-IQ can stack one sofa upside down on top of another.”

https://support.magiclogic.com/hc/en-us/articles/38575070713869-L-Shaped-products-in-Cube-IQ

Only the L-shape is documented; 'tapered' cases are a marketing phrase on the Developers page with no documentation.

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.

“We build the stroller as a container with zones to model the dimensions.”

https://support.magiclogic.com/hc/en-us/articles/35123386988557-How-to-use-the-Items-feature-within-Products

“Our container in stage 1 is the created stroller. Items will be loaded into the zone we created.”

https://support.magiclogic.com/hc/en-us/articles/35123386988557-How-to-use-the-Items-feature-within-Products

How it is done with general settings

1. Model the item that has free space (e.g. a stroller) as a container and add a zone describing its free internal space (How to use the Items feature within Products, https://support.magiclogic.com/hc/en-us/articles/35123386988557-How-to-use-the-Items-feature-within-Products; How To Divide Containers Into Zones, https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones). 2. Switch on multi-stage loading (Options > General > Multi-stage loading) (How To Set Up a 2 Stage Load, https://support.magiclogic.com/hc/en-us/articles/30961394303245-How-To-Set-Up-a-2-Stage-Load). 3. In stage 1, load the smaller items into that container/zone (Items article). 4. In stage 2 the loaded 'container' becomes a product and is loaded into the shipping container or box (Loading in Cube-IQ, https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ).

• Combination of general settings, shown by the vendor

The Items article is terse (no settings shown). No documentation that other cargo can use the free space under an L-shape's seat within a normal load.

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 object must be rectangular, cylindrical or 'sofa'-shaped (a 3-dimensional L-shape).”

https://downloads.magiclogic.com/Help/REST/glossary.html

“Create graphical representations of products using draw-boxes for more realistic load diagrams.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Evidence is documentation five or more years old
• The vendor's own sources disagree on this point

The current Shape tab (screenshot) lists 'Complex' greyed out. Draw-boxes are for diagrams only.

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.

“Bulk”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Shapeless / Amorphous”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Evidence is a label in a screenshot

Both appear as options on the product Shape tab (screenshot) with no description of how they occupy space; per the definition note this counts as claimed.

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.

“define the compressionlength , compressionwidth , or compressionheight attributes for your product(s) in the < products > section of your XML request.”

https://support.magiclogic.com/hc/en-us/articles/38262217295757-Product-Compression-for-Oversized-Items-in-BlackBox

“compressionlength="50" means the product can be reduced to 50% of its original length during packing.”

https://support.magiclogic.com/hc/en-us/articles/38262217295757-Product-Compression-for-Oversized-Items-in-BlackBox

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

BlackBox 5.1.9+ only, per product and dimension, as a percentage. Described for items larger than any container; whether it is also used to squeeze items into partly filled space is not stated. No Cube-IQ desktop/web equivalent documented.

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.

“Cube-IQ will automatically select the best Configs to load out of the Quantity of an order and/or by Priority.”

https://support.magiclogic.com/hc/en-us/articles/25143655295373-How-to-Set-Up-Product-Configurations

“It is only necessary to enter the order Quantity of the Product Id, and Cube-IQ will automatically break the Load Quantity down into different Config packages, and optimize them into selected Containers.”

https://support.magiclogic.com/hc/en-us/articles/25143655295373-How-to-Set-Up-Product-Configurations

A product uses either Orientations or Configurations, not both.

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.

“SIDEUPOK Default Value should be False to prevent products from getting loaded on their side.”

https://support.magiclogic.com/hc/en-us/articles/25455347460109-How-To-Import-Products-From-Excel-Into-Cube-IQ

“"turnable" : true, "flatok" : true, "sideupok" : true, "endupok" : true”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

• Evidence is a label in a screenshot

Per product: Orientations tab options (screenshot) and XML flags turnable, flatok, sideupok, endupok. Global switches 'Load all Products upright' (Settings, Client Specific) and 'Load Pallets always upright' (Options) also appear in screenshots. The linked article 'How to Set Up Allowed Orientations for Loading Products' (and 'How To Import Custom Orientations For Your Products From Excel') is login-gated (manual-checks #7) and was not used.

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.

“"turnable" : true”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

“Allowed orientations: As defined, .. or turned, All six, Custom”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

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

• Evidence is a label in a screenshot

For products: the 'As defined' option (vs '.. or turned') and the XML turnable flag. For built pallets in stage 2: 'Not turnable in stage 2', described in text. The linked article 'How to Set Up Allowed Orientations for Loading Products' (and 'How To Import Custom Orientations For Your Products From Excel') is login-gated (manual-checks #7) and was not used.

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.

“SIDEUPOK Default Value is True, this rule means Products can get loaded on their side.”

https://support.magiclogic.com/hc/en-us/articles/25455347460109-How-To-Import-Products-From-Excel-Into-Cube-IQ

“Allowed orientations: As defined, .. or turned, All six, Custom”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

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

• Evidence is a label in a screenshot

Loading on the side is explained in text; standing on the end rests on the 'All six' label and the endupok field.

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.

“SIDEUPOK Default Value is True, this rule means Products can get loaded on their side.”

https://support.magiclogic.com/hc/en-us/articles/25455347460109-How-To-Import-Products-From-Excel-Into-Cube-IQ

“"turnable" : true, "flatok" : true, "sideupok" : true, "endupok" : true”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

Setting sideupok true and endupok false would allow the side but not the end; the flags are independent fields, but only sideupok is described.

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

“Allowed orientations: As defined, .. or turned, All six, Custom”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Evidence is a label in a screenshot

A 'Custom' option exists on the Orientations tab (screenshot) and the Data Schema Reference lists an 'Orientation Rules' object, but the custom editor, the orientation-rules schema page and the custom-orientations import article are login-gated or unpublished. The public flags (turnable, flatok, sideupok, endupok) are axis-style toggles and are not shown to reach every subset of six. The linked article 'How to Set Up Allowed Orientations for Loading Products' (and 'How To Import Custom Orientations For Your Products From Excel') is login-gated (manual-checks #7) and was not used.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: 'Custom' orientation option, six-orientation mask/checkboxes, custom orientations import, orientation rules object. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Configuration priority (1-9) is a soft preference among packaging configurations, not among orientations of one item.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: preferred orientation, soft orientation preference, orientation priority. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Placement flags (On floor only, Not on floor) exist per product and per configuration, and the Products article says rules can be set per orientation, but no documentation ties an orientation to floor or non-floor placement. A route via one configuration per orientation (How to use multiple Orientation Dimensions) with its own placement flags is conceivable but undocumented for this purpose.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: orientation allowed only on floor / not on floor, bottom layer, per-orientation placement. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Configure allowed product orientations and rules for each.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Define orientation-specific data such as: Maximum Stack: Number of units in a stack. Supported Weight: Maximum weight that can be loaded on the product. Stack Index: Assigns products to higher or lower levels based on weight or fragility.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Follows from documented behaviour rather than stated outright

The per-orientation editing grid is never shown; only product-level fields are visible. The linked article 'How to Set Up Allowed Orientations for Loading Products' (and 'How To Import Custom Orientations For Your Products From Excel') is login-gated (manual-checks #7) and was not used.

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

Counts when: Documentation of automatic non-orthogonal placement.

The Load Edit shortcuts 'roll' and 'pitch' only push items onto their side or front (90-degree turns, manual editing). No automatic non-orthogonal placement is documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: angled, tilted, leaning, non-orthogonal placement; Load Edit roll/pitch. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

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

Cylinder/Roll/Tube is one shape type; no article says whether the user can choose upright or lying, or how orientation flags apply to cylinders.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: cylinder/roll/drum upright vs lying, standing, on side, tube orientation. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“On top only”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“"toponly" : false”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

• Evidence is a label in a screenshot

Per product (Orientations tab 'On top only', XML toponly) and per configuration. A Max. supported weight is also available (see stacking-bearing), but a value of zero is not documented as meaning 'nothing on top'.

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.

“On floor only”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“"bottomonly" : false”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

• Evidence is a label in a screenshot

Per product (Orientations tab, XML bottomonly) and per configuration; also a global weight threshold that makes heavier products floor-only (Options > Loading Rules, screenshot).

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.

“Not on floor”

https://support.magiclogic.com/hc/en-us/articles/25143655295373-How-to-Set-Up-Product-Configurations

• Evidence is a label in a screenshot

Only on product configurations (Placement section of the Configurations tab); not on the plain Orientations tab.

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.

“A Product's stacking can be controlled by its Product attribute Maximum Stack; however, Maximum Stack only limits how many it can stack on itself.”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

“Products imported will now only stack 7 high and will not be loaded on their side.”

https://support.magiclogic.com/hc/en-us/articles/25455347460109-How-To-Import-Products-From-Excel-Into-Cube-IQ

Per product (Maximum Stack; XML maxinlayer, default 999999 = no limit), per configuration ('Max. Stack'), and per orientation (see orientation row).

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.

“Limit the stacking quantity level in a Container with the General Maximum Stack Quantity Setting.”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

“Once Cube-IQ is showing the Client Specific tab, the General Max Stack Quantity can be changed from the 999999 default to 2.”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

Documented limitation alongside: the per-product Maximum Stack does not cap mixed stacks. The Client Specific tab is hidden by default and says its fields should be left blank unless advised by MagicLogic (screenshot).

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

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

“"max_stack_height": 5”

https://support.magiclogic.com/hc/en-us/articles/34464697053197-Products

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

The API Products article's illustrative object has "max_stack_height": 5 without a unit or description; the article says field names are illustrative and it differs from the XML examples. No per-item height limit in length units is documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: maximum placement height, maximum stacking height per item, height limit in length units. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“To set a Product's Max supported weight limit: Click Products menu Click Stacking tab Type 100 in Max. Supported weight field”

https://support.magiclogic.com/hc/en-us/articles/25048950806029-How-To-Set-Product-Max-Supported-Weight

“The left Container is loaded wrong on account of the combined weight of red and yellow Products on top of blue Products is greater than than 100 lbs.”

https://support.magiclogic.com/hc/en-us/articles/25048950806029-How-To-Set-Product-Max-Supported-Weight

Scale limit: switched off automatically when a load has more than 200 units. Not evaluated as pressure.

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.

“Our software ensures your pallets are loaded accurately, calculating cartons’ strength and crush resistance and ensuring only lighter items are placed on top.”

https://magiclogic.com/load-planning-cartonization-and-palletization-now-accessible-in-the-cloud/

The cloud announcement blog claims BlackBox calculates 'cartons’ strength and crush resistance', but no pressure- or area-based bearing limit is documented; Max supported weight is a plain weight.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: pressure, weight per area, contact area, crush resistance per face. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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 Max supported weight example uses different products on top of the blue product; no article states whether the limit is also checked within a stack of the same product (Maximum Stack is the documented like-item control).

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: supported weight on identical products, like-item stacks. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

Counts when: A documented weight-ordering stacking rule.

“Our software ensures your pallets are loaded accurately, calculating cartons’ strength and crush resistance and ensuring only lighter items are placed on top.”

https://magiclogic.com/load-planning-cartonization-and-palletization-now-accessible-in-the-cloud/

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

Blog claim about BlackBox palletisation only. The documented Stack Index 'assigns products to higher or lower levels based on weight or fragility' but its rule is not described (see stacking-strength-index).

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.

“Stack Index: Assigns products to higher or lower levels based on weight or fragility.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“"stackindex" : 2”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

Per product, per orientation and in XML. The direction of the rule (whether higher numbers go higher) and whether it is a hard 'never on a weaker index' rule are not documented. Reports can recolour products 'By stack index'.

Correction: Stack Index text gives no ordering rule; the auditor's own ambiguity note conceded the gap.

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.

“Stack Code: Restricts stacking combinations using a matrix.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Use the Stacking Matrix to determine which products can be stacked on others.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

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

'Stack only on the same item' is reachable by giving an item a unique code and allowing only the diagonal, or via the 'Stack only if stack code the same' switch (screenshot). The article 'How To Control Product Stacking Using The Stacking Matrix' is login-gated (manual-checks #7).

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.

“Supports Same Footprint Only: Ensures only identical products are stacked together.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Stacks upon same footprint only”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• The vendor's own sources disagree on this point
• Evidence is a label in a screenshot

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.

“Minimum support factor”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“BlackBox ensures no cartons or items overhang the pallets or the layers underneath, based on the item’s precise weight and dimensions.”

https://magiclogic.com/load-planning-cartonization-and-palletization-now-accessible-in-the-cloud/

• Evidence is a label in a screenshot

For pallets built in layers, 'Minimum Layer Footprint' sets how much a layer must cover over the layer beneath (text), which is a layer rule rather than a per-item support share.

The user can set how large a height difference between neighbouring supporting surfaces an item may bridge.

Counts when: A documented maximum vertical gap or height-difference parameter for stacking across several items.

“The following Palletizing Rules settings are automatically updated: Use seq/groups only for depalletizing Maximum gap after spreading Minimum bridging support Max. height difference in layer Max. height difference in layer at top Max. height differential”

https://support.magiclogic.com/hc/en-us/articles/26113101431949-How-To-Load-Layers-On-A-Pallet

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

Filled by a 'Set Values' button; units and meanings are not given.

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.

“Enter the nesting height increment (e.g., 0.1 cm ). This value tells Cube-IQ how much height is added when an additional unit is stacked.”

https://support.magiclogic.com/hc/en-us/articles/41226254056205-Nesting-Behavior-in-Load-Optimization

“If a product has a total height of 10 and a stackheight of 2.5: 1 unit = 10 height 2 units = 10 + 2.5 = 12.5 height”

https://support.magiclogic.com/hc/en-us/articles/41226254056205-Nesting-Behavior-in-Load-Optimization

The open-top variants and the smaller-top fields are visible only in a Stacking-tab screenshot; release notes name the feature ('Handling of open top boxes'). The nesting part is fully described in text.

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.

“Load full stacks only – Loads only complete stacks or layers, no partial stacks.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

“Complete Layers Only This option disallows incomplete layers.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

Remainder is left unloaded (documented for Complete layers only); remainder handling for 'Load full stacks only' is not stated.

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

“Cube-IQ allows you to assign group numbers to products that you wish to keep together”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

“Open a load in the Load Setup area, and enter a number in the Grp column for each product. Products of the same group number will be grouped together within the load.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

How it is done with general settings

1. In Load Setup, give each product line its own number in the Grp column (How To Group Products Together Within a Load, https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load). 2. Optimise: products with the same group number are kept together rather than spread among other products (same article).

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

No dedicated 'keep identical items together' switch is documented; block-building settings ('Create single Unit blocks', 'Target minimum number of Units per block') exist only as screenshot labels on the Client Specific tab.

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.

“Products of the same group number will be grouped together within the load.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

“If you need to sequence products belonging to a group within a group's container, you can use Cube-IQ's Use 'sequence' with groups feature.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

Per product-to-load 'Grp' column (XML defaultgroup). Sequence within groups gives a second level. A product 'Master Package Code' that 'Groups similar products' exists with no described effect.

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.

“Never allowed: Groups must stay together at all times. If a group is too large or heavy for one container, it will not be loaded at all.”

https://support.magiclogic.com/hc/en-us/articles/37883088205069-Splitting-Groups-Over-Containers

“Allowed if it avoids an extra Container: Groups are kept intact unless splitting them avoids using an additional container.”

https://support.magiclogic.com/hc/en-us/articles/37883088205069-Splitting-Groups-Over-Containers

Failure mode documented: with 'Never allowed' an oversized group is left unloaded.

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.

“If “Never Allowed” Setting is selected, products to load may not get loaded into a container if no container is large enough to load the entire product group.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

“In this scenario, the Not Loaded columns confirms how all yellow products have 28 not loaded items each after re-optimizing .”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

Documented for the case where the group is larger than any available container type. Whether a group is also dropped whole when the available container quantity runs out is not stated.

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

“Product sequence is drop sequence”

https://support.magiclogic.com/hc/en-us/articles/28426447989901-Why-priority-on-product-configurations-is-not-working

“Thickness of wall/space to separate drops”

https://support.magiclogic.com/hc/en-us/articles/33952603524493-Adjusting-the-Maximum-Block-Length

• Evidence is a label in a screenshot
• Relies on a setting other rows also use; they may not all work at once

A text-documented alternative: define one zone per section and give each group's products the zone's matching code (zones article), so each group is confined to its own zone.

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.

“Stack only if sequence the same”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

“Stack Code: Restricts stacking combinations using a matrix.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Evidence is a label in a screenshot
• Relies on a setting other rows also use; they may not all work at once
• Follows from documented behaviour rather than stated outright

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.

“Assign combination codes to products to control which products can be loaded together.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Configure the Combination Matrix to establish compatibility between product combinations.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Follows from documented behaviour rather than stated outright

The article 'How To Control Which Products Can Be Combined In A Loaded Container' is login-gated (manual-checks #7).

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.

“Grouping or zoning requirements, such as separating hazardous materials or temperature-controlled goods.”

https://support.magiclogic.com/hc/en-us/articles/33696533383181-Load-Setup

“Match: rule to only allow Products with equal Match Code to load into Zone.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

How it is done with general settings

1. Enable zones and define two zones in the container, positioned apart (for example one at the rear and one at the front, with a gap between them) (How To Divide Containers Into Zones, https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones). 2. Give each zone a Match code (same article). 3. Give the products of each class the matching code of their zone (Products, https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products: 'Matching Code: Restricts products to specific containers or zones.'). 4. Optimise; each class stays within its own zone (zones article).

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

Load Setup names 'zoning' for separating hazardous or temperature-controlled goods but shows no example. No separation-distance or not-above rule exists as such.

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.

“HAZMAT and Liion shipping rules are complicated, but Cube-IQ handles them with ease.”

https://magiclogic.com/answers-to-15-common-load-optimization-problems/

“Our customizable loading rules ensure all hazardous or combustible products are loaded safely”

https://magiclogic.com/answers-to-15-common-load-optimization-problems/

No hazard-class attribute or built-in segregation table is documented. Documented hazmat tools are the Q-value cap (sum ≤ 1.0 per container) and user-built combination codes or zones.

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.

“the value of the products loaded will not exceed the maximum allowable value of goods in the container.”

https://support.magiclogic.com/hc/en-us/articles/25046712114573-How-to-Limit-the-Total-Value-Cost-of-Loaded-Items

“The combined Q-value sum of all products in a single container cannot exceed 1.0 .”

https://support.magiclogic.com/hc/en-us/articles/28749189944333-How-to-Limit-Quantities-of-Hazardous-Products-using-Q-value

Value requires the Client Specific data to be shown. Ceiling for the value cap: 9999999/2.

The user can cap how many distinct items (or orders) a unit may contain.

Counts when: A documented per-unit (or per-zone) limit on distinct item types or order numbers.

“Max # Products (Prds): rule for Maximum number of Product IDs to loaded into Zone”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“Maximum number of POs per Container”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

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

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.

“If you have a requirement to load a group of articles or items which must be kept in exact proportional quantities, you can use Cube-IQ's 'treat groups as sets' feature.”

https://support.magiclogic.com/hc/en-us/articles/28624305444877-How-To-Load-Items-In-Proportional-Quantities-Using-Cube-IQ-s-Treat-Groups-As-Sets-Feature

“As you can see, each item is loaded in the correct ratio with its other set members, and the overall loading is extremely efficient”

https://support.magiclogic.com/hc/en-us/articles/28624305444877-How-To-Load-Items-In-Proportional-Quantities-Using-Cube-IQ-s-Treat-Groups-As-Sets-Feature

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

Behaviour when the ratio cannot be met is not described.

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

Counts when: A documented batch or multiple-of-N rule per item.

“"batch" : 1”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

The API load example has an undescribed 'batch' field on products-to-load; configurations turn N units into one rigid package (a stronger constraint than a count multiple); Config4QTY rounds order quantities up to whole packs. None is documented as a multiple-of-N-per-unit rule.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: multiple of N per container, batch, fixed quantity per unit, 'Fixed stack qty', Config4QTY. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

The user can fix part of a plan (placed items, pre-loaded pallets or whole units) and have the planner complete or re-plan the rest around it.

Counts when: Documentation shows existing placements kept fixed while the planner adds or re-plans the remaining cargo.

“Click on the status bar at the bottom of the screen to lock specific parts of the load. After locking parts of the load, make changes to the Load List or Settings, and re-optimize using the Load Setup screen.”

https://support.magiclogic.com/hc/en-us/articles/33723815682701-Load-Plan

“Use the Modify button to fix specific products. Make changes and click Re-Optimize to adjust the remaining portion of the load.”

https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ

Loaded containers also carry a 'Locked' checkbox in Load Setup (screenshot). Manual Load Edit placement followed by locking and re-optimising is the documented path to hand-placed items.

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

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

“Coordinate (Crd): for where the Zone begins from the rear wall, left wall, and floor as the”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“Match: rule to only allow Products with equal Match Code to load into Zone.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

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

No coordinate input on the item itself is documented; the vendor's own route to an exact position is manual Load Edit plus locking (a workaround).

Correction: Zone recipe is auditor-built and relies on undocumented zone behaviour; the vendor's route is manual Load Edit plus Modify to fix products.

The user can confine an item to a defined region of the unit, such as the front, the rear, one side or a zone.

Counts when: A documented per-item (or per-class) region, zone or location rule the planner respects.

“Match: rule to only allow Products with equal Match Code to load into Zone.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“Assign product matching codes for specific zones to create complex loading scenarios.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Zones must be enabled in Options; a 'Flex.' option lets a zone 'adjust dimension automatically if necessary to provide better fit' (extent undocumented).

The user can keep items out of a defined region of the unit (for example the first metre at the door, or a central aisle).

Counts when: A documented rule that keeps an item, or all items, out of a region of a unit.

“Match: rule to only allow Products with equal Match Code to load into Zone.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“Specify 3D rectangular spaces within the container that cannot be used for loading.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Both zones and unusable spaces are defined on the container record, not per plan; the zone route is item-selective.

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.

“TRUE means Products load from bottom to top and FALSE means back to front.”

https://support.magiclogic.com/hc/en-us/articles/25047001354125-How-to-import-Containers-in-Excel-to-Cube-IQ

“TRUE means Container is compacted in height and FALSE compacts along container's length.”

https://support.magiclogic.com/hc/en-us/articles/25047001354125-How-to-import-Containers-in-Excel-to-Cube-IQ

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.

“TRUE means Products load from bottom to top and FALSE means back to front.”

https://support.magiclogic.com/hc/en-us/articles/25047001354125-How-to-import-Containers-in-Excel-to-Cube-IQ

“In this exercise we will begin with a Pallet Container having default settings and configured for "Bottom to Top" Load direction and "In Height" Load compacting.”

https://support.magiclogic.com/hc/en-us/articles/26113101431949-How-To-Load-Layers-On-A-Pallet

• Follows from documented behaviour rather than stated outright

Scope is per container, not per item.

The user can make the planner respect handling-equipment limits: how deep a loading block may reach, or room to turn an item with a forklift.

Counts when: A documented maximum reach or block depth, or a forklift-turning check.

“The maxreach setting limits how far back subsequently loaded items can be placed from the front most item in the container.”

https://support.magiclogic.com/hc/en-us/articles/33107389209869-Adjusting-the-Maximum-Reach-Setting

“Maximum Block Length in Load Plans Defines the maximum depth of a block in the direction of loading .”

https://support.magiclogic.com/hc/en-us/articles/33952603524493-Adjusting-the-Maximum-Block-Length

Per settings profile (Operational Settings), in length units.

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.

“Space to be left open ... .. overall in width direction .. between Units - length direction .. between Units - width direction .. between Units - height direction”

https://support.magiclogic.com/hc/en-us/articles/33952603524493-Adjusting-the-Maximum-Block-Length

• Evidence is a label in a screenshot

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.

“Maximum bracing distance”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

• Evidence is a label in a screenshot

A container field 'Maximum bracing distance' appears in Containers-tab screenshots with no description; it may relate to this row but its effect is not documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: bracing, backed by wall, lateral support, shift, load securing check. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Weight Capacity: Maximum weight the container can hold.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

“Products exceed maximum weight capacity of available containers.”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

Per container type; pallets are containers, so this is also the pallet's maximum load. No gross-vehicle-weight (tare-inclusive) form documented.

Each compartment, deck or part of a unit can have its own weight limit, which the planner respects.

Counts when: A documented weight limit per compartment, section, zone, deck or part.

“Max Weight: rule for maximum Weight Capacity for a Zone”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“the Max Weight rule will also prevent Products from getting loaded into a Zone if combined weight is greater than the Zone's Max Weight.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

Per zone.

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.

“Here is an example where this Semi-Trailer must adhere to rules where front area can only support a weight of 5000kg, rear can only support a weight of 5,500kg and the difference of 12,000kg can only be supported in the middle. A rear, middle, and front Zone can be defined for these Max Weight rules.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

“There is also a Max. Weight restriction for each Zone where Zone weight cannot be greater 4,500kg in the rear, 12,000kg in the middle, and 5,000kg in the front Zone.”

https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones

How it is done with general settings

1. Enable zones and add consecutive zones along the length (rear Depth Crd 0, middle 351 cm, front 936 cm) spanning the full width and height (How To Divide Containers Into Zones, https://support.magiclogic.com/hc/en-us/articles/26247534060813-How-To-Divide-Containers-Into-Zones). 2. Set Max Weight on each zone (same article). 3. Optimise; products are kept within zone boundaries and zone weight limits (same article).

• Combination of general settings, shown by the vendor

The article's own numbers differ (5,500 kg vs 4,500 kg for the rear).

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.

Only fixed zones with Max Weight are documented (see weight-length-sections); no continuous weight-per-length rule.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: weight per metre, per unit length, linear load, floor load per length. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

“Configuring axles ensures that optimized loads comply with real-world transport rules, balancing cargo across axle groups and avoiding overweight violations.”

https://support.magiclogic.com/hc/en-us/articles/39272917952909-How-to-Setup-Axles-for-Truck-Containers

“Dist from Back – The distance (in inches or mm) from the back of the container. Weight Limit – Maximum allowable weight for the axle.”

https://support.magiclogic.com/hc/en-us/articles/39272917952909-How-to-Setup-Axles-for-Truck-Containers

Container type Truck, Axle Weights tab, Cube-IQ v5+. The axle-load model (rigid truck vs trailer, kingpin, tare) is not described.

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.

“Click Add Axle to create a new axle group.”

https://support.magiclogic.com/hc/en-us/articles/39272917952909-How-to-Setup-Axles-for-Truck-Containers

“Define the following for each axle:”

https://support.magiclogic.com/hc/en-us/articles/39272917952909-How-to-Setup-Axles-for-Truck-Containers

• The vendor's own sources disagree on this point

The Axles article (Sep 2025) has an add-row grid; its screenshot shows two rows. The Containers overview says two axles.

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.

The only tare field is the container's 'Tare Weight' on the Outside Dims tab, documented for use when the loaded container becomes a product in the next stage, not for axle loads.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: tare per axle, empty axle load, vehicle tare, tare centre of gravity. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Axles are defined only by distance from the back of the container and a weight limit; no towing unit is modelled.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: kingpin, fifth wheel, tractor, drawbar, coupling, semi-trailer axle transfer. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Our software can calculate loads taking into account weight distribution front/back and left/right, and can also balance weight across axles, meeting all state regulations and avoiding those pesky fines that mount up so quickly.”

https://magiclogic.com/answers-to-15-common-load-optimization-problems/

A blog post claims the software can 'balance weight across axles, meeting all state regulations', but no jurisdiction setting or built-in legal limits are documented; limits are typed per axle.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: jurisdiction, state, region, legal limits, bridge formula, permits. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Set minimum and maximum positions for the COG. Use percentages of the container’s length and width.”

https://support.magiclogic.com/hc/en-us/articles/39200622809997-How-To-Use-The-Center-Of-Gravity-Setting-In-Cube-IQ

“Set Minimum % of length from back to 40%. Set Maximum % of length from back to 60%. When you reoptimize the load, the heavy pink products are now loaded in the center of the container.”

https://support.magiclogic.com/hc/en-us/articles/39200622809997-How-To-Use-The-Center-Of-Gravity-Setting-In-Cube-IQ

Per settings profile (Operational Settings, 'Range for Center of Gravity Location'), as % of container length from the back. Whether it is a hard limit or a target is not stated; the examples show the load moving into the range.

The user can set a permitted range for the sideways position of the load's centre of gravity (left/right balance), and the planner keeps within it.

Counts when: A documented lateral centre-of-gravity range, or maximum left/right difference, that the planner enforces.

“Set minimum and maximum positions for the COG. Use percentages of the container’s length and width.”

https://support.magiclogic.com/hc/en-us/articles/39200622809997-How-To-Use-The-Center-Of-Gravity-Setting-In-Cube-IQ

“Minimum % of length from back Maximum % of length from back Minimum % of width from left Maximum % of width from left”

https://support.magiclogic.com/hc/en-us/articles/39200622809997-How-To-Use-The-Center-Of-Gravity-Setting-In-Cube-IQ

• Evidence is a label in a screenshot

Width range as % from the left wall. Only lengthwise examples are shown; field names for width are from the article's screenshot, the text names both length and width.

The user can cap the height of the load's centre of gravity.

Counts when: A documented vertical centre-of-gravity limit that the planner enforces.

The CoG range covers length and width only.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: vertical centre of gravity, height of COG, COG height limit. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Our software can calculate loads taking into account weight distribution front/back and left/right, and can also balance weight across axles”

https://magiclogic.com/answers-to-15-common-load-optimization-problems/

“Configuring axles ensures that optimized loads comply with real-world transport rules, balancing cargo across axle groups and avoiding overweight violations.”

https://support.magiclogic.com/hc/en-us/articles/39272917952909-How-to-Setup-Axles-for-Truck-Containers

No option to centre the load or even out axle loads without a bound is documented; the documented CoG control is a min/max range.

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.

Products have dimensions and weight only (plus Net weight in a screenshot).

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: item centre of gravity, off-centre COG, eccentric weight. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Interpret Product sequence as ‘priority’ – Loads lower sequence numbers first, treating them as higher priority.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

“Enable the "Use Group number as primary sequence" feature to load groups in the order of their group number.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

Direction: lower sequence numbers are loaded first, so with back-to-front loading they sit deeper; the Maximum reach article implies later sequences should be nearer the door. The direction is inferred from 'loaded first', not stated as a position rule.

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.

“Interpret Product sequence as ‘priority’ – Loads lower sequence numbers first, treating them as higher priority.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

“Prioritization and Sequencing. Load priority items first and fill to capacity with option items to max out the cube.”

https://magiclogic.com/developers/

Per load Loading Rules option. That lower-priority lines are the ones left out when space runs out is implied by 'loaded first' rather than stated.

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.

“Prioritization and Sequencing. Load priority items first and fill to capacity with option items to max out the cube.”

https://magiclogic.com/developers/

“You can even have additional fill items packed to cube out a load when necessary, avoiding paying for empty space in an expensive container.”

https://magiclogic.com/answers-to-15-common-load-optimization-problems/

No optional or fill-item flag is documented in the help centre or API.

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.

“Product sequence is drop sequence”

https://support.magiclogic.com/hc/en-us/articles/28426447989901-Why-priority-on-product-configurations-is-not-working

“Thickness of wall/space to separate drops”

https://support.magiclogic.com/hc/en-us/articles/33952603524493-Adjusting-the-Maximum-Block-Length

• Evidence is a label in a screenshot
• Follows from documented behaviour rather than stated outright
• Relies on a setting other rows also use; they may not all work at once

Also marketing: 'facilitates loading in specific sequences' (Cube-IQ page).

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.

Maximum reach limits how far back later items may be placed from the front-most item and 'Stack only if sequence the same' (screenshot) limits cross-sequence stacking, but neither is documented as a guarantee that each stop unloads without moving other goods.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: later stops never in front of or on top of earlier stops, unload without moving goods, LIFO. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Maximum # of Sequence to look ahead – Sets how many future sequences are considered during optimization.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

“"sequencemixok" : true”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

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

• Follows from documented behaviour rather than stated outright

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.

The cloud announcement's 'pick or drop sequence' does not describe per-item pickup stops.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: pickup stop, origin and destination per item, pick-up and delivery. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

Sequence rules operate in multi-container loads ('One Container per sequence number', 'Product seq. is Container seq.', 'Sequenced reaching minimum fill first'), but no article states that drop-order placement holds within or across several units.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: drop sequence across several containers, multi-stop in multi-container loads. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Finish each Product sequence – Decides if a sequence must be completed in one container or can be split.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

• Follows from documented behaviour rather than stated outright

'Finish each Product sequence' 'Decides if a sequence must be completed in one container or can be split'; it concerns splitting across containers, and its other values and behaviour when a sequence does not fit are not documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: sequence loaded completely or not at all, partial sequence, finish each sequence. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Loads carry a date field (API example "date" : "17-11-2015") with no planning effect described.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: due date, ship date, storage date, date range, date-based allocation. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“In Cube-IQ, a pallet is treated as one type of container .”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

“Columns G's "Outside Height" in this example is the height of the container's floor; therefore, the mapping for this column G in Cube-IQ is OUTSIDEEXTRAHEIGHT.”

https://support.magiclogic.com/hc/en-us/articles/25047001354125-How-to-import-Containers-in-Excel-to-Cube-IQ

The pallet container's Height is the load-height limit above the deck; the deck height ('Height to be Added') is added when the built pallet moves to the next stage. A total-height limit including the deck is therefore entered as container height minus deck height; no single 'total height' field is documented.

For a single item type, the planner generates the layer pattern and number of layers for a pallet (Hi/Ti).

Counts when: Documentation of automatic single-item pallet pattern generation.

“The green Product's formation has changed to be more suited to load a Pallet of green Products.”

https://support.magiclogic.com/hc/en-us/articles/26113101431949-How-To-Load-Layers-On-A-Pallet

“Pallet Rules tell Cube-IQ how to stack products on a pallet.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

The optimiser builds the layer pattern and number of layers itself; one result per run, no list of alternative patterns documented.

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.

“Rotate Layers Check this box to rotate every second layer by 180° to make the stack stronger.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

“Spread Units Check this box to leave more space between products, so that each layer covers the largest possible amount of available surface area.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

• The vendor's own sources disagree on this point
• Evidence is a label in a screenshot

The planner builds pallets that carry several different item types.

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

“Mixed Layers Check this box if you wish to allow the optimizer to mix multiple different products in the same layer.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

“Once a Pallet load has been created, in the settings tab under client specific you can select Use the Mixed Palletization Optimizer to introduce the feature.”

https://support.magiclogic.com/hc/en-us/articles/32799625579661-Mixed-Pallet-Optimizer

What the Mixed Palletization Optimizer does differently, and which rules it honours, is shown only by before/after animations.

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.

“Maximum Overhang (per side) This setting specifies how much of the pallet's length or width refers to an area hanging over the side of the pallet.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

“If the actual pallet width is 90 cm, but you wish to allow 5 cm of overhang on each side, you should define it as 100 cm wide (5cm on left + 90 cm width + 5 cm on the right) and set Maximum Overhang in Width Direction to 5 cm.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

Per pallet, length and width per side; the pallet must be defined including the overhang.

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.

“Check Center Load to center the load on the Pallet, in both length and width direction. If overhang is allowed, the Load will always be centered, as this minimizes the use of overhang.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

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

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

Not mentioned in any source.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: slip sheet, tier sheet, interlayer, layer pad, separator sheet. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

““Never Allowed” setting will never split grouped products, will always load grouped products together in one container.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

“Select "Okay only when too large for container" setting if groups cannot share the same container and each group can split between more than one container.”

https://support.magiclogic.com/hc/en-us/articles/26109959849869-How-To-Group-Products-Together-Within-a-Load

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

The group rules are documented with ocean containers; their use for pallets follows from pallets being a container type but is not shown.

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.

“Cube-IQ can even handle a more complete scenario when you need to optimize the products into cartons, the cartons into pallets and the pallets into Trucks or maritime containers. An you can optimize all the stages with a single click of a button.”

https://support.magiclogic.com/hc/en-us/articles/30961394303245-How-To-Set-Up-a-2-Stage-Load

“Cube-IQ will optimize both stages of the load.”

https://support.magiclogic.com/hc/en-us/articles/41508244709645-Loading-Products-in-Multiple-Stages

Options > General > Multi-stage loading must be switched on; containers need Outside Dimensions.

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.

“Once Stage 1 is completed, Cube-IQ automatically converts loaded containers into Stage 2 products for the next stage.”

https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ

“For the Multi-Stage Loading feature to work properly, containers should be defined with Outside Dimensions .”

https://support.magiclogic.com/hc/en-us/articles/41508244709645-Loading-Products-in-Multiple-Stages

Outside length/width/height, height to be added, tare weight and stack code carry into the next stage.

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.

“Once products have been loaded into containers in the first stage, those containers may be loaded into larger containers in a second or third stage.”

https://support.magiclogic.com/hc/en-us/articles/41508244709645-Loading-Products-in-Multiple-Stages

“optimize the products into cartons, the cartons into pallets and the pallets into Trucks or maritime containers.”

https://support.magiclogic.com/hc/en-us/articles/30961394303245-How-To-Set-Up-a-2-Stage-Load

Three stages documented; configurations can be assigned to stages by priority number.

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.

“If set to true , the product will only be placed into a container (e.g., carton, master box) if that container is already being used and has leftover space. It will never trigger the creation of a new container on its own.”

https://support.magiclogic.com/hc/en-us/articles/39256010460429-Shipping-Pre-Packaged-Items-Without-Extra-Cartons-in-BlackBox

“Place it into a carton only if it fits without requiring additional or larger cartons.”

https://support.magiclogic.com/hc/en-us/articles/38919586622221-Shipping-Pre-Packaged-Items-Without-Extra-Cartons-in-Cube-IQ

Complete-layers-only remainders are left unloaded for another pallet.

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.

“Check Not turnable in stage 2 if the loaded pallet is meant to go into another container in the second stage, and you wish to restrict the optimizer from changing the pallet's orientation.”

https://support.magiclogic.com/hc/en-us/articles/41898310053133-Pallet-Rules-and-How-to-Configure

“Usually, pallets do not stack on each other. Then, by default, pallets are not allowed to stack on stage 2.”

https://support.magiclogic.com/hc/en-us/articles/30980066402957-How-To-Allow-Pallets-To-Stack-On-Stage-2

Stacking pallets in stage 2 needs the Stage2Stacks feature code and a restart. No rule on how full a pallet's top must be is documented.

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

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

Container sizing lets the optimiser choose a container's dimensions within a range (documented for bags); its use to size pallet heights to the vehicle in a multi-stage load is not documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: pallet height adapted to vehicle, shorter top-tier pallets, dynamic pallet height, container sizing for pallets. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“By default Cube-IQ will attempt to fill containers with the maximum loaded volume or loaded weight feasible.”

https://support.magiclogic.com/hc/en-us/articles/31270821474317-How-to-set-Fill-limits-on-containers

“The BlackBox load engine has maximum fill rate as its main objective.”

https://magiclogic.com/products/blackbox/

Measure: volume or weight ('maximum loaded volume or loaded weight feasible'); which one governs is not stated. Unloaded excess is reported in the Not Loaded column.

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.

“Best fill: All containers are simulated per step. The container with the highest utilization is selected.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

The default objective is stated as 'maximum loaded volume or loaded weight feasible' and 'Best fill' picks 'the highest utilization', but no setting lets the user choose weight over volume.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: weight utilisation objective, maximise weight, weight-based selection rule. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Load proportionally – Distributes products evenly across containers rather than filling one at a time.”

https://support.magiclogic.com/hc/en-us/articles/38593689465357-What-are-Loading-Rules

Per load Loading Rules option. The measure (volume, weight or count) is not defined.

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.

“Assign large loading quantities to each item, and make sure the quantity reflects the ratio between each item.”

https://support.magiclogic.com/hc/en-us/articles/28624305444877-How-To-Load-Items-In-Proportional-Quantities-Using-Cube-IQ-s-Treat-Groups-As-Sets-Feature

“we want to load exactly one dining table, two arm chairs and four standard chairs multiple times. Similarly for the bed set, we want to load a headboard, a footboard and two rails, multiple times, and overall load as many items as possible”

https://support.magiclogic.com/hc/en-us/articles/28624305444877-How-To-Load-Items-In-Proportional-Quantities-Using-Cube-IQ-s-Treat-Groups-As-Sets-Feature

Cube-out relies on entering a quantity larger than will fit; there is no mode that works without a quantity.

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.

“The "Maximum run time" setting defines the strict time limit the optimizer uses when working on each container.”

https://support.magiclogic.com/hc/en-us/articles/37229392649485-BlackBox-CubeIQ-Optimizer-Settings

“The "Maximum number of non-improving iterations" determines how many additional optimization attempts can be made without finding a better result”

https://support.magiclogic.com/hc/en-us/articles/37229392649485-BlackBox-CubeIQ-Optimizer-Settings

Per settings profile (XML maxruntime, maxnonimproveiters); Interrupt keeps the best load so far. Results are not reproducible run to run (documented limitation). A 'Stop as soon as everything loaded' switch appears in a screenshot.

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.

“Minimum overall cost + Largest first: Runs the optimizer twice, once using each rule. Then selects the better result.”

https://support.magiclogic.com/hc/en-us/articles/37580174850829-Container-Selection-Rules

'Minimum overall cost + Largest first' runs the optimiser twice and keeps the better result; it does not return both for comparison.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: multiple solutions, alternative plans, compare plans, scenarios. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

The user can write a rule that selects items by a condition on an attribute (for example all items over 500 kg) and applies a constraint to them.

Counts when: A documented rule mechanism that selects items by an attribute condition.

“Make Product floor-only if weight more than ...”

https://support.magiclogic.com/hc/en-us/articles/28426447989901-Why-priority-on-product-configurations-is-not-working

• Evidence is a label in a screenshot

No general rule builder over attributes is documented.

The user can define their own item attributes and use them in planning rules.

Counts when: Documentation of user-defined fields that a rule, matrix or objective can select on.

“Use attributes like supplier or plant location to refine product visibility during load setup.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“SQL commands are useful to get customized information from Cube-IQ's database.”

https://support.magiclogic.com/hc/en-us/articles/30922405969549-How-To-Use-The-SQL-Interpreter-in-Cube-IQ

Products have Filtering Attributes 1-4 ('refine product visibility during load setup'), loads can show user fields and the Load Setup grid shows PUserString columns (screenshot), and an SQL interpreter queries the database; none is documented as usable in a planning rule. Free-text codes (matching, stack, combination, group) drive built-in rules and are scored under the between-items rows.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: user fields, user data, attributes, filters, SQL interpreter, PUserString. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

The user can define item classes and a matrix of which class may be stacked on which.

Counts when: A documented class code per item and a class-to-class stacking matrix.

“Create and assign stack codes to products to define stacking rules.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Use the Stacking Matrix to determine which products can be stacked on others.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Follows from documented behaviour rather than stated outright

Stack codes on products, configurations and next-stage containers; 5.1 adds 'Sorting on stack codes'. Per-orientation exceptions are possible only through configurations (each has its own code). No class-count guidance.

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

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

“Assign combination codes to products to control which products can be loaded together.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Configure the Combination Matrix to establish compatibility between product combinations.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

• Follows from documented behaviour rather than stated outright

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

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

Only fixed attributes are capped: declared value ('Maximum total loaded value') and hazmat Q-value (cap 1.0). Both pass between-sum-cap only.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: user-chosen attribute sum cap, custom capacity, per-group cap. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

Rule settings can differ from one equipment unit to another within one plan.

Counts when: Documentation of rule or optimiser profiles assigned per unit or equipment type.

“Settings: Optimization parameters selected from the drop-down list or defined through the Settings tab.”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

“"settingsid" : "Box Default"”

https://support.magiclogic.com/hc/en-us/articles/34463597171341-Containers

Named settings profiles (Optimizer Settings, Operational Settings, Loading Rules, Client Specific) are assigned per container type; pallet rules and fill limits are also per container type.

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.

“Configure stacking rules for products, such as: Stack Code: Restricts stacking combinations using a matrix. Supports Same Footprint Only: Ensures only identical products are stacked together. Nested Stacking: Defines height adjustments for stacked products.”

https://support.magiclogic.com/hc/en-us/articles/33735548703117-Products

“Setting Maximum Stack to 2 for four different Products does not prevent these four Products from stacking 8 levels high”

https://support.magiclogic.com/hc/en-us/articles/25145299298573-How-to-Control-the-Stack-Quantity-Level-in-a-Container

• Follows from documented behaviour rather than stated outright

Correction: Passed on stacking fields sitting in one product record, the same reading scoring rejected for SeaRates (expressiveness-combine-stacking). Applied to both for consistency.

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.

Only single selection rules exist; 'Minimum overall cost + Largest first' runs two rules and keeps the better result, which is not an ordered or weighted combination.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: ordered objectives, weighted objectives, tolerance, multi-criteria. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Over half of all implementations involve customization to meet specific customer needs.”

https://support.magiclogic.com/hc/en-us/articles/33953562754445-Introduction-to-BlackBox

“FeatureCode=022;Locus;013; Configures feature-specific options.”

https://support.magiclogic.com/hc/en-us/articles/33171671730829-Understanding-the-BlackBox-Configuration-File

Extension is vendor-side: feature codes supplied by MagicLogic (e.g. Config4QTY, Stage2Stacks, 'FeatureCode=022;Locus;013;'), a Client Specific tab whose fields 'should be blank or unchecked, unless you have been advised otherwise by MagicLogic' (screenshot), and BlackBox rule-set customisation ('Over half of all implementations involve customization'). These fail as user capabilities per the definition note.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: script, plug-in, callback, custom rule, feature code, customization. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“The default behavior is to select the configuration with the better fit.”

https://support.magiclogic.com/hc/en-us/articles/28426447989901-Why-priority-on-product-configurations-is-not-working

“With this box checked, Cube-IQ will not allow a product to be loaded in a configuration with a lower priority if a configuration with a higher priority is possible.”

https://support.magiclogic.com/hc/en-us/articles/28426447989901-Why-priority-on-product-configurations-is-not-working

Group splitting also offers graded strictness (always / if it avoids a container / only when too large / never).

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.

“For every loaded block representing a specific product in a particular orientation, the Load Plan outlines exactly how it should be assembled and where it should be placed. This information is presented not only in precise coordinates but also visually”

https://support.magiclogic.com/hc/en-us/articles/36561083209741-Generate-Load-Plan-Report

The Maximum Block Length screenshot shows each block with 'Qty: 24 (48 of 72) (2 x 3 x 4)', block and product dimensions, and its position 'from back', 'from left', 'from floor'; orientation is implied by the placed product dimensions. BlackBox result schema is not public ('contact MagicLogic for examples').

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

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

“The Load Plan provides a comprehensive report detailing how to load each container within the current loading scenario. In essence, it serves as the complete set of loading instructions.”

https://support.magiclogic.com/hc/en-us/articles/36561083209741-Generate-Load-Plan-Report

“Use the Slider on the right side of the screen to view the load's step-by-step build.”

https://support.magiclogic.com/hc/en-us/articles/33723815682701-Load-Plan

Block size per step can be limited with 'Maximum block length in Load Plans'.

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.

“Load Overview Tab: Displays a summary of loaded containers.”

https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ

“In the Load Setup View, take note of the Loaded Weight of the container.”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

Per loaded container (screenshot): # Units/Items/Prds, loaded volume and %, loaded weight and %, gross weight, length used and %. Pallets are containers, so built pallets get the same figures; a pallet 'Stability Index' is shown in one example (calculation undocumented).

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

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

“Load Details Window: Displays weight distribution, load dimensions, and other key metrics.”

https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ

• Evidence is a label in a screenshot

The 'Length used' figure is visible in the Load Setup screenshot (e.g. 230.34 inch, 99.28%).

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

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

“Note the quantities in the Not Loaded column. They indicate that there are products which have been left out of the optimized load.”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

Per product-to-load line in Load Setup; an Options switch 'Add not-loaded units to Export' appears in a screenshot.

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

“Here is a list of some of the most common reasons for unloaded products:”

https://support.magiclogic.com/hc/en-us/articles/33477496510093-Troubleshooting-Unloaded-Products

The troubleshooting article gives a general list of common causes (containers, weight, value, matching code, fill limit, Q-value) for the user to check by hand, which the definition note says fails. BlackBox error messages concern input data only.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: reason per unplaced item, not loaded reason, diagnostics, error messages. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Show Center of Gravity in Load Plans”

https://support.magiclogic.com/hc/en-us/articles/33732217889549-Containers

Containers have 'Show Center of Gravity in Load Plans' (screenshot), which draws the CoG in diagrams; no numeric CoG output is documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: numeric centre of gravity, COG coordinates, COG offset output. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

“Automatically calculates axle weights for legal and safe loads”

https://magiclogic.com/products/cube-iq/

“Cube-IQ ensures all axle weights are accurately calculated, so loads are safe and legal.”

https://magiclogic.com/load-planning-cartonization-and-palletization-now-accessible-in-the-cloud/

No documented output field or report shows per-axle load figures; Load Details shows 'weight distribution percentages'.

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.

“Show weight distribution: Displays weight spread across the container (in supported reports).”

https://support.magiclogic.com/hc/en-us/articles/36927375139981-Customizing-Load-Plan-Reports-and-Diagrams-in-Cube-IQ

“Check the Load Details window to view weight distribution percentages.”

https://support.magiclogic.com/hc/en-us/articles/33947916783245-Loading-in-Cube-IQ

• Follows from documented behaviour rather than stated outright

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.

• Evidence is a label in a screenshot

Load Setup shows a 'Gross Weight' per loaded container (screenshot) with no definition; in the example it equals the loaded weight (102 lbs), so whether it includes tare is not shown. Tare weight is documented only for next-stage use.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: gross weight including tare, VGM, total weight with container. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Reports can recolour products by sequence number, sequence and group, or PO, which is display colouring, not a per-stop summary or view.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: per-stop summary, per-drop view, contents per stop. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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.

Load Edit allows drag-and-drop editing; a 'Validate' button appears on the Products ribbon (screenshot) and 'Load Edit cannot increase Load List quantities' in Options (screenshot), but no validation of an edited plan against item rules is documented. 'Diagnostics' checks input data.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: validate plan, rule violations, warnings after Load Edit, check manual edits. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

Counts when: Documented void or empty-space output.

Marketing mentions minimising void space; no void output is documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: void, empty space, dunnage, airbag, gap report. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.

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

Counts when: Documented plan cost output.

'Shipping cost' per container is an input to the 'Minimum overall cost' rule; no cost figure in the output is documented.

Where we looked

Full text of all 100 public en-us help-centre articles (Zendesk API articles.json?per_page=100, bodies converted to text), all 35 REST manual topics at downloads.magiclogic.com/Help/REST/, the magiclogic.com Cube-IQ, Cube-IQ Web, BlackBox, Developers, FAQ and home pages, and all 27 magiclogic.com blog posts (wp-json/wp/v2/posts); searched for: plan cost, shipping cost output, cost per item, cost allocation. Also reviewed the first-pass audit records and screenshots of the Products, Containers, Settings and Options tabs.