The Landed Cost module in Dynamics 365 SCM

For companies importing goods internationally, the purchase price is only part of the cost. Freight, insurance, duties, brokerage, port charges, and inland transportation add 10–30% to the unit cost — and that "landed cost" is what should appear on the inventory valuation, not just the supplier invoice. The Landed Cost module in Dynamics 365 SCM models this end-to-end.

Why a separate module. The classic F&O Misc Charges mechanism lets you add charges to a purchase order, but it doesn't model:

• Multiple shipments converging into one voyage.
• Charges incurred against a container, not a single PO.
• Cost allocation across many POs and many lines.
• Cost-as-of dates differing from invoice posting dates.

Landed Cost adds voyages, containers, and cost types as first-class entities that aggregate across purchase orders.

Core entities.

• Voyage — a vessel's trip from origin to destination, with a departure and arrival date.
• Container — a shipping container within a voyage, holding cargo.
• Folio — a grouping of charges (often per shipment).
• Cost type — a category of charge (sea freight, insurance, duty, broker fee).
• Cost allocation method — how a charge is distributed (by weight, volume, value, quantity, equal split).

Workflow.

1. Purchase orders are created normally.
2. A shipping container is created and PO lines assigned to it; the system computes total weight, volume, value per container.
3. The container is added to a voyage.
4. Estimated charges are recorded against the voyage or container (sea freight estimate, broker estimate, duty estimate). These flow into estimated landed cost on each PO line.
5. When the goods arrive, the receipt posts at estimated landed cost.
6. Actual invoices arrive over weeks (freight, duty, broker). Each is recorded against the voyage or container as actual charges.
7. Cost adjustment routines reconcile actuals vs estimates and post the variance.

Allocation methods. For each charge, choose:

• By weight — heavy items absorb more.
• By volume — voluminous items absorb more.
• By value — high-value items absorb more.
• By quantity — flat per unit.
• By equal share — flat per PO line.

The right method per charge type matters: freight is usually weight or volume; insurance is usually value; duty is per-line per-tariff. A landed cost setup that uses one method for everything is naive.

Estimated vs actual. Estimates flow into inventory cost immediately at receipt — without estimates, inventory is valued at supplier price only. When actuals arrive:

• Variance = actual - estimate per cost type.
• Adjustment routine processes the variance into existing inventory and COGS for already-sold items.
• Variance accounts capture systematic over- or under-estimation patterns.

Duty and customs. Country-specific tariff codes and duty rates drive duty calculation. Landed Cost can compute duty per line based on Harmonised System (HS) codes and country of origin, integrating with customs declaration data. For complex customs, partner extensions (Avalara, Vertex landed cost) layer on top.

Multi-currency. Cost types are typically denominated in different currencies — sea freight in USD, broker fees in local. The module handles per-currency conversion at the appropriate rate (charge date, receipt date, or invoice date — configurable).

Reporting.

• Voyage cost analysis — total landed cost per voyage, broken down by cost type.
• Container utilisation — value vs capacity.
• Variance by cost type and supplier — where estimates routinely miss.

This reporting is where landed cost yields ROI — identifying which trade lanes, which freight forwarders, which products consume more cost than expected.

Integration with inventory cost. Landed Cost integrates with the F&O cost engine:

• Inventory close runs respect landed cost adjustments.
• FIFO/Weighted Average calculations use the landed cost, not just supplier price.
• COGS at the moment of sale reflects the most current landed cost calculation.

Common pitfalls.

• Estimates too optimistic. Persistent under-estimation; variances always negative; finance distrusts the module.
• Allocation method mismatch. All charges allocated by value; freight on a low-value bulky item is wrong.
• Cost type proliferation. Dozens of cost types where five would do; reconciliation becomes painful.
• Late actuals. Invoices arriving months later; inventory has already been sold; adjustments hit COGS unexpectedly.
• Integration with broker spreadsheets. Broker provides duty in Excel; manual re-keying introduces errors. Build an import process.

Operational rhythm. A monthly landed cost close: confirm all voyages with departures in the month are estimated; reconcile any actuals received; post adjustments. A quarterly variance review identifies systematic estimation issues.

When to use it. If imports are >5% of cost and >20% of inventory by value, Landed Cost pays back. For occasional imports, the simpler Misc Charges approach is sufficient.