NetSuite records what a company pays its suppliers on every Purchase Order and Vendor Bill. The freight that brings those goods in is a separate bill from a separate vendor, and it often arrives weeks after the warehouse has received the product. When that bill is coded straight to freight expense, the cost never reaches the items it moved, and item margins run on purchase price alone.
Consider a cookware brand running NetSuite that imports from a manufacturer overseas. One container holds three Purchase Orders: cast-iron skillets, enameled Dutch ovens, and silicone utensils. The warehouse receives each order on a different day, and the ocean freight invoice arrives three weeks after the container. This post follows that container from the Item Receipt to the freight bill, and shows how NetSuite landed cost puts the freight on the items that caused it.
Inbound freight belongs on item cost because it is part of what the inventory cost to acquire. Booked as an expense, it understates inventory value and moves freight cost into the month the bill was entered instead of the month the items sell.
The cookware container shows why the distortion is uneven. A cast-iron skillet weighs many times more than a set of silicone utensils, so it absorbs far more of the container’s freight per dollar of product. At purchase price alone, the skillet looks more profitable than it is, and pricing starts from the wrong number.
Only inbound freight goes on item cost. Freight-in, from supplier to warehouse, becomes part of inventory value. Freight-out, from warehouse to customer, is a cost of delivering the sale: outbound shipping cost written back to the Item Fulfillment stays an expense and does not go through landed cost.
NetSuite landed cost allocates charges entered on the Landed Cost subtab of an Item Receipt or Vendor Bill across the items on that transaction, using one allocation method per transaction: weight, quantity, or value. The feature is turned on under Setup > Company > Setup Tasks > Enable Features, on the Items & Inventory subtab.
Four pieces have to be in place before the container lands:
|
Setting |
Role in landed cost |
What the cookware brand sets |
|
Cost category |
Names the charge and points to a holding expense account |
A Freight category with its own holding account |
|
Track Landed Cost |
Makes an item eligible for allocation |
Checked on every imported item |
|
Landed cost item |
Lets a bill with no inventory items carry landed cost |
A Freight item for the forwarder’s invoice |
|
Allocation method |
Splits the charge across eligible items |
Weight, which needs a weight on every item record |
The holding account works as a clearing account: the freight bill posts to it, and the allocation on the receipt clears it into inventory. Weight allocation stops with an error when an item has no weight, so weights belong on the item records before the first receipt, not after the first error. For the full setup, see BrokenRubik’s NetSuite landed cost setup guide.
When the freight bill arrives after the goods, the Item Receipt is edited and the bill is selected as the source of its landed cost. This flow assumes Advanced Receiving, where receipts are entered separately from bills.
The skillets were received with nothing on the Landed Cost subtab. Three weeks later the forwarder’s invoice arrives. Accounts payable enters it as a Vendor Bill with the Freight landed cost item, selects the Freight category on the line, and puts the container number in the memo, which shows in the list used to pick the bill later.
On the receipt, next to the Freight category, Source is set to Other Transaction, the Vendor Bill is selected, and the receipt is saved.
NetSuite applies the entire bill; it cannot apply part of one. A bill can be sourced to only one receipt, and once allocated it drops out of the list for other receipts. Oracle’s documented example for this flow also excludes standard cost items, so companies on standard costing should test the posting in a sandbox first.
That second rule is the problem for the cookware brand. Its freight invoice covers all three receipts, so sourcing it to the skillet receipt would put the whole container’s freight on the skillets.
One freight bill is split across several Item Receipts either by entering each receipt’s share manually or by recording the container as an Inbound Shipment and entering the freight there.
The manual path sets Source to Manual on each receipt’s Freight category and enters that receipt’s share. It works, but someone calculates the split outside NetSuite, and the bill is not linked to the receipts it paid for.
The second path models the container. With Inbound Shipment Management, the container is its own record, holding the lines from all three Purchase Orders. Its Landed Cost subtab takes a cost category, amount, currency, and allocation method, so the freight is entered once, on the shipment. For a brand receiving containers every week, it is usually the cleaner setup.
Yes. Estimated Landed Cost, part of the Supply Chain Management SuiteApp that Oracle sells through the account manager, applies landed cost estimates automatically as items are received on Purchase Orders, Item Receipts, or standalone Vendor Bills.
Estimates run on landed cost templates assigned to inventory and assembly items. A template holds several cost categories, each with its own allocation method and cost factor, so the cookware brand can estimate freight by weight and duty by value on the same items.
An estimate is only as good as its cost factor. A % Value factor is easy to maintain and usually wrong for heavy goods like cast iron. With the Weight method, the cost factor is a cost per unit of weight, so a quoted rate for the lane, from the forwarder or a TMS, gives a better number, and the audited carrier invoice is the figure to check the estimate against when the bill arrives.
A TMS fits at both ends of inbound freight: it tracks the inbound Purchase Order shipment before receipt, and it turns the audited carrier invoice into the Vendor Bill that landed cost sources.
FreightPOP creates Vendor Bills in NetSuite from approved carrier invoices, and its Vendor Bill field mapping can be extended to the fields NetSuite landed cost uses. When that bill carries the landed cost item and the Freight category, it appears in the receipt’s source list like any other freight bill, already checked against the quoted rate.
NetSuite landed cost needs custom work when a purchasing flow links records that the standard feature treats one at a time, such as a freight bill that has to follow its Purchase Order across several receipts and bills.
A Utah company needed shipping, duty, and tax applied as landed cost across Purchase Orders, Item Receipts, and Vendor Bills, with tax spread proportionally across each receipt’s lines, a separate freight bill tied to the same purchase flow, and the Vendor Bill as the source of truth. BrokenRubik built it on top of the native feature with scripts and custom fields, so an edit to a bill updates the related records without manual corrections.
No. Freight reaches item cost only when it is entered as landed cost on an Item Receipt or Vendor Bill, for items with Track Landed Cost checked. A freight line coded to an expense account stays an expense.
Not by sourcing. A bill sources to one receipt and is applied in full. Each receipt’s share can be entered manually, or the freight can be entered once on an Inbound Shipment.
Weight usually fits freight, provided every item record has a weight. Value fits duty and insurance. A transaction uses one method; Estimated Landed Cost templates let each category carry its own.
No. Landed Cost is a NetSuite feature enabled in Enable Features. The SuiteApp adds Estimated Landed Cost templates.
NetSuite already holds the purchase record: Purchase Orders, Item Receipts, Vendor Bills, and item costs. Landed cost adds the step that record cannot take alone, moving each freight bill onto the items it paid for, whether the bill arrives late, covers a whole container, or has not been issued yet.
BrokenRubik, a NetSuite-only engineering studio since 2017, contributed to this guide.