AWRA OpsHub Search

The Bill and the Sum of Its Parts

A freight bill is a fixed amount of money. However many containers the order arrives in, the goods have to carry that amount between them and no more. A system that allocates it once per delivery books an order that came in two parts at twice the freight that was paid. AWRA allocates across every receipt on the order, and a test holds the total to the bill.

Inventory Insights AWRA OpsHub Team 11 min read

Here is a claim so obvious it sounds like it needs no checking. You paid one freight bill. You spread it across the goods it brought. Add up what every unit is carrying and you get back the bill. Not approximately — exactly, because it is the same money looked at from the other end.

It is also a claim that is easy to get wrong and rarely checked. Take an order for a hundred units, one freight charge, delivered in two parts: sixty, then forty. A system that allocates the order’s costs to whichever delivery has just landed brings the goods out carrying double the freight that was paid.

Not a rounding difference. Exactly twice, because each delivery is given the whole bill.

Why this matters most on the islands

Because of where an error like this can hide, which is not where you would guess.

A distributor buying from a supplier an hour up the road pays freight that rounds to nothing against the value of the goods. Double it and the unit cost barely moves. The error is real, and it is invisible because it is small.

An importer in Port Louis, Victoria, Antananarivo or Moroni is in the opposite position. Sea freight, insurance, port handling and inland delivery are not a rounding item against the value of a container of goods — they are a large and well-understood share of what those goods end up costing, which is exactly why landed costing matters more here than in most places, and why anyone running an import business in these markets can quote the share from memory.

Double a rounding error and it stays a rounding error. Double a number that genuinely drives your unit cost and it does not look like a bug. It looks like a bad quarter.

That is the whole argument for putting this post here. The error is least visible precisely where it is largest, because where freight matters most, a unit cost that has come out high is the most ordinary thing in the world. You do not go looking for a defect. You go looking for a cheaper shipping line.

And the trigger is routine here, not exceptional

The error needs one condition: an order arriving in more than one delivery. On a short road route that is an exception worth a phone call. Where stock arrives by sea against a sailing schedule, an order split across two sailings — or arriving with a container short, the balance following a fortnight later — is not an exception at all. It is Tuesday. We have argued elsewhere that ordering to a sailing schedule breaks the assumption that a lead time is a single number; this is the same calendar breaking a different assumption, one module downstream.

So the population most exposed to the arithmetic is also the population where the triggering event is normal, and where the resulting number is least likely to be questioned. Three properties that individually mean nothing and together mean a defect can sit undisturbed for as long as you like.

What goes wrong, in English

Costs are attached to the order and allocated when goods arrive, which is how landed costing works in any system that does it properly. That allocation runs every time something is received, which is correct. The mistake is for it to look only at the delivery that has just landed and give that delivery the entire order's costs. Run it once, and one delivery holds the whole bill. Run it again when the balance arrives, and the second delivery holds the whole bill too. Nothing subtracts what has already been allocated, because nothing looks further back than the most recent arrival.

The figures on screen are individually plausible throughout. A consignment carrying a freight allocation is what you expect to see. Only a check that reconciles the total of those allocations back to the bill that was paid will find it, and that check is the one nobody runs.

One order, 100 units, one freight bill of 1,000 Allocated per delivery Allocated across receipts (AWRA)
Freight carried by the first delivery of 60 1,000 600
Freight carried by the second delivery of 40 1,000 400
Total carried by the goods 2,000 1,000
The bill that was actually paid 1,000 1,000
Landed unit cost inflated by the number of deliveries the same whether it came in one part or four

The right approach is obvious once the invariant is written down, and it is what AWRA does: allocate across every settled receipt on the order each time, in proportion to what each one actually holds, so the total is the bill by construction rather than by luck. The order costs the same whether it arrives in one delivery or four.

The lesson worth taking into any evaluation

This blind spot is rarely confined to one place. An over-receipt guard — the control stopping a supplier delivering more than you ordered — has the same shape: one that compares each receipt against the order rather than against everything received so far can be walked past by splitting the delivery. AWRA’s guard compares against everything received so far.

Where one control makes the assumption, the next service over often makes it too, because a fix tends to be applied to the place a bug was found rather than to the class of bug. That is a more useful thing to know about software than any individual defect.

So the question worth carrying into any evaluation is not "does your system handle partial deliveries", which every vendor answers yes to and every vendor believes. It is narrower and much harder to answer falsely: which of your controls compare a receipt against the order, and which compare it against everything received so far? Anywhere the answer is the first, splitting a delivery changes the outcome.

Costs attached to an order and allocated to the goods at arrival

Freight, duty, insurance, handling and inland transport become part of unit cost rather than a separate expense line.

Built in

Allocation that totals the bill across any number of deliveries

Recomputed across every settled receipt on the order as each one lands, in proportion to what it holds, and locked down by a test that reconciles the total back to the bill.

Built in

The allocation kept on the consignment

So what a specific arrival cost to land is recoverable afterwards rather than being folded away into an average.

Built in

Allocation by weight or volume

Not built. Costs are apportioned by value or by quantity only, so freight on heavy-but-cheap goods cannot be spread by mass.

Commission it
We can add

Re-costing stock that has already been sold

Not built. A late-arriving freight invoice moves the cost of what you still hold; it does not reach back into sales already posted.

Commission it
We can add

What we would build

Two, both about checking the number nobody checks

Allocation across deliveries is built and tested. These are the two things that make a costing error visible on screen, or make the allocation fit your freight.

A reconciliation view: costs charged against costs allocated

One screen per order showing what was billed, what has been allocated to goods so far, and the difference. On a fully received order the difference is zero and the screen is boring, which is the point — a number that should always be zero is the cheapest possible control.

Allocation by weight or volume

Sea freight is commonly charged by whichever of weight or measurement is greater, and neither is available to us as a basis today. Spreading a container's freight by the value of its contents subsidises the bulky, heavy, low-value goods at the expense of the small dense ones — which for an importer is not a rounding decision.

The first of those two is the one we would do first, and it is small. An error that can only survive where nothing adds two numbers together is not really a costing problem; it is a screen.

Talk to us about import costing

Four questions that find this class of defect in any system

Receive one order in two deliveries. Do the allocations add back up to the freight bill?

What a straight answer sounds like

Two numbers and their total, on screen, next to the bill.

Why it matters

This is the whole test. It takes ten minutes and almost nobody runs it.

Which of your receiving controls compare against the order, and which against everything received so far?

What a straight answer sounds like

A specific answer per control. Anything vaguer is a no.

Why it matters

Every control of the first kind can be walked past by splitting a delivery. This is the general form of the bug.

What happens to unit cost if the same order arrives in four parts instead of one?

What a straight answer sounds like

Nothing. It should be identical.

Why it matters

If the number moves, the allocation depends on delivery shape, and delivery shape is your supplier's decision rather than yours.

Show me a test that reconciles allocated cost back to the invoiced cost.

What a straight answer sounds like

A test, named. Or an admission that there is not one.

Why it matters

An untested invariant is an opinion. Ours is held by a test that reconciles the allocation to the bill.

Landed cost across deliveries — what ships today, and what we can add

What AWRA OpsHub does today

  • The total allocated equals the bill, across any number of partial deliveries, enforced by a test rather than by assumption.
  • Allocation in proportion to what each delivery actually holds, so the order costs the same however it is split up.
  • Costs attached at the order and applied at receipt, which is the point at which the goods and the charge are both known.
  • The allocation retained per consignment, so the landed cost of one arrival can be reconstructed later.

More we can add to your workspace

  • An allocation by weight or volume. Value and quantity are the two available bases, which is a poor fit for freight billed by measurement. Commission it
  • Re-costing of stock already sold, so an invoice arriving after the goods have moved corrects the future and not the past. Commission it
  • Cost types beyond the five that ship, so charges that do not fit those names are filed under whichever is closest. Commission it
  • A record of who was contractually liable for a cost, so a charge that was the seller's raises an objection when attached to your order. Commission it

Where we point you to a specialist

  • We are not going to tell you what share of your landed cost freight ought to be. You know your lane better than we do, and a vendor quoting an industry figure at an importer is telling you something about themselves.
  • We do not claim to know which other systems allocate per delivery. The test above is how you find out about any system, ours included.

The verdict

What is worth carrying away is the shape of this error: an invariant that everybody assumes, that nothing checks, in a number that is large enough to matter and ordinary enough never to be questioned. If you import into a small market where freight is a serious share of what your goods cost, you have systems making exactly this kind of assumption right now. The test is ten minutes long. Receive one order in two parts and add up what the goods are carrying.

Bring us a real consignment

One order, its freight and clearing charges, and the way it actually arrived — in parts, short, or a fortnight late. We will show you exactly what it costs to land in our system and where our allocation is still too blunt for your lane.

Talk to us about landed cost

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center