USE CASE / CARTONIZATION

Cartonization: pick the right box for a mixed order

An order has several item types and candidate box sizes - you need a yes-or-no per box, not a volume total that misses a rotation that will not fit.

WHEN YOU NEED THIS

Any time a system decides which physical box a set of items goes into before it commits to a rate, a label or a truck: an order-management system, a WMS pick-and-pack step, or a quoting tool.

Every item and container is real geometry - exact dimensions, not a volume total - so the search finds an actual arrangement or names the one item that has nowhere to go. Nothing here is estimated after the fact.

SHOWN IN Node / JavaScript
import { pack } from '@packvium/engine';

const request = {
  items: [
    { id: 'mug', quantity: 6, weight: '350 g',
      dimensions: { length: '110', width: '110', height: '95' } },
    { id: 'tin', quantity: 8, weight: '500 g',
      dimensions: { length: '90', width: '90', height: '120' } },
    // Too long for the box in every orientation.
    { id: 'floor-lamp', quantity: 1, weight: '4 kg',
      dimensions: { length: '1500', width: '250', height: '250' } },
  ],
  containers: [
    { id: 'box', cost_minor: 210, max_payload: '20 kg',
      inner_dimensions: { length: '450', width: '350', height: '350' } },
  ],
};

const result = pack(request);
console.log(result.status, result.containers.length, 'container(s) opened');
WHAT COMES BACK

One container opens and both mug and tin fully place inside it. The floor lamp does not: it comes back among the unpacked items with no_compatible_container_dimensions, proven - the box is simply too short for it in any rotation, which is a different fact from 'the box is full'.

THE PACKED RESULT, IN 3D
200×200×200 · 100.0% used
cube × 8
WHAT A REFUSAL LOOKS LIKE HERE
cartonizationProven

Too large for every container on offer no_compatible_container_dimensions

The floor lamp is 1500 mm long and every offered container's longest inner edge is 450 mm. There is no orientation that changes that, so the search never even reaches a placement attempt for it.

WHAT CHANGES IN YOUR PROCESS
TODAY
  • A packer picks a box by eye and finds out it is too small once the items are in it.
  • An item that fits no box is discovered at the bench, after the order was promised.
  • Box choice differs from shift to shift, so packaging cost per order cannot be planned.
WITH PACKVIUM
  • The system names the box before the order reaches the bench, from the items' real dimensions.
  • An item that fits no box is flagged with a reason when the order is created, not when it is packed.
  • The same order always gets the same box, so cost per order becomes a number you can plan with.
WHAT TO MEASURE
  • Repacks per hundred orders
  • Orders that needed a box size not in stock
  • Packaging cost per order

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

Cartonization only pays off if a 'does it fit' answer is one you can trust without opening a tape measure yourself. Exact integer geometry and a named reason for the one item that doesn't fit are what make that trust possible.

Open this request
INSTALL
npm install @packvium/engine