USE CASE / CONTAINER-LOADING

Container loading: respect container eligibility

Not every container may carry every item: a chilled pallet cannot go in a dry one, and volume alone cannot see that rule.

WHEN YOU NEED THIS

Any load plan where a subset of the container fleet is disqualified for reasons volume and weight cannot express - temperature control, hazard class, or a customer's own routing rule.

eligible_container_tags on an item and tags on a container are checked before geometry is: an item that shares no tag with any offered container is refused outright, never placed into one it should not reach.

SHOWN IN Python
from packvium import Container, Dimensions, Item, Packer, PackingConfig, explain_unpacked_item

items = [
    Item.create(
        "chilled-pallet", Dimensions.mm("1000", "800", "1000"), weight="300 kg",
        eligible_container_tags=("reefer",),
    ),
]
containers = [
    Container.create(
        "dry-van", Dimensions.mm("6000", "2400", "2600"),
        max_payload="5000 kg", tags=("ambient",),
    ),
]

result = Packer(PackingConfig.balanced()).pack(items=items, containers=containers)
print(result.status)
for unpacked in result.unpacked:
    print(unpacked.instance.item.id, explain_unpacked_item(unpacked))
WHAT COMES BACK

The dry van has more than enough room and payload for the pallet by every measurement - and the pallet is refused anyway, because the only container offered is tagged ambient and the pallet will only travel in one tagged reefer.

THE PACKED RESULT, IN 3D
121×121×100 · 19.7% used
slab × 4
WHAT A REFUSAL LOOKS LIKE HERE
container-loadingProven

No container passes its eligibility checks no_eligible_container

The pallet declares eligible_container_tags: ["reefer"], the dry van declares tags: ["ambient"], and the two share nothing. The request alone rules the placement out, however far the search gets, so the refusal is proven - in every engine since 1.7.0, when the JavaScript engine stopped calling it inferred.

WHAT CHANGES IN YOUR PROCESS
TODAY
  • Which goods may go in which container - reefer, hazard class, customer rule - is checked by a person after the plan is made.
  • A plan that breaks a rule is caught at the dock, and the load is rebuilt there.
  • Rules live in people's memory, so they differ between planners.
WITH PACKVIUM
  • Eligibility is part of the request: an item is only ever placed in a container it may travel in.
  • An item no container may take is named with a reason when the plan is made, not at the dock.
  • Every planner's request carries the same rules, so every plan follows them.
WHAT TO MEASURE
  • Loads rebuilt at the dock
  • Shipments held for a compliance problem
  • Time from order to approved load plan

Run a month of past orders through the same request and compare these numbers with what you actually shipped. That comparison, on your own data, is the only figure worth quoting.

WHY PACKVIUM

A container that has room is not the same question as a container that is allowed to carry the load. Keeping eligibility as declared data means the rule travels with the request, and a violation is refused before it ever reaches a yard.

Open this request
INSTALL
pip install packvium