Module

Container Stuffing

How many boxes, which kind, and what goes where — with the arithmetic beside every count.

Running in production₹15,000 / month
See pricing

What it produces

  • Containers needed per type — 20', 40', high cube, reefer, open top, flat rack, ISO tank, flexitank
  • Pallets and packages per container, by line, with a top-view floor plan
  • Gross weight, cube and payload utilisation per container, and which constraint bound it
  • Packages per pallet worked from carton and pallet dimensions, or taken as the planner stated
  • Lines that could not be planned, named with what is missing

A worked example

SO-2041 — 11 pallets, 704 cartons, 1 × 20' standard dry
400 × 300 × 250 mm cartons on 1,200 × 800 pallets: 8 per layer × 8 layers = 64 per pallet
floor 5,878 × 2,332 mm: 7 in a 1,200 mm strip + 4 in the remaining 1,132 mm = 11 positions
11 × 1,625 kg = 17,875 kg of 28,180 kg payload → the floor binds, not the weight
40HC would take the same 11 pallets with 30% of its cube empty — 20GP suggested

Illustrative figures. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

Every freight forwarder's card says eleven Euro pallets fit a twenty-foot box. What it does not say is whether your cartons make eleven pallets, whether the twelfth is the floor's fault or the payload's, or what a forty-foot high cube would leave empty. This plans it from how each material is actually packed, draws the floor, names the constraint that bound the box, and refuses a line it cannot plan rather than guessing.

Opened by the logistics manager, the planner and the supply chain manager — what each of them sees first.

Said before you ask

What is not finished.

The engine is built and tested. It plans at the level a forklift loads at — pallet footprints on a floor, one carton size floor-loaded in layers, litres in a tank — and refuses mixed loose cartons of different sizes by name rather than pretending to solve three-dimensional packing. It needs one table most ERPs do not carry: how each material is packed, which imports through the material_packaging template. Until that carries rows every line reports NO_PACKAGING rather than a plan around a guessed carton. The container catalogue is typical published figures and says so; a tenant's own carrier sheet and road payload limit import through container_types and take precedence. No customer has yet planned a real consignment with it.

Where this sits

One of 18 modules, on one engine.

Container Stuffing reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 17 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.