Landed cost locked when the PO is raised, not when the bill arrives
Freight, duty, surcharges, and accessorials applied against the NetSuite purchase order at creation, while the buying decision can still change.
NetSuite can hold landed cost. The problem is almost never the field, it is the timing. Most teams populate it after the fact, from the vendor bill, which means the number is correct in the ledger and useless for the decision. Freightgate's NetSuite TMS integration applies the real cost components at PO creation, so the margin you see when you approve the order is the margin you get.
A landed cost that arrives with the invoice is a report, not a decision.
The purchase order is approved on an estimated freight number. Six weeks later the vendor bill lands with the actual 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.
None of that was available at the moment it mattered, which was when somebody decided to buy 2,000 units from that supplier on that lane instead of a different supplier on a different one.
Every cost component, applied at creation.
Freight from the contract, not an estimate
The contracted rate for that lane and mode is applied against the PO automatically, so the freight line is the real freight line.
Duty and tariff modeled on the item
Duty and tariff exposure is calculated against the item and its classification rather than added as a flat percentage after the fact.
Surcharges and accessorials included
Fuel, chassis, demurrage exposure, and accessorial charges are applied as part of the cost at creation, which is where most landed-cost variance actually comes from.
Variance held before it is paid
When the carrier invoice arrives, it is matched against the applied rate before the vendor bill is approved, so a variance is caught at the door rather than paid and chased.
From PO to reconciled bill.
PO created
Item, supplier, origin, and destination read from the NetSuite record.
Cost components assembled
Contract freight, duty, surcharges, and accessorials applied.
Landed cost written to the order
Visible while the buying decision is still open.
Shipment executes
Actual events and charges captured against the same record. For an ocean move, that includes the contracted ocean rate and the sailing it was booked against.
Invoice pre-audited
Carrier invoice matched to the applied rate before the vendor bill posts.
“The seamless integration into NetSuite makes compliance a no-brainer.” Ascensia
What NetSuite teams ask first.
Does NetSuite have landed cost natively?
NetSuite supports landed cost as a concept and a field. What it does not do on its own is source the real freight, duty, and surcharge values at the moment the purchase order is created. That is the gap Freightgate fills.
When is landed cost applied?
At purchase order creation, while the buying decision can still change, rather than when the vendor bill arrives.
What cost components are included?
Contracted freight, duty and tariff, fuel and other surcharges, and accessorial charges.
How are duties and tariffs calculated?
Against the item and its classification on the NetSuite record, rather than applied as a flat uplift.
What happens when the carrier invoice does not match?
The invoice is matched to the applied contract rate before the vendor bill is approved, so the variance is held for review rather than paid and recovered later.
Does this work for inbound freight on purchase orders?
Yes. Inbound PO freight is the primary use case for this module.
Do we need to change how we use NetSuite?
No. The costs are applied against the purchase order, item, and vendor bill records your team already works in.
Is this a validated SuiteApp?
Yes. Freightgate is a Built for NetSuite validated hybrid SuiteApp.
Pairs well with
Run it against one of your own POs.
Bring one purchase order and one lane. We will show you the landed cost assembled at creation and the invoice matched back to it.