Run the numbers
Three calculations, yours to argue with.
Everything else on this site is a screenshot or a claim. This page is neither: these are the three pieces of arithmetic the product exists to do, running live in your browser. Change any figure and the answer moves — including, on the second one, which supplier wins.
Same formulas, loaded with the worked example
Each calculator starts on the numbers from the nineteen-step worked example, so its first answer is the one the screenshots show. The formulas are the app’s own, written out under each result. Nothing is sent anywhere: the arithmetic runs on your machine, and the page keeps nothing.
One · the signal
Does this part have to be ordered today?
A part is in trouble when what is left on the shelf runs out before a replacement could arrive. That is the whole of it — the cockpit’s verdict on every one of a hundred and twenty-one parts is this sum, applied consistently.
The rule, exactly as the app applies it: cover below the lead time is order now; cover below the lead time plus one month is order next month; anything else is on track. The reorder point is usage × (lead time + safety stock) — the level at which ordering can no longer wait. See it on the cockpit →
Two · the comparison
Which of these quotations is actually the cheapest?
Three real offers for the same four busbar lines — 7,200 pieces — in two currencies, into two ports. The quoted column is what each supplier asked for. The landed column is what the goods cost standing in the factory. They do not agree, and the gap is not small.
Landed = quoted × rate × (1 + duty + freight & clearance). The duty and the uplift are the ones the example dataset carries; drop Aolin’s freight to Halden’s and watch the ranking change back — which is the argument for pricing a quotation properly rather than for distrusting any one supplier. The full comparison screen →
Three · the claim
What is a late shipment worth?
Nearly every supply contract has a liquidated damages clause, and nearly every team tracks it by hand, late, or not at all. It is not hard arithmetic. It is four numbers that usually live in four different places.
In the app this is entered once as a clause and then computes itself per part, per schedule reference, in the purchase order’s own currency — and prints as a statement addressed to the supplier. The penalty screen and the statement →
Three sums here. A hundred and twenty-one parts there.
None of this is difficult arithmetic, which is exactly the point: it is not the sums that go wrong, it is doing them for every part, every week, from four spreadsheets, and still being able to say six months later why the order was placed.