Landed Cost Items

Group: Inventory

A landed cost item decides which vendor bill charges, such as freight, duty, insurance, and handling, can be added to the value of received stock (capitalized), and how each charge is spread over the receipt lines.

A landed cost item is a setting, not a line of a landed cost or an item in your stock. It decides which vendor bill charges count as landed costs and how they are handled. You set it up once, not for each shipment. To stop a landed cost item from matching vendor bill lines, set its active to false or delete it.

Each landed cost item says:

Which vendor bill lines it covers: lines whose item matches its itemId, such as a freight service item, or whose general ledger account matches its accountId, such as a freight expense account.
How to spread (allocate) the charges over the receipt lines, in allocationMode.
Which costing element type the inventory revaluations get when a landed cost is committed, in costingElementTypeId.

allocationMode can be:

'Equal': evenly per line.
'Quantity': by the quantity received.
'LineTotal': by what the goods cost.
'Weight': by weight. Every selected receipt line's item needs a gross weight, weight, or net weight. When an item has more than one, the gross weight is used, then the weight, then the net weight.
'Volume': by volume. Every selected receipt line's item needs a volume per unit, or every one needs a length, width, and height.

Creating or updating a landed cost fails when a selected receipt line's item is missing what its allocation mode needs. A value of zero or less counts as missing. 'Volume' uses one kind of volume for all the items: either every item has a volume per unit, or every item has a length, width, and height. For example, the request fails when one item records only a volume per unit and another records only its length, width, and height. Before the charge is spread, weights and volumes are converted to one unit. Each item's weight is converted to kilograms with its weightUnit, and each volume per unit to cubic metres with its volumeUnit. So an item weighed in pounds and an item weighed in kilograms are compared by their real weight. If an item's weightUnit is empty, its weight is read as kilograms. If its volumeUnit is empty, its volume per unit is read as cubic metres. Length, width, and height have no unit field, so they are multiplied as recorded. Record them in the same unit, such as centimetres, on every item, or the charge is spread incorrectly. See weightUnit and volumeUnit on GET inventory/items/:id (getItem).

For example, a landed cost item for freight covers the freight expense account and spreads by 'Weight'. When a freight bill is approved, its line appears on GET inventory/landed-costs/vendor-bill-lines with 'Weight' as its allocationMode. You add the line to a landed cost. When you commit the landed cost, its inventory revaluation gets the freight costing element type.

A charge sent to POST inventory/landed-costs without allocationMode does not use the mode set here. It uses the item's own default allocation mode, or 'Equal'.

Endpoints

List landed cost items: GET /inventory/landed-cost-items
Create a landed cost item: POST /inventory/landed-cost-items
Bulk create landed cost items: POST /inventory/landed-cost-items/bulk
Bulk delete landed cost items: POST /inventory/landed-cost-items/bulk-delete
Search landed cost items: POST /inventory/landed-cost-items/search
Retrieve a landed cost item: GET /inventory/landed-cost-items/{id}
Update a landed cost item: PATCH /inventory/landed-cost-items/{id}
Delete a landed cost item: DELETE /inventory/landed-cost-items/{id}