The bottom line
Landed cost is the true cost of inventory: the purchase price plus every cost to get it onto your shelf — freight, customs duty, insurance, clearing and handling. If the ERP expenses those as period costs instead of allocating them to the stock, the inventory is undervalued and every margin, costing and pricing figure built on it is overstated. Correct landed costing allocates each of those costs across the receipt by a sensible basis (value, weight or volume, depending on the cost) so each unit carries its real cost. The complications are timing (the freight invoice often arrives after the goods) and allocation basis (duty by value, freight by weight). A spreadsheet cannot keep this accurate at volume; a proper ERP applies it at receipt and reconciles later invoices. Where it breaks: estimated costs need truing-up, and bad allocation is worse than none because it looks precise.
In This Article
The cost on the shelf is not the price on the PO
A purchase order records what you paid the supplier for the material. It does not record what it cost you to have that material sitting in your warehouse ready to use — and the gap can be 10-20% or more for imported goods. Freight, customs duty, insurance, clearing fees and handling all add to the real cost of the inventory, and where those land in your accounts decides whether your numbers are honest.
If the ERP books them as period expenses — freight to a freight account, duty to a duty account — the inventory sits on the books at the PO price, undervalued, and every downstream number inherits the error: product cost is too low, gross margin too high, pricing decisions based on a cost that is not the real one. Landed costing fixes this by allocating those costs onto the inventory itself, so each unit carries its true cost. It is unglamorous and it is foundational.
What goes into landed cost
Landed cost is the purchase price plus every cost incurred to get the goods to a usable state in your location. The usual components: inbound freight and shipping, customs duty and import taxes that are not recoverable, insurance in transit, clearing and brokerage fees, port and handling charges, and any inspection or certification cost required before the goods can be used. The principle is simple — if the cost was necessary to get this inventory onto your shelf, it belongs in the inventory value.
What does not belong is equally important: recoverable taxes (where you reclaim the input credit), general procurement overhead, and costs incurred after the goods are available for use. Getting the boundary right matters because over-inclusive landed costing inflates inventory and under-inclusive understates it — both distort margin. The list is usually stable per supplier and route, which is what makes it automatable once defined.
The allocation basis decides the per-unit cost
A landed cost on a shipment has to be spread across the items in that shipment, and the basis matters because different costs behave differently. Customs duty is typically a percentage of value, so it allocates by value. Freight is usually driven by weight or volume, so allocating a container's freight by value would overcharge the expensive-but-light items and undercharge the cheap-but-heavy ones. Handling may be per-line or per-unit. Using one blanket basis for every cost type produces per-unit costs that are precisely wrong.
A proper landed-cost calculation lets each cost type use its appropriate basis — duty by value, freight by weight or volume, handling by line — so each unit's share reflects what it actually drove. For a mixed shipment of heavy low-value and light high-value items, the difference between value-based and weight-based freight allocation can materially change the costed margin of each product. The allocation basis is not a technicality; it is the accuracy of the per-unit cost.
Allocate each cost by what drives it: duty by value, freight by weight or volume, handling by line. A single blanket allocation basis gives you per-unit costs that look exact and are wrong — which is worse than a rough estimate you know is rough.
The timing problem: costs arrive after the goods
The practical headache is that the additional costs rarely arrive with the goods. The material is received and needs a cost now, but the freight invoice comes a week later, the duty is assessed at clearance, and the clearing agent bills at month-end. If the ERP waits for every actual cost before valuing the receipt, inventory sits uncosted; if it ignores them, inventory is undervalued.
The workable pattern is to apply estimated landed costs at receipt — based on the known rates for that supplier and route — so the inventory carries a realistic cost immediately, then true up to actuals when the real invoices arrive, posting the variance. This keeps inventory valued in real time while staying accurate once costs settle. Doing this by hand across many receipts is where spreadsheets collapse; it is exactly the kind of estimate-then-reconcile process an ERP is built to run.
Why this belongs in the ERP, not a spreadsheet
Landed costing touches inventory valuation, product costing, margin reporting and the general ledger simultaneously, and it has to stay consistent across all of them at the volume of receipts a manufacturer processes. A spreadsheet can compute a landed cost for one shipment; it cannot keep the inventory sub-ledger, the costing and the GL reconciled across hundreds of receipts a month with estimate-and-true-up variances flowing through correctly.
An ERP that handles landed cost applies the allocation at receipt, carries the costed value into inventory and product costing, posts the accounting, and reconciles the later actual invoices with the variance tracked — all as one consistent flow. That is the difference between a landed cost that is a periodic manual exercise (and therefore usually skipped under pressure) and one that is simply how every receipt is valued. For a manufacturer importing materials, it is a core ERP capability, not an add-on.
Where this breaks
Estimates that are never trued up are their own trap: if the ERP applies an estimated landed cost at receipt and the actuals are never reconciled, the inventory carries a plausible-looking wrong cost indefinitely, and the variance quietly accumulates. The estimate-then-true-up discipline has to actually close the loop, or it is just a different way of being wrong.
Bad allocation is worse than none because it carries false confidence — a blanket allocation basis produces per-unit costs that look rigorous and mislead pricing and margin decisions, whereas an acknowledged rough estimate at least invites scepticism. And landed costing cannot fix upstream data gaps: if freight and duty are not captured against the receipt at all, or supplier and route rates are unknown, the calculation has nothing to allocate. The prerequisite is capturing the additional costs against the receipt in the first place.
What to do first
Define the cost components and bases, then let the ERP apply them consistently.
- List the landed-cost components that apply to your inbound goods (freight, duty, insurance, clearing, handling) and exclude recoverable taxes and post-receipt costs
- Set the allocation basis per cost type — duty by value, freight by weight or volume, handling by line — rather than one blanket basis
- Apply estimated landed cost at receipt from known supplier/route rates so inventory is valued immediately
- True up to actual invoices when they arrive and post the variance — close the loop, do not leave estimates standing
- Confirm the costed value flows consistently into inventory valuation, product costing and the GL, rather than living in a spreadsheet
If freight and duty are hitting expense accounts instead of your inventory value, your margins look better than they are. Book 30 minutes with Amit on landed costing in a manufacturing ERP — components, allocation and the estimate-and-true-up that keeps it accurate. No slides, no pitch deck, no obligation to proceed.
Free Assessment
Where does your operation sit on the data maturity curve?
8 questions. 3 minutes. You get a scored breakdown across data infrastructure, analytics readiness, and automation potential — with a specific next step for your industry.