How the engine decides, written from the code that decides it.
Three explanations of the parts people ask about before they trust a plan: what the stability number measures, how an arrangement is chosen, and what an export does and does not authorize. Every constant on these pages is imported from the file that uses it, so none of them can go stale while the engine moves.
How pallet load stability is calculated
The stability model in full: support measured against real contact surfaces, a centre-of-mass score, the 0.6/0.4 weighting, and what it cannot see.
Mixed-SKU palletizing: three packers, one rule
Shelf first-fit-decreasing, maximal-rectangles and interlocking pattern search — what each is good at, and the stated rule that picks your plan.
Export a pallet plan to a UR robot
What the URScript pose list contains, how the rotation vector is derived, why the exporter refuses an unverified plan, and why it authorizes nothing.
Reading how it decides is one thing; watching it decide on your own SKUs is another.
The engine is Apache-2.0 and unmetered on your own machines — what the hosted plans add is a signature only this service can make, state it keeps for you, and compute on its hardware.
Everything here is Apache-2.0 and checkable: where every figure on this site comes from, what is built and what is not, and what is still wrong with it.