USE CASE / WEIGHT-BALANCING

Weight balancing: keep axle loads inside their limit

A vehicle can have enough total payload and still exceed a declared axle limit, because one axle alone carries more than its own limit.

WHEN YOU NEED THIS

Loading any two-axle vehicle where axle compliance is checked at the roadside independently of gross weight - most road freight, in most jurisdictions.

Declaring both axles' positions and limits on the container turns axle compliance into a constraint the search enforces while placing items, not a spreadsheet check run on the result afterwards.

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

const request = {
  items: [
    { id: 'heavy', quantity: 1, weight: '650 kg',
      dimensions: { length: '200', width: '200', height: '200' } },
    { id: 'light', quantity: 1, weight: '5 kg',
      dimensions: { length: '200', width: '200', height: '200' } },
  ],
  containers: [
    {
      id: 'trailer', cost_minor: 100, max_payload: '2000 kg',
      inner_dimensions: { length: '2000', width: '200', height: '200' },
      axles: [
        { position: '400', max_load: '300 kg' },
        { position: '1600', max_load: '300 kg' },
      ],
    },
  ],
};

const result = pack(request);
console.log(result.status);
for (const unpacked of result.unpacked_items) console.log(unpacked.item_id, unpacked.reason);
console.log(result.containers[0]?.axle_reactions);
WHAT COMES BACK

The light item places; the 650 kg item cannot, at any position. Wherever it stands, the two axles share its whole weight, and two 300 kg limits add up to 600 kg - so one axle is always over, inside a trailer with 2000 kg of payload and most of its floor still empty. The refusal is about axle loads, not about running out of room.

THE PACKED RESULT, IN 3D
100×10×10 · 10.0% used
payload × 1
WHAT A REFUSAL LOOKS LIKE HERE
weight-balancingInferred

Would overload an axle wherever it stands axle_overloaded

No position keeps both axle reactions inside their declared 300 kg limits: together they must carry the item's whole 650 kg, more than the 600 kg they are rated for. From 1.6.0 every engine names that limit, axle_overloaded, instead of reporting only that the search ran out of arrangements.

WHAT CHANGES IN YOUR PROCESS
TODAY
  • A load within the vehicle's total payload is assumed legal, and the axle loads are never computed.
  • An overloaded axle is found at a roadside check, with a fine and a vehicle that cannot continue.
  • Heavy goods are placed wherever they fit, which is often over one axle.
WITH PACKVIUM
  • Every placement is checked against both axles' limits while the load is planned.
  • A load that would overload an axle is never produced; the item that cannot go is named instead.
  • The planner sees what each axle carries before the vehicle leaves.
WHAT TO MEASURE
  • Axle-overload findings at roadside checks
  • Loads rearranged after a weighbridge reading
  • Items left for a second vehicle, and why

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

Total payload capacity is the wrong question for a two-axle vehicle. Packvium checks the axle reactions the load actually produces, at the position it actually settles, against the limits declared on the container - not a rule bolted on after the placements are already fixed.

Open this request
INSTALL
npm install @packvium/engine