Knowing Your True Landed Cost Before Setting Wholesale Prices

Versa Cloud ERP - Blog Knowing Your True Landed Cost Before Setting Wholesale Prices  %Post Title,

The Pricing Decision That Happens Before the Bill Arrives

A product manager at a wholesale importing distributor is reviewing prices for an upcoming season. The purchase orders are placed, the goods are on the water, and the sales team needs confirmed wholesale prices now. The inventory system shows an average cost, but that figure does not separate the current freight rate, the exchange rate applied to the purchase, or the duty and tariff components for this origin. The product manager knows those factors have moved since the last season. What she does not know is by how much, or whether the margin she is quoting still holds.

This is not a crisis. It is a routine gap that importing distributors manage every season, and it is worth examining carefully when evaluating a new ERP.

Why Inventory Cost Alone Is Not Enough

For a distributor sourcing from overseas, the cost of a product is not a single number. It is the sum of the supplier price, the applicable duty rate, any tariff component, freight from origin to warehouse, broker fees, and the exchange rate in effect at the time of purchase. Each of those components can move independently. Freight rates shift with carrier capacity. Exchange rates move with currency markets. Duty and tariff rates can change with trade policy.

When an ERP records only the purchase price as inventory cost, the finance and purchasing teams are left to reconcile the remaining components manually, once the bills have arrived. That reconciliation is necessary for accurate books, but it happens too late to inform the pricing conversation. The product manager quoting wholesale prices is working from an incomplete picture, and the gap between what she assumes and what the product actually cost may not surface until the margin report is run weeks later.

For pick-and-pack lines, where goods flow through without sitting in stock, there may be no ongoing average cost at all. The only cost reference is whatever was estimated at the time of the last order, which may not reflect current conditions.

What Is Actually at Stake

The practical consequence is not necessarily a loss. It is a delay in confidence. A distributor pricing at wholesale needs to know, before confirming a price, that the margin target is covered after all import costs are included. If that confirmation requires waiting for the freight bill, the broker invoice, and the duty statement to arrive and be reconciled, the pricing decision either waits or proceeds on an assumption.

When freight rates or exchange rates have moved materially since the last season, an assumption based on old costs could mean prices are set below the margin threshold. The distributor may not discover this until the period closes. That is a possible risk, not a guaranteed outcome, but it is the kind of risk that a better cost visibility process is designed to reduce.

There is also a management attention cost. When the reconciliation is manual and happens after the fact, someone on the finance or purchasing team is spending time each season reconstructing what the landed cost actually was, rather than confirming what it is expected to be.

What a Better Process Needs to Do

The buying question is not whether freight bills can be recorded, but whether the ERP can build an estimated landed cost at receiving, broken down by component, so that the pricing team has a working replacement cost view before the actual bills are fully reconciled.

A useful landed cost process needs to do three things. First, it needs to apply estimated duty and tariff rates at the point of receiving, so that inventory cost reflects more than just the supplier price from the moment goods are booked in. Second, it needs to allocate freight and broker bills to specific shipment receipts when those bills arrive, so that the cost of a particular shipment is complete and traceable. Third, it needs to report purchase cost, duty, tariff, and freight as separate components, so that when any one of them changes, the team can see the effect in isolation rather than hunting through a blended average.

The practical trade-off is discipline. An estimate-based approach is only as good as the rates being maintained. If duty rates, tariff classifications, or freight estimates are not reviewed when supplier origins or trade rules change, the estimates drift from reality. The approach does not eliminate the need to enter and reconcile actual bills. It moves useful visibility earlier in the process, not around the reconciliation step.

How Versa Supports This Workflow

Versa is configured to support landed cost recorded on each receipt and completed when the actual bills are allocated, addressing each of these requirements as part of its standard ERP workflow.

Duty and tariff rates can be stored against a product, optionally by supplier country of origin, so that when a purchase order receipt is posted, Versa uses the configured rate to calculate an estimated duty component and an estimated tariff component as part of the landed cost for that receipt. Each estimate posts to its own configured payable account, which means finance can see, at any point, which cost components are estimated and which have been settled by an actual bill. The two components are kept separate by design, because combining them into one rate removes the ability to reconcile them independently when the actual charges arrive.

When the freight carrier bill or broker invoice arrives, Versa supports allocating that bill to one or more specific shipment receipts. The allocation distributes the cost proportionally across the products on those receipts, and if some units have already been sold, the system directs the appropriate portion to cost of goods sold rather than inventory. This means the cost of a shipment can be completed even when billing arrives after some of the goods have moved.

When an actual duty or tariff bill is entered through the supported allocation path, Versa reverses the applicable estimate and records the actual amount, so the payable account reflects the real charge rather than the estimate. The cost analysis reporting separates purchase cost, duty, tariff, and other landed cost components, giving the pricing team a view of what each element contributes to the total cost of a product.

For purchases in a foreign currency, the exchange rate used on the transaction is carried with the receipt, so the currency applied to a purchase is part of the record rather than a separate estimate.

The boundaries are worth stating clearly. Estimates depend on rates that the team maintains. Versa does not determine customs classification, legal applicability, or the correct jurisdictional rate. Those decisions remain with the purchasing and compliance team. Actual bills must still be entered and reconciled. The approach provides earlier visibility, not a substitute for the reconciliation process.

What the Pricing Conversation Looks Like With This in Place

Return to the product manager reviewing prices before the season opens. With landed cost recorded on each receipt and completed when the actual bills are allocated, the inventory record for each product already reflects the estimated duty and tariff components from the most recent receipt, applied at the configured rate for that product’s origin. The freight bill from the last shipment has been posted and allocated to those receipts, so the freight component is included in the cost record as well.

When she pulls the cost analysis for the product, she can see the purchase price, the duty estimate, the tariff estimate, and the freight allocation as separate figures. If the freight rate has increased since last season, she can see that in the freight component without it being buried in a blended average. If the exchange rate has moved, the transaction record reflects the rate at the time of purchase. She is not waiting for a manual reconciliation to tell her what the product cost. She is working from a cost record that was built as the goods moved through the receiving process.

The pricing decision is still hers. Versa does not set prices or guarantee margins. But the information she needs to make that decision with confidence is available at the point when it is useful, not weeks after the season has opened.

See This Workflow in Versa

If landed cost visibility is a requirement in your ERP evaluation, the most useful next step is to see how Versa handles a representative import receipt: how duty and tariff estimates are applied at receiving, how a freight bill is allocated to that receipt, and how the cost components appear in reporting. That walkthrough does not require any preparation on your part.

Request a Versa demonstration focused on the landed cost workflow and we will walk through a representative imported product receipt, from purchase order to cost analysis, so you can evaluate whether the approach fits your pricing and margin confirmation process.

If you would prefer to explore the workflow before speaking with sales, the Versa AI Advisor can answer questions about this workflow and help you decide whether a conversation with the sales team makes sense for your situation.

Request a Versa demonstration focused on the landed cost workflow