Landed Cost in NetSuite: The Field Is Fine, the Timing Is the Problem
October 13, 2026
Ask a NetSuite finance team whether the system supports landed cost and the answer is yes. Ask when the landed cost on a purchase order becomes accurate and the answer is usually "when the vendor bill arrives." That gap, between the moment the PO is approved and the moment its real cost is known, is where margin assumptions quietly fail.
This is not a NetSuite limitation. It is a sourcing problem. The field exists. What does not exist, on its own, is a way to populate it with the real freight, duty, and surcharge values at the moment the order is created. That is the job of landed cost automation in NetSuite.
What happens today
A buyer raises a PO for 2,000 units from a supplier overseas. The freight line is an estimate from the last similar order. The PO is approved on that number. Six weeks later the vendor bill lands with the contracted ocean rate, a fuel surcharge, a chassis fee, and a duty line nobody modeled. The landed cost field gets updated, the item cost is restated, and the margin report for that period moves.
Everything in that sequence is correct in the ledger. None of it was available when the decision was made: which supplier, which lane, which quantity. The number that mattered arrived after the choice it should have informed.
The four components that cause the variance
Landed cost variance rarely comes from one line. It accumulates across four components, and the ones that get missed are usually the smaller ones.
- Freight. The contracted rate for that lane and mode, not an estimate from a previous order.
- Duty and tariff. Calculated against the item and its classification rather than added as a flat percentage after the fact.
- Surcharges. Fuel, congestion, and similar charges that move with the market and the carrier.
- Accessorials. Chassis, demurrage exposure, and the other charges that appear on the invoice and nowhere else.
The last two are where most landed-cost variance actually comes from, and they are the two that an estimate never includes.
What changes when the cost is applied at creation
With Freightgate's SuiteApp, the four components are assembled against the purchase order when it is raised. The contracted freight rate for the lane is applied automatically. Duty is modeled on the item. Surcharges and accessorials are included as part of the cost. The landed cost is written to the order while the buying decision is still open.
The buyer approving the PO sees the margin they will actually get. Finance sees an item cost that will not be restated when the bill arrives. And when the carrier invoice does arrive, it is matched against the rate that was applied before the vendor bill is approved, so a variance is held for review rather than paid and chased.
Why timing beats accuracy after the fact
A landed cost that is perfectly accurate on the vendor bill is a report. It tells you what the order cost. A landed cost that is accurate on the purchase order is a decision input. It tells you what the order will cost, while you can still change it. Both are correct. Only one is useful at the moment someone is choosing between suppliers on different lanes.
The mechanism, the FAQ, and what the invoice match looks like are on the NetSuite landed cost automation page. For how it fits with rates, compliance, and tracking on the same record, see the NetSuite TMS integration overview.