anata

Inventory Operations

5 min read3 sources

How to Allocate Landed Cost Across SKUs: A Worked Example

By Anata Inc. ·

Landed-cost allocation guide: Give Each SKU Its Share.
Fulfillment operationsA visual hook for this fulfillment operations operator guide.

The short answer.

Allocate each inbound charge across the products it actually covers, using a documented basis such as weight, quantity, volume, or value. Add each product's allocated charges to its purchase cost, then divide by its units. Check that every split adds back to the original bill before using the result to compare reorders.

A shipment average can hide expensive products inside cheaper ones. The useful output is a cost you can explain for each SKU, with the invoice and calculation behind it. Our landed-cost definition covers the term; this guide works through the allocation.

Section 01

1. Set the boundary before calculating

Choose a shipment or receipt, a destination, a currency, and a version date. In this example, the boundary ends when inventory reaches the receiving location. It excludes customer delivery, selling fees, advertising, and later storage. Keep those costs in a separate selling-cost calculation so they are neither forgotten nor counted twice.

Build two small tables. The product table holds SKU, received units, supplier cost, and the quantities needed for your allocation method. The charge table holds invoice reference, amount, products covered, whether the amount is estimated or actual, and the chosen basis.

Check the supplier terms before adding a freight line: a cost already included in the goods invoice must not be added again. Have the finance owner confirm which charges belong in your inventory-cost policy. This is an operational allocation example, not a rule for tax treatment or ledger posting.

Section 02

2. Choose a basis for each charge

Oracle's landed-cost documentation distinguishes quantity, volume, weight, item value, and manual factors. These are available approaches, not a requirement to use one method for every bill. Oracle: Landed Cost Charge Lines

NetSuite's documentation gives weight-based freight and value-based insurance as examples when those measures explain the charge. Check the invoice rather than assuming those examples always apply. A carton, a pallet, and an individual unit are different quantities; normalize them before calculating a share. NetSuite: Entering Landed Cost

For each shared charge:

SKU share = charge amount × SKU basis quantity ÷ total eligible basis quantity

Use the eligible lines for that particular charge. If measurements are missing or the denominator is zero, resolve the evidence before allocating.

2. Choose a basis for each charge
BasisEvidence to collectQuestion to resolve
WeightComparable weights for every eligible product lineDoes this charge follow weight?
VolumeComparable space measurements for the eligible linesDoes space explain the charge?
QuantityUnits expressed on the same basisAre these units comparable for this bill?
ValueThe agreed value of each eligible lineDoes value drive this charge?
Direct assignmentAn invoice line naming the productCan the amount stay with that product?

Section 03

3. Work through a mixed shipment

The following numbers are invented for arithmetic only. They are not Anata rates, customer results, or recommended accounting entries. All ordered units were received and accepted; amounts are USD.

Assume the freight invoice is $1,000 and the approved method allocates it by the listed weight. A separate receiving bill charges $0.50 for each unit received, totaling $175. A $150 inspection invoice names SKU C only. These three charges are additional to the goods invoice.

Freight for A is $1,000 × 100 ÷ 500 = $200. B receives $300 and C receives $500. Receiving follows the bill's unit rate: $100, $50, and $25. The inspection charge stays entirely with C.

The total reconciles: $6,400 + $1,000 + $175 + $150 = $7,725. The SKU totals also equal $7,725.

Dividing the entire shipment cost by 350 would produce an average of about $22.07. That is a shipment summary, not a substitute for these three different SKU costs. For a supplier comparison, rebuild the same allocation using the new quantities and quotes.

Read the example down each SKU column as well as across each charge row. For A, the goods cost is 200 units multiplied by $12, or $2,400. Its freight share is one fifth of the $1,000 invoice because its 100 kg is one fifth of the eligible 500 kg shipment. Add $100 of receiving and no inspection cost to obtain $2,700. Dividing that amount by 200 received units gives $13.50 per unit.

For B, the 150 kg share allocates $300 of freight. Add the $2,000 goods cost and $50 receiving charge to get $2,350, then divide by 100 units for $23.50 each. For C, 250 kg allocates half the freight bill, or $500. Add $2,000 of goods, $25 receiving, and the directly assigned $150 inspection charge. The resulting $2,675 divided by 50 units is $53.50 each.

3. Work through a mixed shipment
InputSKU ASKU BSKU CTotal
Units20010050350
Supplier price per unit$12$20$40Not applicable
Goods cost$2,400$2,000$2,000$6,400
Shipment weight, kg100150250500
3. Work through a mixed shipment
AllocationSKU ASKU BSKU CTotal
Goods cost$2,400$2,000$2,000$6,400
Freight$200$300$500$1,000
Receiving$100$50$25$175
Inspection$0$0$150$150
Allocated total$2,700$2,350$2,675$7,725
Cost per received unit$13.50$23.50$53.50Not applicable

Section 04

4. Review the split before using it

Use a review row for each bill: source amount, allocated amount, difference, explanation, and owner. Keep full precision during calculation and document any final rounding adjustment. A total that reconciles is necessary, but it does not prove the chosen basis is appropriate.

Also check whether a charge is still available to allocate. Intuit's Enterprise Suite documentation explicitly tracks full and partial allocations and their remaining amounts. That is a useful control to require in your own review, whatever system holds the records. Intuit: Allocate landed costs

Keep a dated comparison between estimates and actual invoices. When a late bill arrives, show the changed input and resulting SKU costs; preserve the earlier version. If receiving quantities differ from the order, reconcile the quantities before reusing this example's divisor.

For Shopify workflows, our purchase-order and transfer reconciliation guide explains the related records. Our month-end inventory-value guide covers the subsequent reporting reconciliation. An allocation worksheet does not itself update either system.

Keep the bill-level review separate from the SKU-level review. Freight should reconcile to $1,000, receiving to $175, and inspection to $150. Then confirm that A, B, and C total $7,725 together. This catches a charge that was omitted, allocated twice, or assigned beyond its eligible products. It does not validate the invoice itself or decide whether the cost belongs in inventory.

When you reuse the worksheet, replace the example inputs before calculating a new total. Retain the charge reference, the products covered, and the source of each weight or quantity. If a later invoice changes a charge, record which version was used for the earlier decision and reconcile the change with the finance owner. Do not silently replace a historical cost with a new estimate.

Questions, answered.

Should I divide every shared cost equally by unit?
Only when that basis is appropriate for the charge. In the example, receiving is billed per unit, while freight follows weight and inspection belongs to one SKU. Document the reasoning for each split.
Is allocated landed cost the same as total cost per customer order?
No. This example ends at the receiving location. Add the relevant outbound fulfillment, delivery, selling, and other costs separately when evaluating an order. Use our fulfillment cost comparison guide for that different decision.
Can I use this table to calculate customs duties or taxes?
No. It distributes supplied charge amounts; it does not determine tariff classifications, duty rates, recoverable taxes, or accounting recognition. Obtain the actual applicable amounts and treatment from the responsible specialists before including them.
Does this describe a built-in Anata allocation feature?
No. It is a calculation and review workflow. It makes no claim about automatic landed-cost posting, integrations, or software functionality.