Stop Calling the Factory Quote Your Product Cost

How to Use This Tool

Allocate freight, insurance and duty across the shipment before setting a selling price. Calculate landed cost per imported unit from goods value, freight, insurance, duty and shipment quantity. Uses editable inputs and runs locally.

The failure Landed Cost per Unit is designed to catch

The denominator must be sellable units received, not units ordered, when damage or inspection rejects reduce usable inventory. The boundary is the job stated in Stop Calling the Factory Quote Your Product Cost; Landed Cost per Unit is not intended to score or transform a different workflow.

The Landed Cost per Unit input contract

The fields used for this specific operation are Goods value, Freight and insurance, Duty and import charges, Units received. Keep the source values beside the Landed Cost per Unit result, because replacing the original would remove the evidence needed to reproduce or reverse the operation.

• For Landed Cost per Unit, Goods value starts at 5000 in the worked case; replace that example with the matching source value.
• For Landed Cost per Unit, Freight and insurance starts at 1300 in the worked case; replace that example with the matching source value.
• For Landed Cost per Unit, Duty and import charges starts at 500 in the worked case; replace that example with the matching source value.
• For Landed Cost per Unit, Units received starts at 500 in the worked case; replace that example with the matching source value.

Worked result for Landed Cost per Unit

The executable case called Default decision scenario expects out: $13.60. Verify that observation before entering real material, and then change one Landed Cost per Unit field at a time so an unexpected direction or formatting change can be traced to a specific input.

Reading the Landed Cost per Unit output

It combines goods value, freight and insurance, duty and import charges and units received into one decision result using the formula explained on the page. Apply that answer only when Goods value, Freight and insurance, Duty and import charges, Units received describe the same scope and format as the worked operation. If the source uses different units, quoting, nesting, timing or account rules, a plausible-looking Landed Cost per Unit output is not sufficient validation.

Assumptions attached to Landed Cost per Unit

• Landed Cost per Unit assumes that all inputs describe the same unit or reporting period unless the field explicitly says otherwise.
• Landed Cost per Unit assumes that the model includes only the four visible inputs and does not infer hidden platform charges.

If one of these Landed Cost per Unit assumptions is false, keep the result as a diagnostic rather than production or decision data, and choose an implementation that explicitly supports the missing rule.

Evidence maintained for Landed Cost per Unit

The recorded reference is US SBA — marketing and sales. Reopen that source when the definition, format, fee or policy behind Landed Cost per Unit changes; private configuration and downstream acceptance still have to be checked in the user's own system.

Where Landed Cost per Unit runs

The named operation executes in browser JavaScript without an ecech calculation API. For Landed Cost per Unit, local execution reduces transmission but does not control browser extensions, device security or the destination where the result is pasted, so sensitive inputs still require the user's normal handling rules.