Skip to main content

Cartonization: why a unit is not placed

What this shows. The checks the solver makes, in order, when a unit goes into no box, and what the order screen shows for each reason.

Check 0 runs before any packing. Checks 1 to 4 run only after the solver found no place, in the order drawn. "Nothing fits" is the default answer, so it comes last.

What you see and what fixes it​

Reason on the Exceptions tabHint on the screenWhat to change
No dimensionsfix on the pack cardLength, width and height of the pack item.
No weightfix on the pack cardWeight of the pack item, or set every carton's max gross weight to 0.
No candidate cartonsfix in the policyAdd or activate a carton row.
Splitting not allowedfix in the policySet Pick splitting to Allow.
Overweightfix in the policyRaise the max gross weight of a carton, or correct a wrong pack item weight.
Nothing fitsfix in the policyAdd a bigger carton. A max-units limit that blocks the unit is also reported as "Nothing fits".

The action on every row is always "Stop this line". The six "Exception handling" drop-downs on the policy are read and then ignored. Save refuses Ship as is.

To recover, fix the data, then reserve or release the order again. The plan input holds sizes, weights, rotation rule and the whole policy. If any of them changed, the plan is recalculated. If nothing changed, the old result stays.

Where it comes from​

ClaimSource
Missing size is tested before packingcrates/libs/wms-outbound/src/cartonization/pack.rs:295
Order of the other reasonscrates/libs/wms-outbound/src/cartonization/pack.rs:574
No active cartoncrates/libs/wms-outbound/src/cartonization/pack.rs:582
Splitting preventedcrates/libs/wms-outbound/src/cartonization/pack.rs:613
No weight or overweightcrates/libs/wms-outbound/src/cartonization/pack.rs:623
Default answercrates/libs/wms-outbound/src/cartonization/pack.rs:629
Unit-count limit is not a weight reasoncrates/libs/wms-outbound/src/cartonization/pack.rs:714
Action is always Stopcrates/libs/wms-outbound/src/cartonization/write.rs:556
Plan status with unplaced unitscrates/libs/wms-outbound/src/cartonization/write.rs:142
Pick with no placement is Blockedcrates/libs/wms-outbound/src/cartonization/write.rs:619
Reason and fix hint on the tabcrates/services/web-ui-server/src/extensions/customization/shipment_order/cell_renderers.rs:82
Screen wordscrates/libs/wms-lib-sql/sql/wms-meta-ui/migrations/015_the_order_screen_shows_the_cartonization.sql:93
Blocked picks get no taskcrates/libs/wms-outbound/src/cartonization/handoff.rs:65
Save refuses ShipAsIs on the six drop-downscrates/libs/wms-lib-core/src/model/policies/cartonization_aggregate.rs:167
Changed input gives a new plancrates/libs/wms-outbound/src/cartonization/ensure.rs:194