Most small businesses do not miss margin because the supplier price is invisible. They miss margin because the supplier price is not the full cost.
Freight arrives on a separate invoice. Delivery fees get recorded as shipping expense. Duties or handling fees show up later. The PO says an item cost $8.40, the business prices from $8.40, and the real cost of getting that item into sellable inventory was $9.15.
That gap is landed cost. It is the purchase price plus the extra costs required to get inventory into usable stock: freight, delivery, duties, insurance, handling, pallet fees, prep fees, and similar charges.
The problem is not that landed cost is conceptually hard. The problem is that most systems make the workflow too heavy for a small team.
Quick answer
The easiest way to handle landed costs is to keep them on the live purchase order.
Add shipping, freight, delivery, duty, or handling as an additional cost line. Choose how that cost should be allocated across the PO items. Then let the allocated amount flow into item-level cost, COGS, price trends, recipe or BOM costing, and reporting.
In LineNow, landed costs can be allocated four ways:
| Method | Best for |
|---|---|
| Value | Freight, duties, or insurance that should follow item value |
| Quantity | Delivery or handling costs where each unit carries a similar share |
| Equal | Simple order-level fees split across included items |
| Manual | Known exceptions where one item should carry a specific dollar amount or percentage |
This keeps the workflow close to where the operator already works: the PO.
Why landed costs usually disappear
The classic small-business workflow separates the pieces:
- The supplier invoice has the item prices.
- The carrier or supplier adds a shipping charge.
- A broker, delivery service, or warehouse adds another fee.
- Accounting records those extra costs somewhere else.
- Inventory, margins, and price history continue using the original item price.
The books may still balance, but item economics are wrong.
That matters for any business that buys physical goods:
- A restaurant's recipe cost is understated when ingredient delivery fees never reach the ingredient.
- A retailer's item margin is overstated when freight is treated as generic overhead.
- A supplement or CPG brand underprices bundles when freight, prep, labels, or handling sit outside SKU cost.
- A light manufacturer builds BOM cost from component prices that exclude inbound freight.
- A dropshipper sees fake margin if supplier shipping is not attached to the ordered product.
The business does not need a bigger spreadsheet. It needs the purchase record to carry the true cost.
The ERP way is often too much
Large ERPs can handle landed cost, but they usually turn it into a costing module project.
The team has to configure cost elements, cost buckets, receiving rules, invoice matching, accounting mappings, inventory valuation behavior, and sometimes separate estimated-vs-actual landed cost workflows. That can make sense for import-heavy businesses with finance staff.
For a small business, that is usually overkill.
The operator's actual question is simpler:
I paid $180 in delivery on this PO. Which items should carry that cost, and should my reports use the adjusted item cost?
That question belongs inside the PO screen, not in a month-end allocation workbook.
A simpler landed-cost workflow
A practical landed-cost workflow has four steps.
1. Add the cost where the PO already lives
The cost should be added as a shipping or additional-cost line on the purchase order.
Examples:
- Supplier delivery charge
- Carrier freight
- Import duty
- Tariff or customs charge
- Pallet fee
- Prep or label fee
- Warehouse-in handling
- Cold-chain delivery
- Supplier surcharge
- Supplier payment surcharge
Keeping the fee on the live PO matters because the PO already knows the supplier, items, quantities, received state, and accounting context.
Tariffs are a clean example
Tariffs show why landed cost matters even when the supplier is not charging more for the product.
Imagine the supplier still sells a component for $10.00. Then a tariff, duty, or customs charge adds $1.25 per unit to get that item into usable inventory. If the business only tracks supplier price, price trends say the item cost is flat. Margins look stable. Reorder math and recipe or BOM costs still use $10.00.
Operationally, nothing is flat. The item now costs $11.25 before it can be sold or consumed.
In a live PO workflow, the buyer can add the tariff as an additional cost line, allocate it to the affected item or items, and let item-level COGS move even though the supplier price did not change. That is the point: landed cost captures the real economic cost of the item, not just the supplier's unit price.
What about credit-card fees?
Credit-card fees are worth separating because the phrase can mean two different things.
If a supplier charges the buyer a card surcharge, processing fee, wire fee, or payment fee required to acquire the inventory, many businesses treat that like an acquisition-side fee for internal margin analysis. It may belong in the landed-cost conversation because it changes the true cost of buying that PO.
If the fee is the merchant processing fee on your customer sale, that is different. That fee is usually a selling or payment-processing expense, not a landed cost of getting inventory into stock.
The practical rule is: if the fee is required to acquire the inventory from the supplier and make it available for sale or production, it can be evaluated as part of landed cost. If the fee happens when your customer pays you, keep it out of landed cost and analyze it separately in margin reporting.
2. Choose the allocation rule
The allocation method should be explicit. Otherwise nobody knows why one SKU absorbed more cost than another.
Value allocation works when the cost is tied to item value. Duties, insurance, and many freight estimates often fit here because high-value items reasonably carry more of the cost.
Quantity allocation works when each unit consumes roughly the same share of the fee. If a delivery charge is really about units handled, quantity is easier to explain.
Equal allocation works when the cost is a simple order-level fee and there is no better driver. It is less precise, but sometimes the cost is too small to justify analysis.
Manual allocation works when the operator knows the answer. Maybe one heavy item caused the whole pallet fee. Maybe one SKU has a supplier prep charge. Manual allocation should allow dollars or percentages, but the total still has to reconcile to the fee amount.
3. Show the true item cost
After allocation, the operator should see the extra cost under the item price.
For example:
| PO item | Supplier price | Allocated cost | True item cost |
|---|---|---|---|
| Matcha powder | $18.00 | $1.20 | $19.20 |
| Syrup bottle | $9.50 | $0.55 | $10.05 |
| Cups | $42.00 | $2.10 | $44.10 |
The important detail is visibility. The buyer should not have to trust that a hidden report changed somewhere. The PO should show the allocated additional cost directly under the item price.
4. Decide what to do if items were already received
Cost changes are easy before receipt. They are more sensitive after receipt because lots, inventory layers, recipe-sale snapshots, and COGS reports may already exist.
The clean small-business workflow is not to lock everything forever. It is to make the choice explicit.
When changing a price or landed-cost allocation for an item that has already been received, LineNow can ask whether to update past sales that used that PO item. That keeps the operator in control:
- Leave past sales alone if the change is only for forward-looking reporting.
- Update past sales if the correction should restate historical COGS for that received item.
The checkbox should be specific because "historical restatement" sounds like accounting jargon. The small-business version is:
Update past sales that used this PO item.
That is the actual decision.
What downstream reports should use
Landed cost becomes valuable only when downstream workflows use it.
Once allocated to PO items, the adjusted item cost should inform:
- Item price trends, so price history reflects true inbound cost, not just supplier invoice price.
- Inventory valuation and COGS reporting, so margin is not inflated by freight left outside the item.
- Recipe and BOM costs, so menu items, bundles, assemblies, and manufactured goods use realistic input cost.
- Supplier and item reports, so buyers can see whether a "cheaper" supplier is still cheaper after shipping.
- GMROI, ABC analysis, and replenishment math, because the cost basis affects inventory value and return.
- Accounting handoff context, so bills can preserve the real supplier-confirmed order state.
This is why the feature belongs in a closed-loop procurement workflow. Landed cost is not just a number. It is a cost correction that should travel from PO to receiving to inventory to reporting.
Accounting: separate line or item cost?
There are two different jobs here:
- Make accounting match the supplier or carrier bill.
- Make item-level operations reflect true cost.
Sometimes the accounting bill should keep shipping as a separate line. That is cleaner when the vendor invoice shows shipping separately and the bookkeeper wants the bill to match the document.
Sometimes the business wants allocated landed cost pushed into item cost for inventory accounting. That can be right when inbound freight or duties are material and the accounting policy capitalizes them into inventory.
The key is not to double count. If shipping is included in item cost for accounting, it should not also post again as a separate expense line for the same allocated amount. If shipping remains separate in accounting, internal operational reports can still use allocated landed cost to show truer item economics.
For many small businesses, the right first step is simple: keep the bill easy to match, and use allocated landed cost inside purchasing, price trends, COGS analysis, and margin reports.
The LineNow approach
LineNow keeps landed costs on the live PO instead of forcing the team into an ERP costing module.
The workflow is intentionally direct:
- Add shipping or another additional cost to the PO.
- Choose value, quantity, equal, or manual allocation.
- Review the allocated cost under each item price.
- Save the allocation.
- If received items are affected, choose whether to update past sales that used those PO items.
That gives the business landed-cost discipline without turning weekly purchasing into a finance project.
Read the landed cost glossary for the formula and replenishment math, then compare it with purchase order accounting integration if you need to decide whether shipping should post as a separate bill line or as allocated item cost.
The practical rule
If freight, delivery, duties, or handling change margin decisions, they should not live only as generic shipping expense.
They should be visible on the PO, allocated with a rule the team understands, and used anywhere item cost matters.
That is the real landed-cost unlock for small businesses: not a complicated module, just true item cost where buying already happens.